John Willis has an interesting blog post in which he ask, Does ITIL Really Matter? I think this is a good discussion to have. Personally I see ITIL at work in customer sites daily. However, I think there is room for improvement in the process, and I know that many close friends (including Luke Kanies from Puppet) have different opinons all together. So I'll ask this question to the wider audience:
Does ITIL Really Matter?
I've posted my two cents as a blog post: ITIL and ITSM still matter in a world with external providers
I think this OMG site has the potential to become the hub for all management discussions, great work!
A question about the mechanics of the discussions. Where do we discuss a topic? John's post is a good example. The available options are:
add a comment to John's post (as Ben did)
post a reply in the forums (like this one)
write a blog post of your own
There can be a good reason to use any one of these options, the trick is how to keep the discussion in tact? Is there a way/best practice, using tags, etc. ?
Hi mberkay,
Excellent question. For now I've taken things that looked interesting and started a discussion about them. I think the simplest thing to do (until we get the system tweaked up) would be this:
blogs - use these to share your opinions and read others
discussions - use these when you want the community to participate in a discussion in one place.
I personally like the way you handled this situation by creating a blog post with your opinion and then linking to it from the discussion thread. I know it's not perfect, but I think that it will be a somewhat simple solution will we can figure out something better. As far as the tags go, using the tags from the original post (and please follow the format of the other tags) will help people find related materials, but won't necessarily help people in deciding where to talk about what. Thats why I think keeping "discussions" in discussions will be the best solution for the time being.
Ok, reading that back I hope it's not too confusing ![]()
One final thought. If you're writing a blog post and you want to open a discussion around it, why not create the discussion and link to it from your post.
Thanks again for pointing this out,
whurley
"One final thought. If you're writing a blog post and you want to open a
discussion around it, why not create the discussion and link to it from
your post."
This makes sense to me, may be a variation may be to post to forums if there is a comment.
May be the Jive folks have some suggestions ...
So far my impression of ITIL adoption in the operations world is that it has begun to enter the consciousness of some of the senior engineering and management technology ranks. That is, they have heard of ITIL but are rarely familiar with it (though they may have purchased optical disks and books on the subject). The concept of having/needing a CMDB is definitely on the rise though.
When I work with typical release managers and system admins, there is a big drop off of awareness and/or interest in ITIL. ITIL/ITSM definitely is more interesting to enterprise architects who are accustomed to thinking about the business service at a high level.
If there is one area where ITIL can be of help to tool builders, is an established conceptual model from which tool builders can increase inter-operability.
ITIL awareness is increasing, as more large enterprises take the plunge to require Foundation level training. Usually, ITIL is focused on the Support team with it seeping out to Ops, Release and CAB. Vendors have been incorporating ITIL into their pitches, which has added to the awareness. All of this is goodness, if IT organizations can glean some repeatable processes to improve quality and consistency in services. While I find the ITIL books to be over-priced, which usually puts them out of reach of the rank-and-file that need them, and lacking in the details of the process models and devoid of any prescriptive processes, they are nonetheless better than nothing.
I found a lot of interest over the last couple years in the CMDB and Application Mapping. It seems, to me, very fundamental that you should have a central repository that provides consistent and up to date information on assets and their state(s). This is analogous to the data warehouse in a Business Intelligence architecture. After the Service Desk, the CMDB seems like the next essential system/application. We used CMDB to support initiatives in consolidation, virtualization, compliance and disaster recovery as all require an accurate record of current state.
One of the most useful models in IT is that any change should be implemented via People Process and Technology, in that order. ITIL is not about technology per se. Service Desk and CMDB as tools are pretty much incidental to ITIL. You can do ITIL with Post-It Notes. ITIL is about human behaviour.
ITIL tries to argue that CMDB is an essential piece of technology to underpin the cultural change and process maturity that ITIL is really about. I have argued elsewhere that CMDB is not only a waste of resource but infeasible. Please don't approach ITIL from a technical perspective nor try to "do" ITIL with tools. It won't work.
John Willis writes "This kind of future could normalize IT to the status of electricity that is a true commodity" as an ill-concealed reference to Nicholas Carr and Does IT Matter.
The road to making IT a commodity is paved with best-practices such as ITIL. ITIL prevents IT departments from spending vast resources inventing their own practices and processes. It makes job descriptions and recruiting easier, makes it easier to enter into customer service agreements, makes it easier to outsource, and insource, and makes it easier to understand how resources are spent in IT. ITIL is a common language for IT. One day IT will be commoditized and the basic ITIL practices will be assimilated and then fade into oblivion. Hopefully together with most self-appointed ITIL specialists out there.
Actually the electricity metaphor has been around a lot longer than Nick Carr. Around 1998 there was a mini explosion of ASP and MSP's and I created a failed MSP called MyESM for a company called IRC. Prior to that I worked with a few startups in Austin that were providing Tivoli as an MSP. We used that metaphor quite often and in fact in 2000 I gave a presentation at share.org and the electricity company analogy was my first slide. I have been in IT for over 30 years and as brilliant as Nick Carr is, trust me he didn't invent your reference to my ill-concealed electricity metaphor.