Introduction to the Sprint Backlog
The Sprint Backlog represents what the Developers plan to accomplish during the Sprint.
The Sprint Backlog is created by the Developers during the Sprint Planning Event. It describes the why, what and how of the Sprint. It consists of:
- The Sprint Goal which describes the objective for the Sprint.
Why are we doing this Sprint?
- A set of Product Backlog items (PBIs) selected for the Sprint.
Which PBIs will be addressed in this Sprint?
- An actionable plan for how the team will deliver the work and achieve the Sprint Goal.
How will we achieve our Sprint Goal?
Sprint Backlogs are highly-visible and located where anyone on the Scrum Team can see them. They are also continually updated throughout the Sprint to provide a real-time picture of the work the Developers plan to accomplish.
The selected set of PBIs and the plan to achieve them evolve over the course of the Sprint, often during the Daily Scrum. In contrast, the Sprint Goal remains the same for the entire Sprint. In rare circumstances, information is uncovered that makes the Sprint Goal obsolete. In this case, the Product Owner may decide to cancel the Sprint.
Resources: