Post-Project Retrospective Template
Within a week of any project delivery, gather to document what worked and what failed — before memory evaporates.
Goal
Prevent the next project from repeating the same mistakes, via structured documentation right at closure, rather than relying on vague memory months later.
Steps
-
1
Schedule the meeting within 5 business days of actual delivery — delay loses detail.
Expected Outcome
Evidence base
School: Agile Retrospectives / Lessons Learned
Founders: Norman Kerth · PMBOK (2001)
Norman Kerth in "Project Retrospectives" (2001) established the structured post-closure review method; PMBOK formally mandates it within "Close Project or Phase".
Keywords
Frequently asked questions
How long does "Post-Project Retrospective Template" take?
When will I notice the effect of "Post-Project Retrospective Template"?
Is "Post-Project Retrospective Template" evidence-based?
Is "Post-Project Retrospective Template" suitable for beginners?
Subscribe for full access
Subscribe to Plus for full access to this practice and the whole catalogue, or try first — free, no sign-in, no commitment.
7 complete practices (one per domain) are free forever, no sign-in.