pm-closing

Formal PMBOK project closure requires six steps: verify deliverables against the scope baseline, obtain signed Final Acceptance from the sponsor, document lessons learned by knowledge area, archive project artifacts, release the team, and close any supplier contracts.

A closure report should include the Final Acceptance record, final EVM metrics versus baseline, lessons learned per PMBOK knowledge area, archived artifact locations, team release details, contract closure status, and an executive summary of objectives achieved.

Effective lessons learned are captured during the project, not just at the end, and follow an actionable format: context, situation, impact, action taken, and recommendation. Classify each lesson by PMBOK knowledge area and store it in an organizational repository.

Phase closure verifies phase exit criteria and archives phase artifacts while the team may continue to the next phase. Project closure requires full product acceptance, total team release, and closure of all contracts before transitioning to post-implementation stages.

Yes, cancelled projects require formal closure documenting why cancellation occurred, which partial deliverables have value, how contracts were terminated, and lessons about warning signs that were missed. The team must still be formally released.

Do not start closing when deliverables remain incomplete, supplier contracts are still open, or the sponsor is unavailable for formal acceptance. Closing without signed acceptance is only administrative closure, not true project closure.