Skip to content
PMPCAPM

Lessons Learned Register

A lessons learned register is a project document used to record knowledge gained during a project so that it can be used to improve future performance on the current project and for future projects.

Share:

Explanation

The lessons learned register is created early in the project as an output of the Manage Project Knowledge process and is updated throughout the project lifecycle. It captures what went well, what could be improved, and recommended actions for future phases or projects. Entries may cover challenges encountered, risks that materialized, successful strategies, process improvements, and team performance insights.

Unlike the lessons learned repository (which is an organizational process asset), the lessons learned register is a living project document specific to the current project. As the project progresses, team members and stakeholders contribute observations during retrospectives, reviews, and regular meetings. The project manager facilitates this process and ensures the register is kept current.

At project closure, the contents of the lessons learned register are transferred to the organizational lessons learned repository, making them available to future projects. This transfer is one of the key activities in the Close Project or Phase process. Organizations that consistently capture and apply lessons learned demonstrate higher maturity and project success rates.

Key Points

  • Created early in the project and updated continuously throughout
  • Captures successes, challenges, and recommendations for improvement
  • A project document, distinct from the organizational lessons learned repository
  • Transferred to the organizational repository during project closure

Exam Tip

Lessons learned are captured throughout the project, not just at the end. If the exam presents a scenario where a team waits until closure to capture lessons learned, that approach is incorrect.

Frequently Asked Questions

Related Topics

High-yield topics our learners drill most before exam day.

Change Control Board (CCB)

A Change Control Board (CCB) is a formally chartered group responsible for reviewing, evaluating, approving, deferring, or rejecting changes to the project, and for recording and communicating those decisions.

Burndown Chart

A Burndown Chart is a graphical representation of work remaining versus time in a Sprint or release, showing whether the team is on track to complete the planned work.

Resource Leveling

Resource leveling is a resource optimization technique in which adjustments are made to the project schedule to keep resource usage at or below a defined limit, often resulting in a longer project duration.

Risk Register

The risk register is a project document that records the details of individual project risks, including their identification, analysis results, response plans, and current status.

Stakeholder Mapping

Stakeholder mapping is the visual representation of stakeholder relationships, influence, interest, or other attributes using grids, matrices, or diagrams to support analysis and engagement planning.

Relative Estimation

Relative Estimation is an agile technique where work items are sized in comparison to each other rather than in absolute units like hours or days, providing faster and more accurate estimates.

Cost Performance Index (CPI)

Cost Performance Index (CPI) is an EVM efficiency metric that measures cost performance as the ratio of earned value to actual cost: CPI = EV / AC.

Schedule Performance Index (SPI)

Schedule Performance Index (SPI) is an EVM efficiency metric that measures schedule performance as the ratio of earned value to planned value: SPI = EV / PV.

Earned Value Management (EVM)

Earned Value Management (EVM) is a methodology that integrates scope, schedule, and cost data to assess project performance and progress objectively.

Part of

Integration Management

Study full domain →

Test your knowledge

Practice scenario-based questions on this topic with detailed explanations.