Scribd
Upload
826 views5 pages

Lessons Learned Template

This 3 sentence summary provides an overview of the key information from the document: The document presents lessons learned from a completed project, including accomplishments, stakeholders, project description, assessments of schedule, scope and resources, and a review of what went well and what needs improvement in areas like project team management, scope management, time management, resource management, risk management, communications management, and quality management. The lessons learned template is used to systematically capture feedback that can help improve processes and results on future projects.

Uploaded by

Likhit Verma
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
826 views5 pages

Lessons Learned Template

This 3 sentence summary provides an overview of the key information from the document: The document presents lessons learned from a completed project, including accomplishments, stakeholders, project description, assessments of schedule, scope and resources, and a review of what went well and what needs improvement in areas like project team management, scope management, time management, resource management, risk management, communications management, and quality management. The lessons learned template is used to systematically capture feedback that can help improve processes and results on future projects.

Uploaded by

Likhit Verma
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 5

[Project Title], #[Proj.

ID]
Lessons Learned

Presented by [Name]
[Date]

Lessons Learned Template Version 2.2


10/07/2015
Project Description
WHO ACCOMPLISHMENTS
Stakeholders and Team Members:
PM Lead: [SU or OCIO]
[Key Deliverables / Results]
Sponsor: [Sponsor name and SU]
Other stakeholders: [Other SUs impacted by
the project]
OCIO Manager: [Manager name, group)]
OCIO PM/Coordinator: [PM/Coordinator
name)]
Other OCIO Groups: [Other OCIO groups
involved in the project]
WHAT ASSESSMENT
Schedule
Project Description: Scope
[1-2 Sentence Description of Effort] Resources
Overall Results
Actual Completion Date:
Overall Results represents an overall assessment of the project based on project process
[Date] and results, along with Schedule, Scope and Resources performance variance measures.
Schedule, Scope, and Resources indicate the variance between ACTUAL and LATEST
PLANNED project performance as follows:

G = ACTUAL is less than or equal to 10% above LATEST PLANNED;

2 Y = ACTUAL is between 10-30% above LATEST PLANNED;


R = ACTUAL is more than 30% above LATEST PLANNED
Lessons Learned
PROJECT PROCESS AND RESULTS WHAT WENT WELL WHAT NEEDS TO CHANGE

Project Team Management


Were team expectations or ground rules
established?
Did the team comply with the team ground rules?
Overall, did the team work well together?

Scope Management
Was the project scope clear and verifiable?
Was the potential impact of requested scope
changes clearly communicated to stakeholders?
Were changes in Project scope formally agreed
and documented?

Time Management
Was the project schedule realistic with accurate
time estimates?
Was the project schedule kept up to date
throughout the course of the project?
Was care taken to ensure the project schedule
would be met?

Resource Management
Were the right people (skill sets) on the team?
Were all stakeholders adequately represented?
Were the number of required resources accurately
estimated?

3
Lessons Learned
PROJECT PROCESS AND RESULTS WHAT WENT WELL WHAT NEEDS TO CHANGE

Risk Management
Was the team effective in identifying potential
problems?
Were the right people involved in the risk
assessment process?
Were the risks accurately measured (probability
and impact)?
Were the risks effectively mitigated?

Communications Management
Were all planned documents produced?
Was there too much or too little documentation
(number of documents, level of detail)?
Were there many or too few meetings?
Did the appropriate individuals receive information
in a timely fashion?

Quality Management
Were the project requirements traced through
execution and control to help ensure requirements
would be met?
Was the product tested against project objectives /
requirements?
Did the final product meet project objectives /
requirements
Overall, was customer satisfied with the final
product?

4
[Optional Slide for Diagram or Other
Useful Material]

NOTE: You may include a


Design Diagram, Screen Shots
or other material that would
help illustrate results

You might also like