Project completion report
Purpose. Close the engagement with a factual record of what was delivered,
what changed, and what should be done differently.
Project details
| Field | Detail |
|---|
| Project | |
| Customer | |
| Start date | |
| Completion date | |
| Project manager | |
| Sponsor | |
Executive summary
Three paragraphs: what the project set out to do, what it delivered, and what
remains.
Objectives and outcomes
| # | Objective | Success measure | Target | Actual | Met? |
|---|
| 1 | | | | | |
| 2 | | | | | |
| 3 | | | | | |
Deliverables
| # | Deliverable | Accepted | Date | Location |
|---|
| 1 | | | | |
| 2 | | | | |
Scope changes
| CR ID | Change | Approved by | Date | Impact |
|---|
| | | | |
Schedule
| Milestone | Planned | Actual | Variance | Reason |
|---|
| | | | |
Budget
| Item | Budgeted | Actual | Variance |
|---|
| | | |
KPI movement
| KPI | Baseline | Target | Final | Trend |
|---|
| Deployment frequency | | | | |
| Lead time | | | | |
| Change failure rate | | | | |
| MTTR | | | | |
Risks realised
| Risk | Impact | Response | Residual |
|---|
| | | |
What went well
What did not
Lessons for future engagements
| Lesson | Recommendation | Owner |
|---|
| | |
Outstanding items
| Item | Owner | Due | Risk if not done |
|---|
| | | |
Handover confirmation
| Item | Status |
|---|
| Documentation handed over | |
| Training delivered | |
| Runbooks verified | |
| Restore drill completed | |
| Support transition agreed | |
Acceptance
| Role | Name | Signature | Date |
|---|
| Qbits project manager | | | |
| Customer technical owner | | | |
| Customer sponsor | | | |