The ITIL 4 Change Enablement practice introduced the idea of responding differently to varying levels of complexity of change, from the routine to the catastrophic. It also recognises that traditional change control committees act too slowly and delay the delivery of value.
The idea of a CAB is de-emphasised under ITIL4 by the Change Enablement Practice.
The idea of the CAB has been, for the most part, replaced by the “Change Authority”. This is due to:
The CAB concept in ITIL4 has been replaced by criteria in the Definition of Done:
ITIL4 empowers teams to make changes through standardised events:
Depending on the scale of the change, ITIL4 also empowers the Product Owner or a product Manager (SAFe) as the role to authorise major changes.
Those that authorise changes under ITIL4 are called Change Authorities.
For example, an agile product team would make decisions on which elements of the product backlog will be tackled in a Sprint, while the Product Owner would make decisions on which customer requirements would be included into the Product Backlog.Organisations adopting DevOps typically establish systemic approval based on the success of automated checks in the continuous integration/continuous deployment (CI/CD) pipeline.
New ITIL 4 practices reinforce team’s needs to manage software and product changes through:
1. ITIL4. Axelos.