pm-closing

Formal PMBOK 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 with performance evaluations, and close any procurement contracts.

A closure report should include the Final Acceptance Document, final EVM metrics (BAC, EAC, VAC, SPI, CPI), baseline versus actual variance, lessons learned per PMBOK knowledge area, archived artifact inventory, team release records, and contract closure status.

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

Phase closure requires only phase-level acceptance, lessons, and artifact archiving, with partial team release and authorization to start the next phase. Project closure requires full product acceptance, total team release, and closure of all contracts.

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

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