Scrum guide · Artifacts and practices
What Is a Sprint Backlog? Contents, Ownership and Examples
The Sprint Backlog is the Developers' plan for the Sprint. It is a highly visible, real-time picture of the work they plan to accomplish to achieve the Sprint Goal.
Key takeaways
- The Sprint Backlog contains the Sprint Goal, selected items and a plan.
- It belongs to the Developers and changes daily.
- It differs from the Product Backlog in scope, owner and lifespan.
The three parts
- Why: the Sprint Goal.
- What: the Product Backlog items selected for the Sprint.
- How: an actionable plan for delivering the Increment, often tasks.
Ownership and updates
The Sprint Backlog belongs to the Developers. It is updated throughout the Sprint as more is learned, usually at least daily. It should have enough detail that progress can be inspected in the Daily Scrum.
Sprint Backlog vs Product Backlog
| Product Backlog | Sprint Backlog | |
|---|---|---|
| Scope | Everything that might improve the product | Work for the current Sprint |
| Owner | Product Owner | Developers |
| Commitment | Product Goal | Sprint Goal |
| Changes | Re-ordered any time | Updated daily as the plan evolves |
| Lifespan | As long as the product | One Sprint |
Example
Sprint Goal: New customers can sign up and pay by card.
- Item: Sign-up form with email verification. Tasks: form UI, validation, email service, tests.
- Item: Card payment at sign-up. Tasks: payment provider integration, error handling, receipts, tests.
- Item: Welcome email. Tasks: template, trigger, tests.
Free templates for this topic
Frequently asked questions
Can the Sprint Backlog change during the Sprint?
Yes. The plan evolves as Developers learn, as long as changes don't endanger the Sprint Goal.
Who can add tasks to the Sprint Backlog?
The Developers.
What is a Sprint Backlog in Scrum?
The Developers' plan for the Sprint, made up of the Sprint Goal, the Product Backlog items selected for the Sprint and an actionable plan for delivering the Increment.
What is the difference between a Product Backlog and a Sprint Backlog?
The Product Backlog lists everything that might improve the product and belongs to the Product Owner. The Sprint Backlog covers only the current Sprint and belongs to the Developers. See Product Backlog.
When is the Sprint Backlog created?
During Sprint Planning. It is then updated throughout the Sprint as the Developers learn more.
Can the Product Owner change the Sprint Backlog?
The Sprint Backlog belongs to the Developers. The Product Owner can clarify and renegotiate scope with them, but should not make changes that endanger the Sprint Goal.
What happens to the Sprint Backlog at the end of the Sprint?
Completed items form part of the Increment. Unfinished items return to the Product Backlog to be re-ordered, and a new Sprint Backlog is created at the next Sprint Planning.
Should the Sprint Backlog include tasks?
Many teams break items into tasks of a day or less so progress is easy to inspect. The Scrum Guide only requires an actionable plan, not a specific format.
Can improvement actions go in the Sprint Backlog?
Yes. The Scrum Guide says the most impactful improvements from the Retrospective may be added to the Sprint Backlog for the next Sprint.
How do you track progress on the Sprint Backlog?
Most teams use a Scrum board updated at least daily, and some add a Sprint burndown chart.
What is the commitment for the Sprint Backlog?
The Sprint Goal. It is the single objective for the Sprint and gives the Developers flexibility over the exact work needed to achieve it.