Professional Scrum Master I (PSM I)People & TeamsMedium
During a Sprint Review, a key stakeholder expresses strong dissatisfaction with a feature, stating that it does not meet their unstated expectations, even though it aligns with the Product Backlog Item's Definition of Done. This leads to a tense discussion. How should the Scrum Master facilitate this situation?
- AFacilitate a conversation between the Product Owner and the stakeholder to clarify expectations and explore potential solutions for the Product Backlog.
- BSuggest that the Product Owner add a new Product Backlog Item to address the stakeholder's feedback in a future Sprint.
- CRemind the stakeholder that new requirements can only be introduced through the Product Owner and not during the Sprint Review.
- DDefend the Developers' work, emphasizing that the feature meets the Definition of Done.
Show answer & explanationAnswer & explanation
Correct answer: A. Facilitate a conversation between the Product Owner and the stakeholder to clarify expectations and explore potential solutions for the Product Backlog.
The Sprint Review is an inspect and adapt event. The Scrum Master should facilitate a constructive dialogue between the Product Owner and stakeholders to clarify unspoken expectations and incorporate new insights into the Product Backlog, embracing empiricism.
Why the other options are wrong
- B. This is a plausible outcome, but the Scrum Master's immediate role is to facilitate the conversation to understand the feedback first, not immediately prescribe a solution.
- C. While true, this can be perceived as dismissive and unhelpful, hindering open feedback and collaboration with stakeholders.
- D. While the Definition of Done is important, rigidly defending it without addressing stakeholder concerns can shut down valuable feedback and collaboration.
Sprint Review Purpose
The purpose of the Sprint Review is to inspect the Increment and adapt the Product Backlog if needed. The Scrum Team presents the results of their work to key stakeholders and progress toward the Product Goal is discussed.
- Collaboration between the Scrum Team and stakeholders.
- Opportunity to gather feedback and adapt the Product Backlog.
- Informal, not a gate or approval meeting.
Memory trick: Review for feedback, adapt for future track.