A Scrum Team has just completed their Sprint Planning. They have committed to a Sprint Goal and selected several Product Backlog Items. During the Sprint, the Product Owner realizes that a newly emerged market trend makes one of the selected Product Backlog Items obsolete and wants it removed from the Sprint Backlog. What is the most appropriate action?
- AThe Developers remove the item from the Sprint Backlog as they are self-managing.
- BThe Scrum Master facilitates a discussion between the Product Owner and Developers to assess the impact and decide on the best course of action.
- CThe Scrum Team must continue working on the item as the Sprint Backlog is fixed once the Sprint starts.
- DThe Product Owner removes the item from the Sprint Backlog and informs the Developers.
Show answer & explanationAnswer & explanation
Correct answer: B. The Scrum Master facilitates a discussion between the Product Owner and Developers to assess the impact and decide on the best course of action.
While the Product Owner is accountable for the Product Backlog, the Sprint Backlog is created by and belongs to the Developers. Changes during a Sprint require collaboration. The Scrum Master facilitates such discussions to ensure transparency and team consensus on how to adapt to new information.
Why the other options are wrong
- A. Developers can adapt the Sprint Backlog, but a significant change like removing a committed item due to external factors should involve the Product Owner.
- C. The Sprint Backlog is not fixed; it is a highly visible, real-time picture of the work that the Developers plan to accomplish during the Sprint, and can be adjusted by the Developers in collaboration with the Product Owner as new information emerges, as long as the Sprint Goal is not endangered.
- D. The Product Owner cannot unilaterally change the Sprint Backlog once the Sprint begins.
Sprint Backlog Adaptability
The Sprint Backlog is a highly visible, real-time picture of the work that the Developers plan to accomplish during the Sprint, and can be adjusted by the Developers in collaboration with the Product Owner as new information emerges, as long as the Sprint Goal is not endangered.
- The Sprint Backlog is owned by the Developers.
- Changes to the Sprint Backlog during a Sprint require collaboration.
- The Sprint Goal should not be endangered by changes.
Memory trick: Sprint Backlog isn't set in stone, but changing it is a team sport.