The Cabinet Office recently entered into a joint venture (JV) with Capita to manage and develop the U.K. government’s frameworks including ITIL® and Prince2®. More details on the frameworks are available on the Best Practice Management website.
After a week of lobbing emails and phone calls around the industry, I have yet to find any groundswell of support for the move. In fact, most practitioners I spoke to hoped that ITIL will finally be updated on a timelier and consistent basis so that it is more relevant to changes in technology and organizational culture. They also want the guidance to become more practical and support emerging methodologies such as DevOps.
That said, a major objective of the JV is to make money and there will undoubtedly be a widespread hit in the pocket. This Information Age article gives a good perspective on just how much.
So let’s look at some of the challenges for the JV in particular and ITIL as a whole:
- Arrest the decline in ITIL: There is no doubt that most organizations “do” ITIL to some extent, but my recent conversations identify ITIL as heavy, too process-oriented and not aligned to agile process (hence the emergence of DevOps). Many ITIL implementations do not deliver the benefits or value that are assumed as part of the business case.
- ITIL has not kept pace with the changing nature of IT-enabled business: There has been a rapid transition in the market from the CIO just “keeping the lights on” to being a key source for innovation. Business is demanding agility and rapid time-to-market which doesn’t fit well with the traditional ITIL consulting practice. ITIL needs to updated – urgently, in my opinion (for comparison, look at what’s happening with DevOps, which can make companies far more agile and effective.)
- Moving the population beyond Service Operations and Service Transition: Most implementations start with a Service Deck, and then implement Incident, change and problem management, followed by a CMDB. This is all bottoms- up. Organizations need to focus on strategic intent and its impact on the delivery and operations.
- Service Strategy book – fix it or toss it away: ITIL 2011 rewrote Service Strategy and was a major improvement. But it is still not a collective integrated approach-just a collection of strategy disciplines. My advice is to toss it away and look at other intellectual property (IP) already residing within the JV or look to leverage other good external IP. The secret to being of value will be to insure it is well integrated into the flow. The JV could learn a lot from COBIT 5 from ISACA . COBIT 5 delivers a great framework from the Enterprise Governance of IT connecting the business strategy to value to execution. (full disclosure – I am deeply involved in COBIT development).
- Development of the IP moving forward: Bring subject matter experts on staff to write the IP. Make it practical and get the guidance in a truly useable form.
- ITIL a Standard?: Some people still refer to ITIL as a standard, but isn’t that what ISO\IEC 20000 is for? Multiple standards won’t work. If ITIL is to continue as a framework, it needs to map easily to ISO/IEC 20000. If ITIL is to become a standard, then why also have ISO/IEC 20000?
- Future of the itSMF?: As a former international and itSMF USA board member, I believe the JV has the opportunity to financially support and leverage the user community, one that has invested its life in Service Management. The JV should reach out to this community immediately. As with me, they shouldn’t learn what’s going on in a press release
More thoughts to come over the next few weeks. For the JV and ITIL the clock is ticking now and I have been contacted by one group that is preparing to move forward with an alternative approach. If ITIL is to regain its luster and more importantly, become relevant again, the JV had better move swiftly!
What do you think?
Latest posts by Robert Stroud (see all)
- If You’re Not Innovating, It’s Time To Review Your Processes - February 24, 2014
- Innovation is Changing the View of Service - February 3, 2014
- Long Live Service Delivery! - January 28, 2014