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:

Know it well enough for the exam? Questions on Lessons Learned Register are scenario-based, not definitional.

Practice it free

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 plots the work remaining (usually in story points) against time in a sprint or release, alongside an ideal line to zero, so the team can see each day whether it is on track to finish.

Burn-Up Chart

A burn-up chart plots completed work rising over time against a separate total-scope line, so progress and scope changes are visible independently; the work is finished when the two lines meet.

Resource Leveling

Resource leveling is a resource optimization technique that adjusts activity start and finish dates so that demand for a resource never exceeds its availability, accepting a longer schedule and a changed critical path if necessary.

Deliverables

A deliverable is any unique and verifiable product, result, or capability to perform a service that must be produced to complete a process, phase, or project, such as a software release, an audit report, or a trained support team.

Power Interest Grid (Power/Influence Grid)

The power interest grid is a 2x2 stakeholder mapping tool that plots each stakeholder by power (ability to affect the project) and interest (concern about its outcome) to decide how to engage them: manage closely, keep satisfied, keep informed, or monitor.

Critical Path Method (CPM)

The Critical Path Method (CPM) is a schedule network analysis technique that calculates early and late start and finish dates for every activity to find the longest path through the project, the minimum project duration, and the float on every other path.

Weighted Shortest Job First (WSJF)

Weighted Shortest Job First (WSJF) is a prioritization model, popularized by SAFe, that ranks work by cost of delay divided by job duration (usually estimated as job size), so the items that lose the most value per unit of time spent waiting are done first.

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.

Part of

Integration Management

Study full domain →

Practice Lessons Learned Register

Scenario-based questions with a full explanation on every answer — including why the distractors are wrong.