S2 - 10 - Change Enablement Practice

Change Enablement Practice — Purpose

Maximize the number of successful IT changes by ensuring that risks have been properly assessed, authorizing changes to proceed, and managing the change schedule

• Balances risk while maximising thorughput

Change — Definition

The addition, modification, or removal of anything that could have a direct or indirect effect on services

The 3 Types of Changes

• Standard

• Normal

• Emergency

Standard Change — Definition + Related Points

A pre-defined, pre-approved low risk common change that follows a well-defined procedure

• _____ _____s can be considered a Service Request and are typically implemented as a Service Request

• A full risk assessment is done when the _____ _____ is being defined or when a change is being made to the way the standard change is carried out

Normal Change — Definition + Related Points

A change that needs to be scheduled, assessed and authorized by following a defined process

• Must be fully tested and documented prior to implementation

• Triggered by the creation of a change request

• Change Schedule helps manage normal changes

Emergency Change — Definition + Related Points

A change that must be implemented as soon as possible

• Assessment and Authorization can be expedited

• Not recorded in a change schedule

• Examples

  • Resolving incidents | Implementing Security Patches

Change Authority — Definition + Related Points

A person or group who authorizes changes based on the change type and model

• Needs to be assigned to each change

• Made up of any and all stakeholders who will be affected by the change

Change Schedule — Definition + Related Points

Used to show planned and historical changes so that you can plan changes, communicate changes clearly, avoid conflicts, and assign resources appropriately

• Allows collaboration and promotes visibility

• Provides information to incident and problem management practices about planned or deployed changes

• Helps manage normal changes