Fillable Printable Project Lesson Learned Sample
Fillable Printable Project Lesson Learned Sample
Project Lesson Learned Sample
<Client Name>
<Project Name>
PRJ.LL – Lessons Learned
Confidentiality notes
Document is for internal project use only
edited by:
author
approved by:
reviewer
unit:
unit_name
doc ID:
doc ID:
version:
n.m
issue date:
dd/mm/yyyy
doc. model
SMP_RMB.PRJ.LL2.0
PRJ.LL – Lessons Learned
<Client Name –Project Name>
edited by:
author
approvedby:
reviewer
version:
n.m
unit:
unit_name
issue date:
dd/mm/yyyy
pp.:
2/7
confidentiality notes:
document for internal project use only
SMP_RMB.PRJ.LL2.0
Document status
version
date
summary of changes
(approved by)
Summary of changes
List of main changes applied to
previous version:
Attachments:
PRJ.LL – Lessons Learned
<Client Name –Project Name>
edited by:
author
approvedby:
reviewer
version:
n.m
unit:
unit_name
issue date:
dd/mm/yyyy
pp.:
3/7
confidentiality notes:
document for internal project use only
SMP_RMB.PRJ.LL2.0
Contents
1 INTRODUCTION.......................................................................................................4
1.1AIM...................................................................................................................4
1.2REFERENCES......................................................................................................4
1.3CLIENTCONTACTDETAILS...................................................................................4
1.4DEFINITIONS.....................................................................................................5
1.4.1GLOSSARY....................................................................................................5
1.4.2ACRONYMS/ABBREVIATIONS...........................................................................5
1.5DOCUMENTSTRUCTURE......................................................................................5
2 Lessons learned.......................................................................................................6
2.1APPROACH...........................................................................................................6
2.2LESSONS FROM THE CURRENT PROJECT...........................................................................6
2.3STORING AND ACCESSINGPOLICY.................................................................................7
2.4LESSONS LEARNED APPLIED FROM PREVIOUS PROJECTS........................................................7
2.5PROCESS IMPROVEMENT RECOMMENDATIONS....................................................................7
PRJ.LL – Lessons Learned
<Client Name –Project Name>
edited by:
author
approvedby:
reviewer
version:
n.m
unit:
unit_name
issue date:
dd/mm/yyyy
pp.:
4/7
confidentiality notes:
document for internal project use only
SMP_RMB.PRJ.LL2.0
1INTRODUCTION
1.1AIM
The purpose of the lessons learned document for the XYZ Projectis to capture the
project’s lessons learned in a formal document for use by other project managers on similar
future projects.
This document may be used as partof new project planning for similar projects in order
to determine what problems occurredand how those problems were handled and may be
avoided in the future.
Additionally, this document details what went well with the project and why, so that other
project managers may capitalize on these actions.
This document will be formally communicated with the organization and will become a
part of the organizational assets and archives.
1.2REFERENCES
List supporting documentation with appropriate references:
Example:
•[DOC 1]
o“Financial Products” – Excel Document
oVersion 1.0 of 22/11/2007
Supporting evidence must also include the minutes of key meetings where necessary.
1.3CLIENT CONTACT DETAILS
Client contact details for theproject are listed below.
List the contact persons chosen by the Client for these activities, such as:
- Name, Surname and any other useful details
- Role/company position
- Department
- Role andresponsibilities
Example:
- Name: Paolo Rossi – [email protected], Tel 011.12312311
- Company role: Marketing manager
- Department Marketing
- Role in project/activity: Functional Requirements Manager
PRJ.LL – Lessons Learned
<Client Name –Project Name>
edited by:
author
approvedby:
reviewer
version:
n.m
unit:
unit_name
issue date:
dd/mm/yyyy
pp.:
5/7
confidentiality notes:
document for internal project use only
SMP_RMB.PRJ.LL2.0
1.4DEFINITIONS
1.4.1GLOSSARY
List any technical words used in the document, with the relevant definition
Example:
Record
A record is a contract which has not yet come into force
Funding
Funding refers to…
..
..
1.4.2ACRONYMS/ ABBREVIATIONS
List acronyms and abbreviations used in the document, with the relevant definition
BAM
Business Activity Monitoring
BPM
Business process management
BPM
Business Process
BRL
Business Rule
EAI
Enterprise Application Integration
EPC
Event Process Chain
KPI
Key Performance Indicator
…
…
1.5DOCUMENT STRUCTURE
This document is divided into the following sections:
INTRODUCTION
This section describes the aims, main references and document structure.
LESSONS LEARNED
This section contains the core contents of the lessons learned document.
PRJ.LL – Lessons Learned
<Client Name –Project Name>
edited by:
author
approvedby:
reviewer
version:
n.m
unit:
unit_name
issue date:
dd/mm/yyyy
pp.:
6/7
confidentiality notes:
document for internal project use only
SMP_RMB.PRJ.LL2.0
2LESSONS LEARNED
This section contains the approach, the lessons learned from the current project, the note
on how the information included in this document will be stored and accessed in the future,
what lessons were applied from previous projectsand the process improvement
recommendations.
2.1Approach
The lessons learned from the XYZProject are compiled from project journal entries
throughout the project lifecycle.
Lessons learned were also be gathered from both realized and unrealized risks in the
project risk register as well as through interviews with project team members and other
stakeholder as necessary.
The lessons learned from this project are to be used as references for future projects and
contain an adequate level of detail sothat other project managers may have enough
information on which to help base their project plans.
The lessons learned in this document are categorized by project knowledge area.
These knowledge areas consist of: procurement management, risk management,
integration management, quality management, time management, cost management, scope
management, human resource management, and communications management.
NOTE: some knowledge areas may not contain lessons learned ifnone were documented
throughout the project lifecycle.
2.2Lessons from the current project
The following chart lists the lessons learned for the XYZproject.
These lessons arecategorized by project knowledge area and descriptions, impacts, and
recommendations are provided for consideration on similar future new construction projects.
It is important to note that not onlyfailures or shortcomings are included but successes
as well.
Category
Issue Name
Problem/Success
Impact
Recommendation
Procurement
Management
Contract
Requirements
The PM was not fully
engaged in the
contract process.
Allrequirements were
not included in the
initial contract award.
A contract
modification was
required which added
a week to the
project.
PM must be fully
engaged in all
contract processes.
This must be
communicated to
both PM and
contract personnel.
Human
Resources
Management
Award Plan
There was no plan for
providing awards and
recognition to team
members.
Toward the end of
the project morale
was low among the
project team. There
was increased conflict
and team members
were asking to leave
The PM should
institute and
communicate an
awards/recognition
program for every
project.
PRJ.LL – Lessons Learned
<Client Name –Project Name>
edited by:
author
approvedby:
reviewer
version:
n.m
unit:
unit_name
issue date:
dd/mm/yyyy
pp.:
7/7
confidentiality notes:
document for internal project use only
SMP_RMB.PRJ.LL2.0
the project.
Scope
Management
Scope Creep
Stakeholders
continuously tried
adding to the project
scope throughout the
project lifecycle.
The PM did not have
a plan for addressing
scope creep and
allowed some
requirementsto be
added until the
sponsor stopped it.
Overallprojectdelay
of 3 weeks was the
result.
The PM must have
an approval process
for any proposed
scope changes and
communicate this
process to all
stakeholders.
2.3Storing and accessing policy
The lessons learned for the XYZProject will be contained in the organizational lessons
learned knowledge base maintained by the project management office (PMO).
This information will be cataloged under the project’s year (20xx) andthe type of project
for future reference.
This information will be valuable for any project manager assigned to a new similar
project in the future.
2.4Lessons Learned applied from previous projects
The XYZProject usedthe followinglessons learned from past projects:
1.Theaddition of a risk associated with planning cost and schedule based on external
dependencies was determined during the planning process by consulting the lessons
learned from the projectABC.
2.Theplanning of acceptable quality standards was based on lessons learned from the
project DEF. By planning for quality standards the project team was able to avoid
schedule and cost overruns by clearly communicating acceptable quality standards to all
contractors involved withthe project.
2.5Process improvement recommendations
As indicated in the lessons learned chart above, the XYZProject did not have a process
for reviewing and approving requested changes in requirements or project scope.
Not only is this a lesson learned for similar future projects; but the organization must
ensure that all projectmanagers are aware of the need for this process to be included in the
planning of all future projects.
Therefore, it is recommended that prior to work beginning on any new project, the project
manager must brief the project sponsor on theprocessfor requesting and approvingchanges
to project scope.
