The originating organization should decide what information it requires in order to learn from its projects and set up a system to identify, collect, store, update and retrieve that information, with the projects' information management system designed to gather what is relevant so project management processes can be improved. It should keep a list of every significant risk its projects have managed (7.7.5) and make sure relevant information is used by the other projects it starts. Information for learning can come from inside the project, feedback from the customer and the other stakeholders included, and from elsewhere, for example project logs, closure reports, claims, audit results, data analysis, project reviews, and corrective and preventive actions; the originating organization should check its validity before using it. Shortly before the project closes, the originating organization should review project performance, bringing out experience other projects can use, keep the results as documented information, use the project management plan as the framework for the review and, where possible, involve the customer and the other stakeholders. For long projects, interim reviews should be considered so information is gathered better and improvements made in time.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.