Backlog grooming
Definition
Backlog grooming (formally called backlog refinement) is the ongoing activity where the Product Owner and team review the product backlog to clarify requirements, update estimates, reorder priorities, and ensure upcoming items are ready for sprint planning.
"Backlog grooming" is the colloquial term; the Scrum Guide uses "product backlog refinement." Both refer to the same activity. The term "grooming" fell out of favor in some organizations due to cultural concerns, though it remains widely used in the industry.
Refinement is not a formal Scrum ceremony with a set cadence — it's an ongoing activity that happens throughout the sprint, typically consuming no more than 10% of the team's capacity. Many teams schedule a dedicated mid-sprint refinement session of 60–90 minutes.
What happens in a grooming session:
- The Product Owner presents upcoming backlog items.
- The team asks clarifying questions and surfaces ambiguities.
- Stories get sized (story points or t-shirt sizes).
- Large stories get split into smaller, sprint-sized chunks.
- Acceptance criteria get written or refined.
- Items get reordered based on new information.
The output is a "ready" backlog — items at the top are understood, estimated, and small enough to fit in a sprint. Teams that skip refinement suffer in sprint planning: half the meeting becomes clarification of items that should have been clarified a week earlier.
Many teams run grooming sessions at a whiteboard, mapping dependencies, drawing flows, and sketching UI. BoardSnap AI turns that whiteboard session into structured notes — user stories, acceptance criteria, and open questions — before the room breaks up.
Note: grooming and sprint planning are different meetings with different outputs. Grooming prepares the backlog; planning selects from it.
Examples
- Product Owner presents five upcoming stories; team splits two of them into smaller pieces and estimates the rest
- Mid-sprint refinement session reveals a dependency on a third-party API that hasn't been contracted yet
- Team re-estimates a story from 3 points to 8 after a developer explains hidden complexity
- Acceptance criteria written on a whiteboard during refinement, photographed with BoardSnap before the meeting ends
- PO reorders backlog top-to-bottom based on customer interview data from the previous week
Snap a backlog grooming. Ship its actions.
BoardSnap turns any whiteboard — including this one — into a summary and action plan.