A sprint planning meeting that drags on for three hours usually has the same cause: the team discovers the stories for the first time in the room. Questions that should have been asked a week earlier pop up one after another, and the estimate turns into a guess. Our sprint planning guide puts it simply: if more than 20% of the stories discussed in planning are new to the team, refinement needs work.
This article explains what backlog refinement is, what the Scrum Guide actually says about it, how to run a session step by step, and where Planning Poker estimation fits in.
What is backlog refinement?
Backlog refinement is the ongoing work of breaking down and clarifying Product Backlog items until they are small and precise enough for a team to take into a sprint. The 2020 Scrum Guide defines it as "the act of breaking down and further defining" backlog items into "smaller more precise items". The Product Owner and the Developers meet regularly, usually once or twice per sprint, to review the next items in the backlog: they clarify the need, write acceptance criteria, spot dependencies and risks, split items that are too big and estimate them, often with Planning Poker. Refinement is not one of the five official Scrum events, and the current Scrum Guide sets no fixed duration. Earlier editions suggested it should take no more than 10% of the team's capacity, a rule of thumb many teams still use. When sprint planning starts, the top of the backlog is ready, and the team spends its time deciding what to commit to rather than discovering what the stories mean.
Is backlog refinement a Scrum event?
No. Scrum has five events: the Sprint, Sprint Planning, the Daily Scrum, the Sprint Review and the Sprint Retrospective. Refinement is an ongoing activity, which the Scrum Guide describes in the section on the Product Backlog. The guide says the backlog is "refined as needed" and leaves the how and the when to the Scrum Team.
The wording has changed over time, which explains why teams use different names:
| Scrum Guide edition | What it says about refinement |
|---|---|
| 2011 | Introduces "Product Backlog grooming" |
| 2013 | Replaces "groomed" with "refined"; items that are clear and small enough for sprint planning are called "Ready" |
| 2017 | Refinement "usually consumes no more than 10% of the capacity of the Development Team" |
| 2020 | Refinement breaks items down into "smaller more precise items"; the 10% guideline is gone; items that can be Done within one sprint are "deemed ready for selection" |
"Grooming" and "refinement" mean the same thing. Most teams now say refinement.
Who attends a backlog refinement session?
- The Product Owner owns the backlog and its order. They bring the need, the business context and the answers to "why".
- The Developers bring the technical view: how the item could be built, what it touches, what could go wrong, and how big it is. Only they estimate.
- The Scrum Master often facilitates, keeps time and makes sure everyone speaks, especially in the first sessions.
- Guests when needed: a designer, a security expert or a stakeholder who knows the business rule, invited for a specific item rather than for the whole session.
Not every Developer has to attend every session. Some teams send two or three people who rotate. The risk is that the rest of the team discovers the stories in sprint planning, which is precisely what refinement is meant to avoid. If you split the group, keep the estimation vote for the whole team.
How do you run a backlog refinement session?
A one-hour session typically covers five to ten items. The steps below work for most teams.
- The Product Owner prepares. Before the session, they order the backlog and pick the items that will probably enter the next two sprints. Each one has at least a title, a short description of the need and a first draft of acceptance criteria.
- Present the need, not the solution. The PO explains who needs the item and why. The team asks questions about scope and expected behaviour. Avoid sizes and durations at this stage: a figure said too early becomes an anchor.
- Write or complete the acceptance criteria. Together, list the conditions that make the item done. Ron Jeffries called this the confirmation: the test that turns the conversation into an agreement.
- Spot dependencies and risks. Another team, an external API, a migration, a module nobody knows well. Write them down on the item.
- Split items that are too big. If an item cannot be finished within one sprint, cut it into smaller stories that each deliver something testable.
- Estimate. Each Developer votes privately, then all cards are revealed at once. If the votes diverge, the highest and lowest voters explain, and the team votes again. Our step-by-step method for estimating an agile ticket details this step.
- Record what is left open. An unanswered question goes back to the PO with an owner and a date. The item stays below the line until it is answered.
When should you estimate: in refinement or in sprint planning?
In refinement, for most teams. Estimating during refinement has three advantages:
- Sprint planning gets shorter. The team arrives with sized stories and spends planning time on the sprint goal and the plan of work.
- The PO can reorder with sizes in hand. A valuable item that turns out to be a 13 may move down, or be split first.
- Disagreements surface earlier. When two Developers reveal a 2 and a 13, the gap often points to a missing piece of information. Found a week before the sprint, it can still be clarified.
Sprint planning remains the moment to re-estimate an item when something has changed since refinement. Then the team checks the total against its sprint velocity to decide how much to take.
Planning Poker is well suited to refinement because independent votes show how often a team does not agree at first. On the sessions measured on our usage data page, only about a quarter of first votes are unanimous.
How do you know a story is ready?
The Scrum Guide does not define a "Definition of Ready". It only says that items that can be Done within one sprint are ready for selection. Many teams still write a short checklist to agree on what "ready" means for them. Bill Wake's INVEST criteria, published in 2003, are a common starting point:
| INVEST criterion | Question to ask in refinement | Typical action if the answer is no |
|---|---|---|
| Independent | Can we deliver it without waiting for another story? | Reorder, or merge the two stories |
| Negotiable | Is the solution still open to discussion? | Rewrite the item as a need, not a specification |
| Valuable | Who benefits, and how? | Ask the PO to state the user and the outcome |
| Estimable | Do we know enough to size it? | Plan a short spike, or ask the missing question |
| Small | Can it be finished within one sprint? | Split it |
| Testable | Do we know how to check that it is done? | Write the acceptance criteria |
Keep the checklist short. A Definition of Ready with fifteen items turns refinement into a gate, and stories stop moving. Roman Pichler and Mike Cohn describe a good backlog as DEEP instead: detailed appropriately, estimated, emergent and prioritized. Only the top of the backlog needs this level of detail; items further down can stay rough.
How often and how long should backlog refinement be?
There is no official answer, only habits that work.
- Frequency. Once or twice per sprint is common for two-week sprints. A short weekly session keeps the backlog moving without long meetings.
- Duration. One hour per week of sprint is a frequent starting point. The 10% guideline from the 2017 Scrum Guide gives an upper bound: about one day per Developer for a two-week sprint, spread across the sprint.
- Horizon. Aim for one to two sprints of ready items. Refining further ahead wastes effort, because priorities and knowledge change.
- Timing. Avoid the day before sprint planning. The team needs time to answer the questions refinement raised.
If refinement regularly overruns, look at the items, not the clock: they are probably too big or too vague when they reach the session.
What are the most common refinement mistakes?
- The PO arrives with a blank page. The session turns into writing the story live. Prepare the need and the first criteria beforehand.
- The PO arrives with a full specification. The team has nothing left to discuss, and misunderstandings stay hidden until development.
- Estimating out loud. "That's a 3, right?" anchors everyone. Vote privately, then reveal.
- Refining too far ahead. Twenty ready stories for a team that delivers eight per sprint means rework later.
- Never saying "not ready". An item with an open question goes back to the PO. Estimating it anyway produces a number nobody trusts.
AI assistants can help the PO prepare items before the session, by rephrasing a need or listing missing acceptance criteria. Our article on an AI-assisted Product Owner's workflows gives examples, and our guide to Planning Poker and AI explains where AI fits around the vote. Keep the estimate itself with the team, and never paste confidential tickets into an assistant your company has not approved.
Frequently asked questions
What is the difference between backlog refinement and sprint planning? Backlog refinement prepares future work: the team clarifies, splits and estimates backlog items, usually one or two sprints ahead. Sprint planning is a formal Scrum event at the start of each sprint, where the team chooses which ready items to take, sets a sprint goal and plans how to deliver it. Good refinement makes sprint planning short.
How long should backlog refinement take? Backlog refinement has no fixed duration in the current Scrum Guide. Earlier editions suggested no more than 10% of the team's capacity, which many teams still use as a ceiling. In practice, one or two sessions of about an hour per two-week sprint are common, adjusted to the size and clarity of the backlog.
Should the whole team attend backlog refinement? The whole team does not have to attend every backlog refinement session, but the people who will build and estimate the items should hear them before sprint planning. Some teams rotate two or three Developers per session. Estimation votes work best with all the Developers, so that nobody discovers a story for the first time in planning.
Is Definition of Ready part of Scrum? The Definition of Ready is not part of the Scrum Guide, which only defines a Definition of Done. Many teams still agree on a short readiness checklist, often based on the INVEST criteria, to decide when a backlog item can enter sprint planning. Keep it short so it guides the conversation instead of blocking items.
Sources
- Ken Schwaber and Jeff Sutherland, The 2020 Scrum Guide, November 2020
- Ken Schwaber and Jeff Sutherland, The Scrum Guide, November 2017 edition
- Scrum Guides, Revisions to the Scrum Guide
- Bill Wake, INVEST in Good Stories, and SMART Tasks, 2003
- Ron Jeffries, Essential XP: Card, Conversation, Confirmation, 2001
- Mountain Goat Software, Make the Product Backlog DEEP
Estimate your refined stories together
Refinement is where disagreements are cheapest to find. Create a free Planning Poker session, share the link with your team and estimate the items you just clarified: every vote stays hidden until the reveal. No sign-up required.





