Before closure, unless the project is terminated, all activities should be shown as complete, the scope confirmed as delivered, each work package finished or terminated, and any operational duties that remain agreed and accepted. Open actions, risks and issues should be handed to the programme or portfolio manager, or to another named authority where no programme or portfolio exists, and contracts should be examined, their condition checked, and closed where appropriate. The project manager should hold a closure review with the sponsor, key team members and stakeholders, record performance against the plan and achievement of objectives as the basis for authorizing closure, and the sponsor should agree the terms and timing of post-closure reviews, with lessons reviewed, stakeholders told that the project has closed and handover actions carried out. Where a project is terminated, completed and uncompleted activities should be recorded, deliverables transferred with customer acceptance or rejection recorded, work package status noted, documents archived, resources released, ongoing duties agreed and contracts closed.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.