# Sprint Backlog

The Sprint Goal, selected Product Backlog Items, and actionable delivery plan maintained by Developers during a Sprint.

- Type: artifact
- Domain: Delivery & agility
- Level: Foundational
- Last reviewed: 2026-09-24
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/sprint-backlog/>)

## What it means

A Sprint Backlog is the Scrum artifact that combines why the Sprint matters through the Sprint Goal, what the team selected through Product Backlog Items, and how Developers currently plan to create the Increment. It is a real-time plan by and for the Developers, not a frozen assignment list.

## Why it matters

It gives the team a shared, inspectable picture of its immediate objective and plan. Because the plan can change while the goal remains stable, the team can respond to new technical information without losing focus.

## When to use it

Create it during Sprint Planning and adapt it throughout a Scrum Sprint. Do not use it as a manager-owned contract or copy it into parallel plans; teams outside Scrum may use other short-horizon planning artifacts.

## How it works

1. Agree on a Sprint Goal that advances the Product Goal.
2. Select Product Backlog Items that form a credible forecast for the Sprint.
3. Create an actionable plan for producing a usable Increment.
4. Inspect progress toward the Sprint Goal during the Sprint.
5. Update the plan and negotiate scope with the Product Owner without endangering the goal.

## A practical example

A subscription team sets a Sprint Goal to let customers recover failed payments. Developers select related backlog items and outline implementation and testing work. When an API constraint appears, they change the plan and narrow one item while preserving the recovery outcome.

## Where it breaks

The Sprint Backlog is a forecast under uncertainty, not a guarantee. It can obscure outcomes when reduced to task completion, and too much decomposition adds maintenance. It also does not replace product strategy or longer-horizon ordering.

## Common mistakes

- Freezing the Sprint Backlog even when the team learns something important.
- Letting managers assign and update the Developers’ plan.
- Listing tasks without a coherent Sprint Goal.
- Treating selected items as an unconditional scope commitment.

## Sources

1. [The 2020 Scrum Guide](<https://scrumguides.org/scrum-guide.html>) — Scrum Guides · Official framework guide
2. [Scrum Guide Revisions](<https://scrumguides.org/revisions.html>) — Scrum Guides · Official framework history

## Related topics

- [Sprint Planning](<https://wiki.soroush.uk/topic/sprint-planning/>)
- [Product Backlog](<https://wiki.soroush.uk/topic/product-backlog/>)
- [Definition of Done](<https://wiki.soroush.uk/topic/definition-of-done/>)
