The Scrum Framework — Second Edition

This chapter retains the second edition’s historical and practical teaching context. The third-edition curriculum is also available in the contents below.

---

The Sprint Backlog - Example Sprint Task Board - International Scrum Institute

The Sprint Backlog contains the selected Product Backlog items and the developers’ plan for delivering them toward the Sprint Goal. In this practical example, the team estimates tasks in person-hours to track progress and remaining effort; Scrum does not mandate that unit.

The Sprint Backlog is a living artifact, updated throughout the Sprint. In this example, team members record their names when they begin an activity, add newly discovered tasks, and update remaining effort at the end of each day. These updates make the remaining work visible. The Definition of Done determines whether completed work meets the required quality standard.

The Sprint Backlog can be kept electronically in, for example, a spreadsheet or with cards on a task board. The latter has some advantages (e.g. transparency and easy access) but can add complexity if the Scrum Team is distributed over multiple sites. The figure below shows an example of how such a task board could be organized. The structure should be adapted to reflect the needs of the project.