A Scrum Team is experiencing friction because the Product Owner frequently changes the order of Product Backlog Items during a Sprint, often introducing new high-priority items. This disrupts the Developers' flow and makes it difficult to achieve the Sprint Goal. What is the Scrum Guide's guidance regarding changes to the Product Backlog during a Sprint?
- AThe Product Owner can change the Product Backlog at any time, and the Developers must adapt.
- BThe Product Backlog is frozen for the duration of the Sprint once Sprint Planning concludes.
- CThe Product Owner can re-order Product Backlog Items, but new items can only be added during Sprint Planning.
- DThe Product Backlog is actively managed by the Product Owner and refined with the Scrum Team, but the Sprint Backlog is what the Developers focus on.
Show answer & explanationAnswer & explanation
Correct answer: D. The Product Backlog is actively managed by the Product Owner and refined with the Scrum Team, but the Sprint Backlog is what the Developers focus on.
The Product Backlog is a living artifact, and the Product Owner can change its order at any time. However, the Developers work from the Sprint Backlog, which contains the selected items for the current Sprint. While the Sprint Backlog *can* be re-negotiated with the Product Owner if necessary, the Product Backlog itself is dynamically managed and refined continuously.
Why the other options are wrong
- A. While the Product Owner can change the Product Backlog, the Developers focus on the Sprint Backlog, and constant disruption of the Sprint Backlog without collaboration is problematic.
- B. The Product Backlog is never 'frozen'; it's a dynamic artifact. The Sprint Backlog is what the Developers commit to for the current Sprint.
- C. New items can be added to the Product Backlog at any time, not just Sprint Planning. Their inclusion in the Sprint Backlog is the key.
Dynamic Product Backlog
The Product Backlog is a dynamic, living artifact that is continuously managed and refined by the Product Owner and Scrum Team. Its order can change at any time, but the Sprint Backlog represents the Developers' plan for the current Sprint.
- PO manages Product Backlog.
- Dynamic, not frozen.
- Sprint Backlog is Developers' focus.
Memory trick: The Product Backlog is the dynamic 'master plan', but the Sprint Backlog is the 'current mission brief' for the Developers.