In our last episode of Real World
ITIL, we were pleased to note that eWeek magazine covered Evergreen’s
recent survey on ITIL adoption. This week, we’re equally pleased to
note that CIO Insight magazine has
also covered the survey’s interesting findings. We’re appreciative of
this coverage and hope you’ll check out the articles. If you do, we’d
love to hear your thoughts on them! Just click on the Comment link
below to respond.
This week, as promised, we’ll feature another bunch of questions
that we’ve recently heard about ITIL. I’ll offer a few brief thoughts
in reply to each of these questions, but I invite any reader out there
to add additional insight or perspective by clicking on the Comment
link, below.
So let’s make sure our seat backs are straight up, tray tables are
stowed and our seat belts are fastened (and turn off that Blackberry!).
Here we go:
Question: How can you develop and advertise a Service Catalog if you can’t guarantee delivery or cost?
This question came from a shop in Tennessee which is thinking about
implementing ITIL but hasn’t yet formally decided to make the leap.
Insightful questions like this one are indicators that ‘ITIL
consciousness’ is beginning to register in the minds of some
traditional IT veterans. Clearly, the guy who asked it understands how
actions in one process box of the framework can influence activities in
other areas of the framework.
We believe that developing a catalog of standard services is a great
way to start introducing ITIL into your shop. Like a CMDB, a
well-constructed Service Catalog is a foundational element for many
other aspects of ITIL - especially in the areas of Service Level
Management, Financial Management, Capacity Management and Availability
Management. You can read the ITIL documentation to understand why, so I
won’t repeat that info here.
However, a Catalog is a handy thing to have even if you’re not doing
ITIL at all. A key consideration in controlling IT cost is to ensure
that you are neither overprovisioning nor underprovisioning services
compared to the actual IS needs of the business. It should be obvious
that to make this determination IT executives first need to know with
some precision what products their division is actually offering to the
business and then make value judgments accordingly.
So, a catalog is well worth creating even if it’s got some gaps in
the logic. You can always evolve it iteratively into a more
comprehensive tool later (for chargeback and availability negotiations,
foe example). If you can link the catalog that you develop to other
Service Delivery processes, then that’s well and good too.
Nevertheless, we recommend that your team invest the effort in
creating a service catalog if you don’t have one, because even the
effort itself will teach you something you didn’t know about your own
IT department. Just remember to consider IT from a holistic SERVICE or
PRODUCT point-of-view - as opposed to a functional or component view.
If the distinction between these perspectives isn’t clear, pop us a
Comment and we’ll clarify.
Question: Most IT shops seem to start ITIL implementations
with some form of Configuration Management or CMDB effort. Why not
start with Service Level Management instead?
All too often, those of us who work in infrastructure areas take an
insular point-of-view - one that forgets who IT really serves, how IT
gets paid-for, and what factors can lead to IT functions getting
outsourced. This question, from an IT veteran at a shop in Kentucky,
belies his understanding about who butters his daily bread.
Configuration Management is attractive because it’s not hard for any
IT manager to understand why having a concise, accurate list of IT
assets is a great thing to have. Considering the financial implications
alone of minimizing service fees, maintenance fees, property tax,
warranty expirations, and license fees, etc., the logic of tracking
Configuration Items is self-evident.
Also, it usually isn’t difficult for IT managers to understand the
value of linking Change, Release, Incident and Known Error records to
CIs. (I would be willing, though, to bet that few IT managers have
really witnessed the true power of this concept, yet!) So, if your
department has limited time and staff (and especially if your
organizational culture tends to oppose change), Configuration
Management can seem like low-risk, low-hanging fruit that’s not going
to get any manager fired for trying to do it.
But this reasoning doesn’t automatically imply that CM is either the
best or the only place to start with ITIL. Service Level Management and
Financial Management both make excellent starting points as well,
particularly from the perspective of the CIO’s office.
After all, there’s a lot more to IT than just Configuration Items.
If you’re an IT executive and you’ve got continual budget pressure or
you’re attempting to fix damaged relationships with your customer
community, or you’re trying to figure out whether your IT is offering
the right mix of services, you should seriously consider implementing
Service Level Management and Financial Management early on in your ITIL
adoption. The concepts in these processes can help tremendously with
all of these issues. Call us if you’d like to learn more.
Question: Does a credible industry best-practice exist on
what percentage of our infrastructure staff should be allocated to each
ITIL process?
Wouldn’t you love to have the answer to this one? So would we, truth
be told. Since time has run out for this week, we’ll take a bold swing
at this question in our next installment of Real World ITIL.
Aren’t these fantastic questions, though? They came from smart
folks, who are dedicated to improving their company’s IT somehow, and
suspect that ITIL could point the way if only they could understand it
a bit better. If we assume that the best learning experiences begin by
asking great questions, it’s apparent from these that some IT folks out
there are going to get a lot of benefit from their enquiries.
For my own part, the more I learn about ITIL, the more I realize
just how powerful and useful a model it really is. As a result of my
recent experiences, it’s very clear to me that it’s well worth using
ITIL language to talk about your company’s IT even if you’re not
actually implementing the framework for production purposes. The
process alone of working to understand ITIL can teach you important
things about your IT even if you don’t want to put the effort into
transforming your processes just now.
So keep up the great thinking, everyone, and please take time to
share some of it with your fellow readers here on Real World ITIL.
We’ll have a few more questions next episode.
Thanks for reading and see you next time!
Regards,
Scott (your moderator)
Technorati Tags: itil it infrastructure library information technology infrastructure library itsmf cmdb itsm consultingprince2 itsm helpdesk software
—–