Ch9. Project Closure and Lessons Learned — Learning from Success and Failure

Why Project Closure Matters

Many teams rush through — or skip — the closure phase. Yet a proper close is one of the most important investments an organization can make in its future capability.

The cost of a poor closure:
→ Customer does not formally accept deliverables → disputes arise
→ Lessons not documented → the same mistakes are repeated
→ Procurement contracts not closed → legal exposure remains
→ Team contributions not recognized → morale suffers

Types of Closure

Normal closure:
→ All deliverables completed and accepted
→ Formal closure documents signed

Early termination:
→ Project cancelled
Causes: strategic shift, budget exhausted, environmental change
→ Cancellation still requires a formal closure process

Phase-gate closure:
→ At the end of each phase, decide whether to proceed
→ Go / No-Go decision

The Formal Closure Process

1. Final Deliverable Acceptance
   → Confirm acceptance criteria have been met
   → Handle remaining defects or transfer to the next phase
   → Obtain signed Acceptance Document

2. Contract Closure
   → Inspect and accept final vendor deliverables
   → Resolve any outstanding claims
   → Approve final payment
   → Issue formal contract closure notice

3. Administrative Closure
   → Archive project records (per compliance requirements)
   → Disband the project team
   → Release resources (staff, equipment, budget)
   → Write the final project report

Lessons Learned Management

Why Lessons Learned Are Critical

Repeating the same mistakes = organizational waste
→ Industry research: ~75% of projects encounter problems
   similar to those in previous project failures

Value of a lessons learned repository:
→ Saves future PMs time
→ Risk response strategies can be reused
→ Codifies best practices across the organization

Running an Effective Lessons Learned Session

Preparation:
→ Send all team members a pre-session survey (anonymous is fine)
→ Prepare data: schedule, cost, and quality variance reports

Facilitation:
→ No-Blame Culture — focus on what happened, not who did it
→ Ask "what" happened (use the 5 Whys technique to find root causes)
→ Celebrate what went well before discussing improvements

Documentation:
→ Situation   (What happened?)
→ Impact      (What were the consequences?)
→ Root Cause  (Why did it happen?)
→ Recommendation (How do we prevent a recurrence?)

Sample Lessons Learned Entry

Situation:    Two key developers left the team in sprint week 3
Impact:       Schedule slipped 2 weeks; $8,500 in additional costs
Root cause:   Staff retention risk was not identified; no backup plan existed
Recommendation: Make contingency planning for key resources mandatory;
               add an intent-to-leave check at least 6 weeks before
               any critical contractor's end date

Final Project Report Structure

1. Project Overview
   → Purpose, scope, duration, budget

2. Performance Summary
   → Were objectives met? (scope, schedule, cost, quality)
   → Status of key deliverables

3. Performance Measurement
   → Planned vs. actual (schedule and cost variance analysis)
   → EVM metrics (SPI, CPI)

4. Key Issues and How They Were Resolved

5. Lessons Learned Summary

6. Recommendations (for future similar projects)

7. Sponsor sign-off

Team Disbandment and Recognition

Why recognition matters:
→ Motivates team members
→ Builds a positive organizational culture
→ Makes it easier to attract talent for future projects

How to do it well:
→ Document each person's contributions individually
→ Report performance to senior leadership
→ Hold a project close-out celebration
→ Record team members' growth → useful as a reference for future roles

Resource release:
→ Notify functional managers of team member returns
→ Close temporary staff contracts
→ Return equipment and software licenses

Project closure = deliverable acceptance + contract closure + administrative closure Lessons learned format: Situation → Impact → Root Cause → Recommendation (No-Blame) Early termination still requires a formal closure process Final report: performance summary + variance analysis + lessons learned + recommendations