Sprintbacklog

The sprint backlog is a Scrum artifact that contains the set of Product Backlog items selected for a sprint, together with a plan for delivering the product Increment and achieving the Sprint Goal. It is owned by the Scrum Team’s Developers and serves as the team’s forecast for the sprint.

During Sprint Planning, the team selects PBIs from the Product Backlog that will help meet the Sprint Goal and creates the Sprint Backlog. The backlog typically includes the Sprint Goal, the selected PBIs, and a detailed plan consisting of tasks, task estimates, and the ordering of work. The plan is refined as more is learned about the work.

Throughout the sprint, the Sprint Backlog evolves. The Development Team updates it during daily work, especially at the Daily Scrum, to reflect the 24-hour forecast. Tasks may be added, split, or re-estimated as needed, but the sprint remains constrained by the selected PBIs and the Sprint Goal.

Relation to the product backlog: the sprint backlog is a subset of the Product Backlog items selected for the current sprint. It acts as the team’s actionable plan for delivering the sprint increment and achieving the sprint objective, while remaining transparent to stakeholders.

Tools and visualization: teams often use a task board or digital tools (such as Jira, Trello, or Azure Boards) to track items from To Do through In Progress to Done. The sprint backlog is not a rigid to-do list; it is a living plan that adapts as work progresses to deliver a coherent increment.