ITIL

Some time ago I did some research for APMG on the state of ITIL. Now the resulting white paper has been published.

The IT Skeptic hears on the grapevine that the ITIL training industry may be having a few meetings of its own at the itSMF UK conference next week. And the topics of conversation may bear on the continued competition between Examination Institutes (EIs).

One sees a few remarks in the webisphere that suggest folk don't get the relationship between Lean IT and ITIL (thanks to my friend Bob Grinsell, RIPOFF #1, for reminding me of this issue by his comment on the itSMF USA forum). Lean is a method. ITIL is a framework. These are different things for different purposes.

Calling all you ITIL theorists, philosophers, pontificators and pundits. Marty is back: our follower from the real world, trying to make sense of ITIL on its home grounds, the operations of big iron batch computing. Marty asks what happens after a service is restored? What does ITIL call the function of undoing the damage done while a service was unavailable? I have a view - of course - but I'm going to stay quiet - for a while- and hear what everyone else thinks. So have at it.

Help me please. I'm thrashing around in the morass of Service Operation, trying to get crystal clear on the difference/relationship between an Alert and an Event. Anyone?

P.S. we did skirt around this discussion before

Not only has ITIL V3.1 2011 not fixed the problems with business-vs-technical services, they have gone the wrong way and reinforced the problem. I will fight to the death to say there is no such thing as internal supporting "services", because I care about ITSM.

Recently I had a few things to say about DevOps. In a nutshell, DevOps is a niche approach to service design and delivery, which won't have much impact in the near future on traditional Operations of core systems. The concept of better integration between Dev and Ops is good, but the cultural issues and most of all the risks speak against it. And the way some people interpret it is downright dangerous. Now I want to zoom in to look at the relationship between DevOps and ITIL.

We have more news on ITIL V3.1 V3 "2011 Edition", from itSMF International. Of most note is the extraordinary increase in the size of ITIL.

Let's discuss the only information we have about the upcoming ITIL V3 2011: this FAQ.

© canstockphoto.com

On July 29 2011 we will get the update to ITIL V3. There are calls for us to just relax and stop worrying about ITIL V3 2011. Those unconcerned by changes to ITIL are those immersed in it: the experts, the consultants, the trainers. The other million users of ITIL can't keep track of all the differences between V2, V3, and V3 2011. They don't have the time or the interest (or the means). Right now they are confused and uncertain. And Castle ITIL aren't helping.