PMP · Question #838
A project manager is working on a hybrid project that has been in progress for the last nine months. Some project stakeholders are becoming frustrated because they do not see the value added by the pr
The correct answer is A. Invite the stakeholders to the next sprint review meeting and review the completed work.. To demonstrate project value to frustrated stakeholders in a hybrid project, the project manager should invite them to a sprint review meeting to see completed work firsthand.
Question
Options
- AInvite the stakeholders to the next sprint review meeting and review the completed work.
- BProduce an extensive report highlighting the project's accomplishments.
- CEnsure that stakeholders are aware of the current process challenges on the project
- DAdd resources to the project so all of the iterations will be completed earlier.
How the community answered
(26 responses)- A73% (19)
- B4% (1)
- C15% (4)
- D8% (2)
Why each option
To demonstrate project value to frustrated stakeholders in a hybrid project, the project manager should invite them to a sprint review meeting to see completed work firsthand.
Sprint review meetings in agile contexts are designed specifically for demonstrating completed, working increments of the product to stakeholders and gathering feedback. This provides a tangible, iterative demonstration of value being delivered throughout the project, directly addressing concerns about not seeing value. Seeing the actual working product is far more impactful than just reading a report.
An extensive report can be useful, but seeing a live demonstration of working software or deliverables (as in a sprint review) often provides a more compelling and immediate sense of value.
Making stakeholders aware of process challenges might explain delays but does not demonstrate value; it could even increase frustration.
Adding resources to complete iterations earlier doesn't directly address the perception of value or show what has been delivered so far.
Concept tested: Demonstrating value in agile/hybrid projects
Source: https://www.scrum.org/resources/what-is-scrum
Topics
Community Discussion
8A is correct. In a hybrid project, the sprint review is purpose-built for showing stakeholders working deliverables and tangible progress, which directly addresses their frustration about not seeing value. B is a trap because static reports do not give stakeholders the interactive demonstration they need. C just makes excuses, and D throws resources at a communication problem, which never fixes perception. Exam tip: whenever stakeholders question value on an agile or hybrid project, the answer almost always involves getting them into the sprint review to see completed work firsthand.
Confirmed A on exam last week. The key word here is "demonstrate" which means showing actual working deliverables, not just talking about them in a report like option B tries to do. One thing I want to understand better: would the answer change if the question said the project was predictive instead of hybrid, since sprint reviews are an agile ceremony?
Good catch on demonstrate, but even in a predictive project the answer stays A because sprint reviews can still apply if the team layers agile practices onto a waterfall baseline, which the exam assumes whenever the ceremony is mentioned regardless of the overall lifecycle label.
Confirmed A on my exam last month. The sprint review is literally where you show working deliverables, which is the fastest way to prove value in a hybrid setup. Does anyone know if the PMI exam always leans toward showing over telling when stakeholders are frustrated, or are there cases where a formal report would actually be the better call?
Hybrid throws a wrinkle in though: if you have compliance-focused or executive stakeholders who arent in the sprint review room, a condensed formal report alongside the demo covers both bases, and PMI does test that combo when the stem mentions distributed stakeholders.
Leaned toward B first, but showing actual completed work beats a report.
A is the right call and it is a quick win you can nail in under 30 seconds. Sprint reviews exist specifically to show working deliverables and get stakeholder feedback, which directly addresses the value concern here. B is a time sink that nobody will read and D is a trap because adding resources midstream just creates Brooks Law chaos. Flag C for review if you have spare seconds at the end since process challenges do not demonstrate value, they just explain delays.
Agreed on A, but the exam usually pairs sprint review with a working increment, so if the stem says nothing is shippable yet, pivot to C since demonstrating value can mean showing progress on process improvements too.