What is the difference between the Product Backlog and the Sprint Backlog?

Question

Accepted Answer

Both are Scrum artifacts that hold work, but at different scopes. The **Product Backlog is the single, ordered list of everything that might be done to the product**. The **Sprint Backlog is the subset the team commits to for the current Sprint**, plus the plan to deliver it.

## Side by side

| Aspect | Product Backlog | Sprint Backlog |
|--------|-----------------|----------------|
| Scope | The whole product, long-lived | One Sprint only |
| Owner | Product Owner | The Developers |
| Contents | All future ideas, ordered | Selected items + Sprint Goal + plan |
| Changes | Continuously refined | Stable toward the Sprint Goal |

## Concrete example

The Product Backlog has 80 items for the next year. During Planning the team pulls the top 8 that fit the Sprint Goal "users can manage their profile" — those 8 plus their tasks become the Sprint Backlog.

## Common pitfalls

- Letting anyone reorder the Product Backlog instead of the Product Owner.
- Treating the Sprint Backlog as fixed task assignments rather than a shared, adjustable plan.
- A Product Backlog that is a dumping ground with no ordering.

## Why it matters

Separating the long-term wishlist from the current commitment keeps the team focused on a small, achievable scope.

Clear ownership — Product Owner for the Product Backlog, Developers for the Sprint Backlog — prevents priority and planning conflicts.

Scope	The whole product, long-lived	One Sprint only
Owner	Product Owner	The Developers
Contents	All future ideas, ordered	Selected items + Sprint Goal + plan
Changes	Continuously refined	Stable toward the Sprint Goal