- Change management is ingrained in every function and guided by overall IT / digital strategy
- A Central Advisory Board review committee is mandatory for every change made to automation landscape
- The CAB must approve any deviations or additional efforts, including scope change, resource, or timeline extension for introducing changes in landscape
Maturity Category: Change Management
Is there an established change management process for automation?
Formal change management
- Every change is notified and submitted to a Change Approval Board (CAB) before it is undertaken for execution
- The proposed change would accompany rollback strategy, potential output, and value
- Effort estimation, resource requirements, and timeline plan accompanies every change request
Informal change management
- Change management is informal and not documented
- Any guidelines are likely defined at the local level and are not propagated across functions. Accountability for change management is not defined
- Changes are not logged, and versions are not controlled
Ad hoc change management
- Changes to automation only happen when required or requested, and there’s no well-defined procedure or version management
- There are no policies governing the circumstances under which bot changes can occur