Sprint Backlog
Purpose
The Sprint Backlog is the Development Team's plan for the Sprint. The Sprint Backlog is created during the Sprint Planning event which is the first event in a Sprint.
Composition
The Sprint Backlog consists of the following:
- A number of items selected from the top of the Product Backlog by the Development Team
- A detailed plan for delivery of the items and realization of the Sprint Goal during the Sprint (tasks)
Changes in the Sprint Backlog
The Sprint Backlog items do not change after the Sprint Planning and the Development Team will focus on delivering an Increment of “Done” based on this plan. However, it is necessary to get more information, justify, or clear some of the items during the Sprint, which should be done in the presence of the Product Owner. The detailed plan (tasks) which is not complete at the end of the Sprint Planning, will continue to be updated as the Sprint continues. So, in general, some parts of the Sprint Backlog do not change during the Sprint, and the others do.
Scaling
In scaled Scrum, each team has its own Sprint Backlog.
External Resources
- Scrum Guide, a definition of the Scrum framework by Ken Schwaber and Jeff Sutherland
- Nexus Guide, a framework for scaling Scrum by Ken Schwaber et al.
- The Scrum Master Training Manual, a free ebook on Scrum, and the Professional Scrum Master™ (PSM™ I) exam
- Scrum Awareness, a free email course on Scrum framework