hardMultiple Choice
Lessons Learned: Collecting What Went Well and What to Improve in Project Closure
A project is closing. The project manager collects feedback from the team on what went well and what could be improved. Which document is being created?
Quick Answer
The correct answer is the lessons learned document. This is because the process of collecting feedback on what went well and what could be improved during project closure is the very definition of creating a lessons learned report, which captures insights and recommendations to enhance future project performance. On the CompTIA Project+ PK0-005 exam, this concept tests your understanding of the closure phase’s key outputs, often appearing in scenario-based questions where a project manager gathers team input to avoid past mistakes. A common trap is confusing this with a project closure report, which focuses on final deliverables and budget, not on qualitative feedback for improvement. To remember, think of the phrase “lessons learned” as the project’s final review mirror—it helps you see what worked and what to fix, not just what was finished.
⚠ Common exam trap
CompTIA often tests the distinction between a final project report (which summarizes performance metrics) and lessons learned (which focuses on qualitative feedback for future improvement), leading candidates to confuse the two because both are created during closure.
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
✓
Lessons learned
The process of collecting feedback on what went well and what could be improved is the essence of creating a lessons learned document. In project management, this document captures insights and recommendations to improve future project performance, and it is a key output during project closure.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Final project report
Why it's wrong here
The final project report summarises performance against scope, schedule, cost and objectives for sponsors; it does not primarily capture team feedback on process improvements. It is tempting because it is also created at closure, but lessons learned is the document that records what went well and what could be improved.
- ✗
Project closure checklist
Why it's wrong here
A closure checklist tracks administrative completion tasks such as releasing resources, archiving documents and obtaining sign-offs; it does not capture narrative feedback. It is tempting because both artefacts are produced at closure, but lessons learned is the specific document recording team reflections on successes and improvements.
- ✗
Project charter
Why it's wrong here
The project charter authorises the project and records high-level scope, objectives and stakeholders at initiation; it is not produced during closure. Retrospective feedback on what went well and what could be improved belongs in the lessons learned register, which the charter predates by the entire project life cycle.
- ✓
Lessons learned
Why this is correct
Lessons learned captures team feedback on successes and improvement areas as the project closes, matching the stem exactly. It records knowledge for reuse in future projects, distinguishing it from the final report, which summarises performance against baselines, and from the benefits realisation plan, which tracks post-closure value.
Go deeper
Related to this question
About these practice questions
Courseiva writes every PK0-005 question from scratch — 954 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
2 more ways this is tested on PK0-005
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. Which TWO documents should be finalized during project closure?
medium- A.Work breakdown structure
- ✓ B.Final project report
- ✓ C.Lessons learned
- D.Project charter
- E.Risk register
Why B: The final project report (B) is a key closure document that summarizes project performance, deliverables, and lessons learned, providing a formal record for stakeholders. Lessons learned (C) captures what went well and what could be improved, which is essential for organizational process improvement and future project planning.
Variation 2. Which THREE documents are typically finalized during the project closure phase?
hard- ✓ A.Lessons learned
- ✓ B.Final project report
- C.Project charter
- D.Stakeholder register
- ✓ E.Approved change requests
Why A: The lessons learned document is finalized during project closure to capture what went well and what could be improved, serving as a knowledge base for future projects. It is a key output of the closing process group, ensuring organizational process assets are updated.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This PK0-005 practice question is part of Courseiva's free CompTIA 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 PK0-005 exam.