Backlog refinement
Backlog refinement is the ongoing activity in which the Product Owner and Developers add detail, estimates, and order to items in the Product backlog, breaking big items down and clarifying them so they’re ready to be pulled into a future sprint planning.
Also known as
backlog grooming · grooming · refinement · story time · “backlog refinement session” “Grooming” is the older term. It’s still widely used, though many teams switched to “refinement” because “grooming” acquired unfortunate connotations. Same activity.
Don't confuse with
Sprint planning. Refinement is continuous and prepares items ahead of time; sprint planning is one event that starts a sprint by selecting from already-refined items. If your planning meetings run long, it’s usually because refinement isn’t happening.
What “refined” means
Refinement makes items meet a team’s Definition of Ready, commonly that an item is:
- Clear: everyone understands what it means,
- Small enough: it fits comfortably inside one sprint (bigger items are split; an oversized item is an epic),
- Estimated: sized (e.g. in story points), and
- Testable: it has acceptance criteria.
Not a formal Scrum event
The Scrum Guide describes refinement as an ongoing activity, not one of the five prescribed events. Many teams still schedule a recurring refinement meeting, which is fine. Just don’t confuse the habit with the official event set.
See also
References
- K. Schwaber & J. Sutherland, The Scrum Guide (2020), “Product Backlog”. Refinement is described inside that section; it is not a separate Scrum event. https://scrumguides.org/scrum-guide.html