What the project is and what it covers are defined and documented so that stakeholders share one understanding, and the sponsors formally approve it: every project has a clear written statement of its nature, scope and deliverables; every project has at least one sponsor with enough authority to manage how it is carried out within the programme; key stakeholders and sponsors from business and IT agree to and accept the requirements, including the definition of success (acceptance) criteria and performance metrics; a dedicated project manager is appointed who understands the technology and the business and is competent to run the project; the definition sets out what a communication plan must cover for internal and external communications; the definition is kept current during the project, with stakeholders approving it as requirements change; and execution is tracked, with timely approval, through mechanisms such as regular reports and reviews at stage gates, releases or phases.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.