Backlog refinement
Definition
Backlog refinement is the ongoing Scrum activity in which the Product Owner and development team collaboratively review the product backlog — clarifying requirements, adding detail, updating estimates, and ordering items so the top of the backlog is always sprint-ready.
The Scrum Guide treats backlog refinement as a continuous activity rather than a formal ceremony, though teams typically schedule dedicated sessions once or twice per sprint. The guideline: refinement should consume no more than 10% of the development team's capacity per sprint.
Why it matters: Sprint planning is time-boxed and fast. If items at the top of the backlog arrive at planning with vague descriptions, no acceptance criteria, and unknown size, the team burns planning time on clarification instead of commitment. Refinement fixes this upstream.
What good refinement produces:
- User stories with clear acceptance criteria
- Stories sized small enough to complete within a sprint
- Dependencies identified and flagged
- Open questions answered before planning
- A rough ordering of the next two to three sprints' worth of work
Definition of Ready is the companion concept — a checklist a story must pass before it's eligible for sprint planning. Refinement is how stories reach "ready."
Refinement is collaborative. Engineers surface technical constraints the Product Owner doesn't see. The Product Owner re-explains business context that changes how engineers approach the work. When run well, it's one of the highest-ROI meetings in the sprint cycle.
Physical whiteboard sessions are common in refinement — story maps, flow diagrams, dependency trees. BoardSnap AI reads these boards and exports the structure as action items, saving time on transcribing what was sketched.
Also called: backlog grooming (older term, still widely used).
Examples
- Weekly 90-minute refinement session where the team sizes ten stories and splits three oversized ones
- Engineer draws a data flow diagram on the whiteboard to explain why a 'simple' feature is actually 13 points
- PO writes acceptance criteria live on the whiteboard while the team asks edge-case questions
- Team discovers that two high-priority stories share a backend dependency and reorders them
- Three-amigos refinement: PO, developer, and QA review each story together to catch gaps early
Snap a backlog refinement. Ship its actions.
BoardSnap turns any whiteboard — including this one — into a summary and action plan.