The scale of ITIL V3

in
This page is part of a set of pages: "About"
Turn the page:

[last updated 11th September 2008]

People are starting to realise how different ITIL v3 ("The Refresh") is from ITIL v2, and how much more extensive the scope and ideas are. There is no doubt that the re-engineering has been extensive. The following diagram makes that clear. A bit like a DOS-based command-line-driven utility being rewritten as a Windows GUI with workflow. The original routines are still in there somewhere but the manuals sure look different! Saying it is an add-on is like saying a Chev Corvette is an add-on to an LS1 V8 motor, or Windows is an add-on to MS-DOS. Sure ITIL2 is still in there somewhere but not so as you'd notice.

Even though OGC are trying to make ITIL3 more integrated than ITIL2, it is a good bet that users will concentrate on the Service Transition and Service Operation books (at least initially), in the same way as we focus on the red and blue books in ITIL2, so that ITIL3 will have its own "lost processes", as I call them. If true, this will serve to mitigate the increase in scale considerably.

Please forgive the fact that in any flat diagram there will be some over-simplifications or even distortions, but the key ideas this diagram tries to impart are:

  • ITIL2 is still there in ITIL3
  • Not only has ITIL3 expanded ITIL2 along the same dimensions that V2 considered (made it "longer" by over a dozen more processes) it has also expanded it in a whole new dimension (made it "wider", changed it from a line to a plane).
  • There was actually much more to ITIL2 than the ten processes in the red and blue books, but often you wouldn't know it to hear folk talk. Some of the processes making ITIL3 "longer" are these "lost processes" being brought back into the core. Others aren't - they are specific to running a lifecycle.

Note: IE7 seems to sit around for a while then finally format the page so you can see all of this...

[Updated: and now with all of the process-like "elements" listed in the ITIL V3 Qualifications Scheme. See also ITIL V3 Processes and especially The IT Skeptic's Unofficial List of ITIL Version 3 Processes]

diagram of the difference between ITIL V2 and ITIL V3

This diagram is not copyright - it is placed in the public domain. It would be appreciated if you would retain the attribution to the IT Skeptic and place a link to www.itskeptic.org if you use it.

Sooner or later it is going to dawn on people that they do need to retrain (upgrade), they do possibly need to change the way they do things (service lifecycle), and there are more than twice as many processes to learn and implement.

Personally I think it is a good move - there had to be a quantum step and one assumes it is aligned with the majority of the feedback. People hate change so there will be much howling and gnashing of teeth, but in a few years I think we will view V2 as quaint. It might be quite a few years though, and in the interim I believe we will see two streams of ITIL: the big boys and the top guns doing ITIL version 3, and the lesser mortals and beginners doing ITIL version 2.

OGC and TSO think they are going to sunset ITIL2 round about end of 2008. I think they don't have a snowflake's chance. Pink Elephant say the ITIL2 Practitioner certifications will survive at least "until late 2008".

This page is part of a set of pages: "About"
Turn the page:

Comments

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

STILL no mention of project management

I am relieved to see that I hadn't missed something in my fruitless search of the manuals, as this mapping still reinforces that ITIL has deemed the project management process as obsolete and no longer a necessary part of managing change in IT. Thank Goodness; projects (and project managers) are such an annoying pain in the butt anyway, so I say good riddance. As long as we have a RFC and a release plan, what happens in between the two is of no particular concern.

T

Other OGC guidance

ITIL's publisher, the Office of Government Commerce, also publishes PRINCE2 project management guidance which I believe is referenced in both ITIL v2 and v3.

In the area of software engineering, they publish (or did publish) SSADM, which may be moribund - anyone know?

Charles T. Betz
http://www.erp4it.com

Mentions of PMBOK and Prince2 in ITIL V3

I wouldn't rate a namedrop as a reference.

OGC

OGC also have MSP, which is about program (programme) management and M_o_R, which is Risk Management.

we have Release Managers for that

Not just "between". Nor should a major Release Plan be executed with project management - we have Release Managers for that

Note: I have updated my post about the mysterious absense of PM in ITIL V3

ITIL & Prince don't meet

In my view this has always been ITIL's big weakness - it doesn't adequately deal with the interface between project management and service management .. having said this I haven't spent a lot of time on v3 yet, so hopefully this has been improved (how can it not be improved if they are looking more at SM lifecycle?)

better in V3

It is better in V3 but not much

The problem is not the structure but the content

Dear Skeptic
I do agree that V2 is getting old and quaint but I doubt that anybody will be doing V3 for a long time. The reason for my skeptism is that V3 is so badly written. The books are uncoordinated and conflicting.

One customer told me that there is already a clash of ITIL schools at his company. V2 and V3 trained people have different opinions on almost every operational process. For most IT Service managers the key issue is to improve the stability and quality of their services. The war of versions is not going to help.

organisations starting out on ITIL

I am recommending to organisations starting out on ITIL that they focus on the red and blue books of V2, and mix and match some good bits from V3 if they are up to it.

On the other hand, I don't think the V3 books are bad. i think they are quite good, some very good. Sure I'm critical of a number of aspects, but nothing is perfect. As user organisations mature in coming years they will get into V3 and find it useful, especially if forewarned about a few things :-D

I don't warn people off V3 because I think it is defective. I warn them off because it is too ambitious, too advanced. When you've been immersed in ITIL for years or decades, it is very hard to step back and see it as someone sees it who has only just now looked at it for the first time.

The really big bit missing is the meta-lifecycle - the lifecycle of implementing the service lifecycle. until some complementary book provides a path - a phased approach - to getting to V3, then V2 will remain a sensible first step.

useful bits

I admit there are useful parts in V3 and I'm pretty sure there are ideas that I have not yet understood. I have also noticed that subsequent materials have fixed some of the most glaring errrors in the original books.

In my environment ITIL is pretty new, most companies have been using it only a couple of years. I think the danger lies in hopping from V2 to V3 in the middle of V2 implementation. It takes time for people to really understand the concepts of itil and it does not help at all that suddenly there are 25 new processes and the barely familiar processes have changed.

My advise to my customers is: do ITIL V2, get ISO 20000 certified or use the standard as a maturity level goal, look at CobIT if you need more guidance. After you've done that, there will be a ITIL V4 or V3.1.

Can you give some examples of good bits

Dear Skeptic

Can you give some examples of "very good" parts in V3.

Br Aale

a very good body of knowledge

Lots of it! It is a very good body of knowledge. Sure it has its deficiencies, which we have discussed on this blog (somebody has to do it) but in general it is good stuff. in fact, it is easier to list the bits that are not good.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.