This article will give a brief introduction to the Change Management process used by IT when we make changes to our systems.
There is more than one type of Change Management used in IT, Project Managers talk about Change Management as a process of managing changes to what a project will deliver.
ITIL Change Management is about managing the changes we make to our systems, this could include:-
Change Management is one of a number of processes that are described in the the IT Infrastructure Library (ITIL), this describes best practices for delivering IT services.
Change Management is a process which allows IT to make changes to our systems, whilst managing the risk and impact to the services IT provide.
Changes are logged by IT Technical staff, sometimes with assistance of Project Managers who will have a clearer view of the business benefit of the change. Requests made by customers may end up being logged as changes in order to deliver what IT has been asked, customers are not expected however to log the change (although may have input into the business justification and timing of the change.)
There are three types of Changes.
The Change Advisory Board (CAB) meet once a week to review any normal changes which have been classified as Significant or Major. These are changes which pose a high risk and/or impact to services. CAB members receive details of the changes to be discussed in advance, this allows them to clarify any details with those proposing the change.
As well as reviewing Significant and Major changes, CAB will also review any changes which are related to services or technologies that are in "Heightened Awareness." A technology or service can be placed into Heightened Awareness when there has been a Major incident relating to the technology/service and IT want to have extra scrutiny on any changes which could cause further disruption to service.
For further details, please contact David Barker, Change Manager.