A visualisation of how ITIL Version 3 transforms ITIL version 2

If you are a visual person like me you may find this diagram helpful in understanding just what ITIL Version 3 means, what has changed.

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:

  • ITIL Version 2 is still there in Version 3
  • Not only has ITIL Version 3 expanded V2 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 V2 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 V3 "longer" are these "lost processes" being brought back into the core. Others aren't - they are specific to running a lifecycle.

Comments?
[Updated: and now with all of the process-like "elements" listed in the ITIL V3 Qualifications Scheme]

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.

Comment viewing options

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

I have updated the diagram

I have updated the diagram. It showed bits of each process spread over multiple books. I'm assured each process is documented in one book.

The Differences Are Huge

Some people are in for a bit of a shock come May 30th. The differences between v2 and v3 are not superficial, they are huge.

The line spun at the start by the OGC, "If it ain't broke don't fix it", becomes stranger each time I think about it.

V2 V3 Differences are immense

I agree and we have been saying this for over a year since the scoping document was published - moving from a silo-based, process improvement strategy to service lifecycle is a dramatic shift in every way, implementation strategy, tools, training, organizational culture....

Having browsed through the draft CDs this weekend (as an ATO) I now know how big a difference this will mean to many. The only saving grace is that the four companion books to the strategy book don't really do a good job of re-aligning the practices with any detailed lifecycle. If you are expecting an application or software development lifecycle.... its not there...

soft-peddle approach to revealing all this

See my new post for more on this

Where has that lovely diagram gone?

The picture spoke a thousand words. Where has it gone?
Deaf-Llama

darn it! fixed now

darn it! fixed now

Comment viewing options

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