The objectives of the Change Management Process are to:
- Respond to the customer’s changing business requirements while maximizing value and reducing incidents, disruption and re-work.
- Respond to the business and IT requests for change that will align the services with the business needs.
- Ensure that changes are recorded and evaluated, and that authorized changes are prioritized, planned, tested, implemented, documented and reviewed in a controlled manner.
- Ensure that all changes to configuration items are recorded in the configuration management system.
- Optimize overall business risk – it is often correct to minimize business risk, but sometimes it is appropriate to knowingly accept a risk because of the potential benefit.
Change types
Change Control supports three types of changes: standard, normal and emergency change. The change type determines which state model is used and the change process that must be followed.
Standard Change
A standard change is a pre-authorized change that is low risk, relatively common and follows a specified procedure or work instruction.
Changes of this type are most frequently implemented, have repeatable steps and were successfully implemented earlier. As Standart changes are pre-approved, they follow the process in which authorization steps are not required.
Approved standard change requests can be predefined as a template in the appropriate catalog to make requesting a change more efficient. Also, this capability lets the team to control the changes that are authorized as standard.
Emergency Change
A change that must be implemented as soon as possible, for example, to resolve a major incident or implement a security patch. The priority of the emergency change lets it bypass group approvals and go straight to the Authorization state, for approval by the CAB group.
The cases where emergency change is suitable are (for example):
- Fix the current fail situation or retroactive where the impact has already been experienced;
- Fix the fail situation where the negative impact is invariable if action is not taken.
The priority of the emergency change lets it bypass group approvals and go straight to the Authorization state, for approval by the CAB group.
These changes do not follow the complete life cycle of a normal change due to the speed with which they must be authorized. Therefore, they progress directly to the Authorize state for approval from the CAB Approval group.
