Preventing Stakeholder Dissatisfaction in Sprint Reviews
During a sprint review, stakeholders express disappointment with the product increment, stating it does not meet their expectations. The team believed they were on track based on the user stories. What should the project manager do to prevent this in the future?
Quick Answer
The answer is ensuring stakeholders are involved in the sprint review and provide feedback early and often. This is correct because the root cause of stakeholder dissatisfaction in a sprint review is a disconnect between the team’s assumptions and the stakeholders’ actual expectations, which can only be resolved through continuous collaboration. The technical concept here is the Agile principle of customer collaboration over contract negotiation, which demands that feedback loops be short and frequent so the product increment aligns with stakeholder needs throughout development, not just at the end. On the PMP exam, this question tests your understanding of stakeholder engagement in Agile frameworks, often appearing as a trap where candidates mistakenly choose to “re-estimate the backlog” or “improve user story writing,” missing the core issue of insufficient feedback. A strong memory tip is to think of the “feedback firewall”—early and often involvement prevents last-minute disappointment by validating expectations incrementally.
⚠ Common exam trap
PMI often tests the misconception that more documentation or more frequent status updates solve communication gaps, when the real solution is structured, iterative stakeholder collaboration during the sprint review.
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
✓
Ensure stakeholders are involved in the sprint review and provide feedback early and often
The root cause of the disconnect is a lack of early and continuous stakeholder involvement. By engaging stakeholders in the sprint review and soliciting feedback frequently, the project manager ensures that expectations are validated against the increment throughout the development cycle, not just at the end. This aligns with the Agile principle of customer collaboration over contract negotiation and prevents the team from building features based on assumptions.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Document the feedback and adjust the next sprint accordingly
Why it's wrong here
This is reactive; prevention is better.
- ✓
Ensure stakeholders are involved in the sprint review and provide feedback early and often
Why this is correct
Regular stakeholder involvement during reviews helps catch misalignment early.
- ✗
Ask the product owner to write more detailed user stories
Why it's wrong here
While helpful, the issue may be about validation, not just detail.
- ✗
Have the team present their work to stakeholders more frequently
Why it's wrong here
Frequency alone may not help if the format doesn't allow for meaningful feedback.
Go deeper
Related to this question
About these practice questions
This PMP question is part of Courseiva's 800-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
3 more ways this is tested on PMP
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. During a sprint review, the product owner expresses dissatisfaction with the feature delivered, stating it does not meet the acceptance criteria. The team disagrees, claiming it meets the definition of done. What should the project manager do first?
medium- A.Escalate the issue to the project sponsor for a decision
- ✓ B.Schedule a meeting with the product owner and the team to review the acceptance criteria and define done
- C.Support the team's position and ask the product owner to accept the deliverable
- D.Ask the team to redo the work to meet the product owner's expectations
Why B: Clarifying expectations by reviewing the acceptance criteria together resolves the misunderstanding and aligns both parties.
Variation 2. During a sprint review, the product owner expresses dissatisfaction with the delivered increment because it does not meet their expectations. The team followed the agreed-upon acceptance criteria. What should the project manager do?
medium- A.Inform the product owner that the work meets the agreed criteria and cannot be changed
- B.Escalate the issue to the project sponsor for a decision
- C.Ask the team to redo the work to meet the product owner's unstated expectations
- ✓ D.Facilitate a conversation between the product owner and the team to clarify expectations and update the acceptance criteria for next sprint
Why D: The project manager's role in an Agile framework is to facilitate collaboration and ensure alignment between the product owner and the development team. Since the team met the agreed acceptance criteria, the gap is in the product owner's expectations, which must be clarified through direct conversation. Updating the acceptance criteria for the next sprint ensures future increments align with the product owner's vision without redoing work that was technically correct.
Variation 3. During a sprint review, the product owner expresses dissatisfaction with a feature delivered by the team, stating it does not meet the acceptance criteria. The team insists they followed the requirements as written. What should the project manager do FIRST?
medium- A.Ask the team to redo the feature to meet the product owner's expectations.
- ✓ B.Facilitate a conversation between the product owner and the team to clarify the acceptance criteria.
- C.Update the project documents to reflect the product owner's new requirements.
- D.Refer to the project charter to determine the original scope.
Why B: The immediate priority is to resolve the misunderstanding between the product owner and the team. The project manager should facilitate a conversation to clarify the acceptance criteria, ensuring both parties have a shared understanding before any rework or documentation changes occur. This aligns with the PMP's focus on stakeholder engagement and conflict resolution within the 'People' domain.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This PMP practice question is part of Courseiva's free PMI 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 PMP exam.