Sprint backlog
Definition
The sprint backlog is the subset of product backlog items the team has committed to delivering in the current sprint, together with the tasks and sub-tasks the team created during sprint planning to accomplish that work.
The sprint backlog is one of three formal Scrum artifacts, alongside the product backlog and the product increment. It belongs to the development team — not the Product Owner. Only developers can add tasks to it, change estimates on it, or update its status during the sprint.
How the sprint backlog forms: At sprint planning, the team selects items from the top of the product backlog that they're confident they can complete in the sprint. They then decompose each item into concrete tasks — the sprint backlog is the resulting combination of user stories plus their tasks.
How it changes during the sprint: The sprint backlog is a living document. New tasks get added as the team learns more about how to do the work. Estimates get updated. In exceptional cases, the team may remove tasks that prove unnecessary. But the sprint goal — the reason the sprint exists — should remain stable unless the scope changes in a fundamental way.
Sprint backlog vs. product backlog:
- Product backlog: everything the team might ever do, owned by the Product Owner.
- Sprint backlog: what the team is doing right now, owned by the developers.
Most teams track the sprint backlog in Jira, Linear, or a physical task board. The physical task board remains popular because it makes work-in-progress visible at a glance — teams see exactly what's moving and what's stuck. A well-run daily standup walks the sprint backlog task by task. BoardSnap AI captures the board when mid-sprint scope changes require a redraw.
Examples
- Sprint backlog of 12 user stories broken into 47 individual tasks, tracked on a physical Kanban board
- Team adds three new tasks mid-sprint after discovering an undocumented API edge case
- Burndown chart derived from sprint backlog showing the team is on track to finish two days early
- Engineer updates a task estimate from 4 hours to 8 hours after hitting unexpected complexity
- Scrum Master removes a task from the sprint backlog after confirming it's already handled by another story
Snap a sprint backlog. Ship its actions.
BoardSnap turns any whiteboard — including this one — into a summary and action plan.