The Sprint Backlog and the Sprint Goal

The Sprint Backlog is composed of the Sprint Goal (why), the set of Product Backlog items selected for the Sprint (what), and an actionable plan for delivering the Increment (how). It is a plan by and for the Developers: a highly visible, real-time picture of the work they plan to accomplish during the Sprint in order to achieve the Sprint Goal. The Sprint Backlog is updated throughout the Sprint as more is learned, and it should have enough detail that the Developers can inspect their progress in the Daily Scrum.

The commitment for the Sprint Backlog is the Sprint Goal: the single objective for the Sprint. Although the Sprint Goal is a commitment by the Developers, it provides flexibility in terms of the exact work needed to achieve it. It also creates coherence and focus, encouraging the Scrum Team to work together rather than on separate initiatives. The Sprint Goal is created during Sprint Planning and then added to the Sprint Backlog, and the Developers keep it in mind as they work.

If the work turns out to be different than they expected, the Developers collaborate with the Product Owner to negotiate the scope of the Sprint Backlog within the Sprint — without affecting the Sprint Goal.

Study focus: the Sprint Goal stays fixed during the Sprint; the selected items and the plan can change. Only the Developers update the Sprint Backlog. If the Sprint Goal itself becomes obsolete, the Product Owner may cancel the Sprint.