Change management
Introduction
We formalize and standardize the change management process across Altus Group with the goal of improving security, availability, and the integrity of production infrastructure, systems, services, applications, and data.
The goal of change management is to improve service resilience by reducing and ultimately eliminating unplanned service disruptions to production services due to change.
Our guiding principles
Changes are logged in the change management system.
Change requests include a risk assessment where all known risks are disclosed and documented.
Changes are reviewed and tested prior to bringing it to CAB/seeking approval
Changes requests are closed after execution with the outcome recorded in the change management system.
Changes have a backout plan documented in the change request
Roles and responsibilities
Change manager
The Change Manager is the final approver for all change requests and is responsible for the creation and maintenance of the Change Management processes. They are responsible for ensuring Change Requests meet the Change Management Policy criteria prior to approval.
Change approvers
Change approvers are the initial approvers of Change Requests that impact or could impact a service or services that they own or are responsible for. Change Approvers identify conflicts due to other activities scheduled on the same day as the Change Request and consult the change calendar for possible conflicts before granting Change Request approval.
Change implementer
In addition to executing the change, the Change Implementer is responsible for verifying that the change met or did not meet the criteria for success and updating the Change Request with the results of the change upon Change Request closure.