I need to say something. I need to say something about ITIL in light of all the “poking” I have done via various mediums (such as the What Next For ITIL? and Giving Back To The IT Service Management Community blogs). The fact that ITIL is an easy target; and that breaking something is far, far easier than creating something. Hopefully, we all appreciate that it isn’t really that difficult to pick fault with just about anything, even if it is nigh on perfect (oh, and that is not intended to be read as “ITIL is perfect”). But as the oft-quoted senior manager quote says: “Don’t bring me problems, bring me solutions.”
I have great admiration for the creators of ITIL (or the IT Infrastructure Library as was) even though I do think that ITIL v3 became bloated, and potentially confusing, misdirecting, and demotivating. And, having only dipped in to my digital copy of ITIL 2011 I can’t yet comment on the latest incarnation of the IT service management (ITSM) best practice framework.
So what do I really want to say? Or “for heaven’s sake man, please cut to the chase.”
ITIL-bashing doesn’t work but we continue to do it
This might be an overly-dramatic statement but a lot of us do it.
I’d like to think that most, if not all, of us do it for the right reasons: we want I&O organizations to be better at managing IT service delivery and at enabling their parent businesses via technology. However, I can’t help think that WE need to change as much as ITIL needs to change.
Let’s look at some “facts” (OK, “facts” might not be the right word):
Read more