Skip to content
PMPCAPM

Lessons Learned Repository

A lessons learned repository is an organizational process asset that stores and organizes lessons learned from completed projects, making them available for use on future projects.

Share:

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

Practice it free

Explanation

The lessons learned repository is an organizational-level store of historical project knowledge. Unlike the lessons learned register (which is specific to a single project), the repository aggregates lessons from many projects across the organization. It is maintained by the project management office (PMO) or a similar organizational entity and is accessible to project managers and teams starting new projects.

The repository typically contains categorized entries covering topics such as risk management successes, scheduling techniques that worked, communication strategies, technical solutions, vendor management insights, and stakeholder engagement approaches. It may be implemented as a database, a knowledge management system, a wiki, or even structured document libraries.

The repository is a key input to planning processes on new projects. When a project manager begins a new initiative, consulting the lessons learned repository helps avoid repeating past mistakes and leverages proven approaches. During project closure, the lessons learned register from the completed project is transferred to the repository, enriching it for future use. Organizations with mature project management practices invest in maintaining and curating this repository.

Key Points

  • •An organizational process asset, not a project-specific document
  • •Aggregates lessons from multiple completed projects across the organization
  • •Key input for planning processes on new projects
  • •Maintained by the PMO or a similar organizational entity

Exam Tip

The lessons learned register is a project document (current project). The lessons learned repository is an organizational process asset (across all projects). The exam expects you to know which is which.

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 Repository

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