Backlog refinement
Backlog refinement (sometimes called grooming) is the recurring practice of clarifying, splitting, estimating, and prioritising stories before they enter a sprint. A well-refined backlog has its top 2-3 sprints' worth of stories crisp enough that planning becomes mechanical — capacity in, stories out. Without refinement, sprint planning sessions turn into design conversations.
Most teams reserve 1-2 hours per sprint for refinement, usually mid-sprint when the next sprint's contents are starting to firm up. Activities include: clarifying acceptance criteria, splitting oversized stories, identifying dependencies, dropping items that no longer matter, and re-prioritising in light of new information. Healthy refinement keeps the top of the backlog 'ready' (clear, sized, dependencies known); the bottom can stay rougher.
Long-form posts that explore backlog refinement in depth — when to use it, common failure modes, how AI helps.
Related terms
- Definition of ready
Definition of Ready is the team's explicit checklist that a story must pass before it can enter a sprint.
- Story splitting
Story splitting is the practice of breaking a large user story into smaller stories that each independently deliver value.
- Capacity planning
Capacity planning is the practice of estimating how much work a team can realistically take on in a sprint, accounting for PTO, meetings, on-call duty, and other non-coding time.