Remarkably frank, but what are the benefits of the ITIL V3 Update?

itSMF International have released a remarkably frank document describing the ITIL V3 Update. It's also a bit odd: it carries the banner of itSMFI but it is unsigned and undated. And it doesn't answer the question it poses: "ITIL® V3 Update, what are the benefits?"

The document is mostly an ordinary description of the ITIL V3 Update, except for its mysterious source, its inability to answer the question it set out to, and a number of blunt statements that won't go down well in some other organisations. Try a few of these:

There is no doubt that there are a number of inaccuracies, inconsistencies and errors in the ITIL® V3 core books. Examples of this are many such as circular references, lack of roles and inconsistent process descriptions with varying degree of detail. One example is proactive problem management, which in the Service Operation book has a reference to the CSI book. In the CSI book, the reference is in the opposite direction...

there is no doubt that the quality of the end product would have benefited from additional time. This didn’t happen because of the desire to release the books on the pre announced date... The usual compromise between time, quality and cost...

Will these changes affect the ITIL® V3 qualifications? It might to a minor degree for some areas... A new version of the ITIL® V3 glossary is expected and ...this new glossary could have an impact on training material, exams etc.

Incidentally it says "ITIL® is the de facto framework most organisations are using." No it isn't. Even tub-thumpers like Gartner say that even amongst the sort of swallow-anything faddists with too much cash who go to Gartner conferences, less than half of them are using ITIL.

I'm really not clear what this document sets out to do, or why, or from whom.

Comments

The link is broken!

The link is broken!

the article has been pulled

No I think you'll find the article has been pulled, in true open democratic itSMF fashion. Let's not discuss the content and explain why it is mistaken or inappropriate, let's just erase it.

One day itSMF will emerge blinking into the 21st century and learn that once it is out there it is out there. For those who would like the full text of the start of the original post, here it is, fresh from the Google cache:

When talking about service management we can't ignore ITIL®. Despite its deficiencies, there is no doubt that ITIL® is the de facto framework most organisations are using. During its 20 year existence, ITIL® has proven its value to many organisations.
In 2007 we got what was originally called the ITIL® refresh and eventually became ITIL® V3. To many it seemed like a huge
"refresh", but strictly speaking there was not so much that was new. Especially if you look at the processes, most of them can be found in the 10 books in the ITIL® V2 library. Gradually, the idea of a service lifecycle and the use of the service portfolio as the central controlling element gained acceptance.
So what is the ITIL® V3 Update? Is ITIL® V4 already under way at a time when we hardly are mastering V3? It isn't, but what is it then?
Was ITIL® V3 born prematurely?
There is no doubt that there are a number of inaccuracies, inconsistencies and errors in the ITIL® V3 core books. Examples of this are many such as circular references, lack of roles and inconsistent process descriptions with varying degree of detail. One example is proactive problem management, which in the Service Operation book has a reference to the CSI book. In the CSI book, the reference is in the opposite direction.
Despite an extensive review in connection with the release of ITIL® V3, there is no doubt that the quality of the end product would have benefited from additional time. This didn't happen because of the desire to release the books on the pre announced date. This has been seen before in other contexts. We have all made compromises in IT projects and made a solution live before it was quite ready. The usual compromise between time, quality and cost.

This attempt to erase history is futile:

  1. You can of course find it on other caching websites as well.
  2. I and many others have downloaded the pdf of the article
  3. As mentioned in the comment above, you can find the original article here: http://www.it-dialog.dk/index.php/smblog/

Silly really.

Where does this article come from? Denmark

Just a little research learned the following:

The article is Danish, probably written by Michael Imhoff Nielsen . You can find the original article here: http://www.it-dialog.dk/index.php/smblog/

Bizzare stuff

If this really is itSMFI's view then its probably out of syncronisation with the rest of the movement. Bizzare!

Syndicate content