1. ITIL Project Change Management Workshop 7 February 2007
John Richards
ITIL Project
Change Management Workshop
7 February 2007

2. Agenda Background Scope Requirements Process Another time … Procedures
Roles
Tools

3. ITIL Roadmap

4. Why manage change? Change already happens
over 80 ‘newsworthy’ changes in 2006
We already ‘manage’ it
It already takes time and effort
Mistakes are potentially even bigger consumers of time and effort

5. What do we want to achieve?
A repeatable process for making changes
Make changes quickly and accurately
Protect services when making changes
Be more efficient and effective

6. The ITIL Definition
“Change Management covers the process of IT change for all types of Change, from the Request for Change, to assessment, to scheduling, to implementing, and finally to the review. It is the Change Management process that produces approval (or otherwise), for any proposed Change.”

7. Change management – outline plan
Hold meeting to determine scope and requirements
Write draft process and procedure
Review and agree process and procedure
Investigate and decide on software
Implementation
Training

8. Scope What is it we are trying to control? All change?
All change that affects production services?
All change that affects more than one team?

9. Requirements minimise disruption to services caused by change
ensure that records of hardware, software, services and documentation are kept up to date.
What types of change?
How much detail?
Who will approve or reject change?
What kind of records?

10. Process