PMP · Question #827
As a project is ending, a business stakeholder requests information from the project manager regarding overall project performance to determine the success of the initiative. What should the project…
The correct answer is B. Document the key performance indicators (KPIs) in the final project report. To determine project success at the end of a project, the project manager should document Key Performance Indicators (KPIs) in the final project report. This provides a comprehensive overview of performance against established metrics.
Question
As a project is ending, a business stakeholder requests information from the project manager regarding overall project performance to determine the success of the initiative. What should the project manager do to provide relevant information to the stakeholder?
Options
- AUpdate the project status report to include current performance information.
- BDocument the key performance indicators (KPIs) in the final project report.
- CDocument the project performance and influencing factors in the lessons learned register.
- DInform the stakeholder that performance will be evaluated three months after project closure.
How the community answered
(27 responses)- A4% (1)
- B70% (19)
- C19% (5)
- D7% (2)
Why each option
To determine project success at the end of a project, the project manager should document Key Performance Indicators (KPIs) in the final project report. This provides a comprehensive overview of performance against established metrics.
A project status report provides current information during execution but is not the final, comprehensive document used to assess overall success at project closure.
Documenting the key performance indicators (KPIs) in the final project report is the most appropriate action because the final project report serves as a definitive summary of the project's outcomes, achievements, and overall performance against predefined success criteria. KPIs provide measurable data that directly addresses the stakeholder's request to determine the success of the initiative, offering a clear and comprehensive overview.
The lessons learned register focuses on processes, challenges, and improvements for future projects, not primarily on summarizing the *overall performance and success* of the current project for stakeholders.
Informing the stakeholder that performance will be evaluated three months after project closure delays crucial information and does not address the immediate request for determining project success *as the project is ending*.
Concept tested: Project closure reporting and success metrics
Topics
Community Discussion
5B is correct because the final project report is the primary closure artifact for communicating overall performance to business stakeholders. The PMBOK emphasizes documenting KPIs, quality objectives, and scope achievements in this final deliverable to validate project success. A is a monitoring and controlling activity, not a formal closure step. C captures future improvement opportunities, not a performance summary.
Saw this one on my exam last spring, and the key is the stakeholder wants to know if the initiative was a success, which points straight to the final report with KPIs. Knocked it out in about twenty seconds because A is a trap for ongoing reporting, C is lessons learned which is a different animal, and D is just absurd.
Good catch on B and I will add one nuance: make sure the KPIs in that final report tie back to the success criteria defined during planning, because the exam loves to test whether you can trace metrics end to end across Domain 5.
C on exam last month, the lessons learned register is where performance gets captured.
Actually B is correct here, Toby, because lessons learned captures experiences and knowledge gained, while the project performance data and metrics get recorded in the work performance reports. Easy way to remember it: lessons learned looks backward at what we learned, work performance reports capture how we are doing right now.