Change management spans identifying, evaluating, authorizing, documenting, implementing and controlling change. Before authorization, the purpose, extent and effect of a change should be analysed, and changes with an effect on the project objectives need agreement from the customer and the other stakeholders. Change management should also address: changes to the project scope, objectives and project management plan; coordination of changes across linked project processes and resolution of any conflicts; processes for documenting change; improvement (clause 8.3); and the effects of change on personnel (clause 6.2.4). Effects of changes on the project should be identified as early as possible, their root causes analysed and the findings used to devise solutions and improve the project process. Before any change is carried out, a change request should be lodged according to the processes set in the project management plan, with supporting documented information that includes a justification. Configuration management is one part of change management: in projects it concerns how the project's products or services are configured, both deliverable items and non-deliverable ones such as test tools and installed equipment (see ISO 10007).
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.