PMP · Question #548
A project manager is leading a product feature rollout that will gain more subscribers for a video- streaming application. During the backlog grooming phase. the business stakeholders were unable to u
The correct answer is A. Include the business stakeholders in the iteration review.. To demonstrate feature integration and alleviate business stakeholder concerns during backlog grooming, the project manager should include them in the iteration review.
Question
A project manager is leading a product feature rollout that will gain more subscribers for a video- streaming application. During the backlog grooming phase. the business stakeholders were unable to understand the feature integration with the product and raised concerns. What can the project manager do to demonstrate the feature integration?
Options
- AInclude the business stakeholders in the iteration review.
- BInvolve business stakeholders in the iteration retrospective.
- CCreate a task for the iteration review and add it to the backlog.
- DReview the backlog in detail with the business stakeholders.
How the community answered
(39 responses)- A82% (32)
- B3% (1)
- C5% (2)
- D10% (4)
Why each option
To demonstrate feature integration and alleviate business stakeholder concerns during backlog grooming, the project manager should include them in the iteration review.
Iteration reviews (or Sprint Reviews) are formal opportunities in agile to demonstrate the increment of work completed to stakeholders and gather feedback. This allows business stakeholders to directly see the feature integrated and functioning, providing clarity and addressing their concerns about integration in a tangible way.
Iteration retrospectives are internal team meetings focused on process improvement, not for demonstrating product features or engaging business stakeholders about product functionality.
An iteration review is a scheduled event, not a task to be added to the backlog; this option misunderstands the agile process flow.
Reviewing the backlog in detail can explain a feature, but it doesn't offer the visual, interactive demonstration of integration that stakeholders need to fully understand and appreciate the functionality.
Concept tested: Agile stakeholder engagement and sprint review
Source: https://www.scrum.org/resources/what-is-a-sprint-review
Topics
Community Discussion
6A. The iteration review is exactly where you show working increments and get stakeholder feedback, which directly addresses their confusion about the feature integration. C is a trap because you don't create a scheduled event as a backlog task, and B is wrong since retrospectives are internal team process meetings, not demos.
A is your quick win. Anyone know why retrospective would burn time here?
I first leaned toward D but stakeholders need to see working integration, which happens at iteration review.
Confirmed A on my PMP attempt last month. Iteration reviews exist specifically to show working increments to stakeholders and get their feedback on integration concerns, which is exactly what the scenario is asking for.
Agree on A but I would add that the review is also where the team confirms whether the iteration goal was met, not just a demo for feedback, since I almost picked C because it mentioned acceptance criteria.
I first leaned toward D because reviewing the backlog in detail sounds like a natural fix for grooming confusion, but the real issue is that stakeholders need to see working integration, not just hear about it. That is exactly what the iteration review is for: it is the Agile ceremony where the team demos a working increment and gathers stakeholder feedback. Remember the mnemonic Review is Real, meaning you show actual integrated features to the business rather than talking through them on a list. This maps to the PMP Execution domain, where engaging stakeholders with verified deliverables resolves those concerns directly.