Aims to maximise how many service and product changes succeed, by making sure each change's risks are properly weighed, by authorizing changes to go ahead, and by managing the schedule of changes. A change is anything added, altered or removed that might affect services directly or indirectly, and every organization sets its own scope for change control. Standard changes are low risk, pre-authorized, well understood and fully documented, and go ahead without further authorization once the procedure itself has been risk-assessed and authorized. Normal changes are scheduled, assessed and authorized through a process, with change models setting roles for each type. Emergency changes go in as quickly as possible, with fast-tracked assessment and authorization and as much testing as the situation permits. A change authority is assigned for each type of change; in high-velocity organizations this role is carried by peer review and automated testing. The change schedule helps with planning and communication, prevents clashes and helps allocate resources. The practice governs changes to the portfolio, policies and practices; treats improvements as changes to be assessed; consults or informs customers and users; contributes greatly to transition; governs changes to built or bought components; and tells delivery and support staff about changes, who may themselves assess and authorize.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.