A project management plan that contains or cites the quality plan should be set up and kept current, its detail depending on factors such as the project's scope, size and complexity. At initiation, the originating organization should find details of relevant earlier projects and pass them to the project organization so their experience, lessons learned for instance, is put to best use. If the project exists to fulfil a contract, contract reviews should be held while the plan is developed to confirm the contract requirements can be met; if not, an initial review should establish the requirements and confirm they are suitable and achievable. The plan should: cite the project objectives and what the customer and the other stakeholders have documented as requirements, recording where each requirement came from so it can be traced; identify the project processes and document what each is for; identify organizational interfaces, especially the project organization's links and reporting lines to the originating organization's functions and the interfaces between functions inside the project organization; bring together the plans produced by other project processes, check them for consistency and settle discrepancies, namely the quality plan, the work breakdown structure (7.3.4), the schedule (7.4.5), the budget (7.5.3), the communication plan (7.6.2), the risk management plan (7.7.2) and the procurement plan (7.8.2); identify, contain or cite the product or service characteristics and the way each will be measured and assessed; set a baseline for measuring and controlling progress so the remaining work can be planned, with reviews and progress evaluations prepared and scheduled; define performance indicators, how to measure them and regular assessments to track progress, which should support preventive and corrective action and confirm the objectives are still valid as circumstances change; provide for the project reviews the contract calls for so its requirements are fulfilled; and be reviewed regularly and whenever significant changes happen. The quality plan should document or cite the project's quality management system, linked to the relevant parts of the originating organization's system, and built as far as practicable by adopting, and adapting where needed, the originating organization's system and processes; where other stakeholders set specific quality management system requirements, the project's system should be compatible with them.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.