When a project, release or iteration ends, stakeholders establish whether it produced the required capabilities and contribution, and the lessons learned are captured and shared: stakeholders accept the deliverables and ownership is handed over; the key closure steps are set out and followed, including reviews after implementation of whether the intended results were achieved; those post-implementation reviews are planned and carried out to find out whether the expected results arrived and to refine the methods used for managing projects and developing systems; any unfinished activities the project still needs to deliver its results are identified, assigned, communicated and followed up; and lessons are gathered from participants both during the project and at its end, reviewed together with the key activities that produced benefits and value, and analysed so other projects can use them.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.