Professional Scrum Master I (PSM I)Scrum FrameworkMedium
A Scrum Team has just completed their Sprint Planning. They have a clear Sprint Goal and a well-defined Sprint Backlog. Midway through the Sprint, a critical, high-priority bug is discovered in the existing production system, which significantly impacts users. What is the most appropriate action for the Developers to take regarding their Sprint Backlog?
- AImmediately stop all current work, address the bug, and then return to the original Sprint Backlog.
- BIgnore the bug and continue working on the planned Sprint Backlog items to meet the Sprint Goal.
- CAdd the bug to the Product Backlog for consideration in a future Sprint by the Product Owner.
- DCollaborate with the Product Owner to determine if the bug should be added to the Sprint Backlog and how it impacts the Sprint Goal.
Show answer & explanationAnswer & explanation
Correct answer: D. Collaborate with the Product Owner to determine if the bug should be added to the Sprint Backlog and how it impacts the Sprint Goal.
The Sprint Backlog is flexible and can be re-negotiated with the Product Owner. While the Sprint Goal should not be endangered, critical issues may necessitate adapting the Sprint Backlog. Collaboration with the Product Owner ensures alignment on priorities and impact.
Why the other options are wrong
- A. Stopping all work without Product Owner consultation might jeopardize the Sprint Goal and is not a collaborative approach to managing changes.
- B. Ignoring a critical production bug is irresponsible and violates the principle of delivering value and responding to change.
- C. Adding a critical, high-priority production bug to the Product Backlog for a future Sprint is inappropriate given its immediate impact on users.
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 to achieve the Sprint Goal. It can be adjusted by the Developers in collaboration with the Product Owner.
- Owned by the Developers.
- Reflects the work for the Sprint Goal.
- Flexible; can be re-negotiated with Product Owner.
Memory trick: Critical Bug? Collaborate, Adapt, Re-align.