Lessons Learned Template
Lessons Learned Template
[Text in red and enclosed in [ ] is explanatory example test and should be deleted]
ID Date raised Event (what happened) Lesson category Early warning signs? Recommendations Action(s) Owner WBS ID Status
[1] [mm/dd/yyyy] [Give a clear detailed description of [Positive / [Note any warning signs that [Recommendation for improvement or to [Actions that will be taken to [Person who [Link to WBS ID [Open / In progress /
what happened and the impact. negative / could be picked up in future] remove the issue for future projects]. implement the lesson learned] will take the if applicable] Closed]
Lessons can be positive as well as action(s)]
negative].
1 03/21/2020 Test of API connection was missed Negative None Add a new test case for this test in QA Request additional test case from Project 2.13.003 API Closed
in QA, which meant that an issue environment test manager and inform PMO. manager connector
with the connection was not picked
up until go live.
2 3/5/2020 Agreeing the rating for defects in Positive Early in UAT issues that During project initiation agree and Share lesson with PMO and Project 3.1 UAT In progress
advance avoided facilitated meant weren't blocking were logged document how issues/defects will be suggest amended to the project manager
that some 'cosmetic' issues could be as defects. rated, and define which issues ratings will initiation process.
fixed post go live. not be blocking for go live. E.g. Defect - a
function doesn't work - blocker for go live
Cosmetic - no impact on function - nice to
have - not blocker for go live.
[Notes
Every organisation has a different approach to the lessons learned log. This example includes all of the information that needs to captured,
and has been used on numerous real world projects. However, feel free to tweak this to fit your project.]