Product Backlog Refinement: A Field Checklist for Scrum Teams

Product Backlog Refinement (sometimes called backlog grooming) is the ongoing activity of the Scrum Team -- the Product Owner, the Development Team, and the Scrum Master -- in which the Product Backlog is reviewed, ordered, detailed, and estimated. The Scrum Guide states that the Development Team should spend no more than 10% of Sprint capacity on refinement. Refinement is not a formal Sprint event, but it is a critical ongoing activity that determines the quality of Sprint Planning.

Checklist Part 1: Is the Backlog Item Ready for Refinement?

• The item has a user story or task description that clearly articulates what is being built, for whom, and why.

• The acceptance criteria are documented. If acceptance criteria are not yet written, refinement begins by writing them -- not by estimating.

• The item is understood well enough that the team can ask meaningful questions about it. An item that generates no questions in refinement is either perfectly clear or not yet understood well enough to be refined.

Checklist Part 2: Refinement Session Quality

1. Refine the top of the backlog, not everything. Refinement should focus on the items most likely to be pulled into the next one to three Sprints. Items further down the backlog will change before they are worked on; refining them in detail now is waste.

2. Break down items that are too large. Items that cannot be completed within a single Sprint must be broken down. Epics should be broken into stories. Stories that are too large should be broken into smaller stories using a slicing technique (by workflow step, by data type, by user role, by acceptance criterion).

3. Estimate using relative sizing. Story points are a measure of relative complexity, not a measure of time. When estimating, the team compares items to each other and to a calibration reference item. Do not convert story points to hours in Sprint planning -- they are not equivalent.

4. Surface and document dependencies. If a backlog item has dependencies on other backlog items, on external teams, or on decisions not yet made, document them. Dependencies that are discovered during Sprint Planning (not in refinement) create Sprint Planning disruptions.

Checklist Part 3: After Refinement

• Items that were refined and estimated but not yet ready for Sprint Planning (missing acceptance criteria, open questions, unresolved dependencies) should be flagged and returned to a pre-refinement state. Do not pull unready items into Sprint Planning.

• Items that were refined and estimated and meet the team's Definition of Ready should be in the top of the backlog, ordered by priority, and available for the next Sprint Planning session.

• The Product Owner should review the backlog ordering after each refinement session to ensure it reflects current stakeholder priorities.

XNM provides Scrum coaching and agile delivery advisory to public-sector organisations. Reach out to XNM's program & project delivery advisory team to discuss backlog management and Scrum implementation for your organisation.