Change Management Training Workshop - Phase 1

Hoorah!  On Wednesday afternoon I delivered a change management (based on ITIL) training workshop to the IT managers of multiple councils as they are working in partnership to deliver shared IT services.  I spent quite a lot of time preparing the materials for it as, knowing my audience, I wanted to be sure I had things they could take away and refer to when I'm not around and to consider which questions were likely to arise that I would need to answer.  The training packs were made up of some change management basics, process framework document, process diagrams, copy of presentation slides and a little 7Rs of Change Management laminated card.

I'd originally scheduled 3 hours for the session to allow for lots of discussion (again, knowing who would be present).  I surprised myself by keeping everyone on-track so that we actually finished in just over 2 hours.  I think this was due to a few factors,  My preparation headed off potential questions and that facilitation training continuing to pay off (thank you Cathy) ;)  My agenda for the afternoon was:

1. Purpose of session
2. Presentation - 'Let's Have Some Change Management - with a Dash of Pragmatism'
3. Normal Change Process (using process framework documentation)
   
4. Emergency Change Process (using process framework documentation)
5. Exercices (1: Name that change 2: Roleplay an emergency change with some curveballs throw in)
   
6. Wrap-up Discussion
   
7. Feedback forms (I believe in self-improvement)
   

I was expecting quite a hard time from some of them - so I was pleasantly surprised that each manager present was taking notes and asking pertinent questions.   The only negative feedback I had was that some of them think we should wait until we have the new ITSM tool in place before introducing change management.  As all you ITSMers out there will know it's crucial to get the process agreed, documented and tested before implementing it in a tool - so I'm not too concerned about this point (although it certainly would be great if a more appropriate tool were in place to support the process in the meantime (and no - this is not an invitation for vendor spam thanks!).

Only time will tell how effective or not the workshop was.  The next stage is rolling out training to all the IT staff.  It certainly achieved it's objective in educating them in the basics of change management, terminology, process, etc.  One of the feedback forms actually showed that they thought they knew a lot going into the session, then coming out realised how much they didn't know and have yet to learn ;)

It's times like this that I wish I would be there for the duration of the journey - letting go is never easy is it?

All change... and introducing change

As those of you who have been here awhile will know, I've been trying to get an ITSM Programme going at my organisation for some time.  I finally get the budget and the buy-in, and submit the mandate for approval to the board only for me to go and get another job.  My timing is impeccable.  I'm finding it quite difficult to let go as I still have this wonderful vision in my head that I want to make a reality.  Anyhow, as that isn't going to happen time to replace it with a new vision - but I digress.

Some months ago I was tasked with quickly introducing change control ahead of change management as part of the approved ITSM Implementation Programme.  As you can imagine, I wasn't keen on doing this as I wanted it to be done in a properly managed way - however the business need was and continues to be there so I threw something together (through workshop with other key managers).  They specificially didn't want a lot of documentation so two sides of A4 had to suffice.  As predicted, confusion reined for people failed to understand what it was all about, how and when to use it, etc.  What did they expect without allowing time for training or enough documentation to provide the detail required?

Anyhow, one of my tasks before I head off is to train the IT managers in the basics of change management and teach them how and when to use our revised new change management process (only covers normal and emergency changes in an initially small scope).  I spent today fleshing out the document with sufficient detail to address the questions they already have and those that will be asked and preparing some training packs and little laminated cards that they can stick by their PCs.  Tomorrow I aim to finish the presentation that will go with it all because I'm delivering it on Wednesday afternoon!  I'll let you know how it goes...

Moving your ITIL Implementation Forward - part 2

This post continues my summary of key points from the itSMF's latest e-symposium, 'Moving your ITIL Implementation Forward' this time focusing upon Malcolm Fry's 'ITIL V3 Essentials and the Role of a CMDB' and Harvey Davison's 'What Should Configuration do for Change?'

Malcolm Fry - ITIL V3 Essentials and the Role of a CMDB
I've seen a lot of presentations from Malcolm on-line but not had the opportunity to see him live so this was particularly interesting to me - if its possible to assess a presenter's style from an online web seminar anyway!

One of the things that I found interesting was his immediate acknowledgment of the v3 certification scheme being superior to that of v2. He strongly felt that in v2 everyone forgot about the other 7 ITIL books (true enough) and that with v3 the assessment of ALL core books will lead to more rounded ITSM professionals.

He also dropped a plug for a book that he is writing at the moment with working title: 'How to build a service management department'. I look forward to seeing what it has to offer.

