Change Management is the process of managing changes in a controlled, efficient, and standardized way with the goal of minimizing business risk and maintaining service continuity. Change Management assesses any impact or potential risk a proposed change could have on your organization before it is introduced.
While Change Management manages the process of updating or introducing a new configuration item (CI), Release Management manages the deployment of those configuration items that are implemented by Change Management. Change Management thus works with the Release Management module to roll out changes in the organization.
Effective Change Management ensures that changes are processed properly. During Change Management, you assess any impact or potential risk that a proposed change could have on your organization before that change is introduced. During Change Management, you control the lifecycle of all changes and ensure that changes are made with as little disruption to the organization as possible. A change is an action that results in a new status for one or more configuration items.
The goal of Change Management is to ensure that standardized methods and procedures are used to process change requests. Successful Change Management minimizes the impact of change-related issues and improves daily operations.
After a change has been approved, Release Management begins the release process, which includes creating a back-out plan to return to an operational start point.
Change State Transitions
A change request is constrained by the different states in its lifecycle. For example, after a change is in implemented state, it cannot be reverted to the scheduled state. The Change Manager role can take a change through different states and is not constrained by its status-driven lifecycle. However, we recommend that the change be driven by its lifecycle states.
|
An emergency change request is not constrained by state transitions as these types of changes are usually created after the fact, solely for recording purposes. Your administrator can create additional statuses as needed. |
Change Approval, Planning, and Scheduling
One of the key principles of Change Management is to ensure there is approval from key stakeholders to move forward with the change. Change approvers are sometimes referred to as Change Advisory BoardThe people who approve the financial, technical, and operational impact of a request for change. members or CAB members. The approval boards set up for Change Management analyzes the impact, risks, and cost associated with most types of changes. In HEAT, standard and minor changes are approved by the Change Manager and do not require the Change Advisory Board, but significant, major, and emergency changes require additional levels of approval. The approval workflow set up by default (which can be reconfigured by your application administrator) determines whether a change requires additional levels of approval before it can be accepted and scheduled. See Approving a Change Request for more information about the approval process.
The CAB, ECAB (emergency CAB), and Management Committee teams determine the risk and cost associated with a potential change. In HEAT, the risk score allows for an appropriate assessment when approving a change. See Setting the Risk Level.
Priority. See Default Priority Values.
When a change is approved, the change is scheduled. The Change Manager can use the Change Scheduler to schedule the change at a time that will cause the least impact to the organization.
From the change record itself, the Change Manager can view which incidents, problem, configuration items (including services), and release the change is linked to, thereby reducing the potential for adversely impacting other configuration items (and services) during the change process. The configuration item owner can define lockout periods for the configuration item as well as identify a favorable change window for implementing the configuration item. In HEAT, the change calendar (see Using the Change Calendar) and change lockout feature lets the Change Manager effectively manage changes and reduce impact and other conflicts.