Scribd
Upload
89 views

Lessons Learned: Project Name: Project Number: Project Manager: Project Sponsor

The document outlines lessons learned from two past projects. The first lesson is that testing an API connection was missed in QA testing, resulting in an issue at go live. The recommendation is to add a new test case to QA. The second lesson is that agreeing on a defect rating system in advance helped resolve minor issues after go live.

Uploaded by

Ranjeet Dongre
Copyright
© © All Rights Reserved
Available Formats
Download as XLSX, PDF, TXT or read online on Scribd
89 views

Lessons Learned: Project Name: Project Number: Project Manager: Project Sponsor

The document outlines lessons learned from two past projects. The first lesson is that testing an API connection was missed in QA testing, resulting in an issue at go live. The recommendation is to add a new test case to QA. The second lesson is that agreeing on a defect rating system in advance helped resolve minor issues after go live.

Uploaded by

Ranjeet Dongre
Copyright
© © All Rights Reserved
Available Formats
Download as XLSX, PDF, TXT or read online on Scribd
You are on page 1/ 6

Lessons Learned

Project name: Project number:


Project manager: Project sponsor:

[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.]

[Columns you might want to add:


Project phase The relevant phase e.g. initiation, build, test etc
Recommended items to add to a process Where the lesson requires an addition to a process note it here e.g. 'add end to end integration test to UAT phase'.
Items to remove from a process Note any items that need to be removed from a process e.g. 'for OOTB SaaS projects remove customisation design from build phase.'
Closed date The date when all actions related to the lessons learned are completed.
Latest progress A progress update e.g. 'sent lesson recommendations to PMO for review.'

www.stakeholdermap.com 1 of 6 © T Morphy. stakeholdermap.com. 2009 - 2099


This template was provided by www.stakeholdermap.com

www.stakeholdermap.com 2 of 6 © T Morphy. stakeholdermap.com. 2009 - 2099


Project Management resources

Project Management Templates

20 Common Project Risks (and how to manage them)!

The Top 50 Business Risks (and how to manage them)!

Issue Log Template [free download]

End Project Report Template

Risk Register Template

Stakeholder Management Templates

Work Breakdown Structure (WBS) template in Excel


Lessons Learned
Project name:
Project manager:

[Text in red and enclosed in [ ] is explanatory example test and should be deleted]
ID Date raised Event (what happened) Lesson category
[1] [mm/dd/yyyy] [Give a clear detailed description of [Positive / negative /
what happened and the impact.
Lessons can be positive as well as
negative].

1 03/21/2020 Test of API connection was missed in Negative


QA, which meant that an issue with
the connection was not picked up
until go live.

2 3/5/2020 Agreeing the rating for defects in Positive


advance avoided facilitated meant
that some 'cosmetic' issues could be
fixed post go live.
Project number:
Project sponsor:

Early warning signs? Recommendations Action(s) Owner


[Note any warning signs [Recommendation for [Actions that will be taken [Person who will take
that could be picked up improvement or to remove to implement the lesson the action(s)]
in future] the issue for future projects]. learned]

None Add a new test case for this Request additional test Project manager
test in QA environment case from test manager
and inform PMO.

Early in UAT issues that During project initiation Share lesson with PMO Project manager
weren't blocking were agree and document how and suggest amended to
logged as defects. issues/defects will be rated, the project initiation
and define which issues process.
ratings will 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.
WBS ID Status
[Link to WBS ID if [Open / In progress /
applicable] Closed]

2.13.003 API connector Closed

3.1 UAT In progress

You might also like