Backlog Refinement
What is Backlog Refinement?
Backlog refinement, once called backlog grooming, is the recurring work of clarifying, splitting, estimating and reordering upcoming backlog items so the top of the backlog is ready for sprint planning.
Updated November 2026 · 3 min read
Backlog refinement is the ongoing work of keeping a product backlog ready for planning: clarifying upcoming items, splitting large ones, adding acceptance criteria, estimating size and reordering based on new information. It ensures that when a team sits down to plan its next sprint, the top of the backlog holds small, well-understood items it can commit to. It used to be called backlog grooming, and many teams still use that name.
In Scrum, refinement is an ongoing activity rather than a formal event. The 2020 Scrum Guide describes it as breaking down and further defining backlog items into smaller, more precise items, with the Developers responsible for sizing. Earlier editions suggested refinement usually takes no more than 10% of the team's capacity, a guideline many teams still use.
Refinement is not the same as sprint planning. Refinement prepares and sizes items ahead of time; sprint planning is the formal event where the team selects ready items and commits to a sprint goal.
What happens during refinement
- Clarifying. The product owner explains the problem and the value; the team asks questions until the need is clear.
- Splitting. Large items are broken into thin slices that each deliver something usable. See story splitting.
- Defining acceptance criteria. The team agrees how it will know each item is done. See acceptance criteria.
- Estimating. Developers size items, often with story points and planning poker.
- Spotting risks and dependencies. Unknowns may lead to a spike; dependencies on other teams get flagged early.
- Reordering and pruning. The product owner adjusts order and removes items that no longer matter.
Who attends backlog refinement
| Person | Role in refinement |
|---|---|
| Product owner | Brings the items, explains value and context, owns the final order |
| Developers | Ask questions, propose splits and approaches, estimate size |
| Scrum Master or facilitator | Keeps the session focused and time-boxed, if needed |
| Subject experts | Join for specific items, such as a designer, analyst or customer-facing colleague |
How to run a refinement session
- Prepare. The product owner selects the items likely to be needed in the next two sprints and adds what is already known.
- Time-box. Hold one or two sessions a week of about an hour, rather than one long session per sprint.
- Work top down. Start with the highest-priority items and stop when time runs out.
- Check against the definition of ready. Use the team's definition of ready to decide whether each item is plan-ready.
- Capture follow-ups. Record open questions with an owner, so items are ready by the next session.
- Keep the backlog short at the top. Aim for about two sprints of ready work. More tends to go stale.
Backlog refinement example
Consider a hypothetical team with a velocity of about 30 story points per two-week sprint, and a backlog of 140 items. At sprint planning, it often discovers that top items are too vague, and planning runs to three hours.
The team starts two 50-minute refinement sessions a week, about 3 hours and 20 minutes per sprint for each person. With a team of six working roughly 70 hours each per sprint, that is under 5% of capacity. The goal is to keep about 60 points, two sprints' worth, ready at all times. The product owner also archives 55 items that have not been touched in a year, leaving 85. After three sprints, sprint planning takes about an hour, and the number of items carried over unfinished drops because fewer surprises surface mid-sprint.
Common pitfalls
- Refining too far ahead. Detailed stories for work months away get rewritten when the context changes.
- The product owner refining alone. Items arrive at planning without the team's understanding, which is the main output of refinement.
- Skipping refinement under pressure. The time is saved once and lost several times over in planning and mid-sprint confusion.
- An endless backlog. Hundreds of items cannot be meaningfully ordered. Archive what will realistically never be built.
- Estimating without understanding. A number agreed before the team understands the item is a guess with false precision.
Backlog refinement keeps the product backlog healthy, feeds sprint planning and is usually led by the agile product owner.
Frequently asked questions
What is the difference between backlog refinement and sprint planning?
Backlog refinement is ongoing preparation: clarifying, splitting, estimating and ordering items ahead of time. Sprint planning is the formal Scrum event where the team picks ready items from the top of the backlog and commits to a sprint goal. Good refinement shortens planning, because the items arriving there are already small and understood by the team.
How much time should a team spend on backlog refinement?
Earlier editions of the Scrum Guide suggested refinement usually takes no more than 10% of a team's capacity, and many teams still use that guideline. A common pattern is one or two sessions a week of about an hour, rather than one long session per sprint, with the aim of keeping roughly two sprints of ready work at the top of the backlog.
Who should be in a backlog refinement session?
The product owner brings the items, explains value and context and owns the final order. Developers ask questions, propose splits and approaches, and estimate size. A Scrum Master or facilitator may keep the session focused and time-boxed, and subject experts such as a designer, analyst or customer-facing colleague join for specific items.
Is backlog grooming the same as backlog refinement?
Yes. Backlog grooming is the older name for backlog refinement, and many teams still use it. Both describe the recurring work of clarifying, splitting, estimating and reordering upcoming items. In Scrum it is an ongoing activity rather than a formal event, and the 2020 Scrum Guide gives Developers responsibility for sizing the items.
Related terms
Story Points
A relative measure of the size of work, used instead of hours.
Planning Poker
A card-based team game for estimating backlog items without anchoring.
Agile Spike
Short, time-boxed research to resolve an unknown before building.
Sprint Planning
The meeting that starts each Sprint by setting a goal and a plan.