EXECUTION & METHODOLOGIES · LESSON 03.06beginner

Backlog refinement.

Keep the top of the backlog ready, the bottom rough.

↳ tl;dr

Backlog refinement (sometimes called grooming) is the ongoing practice of breaking down, clarifying, and ordering Product Backlog items so they're ready for sprint planning. Top items: ready to estimate. Middle: roughly understood. Bottom: rough placeholders.

Why a refined top matters

Sprint planning is fast when the top of the backlog is ready — slow when it isn't. Refinement is the work that makes planning fast. The Scrum Guide doesn't prescribe a ceremony for it (it's a continuous activity), but most teams hold a 30–60 min refinement session weekly.

Definition of Ready

Many teams adopt a Definition of Ready: criteria a backlog item must meet before it can enter a sprint. Common DoR: clear acceptance criteria, agreed estimate, dependencies known, designs (if needed) attached, no open clarifying questions.

↳ the over-refinement trap

Don't refine items deep in the backlog into perfect detail. They'll change before they're ever pulled. Refine just-enough, just-in-time. The top 1–2 sprints worth should meet DoR; anything deeper, rough is fine.

Splitting large items

A 13-point story is a warning sign. Split it. Common splits: by acceptance criteria (the AND in "must do A AND B" is usually a seam), by user (admin path vs user path), by happy path vs edge cases (ship the happy path first, add edge cases later). The split should preserve user-facing value at each step.

// sources

Sources cited