ITIL

The IT Infrastructure Library

New LinkedIn group for Owning ITIL

Submitted by skeptic on Wed, 2009-09-30 21:54

I've launched a new group on LinkedIn. This group is for all decision makers (IT-literate or not) who are presented with an ITIL® proposal or asked to oversee an ITIL project, or who find something called “ITIL” or “Service Management” in their budget. It tells you what the ITIL industry won’t.

For everyone else involved in ITIL projects, join in to help you stay grounded and safe.

The OGC ITIL V3 Change Log's greatest hits

Submitted by skeptic on Fri, 2009-09-25 01:50

If you are thinking the ITIL V3 2nd Edition or Refreshrefresh - or whatever it is called - is just about adding a few missing semicolons and spelling Ivor Macfarlane's name right, think again. Even if they get talked out of this plan to rewrite (read: dumb down) the whole of Service Strategy ("oooh ITIL is HARD - why can't it be easy like TV?"), take a look at some of the errors to be fixed in the books. Remember, paid authors for each book from major corporations, hundreds of reviewers, professional commercial publisher with professional editors... and we get:

Hornbill ITIL State of the Nation survey: Viewer discretion advised

Submitted by skeptic on Thu, 2009-09-24 09:21

Hornbill has released an ITIL State of the Nation survey [registration required]. I think it is a good report, relative to the usual Crap Factoids we see. It doesn't try to get all worked up about any one number. Sadly I think it still suffers from all the flaws we see in these industry "research" reports. It does however point to one interesting result: ITIL V3 doesn't seem to be taking the world by storm.

No new concepts in the ITIL V3 2nd Edition - the ITIL RefreshRefresh?

Submitted by skeptic on Wed, 2009-09-23 06:35

"New concepts are not to be added" says OGC's "Mandate for Change", the Project Requirements for the ITIL V3 Refresh refresh

why on earth did ITIL V3 rename Forward Schedule of Change to Change Schedule?

Submitted by skeptic on Mon, 2009-09-21 06:20

This has been bugging me for a long time: why on earth did ITIL V3 rename Forward Schedule of Change to Change Schedule? Beats me, and it is counter-productive.

Egg on face from the ITIL Refresh Refresh: we can do better at reviewing bodies of work

Submitted by skeptic on Sun, 2009-09-20 21:34

The whole of New Zealand was out by 190 metres - we're in the middle of fixing it. No big deal: redraw, rebrand, reprint, redistribute every single topographical map of the country; recalibrate/reprogram some of the GPS devices; run batch programs to change the coordinate position of everything in every database in the country; work really hard to make sure all the emergency services stay on the same page ...er... map. Simple really. Harder is telling people it is happening: nobody I speak to even knows. It would have been a little simpler if they had got it right the first time, but that is unfair criticism since technology has moved on over the however-many decades or centuries since they surveyed it for the last set of maps. The errors took a long time to show up (when GPS became widely used).

Imagine the reaction if it were to come out in a year or so that the latest set of maps is still wrong.

Recommended links

Submitted by skeptic on Sat, 2009-09-19 22:22

Here are some links that may be of use or interest to readers. [Updated 24/5/2010]

Is ITIL there to describe what the experts know? Or is it there to guide those setting out on the ITSM journey?

Submitted by skeptic on Thu, 2009-09-17 21:43

Once again the comment discussion on this blog has dug down to a very fundamental question: Is ITIL there to describe what the experts know? Or is it there to guide those setting out on the ITSM journey?

Two ITIL-derived rules of thumb for organising the IT department

Submitted by skeptic on Thu, 2009-09-17 03:22

Someone asked on LinkedIn about what guidance ITIL gives us for restructuring an IT department. I came up with two rules of thumb:

ITIL Alligators

Submitted by skeptic on Tue, 2009-09-15 20:16

CanStockPhoto kovalvsHere's a simple analogy for incident, problem and change that I use quite a bit.

Syndicate content