What is a product backlog and what does backlog refinement mean?

Question

Accepted Answer

A **product backlog** is the single, prioritized list of everything that might be built for a product — features, fixes, improvements, and technical work. It's ordered by priority, so the most important items sit at the top. The backlog is the team's source of truth for *what comes next*.

## What a backlog contains

```text
TOP    → well-defined, ready to work on soon (small, clear, estimated)
MIDDLE → roughly defined, needs more detail before starting
BOTTOM → vague ideas and "maybe someday" items (low detail is fine)
```

Detail decreases as you go down. It's wasteful to fully specify items you may never build.

## Backlog refinement (grooming)

**Refinement** is the ongoing activity of keeping the backlog healthy: clarifying items, adding acceptance criteria, splitting big items, estimating, and re-prioritizing.

```text
✓ Add detail to items nearing the top
✓ Split stories too large to finish in a sprint
✓ Re-order as priorities change
✓ Remove stale items that no longer matter
```

## Why it matters

A messy backlog causes wasted time in planning, vague work that stalls mid-sprint, and arguments about what to do next.

Regular refinement means the top of the backlog is always *ready* — clear enough to start immediately — so the team can plan quickly and deliver smoothly.

The backlog itself is just a list; the discipline of keeping it ordered and clear is what makes it useful.