During Sprint Planning for the robot's companion app, the Developers select several Product Backlog items, agree on a Sprint Goal, and sketch out how they'll deliver the work. Who is responsible for creating the resulting Sprint Backlog?
Select an answer to reveal the explanation.
Short Explanation
The Sprint Backlog isn't handed down from above; it's the Developers' own plan for their own Sprint. They pick the Product Backlog items, agree on a Sprint Goal with the Product Owner, and map out how the work will get done. Since they're the ones doing the work, they're the ones who own the plan for doing it.
Full Explanation
The Sprint Backlog is composed of the Sprint Goal, the Product Backlog items selected for the Sprint, and the Developers' plan for delivering them, and the Guide places responsibility for creating and updating it with the Developers themselves. This matters at Nestbot because the app team is closest to the technical reality of the work: they know how a feature decomposes into tasks and can commit to a plan they actually believe is achievable. The Scrum Master's role in the meeting is to help the event happen effectively, not to author the plan; treating them as the compiler reintroduces a hand-off Scrum is designed to remove. The Product Owner selecting items refers to their accountability for ordering the Product Backlog going into the conversation, but the resulting plan for how to build those items belongs to the people building them. "Whoever facilitates" wrongly ties ownership to a rotating logistics role rather than to the accountability the Guide assigns. A useful check: if the Sprint Backlog changes mid-Sprint as the Developers learn more, confirm it's the Developers updating it, not someone external re-planning on their behalf.