Change Management - ITIL V2: Difference between revisions
From IT Process Wiki
mNo edit summary |
No edit summary |
||
| Line 22: | Line 22: | ||
==Sub-Processes== | ==Sub-Processes== | ||
[[Image:overview_chm.jpg| | [[Image:overview_chm.jpg|thumb|699px|none|link=https://wiki.en.it-processmaps.com/index.php/File:Overview_chm.jpg|Overview of Change Management]] | ||
'''Set Rules for the Handling of Standard Changes''' | '''Set Rules for the Handling of Standard Changes''' | ||
*Process objective: Rules are to be set that define explicitly for the IT organization, which Changes are allowed to be implemented without being subjected to the Change Management Process. For this purpose it is also determined, how these Changes ("Standard Changes") are handled. | *Process objective: Rules are to be set that define explicitly for the IT organization, which Changes are allowed to be implemented without being subjected to the Change Management Process. For this purpose it is also determined, how these Changes ("Standard Changes") are handled. | ||
'''Pre-Evaluate RFC''' | '''Pre-Evaluate RFC''' | ||
*Process objective: It is to be ensured, that only [[ITIL Glossary#Request for Change (RFC)|RFC]] which are in accordance with the defined quality requirements are accepted into the Change Management Process. | *Process objective: It is to be ensured, that only [[ITIL Glossary#Request for Change (RFC)|RFC]] which are in accordance with the defined quality requirements are accepted into the Change Management Process. | ||
'''Register and Classify Change''' | '''Register and Classify Change''' | ||
*Process objective: Registration and categorisation of [[ITIL Glossary#Request for Change (RFC)|RFCs]]/ Changes, so that only documented RFCs gain access into the process and are assigned to the correct and appropriate body (Change Manager, CAB, or EC). | *Process objective: Registration and categorisation of [[ITIL Glossary#Request for Change (RFC)|RFCs]]/ Changes, so that only documented RFCs gain access into the process and are assigned to the correct and appropriate body (Change Manager, CAB, or EC). | ||
'''Clearance of Change by the Change Manager''' | '''Clearance of Change by the Change Manager''' | ||
*Process objective: Clearance or rejection of a Change as well as preliminary scheduling and incorporation into the [[ITIL Glossary#Forward Schedule of Changes (FSC)|FSC (Forward Schedule of Changes)]]. | *Process objective: Clearance or rejection of a Change as well as preliminary scheduling and incorporation into the [[ITIL Glossary#Forward Schedule of Changes (FSC)|FSC (Forward Schedule of Changes)]]. | ||
'''Hold CAB Meeting''' | '''Hold CAB Meeting''' | ||
*Process objective: Clearance or rejection of a Change, in addition to preliminary scheduling and incorporation into the [[ITIL Glossary#Forward Schedule of Changes (FSC)|FSC (Forward Schedule of Changes)]]. | *Process objective: Clearance or rejection of a Change, in addition to preliminary scheduling and incorporation into the [[ITIL Glossary#Forward Schedule of Changes (FSC)|FSC (Forward Schedule of Changes)]]. | ||
'''Group Changes into Releases''' | '''Group Changes into Releases''' | ||
*Process objective: Approved Changes are to be grouped into Releases; the clearance for the Rollout is to be issued by Change Management. | *Process objective: Approved Changes are to be grouped into Releases; the clearance for the Rollout is to be issued by Change Management. | ||
'''Evaluate Change (Post Implementation Review)''' | '''Evaluate Change (Post Implementation Review)''' | ||
*Process objective: Appraisal of the process and the results of the Change-implementation, so that a complete documentation is present for later reference and lessons may be learnt from any mistakes. | *Process objective: Appraisal of the process and the results of the Change-implementation, so that a complete documentation is present for later reference and lessons may be learnt from any mistakes. | ||
'''Handling of Urgent Change by Emergency Committee (EC)''' | '''Handling of Urgent Change by Emergency Committee (EC)''' | ||
*Process objective: Quickest possible clearance or rejection of an Urgent Change, which is to serve to fight an emergency. | *Process objective: Quickest possible clearance or rejection of an Urgent Change, which is to serve to fight an emergency. | ||
==Involved Roles== | ==Involved Roles== | ||
| Line 65: | Line 54: | ||
*'''Emergency Committee (EC)''': The Emergency Committee represents the body for the approval of changes in emergencies which, due to their urgency, do not allow an orderly convening of the CAB. It is convened by the Change Manager or his representative for emergencies, whereby the constitution is determined by each individual situation. In order that the EC is definitely in a position to act in an emergency, rules for availability and temporary replacements must be reached with the members. | *'''Emergency Committee (EC)''': The Emergency Committee represents the body for the approval of changes in emergencies which, due to their urgency, do not allow an orderly convening of the CAB. It is convened by the Change Manager or his representative for emergencies, whereby the constitution is determined by each individual situation. In order that the EC is definitely in a position to act in an emergency, rules for availability and temporary replacements must be reached with the members. | ||
* [[Release Management#Involved Roles|Release Manager]] | * [[Release Management#Involved Roles|Release Manager]] | ||
==Related Checklists and KPIs== | ==Related Checklists and KPIs== | ||
| Line 75: | Line 62: | ||
====KPIs==== | ====KPIs==== | ||
*[[KPIs Change Management|Key Performance Indicators "Change Management" according to ITIL V2]] | *[[KPIs Change Management|Key Performance Indicators "Change Management" according to ITIL V2]] | ||
==Related [[ITIL Glossary]] Terms== | ==Related [[ITIL Glossary]] Terms== | ||
| Line 83: | Line 68: | ||
*[[ITIL Glossary/_ITIL_Terms_F#Forward Schedule of Changes (FSC)|Forward Schedule of Changes (FSC)]] | *[[ITIL Glossary/_ITIL_Terms_F#Forward Schedule of Changes (FSC)|Forward Schedule of Changes (FSC)]] | ||
*[[ITIL Glossary/_ITIL_Terms_P#Projected Service Availability (PSA)|Projected Service Availability (PSA)]] | *[[ITIL Glossary/_ITIL_Terms_P#Projected Service Availability (PSA)|Projected Service Availability (PSA)]] | ||
<!-- This page is assigned to the following categories: --> | <!-- This page is assigned to the following categories: --> | ||
[[Category:ITIL V2]][[Category:ITIL process]][[Category:Service Support]][[Category:Change Management]] | [[Category:ITIL V2]][[Category:ITIL process]][[Category:Service Support]][[Category:Change Management]] | ||
<!-- --- --> | <!-- --- --> | ||
Latest revision as of 18:54, 4 February 2016
ITIL Version: ITIL V2 → see also Change Management - ITIL V3
Process-Objective: In Change Management, all Changes to the IT infrastructure and its components (Configuration Items) are authorized and documented, in order to ensure that interruptive effects upon the running operation are kept to a minimum. The implementation steps are planned and communicated, in order to recognize potential side-effects as early as possible. The Change Manager and (for further-reaching Changes) the Change Advisory Board (CAB) bear the responsibility for this. A specific procedure is in existence for emergencies, dealing with Urgent Changes.
Part of: Service Support
Process Owner: Change Manager
Sub-Processes
Set Rules for the Handling of Standard Changes
- Process objective: Rules are to be set that define explicitly for the IT organization, which Changes are allowed to be implemented without being subjected to the Change Management Process. For this purpose it is also determined, how these Changes ("Standard Changes") are handled.
Pre-Evaluate RFC
- Process objective: It is to be ensured, that only RFC which are in accordance with the defined quality requirements are accepted into the Change Management Process.
Register and Classify Change
- Process objective: Registration and categorisation of RFCs/ Changes, so that only documented RFCs gain access into the process and are assigned to the correct and appropriate body (Change Manager, CAB, or EC).
Clearance of Change by the Change Manager
- Process objective: Clearance or rejection of a Change as well as preliminary scheduling and incorporation into the FSC (Forward Schedule of Changes).
Hold CAB Meeting
- Process objective: Clearance or rejection of a Change, in addition to preliminary scheduling and incorporation into the FSC (Forward Schedule of Changes).
Group Changes into Releases
- Process objective: Approved Changes are to be grouped into Releases; the clearance for the Rollout is to be issued by Change Management.
Evaluate Change (Post Implementation Review)
- Process objective: Appraisal of the process and the results of the Change-implementation, so that a complete documentation is present for later reference and lessons may be learnt from any mistakes.
Handling of Urgent Change by Emergency Committee (EC)
- Process objective: Quickest possible clearance or rejection of an Urgent Change, which is to serve to fight an emergency.
Involved Roles
- Change Advisory Board
- Change Manager
- Configuration Manager
- Emergency Committee (EC): The Emergency Committee represents the body for the approval of changes in emergencies which, due to their urgency, do not allow an orderly convening of the CAB. It is convened by the Change Manager or his representative for emergencies, whereby the constitution is determined by each individual situation. In order that the EC is definitely in a position to act in an emergency, rules for availability and temporary replacements must be reached with the members.
- Release Manager
