PMP Lessons Learned Practice Question
During project closure, the customer is satisfied with the deliverables and has signed off. However, the project team has not completed the lessons learned documentation. Which TWO actions should you take?
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Document the lessons learned based on your own observations and interview key stakeholders
Options C and E are correct because lessons learned should be documented as part of project closure. While the customer has signed off, the project is not fully closed until administrative closure is complete, which includes capturing lessons learned. Option C allows you to gather lessons learned through your own observations and interviews, ensuring key knowledge is captured even if the team hasn't completed documentation. Option E involves facilitating a session with the team, which is the best practice for comprehensive knowledge capture before final closure. Options A and D are incorrect because they ignore or postpone lessons learned, missing the opportunity for organizational improvement. Option B is incorrect as delaying closure solely for lessons learned is inefficient; closure can proceed while lessons learned are collected in parallel.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Proceed to close the project and archive the documents without lessons learned
Why it's wrong here
Skipping lessons learned during project closure is a critical oversight, as the Project Closure Process Group explicitly requires the capture of this valuable knowledge. Lessons learned are essential Organizational Process Assets (OPAs) that document successes, failures, and recommendations, directly contributing to the organization's continuous improvement and future project success. Failing to do so deprives the organization of crucial insights and violates standard project management practices.
- ✗
Delay project closure until lessons learned are completed
Why it's wrong here
Delaying project closure solely to complete lessons learned is generally unnecessary and can prolong the administrative closure process. While lessons learned are a vital component of project closure, they are integrated within the process, not a preceding gate that must fully conclude before any closure activities can proceed. The project manager should manage the closure activities, including lessons learned, concurrently to ensure an efficient and timely formal completion of the project.
- ✓
Document the lessons learned based on your own observations and interview key stakeholders
Why this is correct
Documenting lessons learned through personal observations and direct interviews with key stakeholders is a highly effective and proactive approach. This method allows the project manager to gather diverse perspectives and capture nuanced insights that might not emerge in a group setting, ensuring a comprehensive collection of project knowledge. It directly contributes to developing robust Organizational Process Assets (OPAs) for future reference and organizational learning.
- ✗
Close the project and submit lessons learned later
Why it's wrong here
Closing the project and then submitting lessons learned at a later, separate time diminishes their formal integration and value within the Project Closure Process Group. Lessons learned are a formal output of administrative closure, requiring proper documentation and archiving as part of the project's official records. Separating this activity risks incomplete capture, loss of context, and a lack of formal recognition as a critical Organizational Process Asset (OPA).
- ✓
Facilitate a lessons learned session with the team before final closure
Why this is correct
Facilitating a dedicated lessons learned session with the project team before final closure is a cornerstone practice for comprehensive knowledge capture. This collaborative approach encourages open discussion, allows for collective reflection on successes and challenges, and ensures that diverse team experiences are formally documented. It is an excellent method for identifying actionable insights and contributing to the organization's knowledge base for future projects.
Go deeper
Related to this question
About these practice questions
One of 800 original PMP practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This PMP practice question is part of Courseiva's free PMI certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the PMP exam.