Scope should sit in the project plan, be defined, and then be managed so that only work formally approved enters the project and both deviations and delivery of the scope stay controlled. Defining scope should make clear what the project will add toward the goals set by the sponsoring organization or the customer, and the scope once defined should guide later decisions and communication about the project and its benefits. Scope should capture needs with their acceptance criteria and be sharpened as work moves on, may be shown through goals, a mapping or a work breakdown structure, should be split into pieces of work where useful, and should carry agreed acceptance criteria. Scope control should raise positive and lower negative effects of scope change, compare present scope with the approved baseline to spot variance, influence the causes of change and curb their impact on goals, and handle scope change requests in a controlled way that is joined up with the other control areas. Delivery of the outputs and outcomes that form the scope should be confirmed against the agreed acceptance criteria, including checking that quality needs and standards were met, confirming that the body funding the work, its customers and everyone else with a stake are ready to take delivery and, where relevant, to use what is delivered, managing handover of deliverables and duties from the team, and obtaining confirmation that handover was completed.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.