His presentation faltered a moment for me when he talked about the v3 lifecycle and had the wrong order of the core books up on screen (had transition after operation instead of before). Something fundamental like that inevitably then makes you question the accuracy and validity of the rest of the presentation but thankfully that was the only error I spotted.

The slides showing how v2 and v3 work together were quite helpful, but most amusing was his use of a perfume analogy to achieve an ITIL implementation road map. Apparently in perfume making there are four key things: Primary, Modifier, Blender and Fixative. He expounded upon the analogy by showing how the various ITIL processes could slot into one of these categories, e.g. Incident, Problem, and Change Management came under Primary with Financial management listed as a fixative.

There wasn't really anything of note in the section on the Service Knowledge Management System (SKMS) except that he reiterated the benefits of template CIs. Towards the end of the presentation he did make a joke regarding how there should be a 'decision management' process in ITIL. Someone pointed out in the Q&A afterwards that this exists in the form of IT governance and went on to promote A 8015:2005 which is the Australian standard which has been taken to form the basis of a new ISO standard.

Harvey Davison's 'What Should Configuration do for Change?'
Of all the presentations I think that this was the most interesting and useful for me. This may be because he is working in the trenches of Lloyds TSB and using ITIL theory successfully in practice. I really liked the whole approach to identifying which areas to attack first in the creation of a CMDB and using change management as a driver for this.

The approach sounds simple enough... define the objectives, identify the results required, and ascertain what is needed to deliver those results. Actually doing this can be quite a challenge though.

When it came to defining their CIs they divided into type, role, and status. In doing this they were then able to produce a cube which showed where best to focus their efforts.



An analogy I liked was seeing the infrastructure as a jenga tower. The CMBD then tells you which brick you can pull out safely without the tower falling down.

To be honest there was so much good stuff in this presentation that, rather than me trying to summarise it here, I highly recommend that you sign up to the itSMF e-symposium and go listen to it and download the slides in the archive!

Check back on Tuesday for the final summary featuring Georges Ataya's and Rob Stroud's presentation on 'IT Governance for the Real World, Mapping COBIT & ITIL' and a summary of the roundtable Q&A.

The 7 Sources Of Problems

I imagine that many of the ITIL readers out there are familiar with Dr ITIL. Some of you may even recall a series he wrote regarding the 7 sources of problems. I found it so useful that I diligently saved the articles to my hard disc for future reference; so when I found out about his first e-book 'The S7ven Sources of Problems: How to eliminate problems before they impact your business' I found myself wondering why I should pay for content that was already out there on the internet. That was until I read it!

The e-book goes far beyond the previous articles; a total of 66 pages. Diagrams are kept to a minimum, the majority of the book is content, content, content. It neatly distills not just what the 7 sources of problems are; but importantly HOW to mitigate and in some cases completely eliminate them. I find the writing style no-nonsense and conversational which makes for an easy read. Admittedly much of what he writes may be common sense to some people; but sometimes you need someone to remind you of what you already know; let alone point out the things you don't know.

In my view this should be mandatory reading for not just problem process owners everywhere, but anyone involved in project or change management, in fact include anyone supporting the IT environment and frustrated with the constant fire-fighting.

Start your journey of problem elimination by opening the door with the golden key (nudge, nudge, wink, wink!).

And the answer is...

In our case we don't have the resources to go for a big bang (and nor would we want to). ITIL is very much about culture change, so it isn't going to happen overnight (more like years, especially in the public sector). Harnessing the support of everyone in IT will be fundamental to the success of the implementation.

To answer my question posed on Tuesday, the service support processes identified to help eliminate our pain areas are:

1. Service Level Management
2. Review maturity of current Service Desk Function and Incident Management
3. Change Management
4. Problem Management
5. Configuration Management

It may be that we can run change and configuration concurrently, I always think they are like the chicken and the egg. You don't want to implement Configuration management with change management otherwise you have no controls over the Configuration items; but if you implement Change with the configuration then you don't have the links to what are you changing... 'A person could go mad thinking about this... (10 points to the person who knows where that is from).

There are of course a lot of things involved from the people side with awareness training and workshops, to benchmarking existing processes, to consideration of the right tools to support those processes.

My intention is to manage the implementation as a 'Programme' of distinct projects, using Prince 2 Lite as the methodology. The high level plan has been drafted, let's see what the coming week holds...

For those of you in the UK - have a good bank holiday weekend!