PMP · Question #1135
A project manager has just been assigned to a new project. The project manager's first task is to present the project benefits to the stakeholders. Which three items should form part of the…
The correct answer is A. Risks associated with achieving the target benefits D. Expected business value E. Metrics to measure benefits throughout the project. When presenting project benefits, a project manager should include the anticipated business value, the metrics for measuring success, and the associated risks.
Question
Options
- ARisks associated with achieving the target benefits
- BStakeholder register
- CCommunications management plan
- DExpected business value
- EMetrics to measure benefits throughout the project
How the community answered
(22 responses)- A91% (20)
- B5% (1)
- C5% (1)
Why each option
When presenting project benefits, a project manager should include the anticipated business value, the metrics for measuring success, and the associated risks.
Presenting risks associated with achieving target benefits ensures stakeholders have a realistic view of potential challenges and encourages proactive risk management.
A stakeholder register is an internal project management document listing stakeholders, not an item to be presented to stakeholders regarding project benefits.
A communications management plan outlines how project information will be exchanged, but it is a procedural document, not a direct component of a benefits presentation itself.
The expected business value directly addresses what stakeholders care about: the tangible and intangible gains the project will deliver, justifying its existence and investment.
Metrics to measure benefits throughout the project provide concrete, measurable ways to track progress and success, allowing stakeholders to understand how and when value will be realized.
Concept tested: Project benefits management and communication
Source: https://www.pmi.org/pmbok-guide-standards/foundational/pmbok/benefits-management-plan
Topics
Community Discussion
6A, D, and E. My senior PM always says when you pitch benefits you have to show the business value, how you will measure them, and the risks that could derail them. B and C are operational documents you build later, not stuff you present to sell the vision.
Agree on A, D, and E, though I would frame B as a program governance artifact that actually strengthens the benefits pitch if you bring it to the table early, since stakeholders want to see the measurement framework before they sign off on the vision.
A, D, E confirmed. B and C are process documents, not benefit content, though I'd argue you wouldn't present risks this early either. PMI wants you talking expected business value and how you'll measure it, so memorize the logic, not the letters.
Leaned toward B and C first. Reframed around benefits: value, risks to value, and measuring value = A, D, E.
Leaned toward B first but benefits realization needs risks, value, and metrics, not registers.
B is the right call and yeah, benefits realization is about tracking outcomes against the business case, not maintaining a risk log. I would add that the trap with these is people see the word realization and jump to formal documentation artifacts when the question is really asking about measuring whether the program delivered what it promised.