PMP · Question #422
After a couple of iterations, the project manager decides to present the product to a key stakeholder. The stakeholder's feedback is that the team missed the mark on many features. What should the pro
The correct answer is B. Schedule adequate sprint demos to gather early feedback from the stakeholders and adapt the. To avoid missing stakeholder expectations, the project manager should ensure frequent sprint demos are held to gather early and continuous feedback, allowing the team to adapt and adjust the product iteratively. This agile practice fosters alignment and reduces the risk of rework
Question
After a couple of iterations, the project manager decides to present the product to a key stakeholder. The stakeholder's feedback is that the team missed the mark on many features. What should the project manager do to avoid this in the future?
Options
- ASet up requirements-gathering sessions with all key stakeholders to evaluate the scope once
- BSchedule adequate sprint demos to gather early feedback from the stakeholders and adapt the
- CIncorporate design thinking practices into the project life cycle to better understand the product's
- DEvaluate the team's skills to look for someone with experience in product design and assign that
How the community answered
(35 responses)- A3% (1)
- B83% (29)
- C3% (1)
- D11% (4)
Why each option
To avoid missing stakeholder expectations, the project manager should ensure frequent sprint demos are held to gather early and continuous feedback, allowing the team to adapt and adjust the product iteratively. This agile practice fosters alignment and reduces the risk of rework or misinterpretation of requirements.
Setting up requirements-gathering sessions once is characteristic of a waterfall approach and would not prevent missed features in an agile context where requirements can evolve, leading to the same problem of late feedback.
Sprint demos, a core agile practice, are designed to regularly present working increments of the product to stakeholders, enabling early and continuous feedback. This iterative feedback loop allows the team to understand if they are meeting expectations, correct course promptly, and adapt the product backlog to better align with stakeholder needs, thereby preventing significant misalignments later in the project.
While design thinking can improve product understanding, it's a broader practice; scheduling sprint demos specifically addresses the issue of gathering early feedback on developed features from stakeholders to ensure alignment.
Evaluating team skills might be a general improvement, but it doesn't directly solve the communication and feedback gap with stakeholders that led to features missing the mark.
Concept tested: Agile feedback loops and stakeholder engagement
Source: https://www.scrum.org/resources/what-is-scrum/scrum-events/sprint-review
Topics
Community Discussion
5
Brenda K.Mar 9, 2026B is the fast pick. Agile lives on frequent feedback loops, so scheduling regular sprint demos catches misalignment early instead of waiting until a stakeholder review reveals a big miss.
Lena V.Mar 11, 2026Agreed on B, but the exam also wants you to connect those demos back to the backlog as the mechanism for actually reprioritizing based on what stakeholders flag, not just collecting the feedback.
Imani T.Mar 3, 2026B is the right call here because sprint demos catch misalignment early instead of waiting until stakeholders are already disappointed. Question though, is there a scenario on the PMP where design thinking (option C) would actually be the better answer over regular demos, or does PMI always favor the inspect-and-adapt loop?
Brenda K.Mar 5, 2026Good call on B, but watch the clock on these: C becomes the answer when the stem mentions discovering user needs or defining the problem before solutioning, because design thinking is front-loaded empathy work while demos are mid-sprint validation, so read the question fast and if you see empathy or ideation, pick C and move on in under 30 seconds.
Lena V.Feb 18, 2026B. Saw this on my exam last month and the key was "after a couple of iterations" meaning feedback came too late. Sprint demos are the agile mechanism for catching misalignment early, plain and simple.