UBC — AI Solutions

Audit — Dynamic Documentation Platform

Living documentation that stays in sync with engineering, cloud, AI, and compliance activity. Documents update themselves as the organization changes.

Back to library
SOP
Fresh

SOP-PM-10 — Project Closure & Lessons Learned

Closes projects, captures lessons learned, and feeds them back into organisational learning.

Owner: PM GuildApprover: PMO DirectorVersion: 2.0Updated: 10/18/1969

1. Purpose

Close projects cleanly and capture organisational learning.

2. Scope

All projects.

3. Definitions

  • Closure report — The end-of-project document summarising outcomes and lessons.

4. Roles & Responsibilities (RACI)

ActivityRACICadence
Author closure reportPMPMO DirectorSponsor, TeamPortfolioPer project
Facilitate lessons sessionPMPMO DirectorTeamPMOPer project

5. Procedure

  1. Complete outstanding acceptances and financials.
  2. Author the closure report (outcomes vs. objectives, budget, lessons).
  3. Hold a lessons-learned session with the team.
  4. Publish lessons to the organisational lessons library.
  5. Release team members and archive project artefacts.

6. Inputs & Outputs

Inputs

  • Deliverables
  • Financials
  • RAID history

Outputs

  • Closure report
  • Lessons entries

7. Controls & Metrics

MetricTarget
Projects with published closure report100%
Lessons entries per project≥ 3

8. Exceptions & Escalation

  • Cancelled projects require an abbreviated closure report within 10 business days.

9. Records & Retention

RecordRetention
Closure reports10 years
Lessons libraryPerpetual

10. Related Documents

  • SOP-PM-09
  • SOP-QMS-10

11. References

  • PMBOK 7
  • PRINCE2

12. Revision History

See the Versions tab for the full change history maintained by the Auto-Doc Engine.

Document code: SOP-PM-10 · Aligned to PMBOK 7 / PRINCE2 CP. Controlled document — reproduction outside the UBC QMS requires the Quality Manager's approval.

Suggested by AI
No suggestions right now.
Frameworks
PMBOK 7
PRINCE2
ISO 9001