Checklist Change Record: Difference between revisions
From IT Process Wiki
mNo edit summary |
No edit summary |
||
| Line 16: | Line 16: | ||
'''Checklist Category''': [[ITIL-Checklists|ITIL Templates]] - Change Management | '''Checklist Category''': [[ITIL-Checklists|ITIL Templates]] - Change Management | ||
'''Source''': Checklist "Change Record" from the [https://en.it-processmaps.com/products/ | '''Source''': Checklist "Change Record" from the ITIL Process Map V2 | ⯈ [https://en.it-processmaps.com/products/itil-process-map.html ITIL Process Map V3] | ||
<p> </p> | <p> </p> | ||
| Line 60: | Line 60: | ||
<p> </p> | <p> </p> | ||
<html><a rel="author" href="https:// | <html>By:  Stefan Kempter <a rel="author" href="https://www.linkedin.com/in/stefankempter"><img style="margin:0px 0px 0px 0px;" src="/images/bookmarking/linkedin.png" width="16" height="16" title="By: Stefan Kempter | Profile on LinkedIn" alt="Author: Stefan Kempter, IT Process Maps GbR" /></a>, IT Process Maps.</html> | ||
<!-- This page is assigned to the following categories: --> | <!-- This page is assigned to the following categories: --> | ||
Latest revision as of 20:00, 29 March 2019
ITIL Process: ITIL Service Transition - Change Management
Checklist Category: ITIL Templates - Change Management
Source: Checklist "Change Record" from the ITIL Process Map V2 | ⯈ ITIL Process Map V3
The Change Record builds upon the RFC; it therefore contains the information from the RFC augmented by statements as to the decision-making and implementation progress:
- Unique Change ID
- Initiator of the RFC
- Date of submission
- Short description of the Change being applied for
- Reason for the Change to be implemented (Business Case)
- Effects upon:
- Business areas on the client-side
- IT Services
- IT Infrastructure components (CIs)
- Technology spectrum (is a new technology being introduced?)
- Risks during the implementation of the Change
- Types of risk
- Counter-measures (e.g. reversion procedure)
- Priority (urgency)
- Category (effects)
- Predicted/suggested time schedule for the implementation
- Review comments from the clearance process
- Constraints (i.e. restrictions, which arise due to the evaluation of the Change by the CAB)
- Resources for the implementation
- Required personnel resources (from which areas?)
- Estimated work effort for the required personnel resources
- Necessary training measures
- Users on the client-side
- IT Employees
- Cost estimate
- Statement as to whether the costs are included in the planning of the budget
- History of events
- Date of submission of the RFC
- Date of the receipt of the RFC by the Change Manager
- Date of the acceptance or rejection of the RFC
- Date of the clearance or rejection of the Change
- Date of transferal to Release Management
- History of decisions
- Person/ body in charge for the decision about clearance/rejection (Change Manager/ CAB/ EC)
- Where necessary, the reason for the rejection of the Change by the Change Manager/ CAB/ EC
By: Stefan Kempter 
, IT Process Maps.
