How often should backlog refinement happen?

Most teams benefit from one or two refinement sessions per sprint. A common pattern for a two-week sprint is a one-hour session in the middle of the sprint. Some teams prefer shorter, more frequent sessions (30 minutes twice a week). The key is consistency and ensuring items are ready before sprint planning.

Who should attend backlog refinement?

The product owner and development team should attend. The Scrum Master facilitates. Subject matter experts may be invited when specific domain knowledge is needed. Stakeholders generally do not attend refinement but may attend sprint reviews to provide feedback on completed work.

What is a "definition of ready"?

A definition of ready is a team agreement on the criteria a backlog item must meet before it can be brought into a sprint. Common criteria include: user story format is complete, acceptance criteria are defined, dependencies are identified, the item is estimated, and the team understands the item well enough to start work. It complements the definition of done.

Book Free Assessment Calculator

Backlog Refinement

Also known as:backlog groomingstory refinementproduct backlog grooming

The ongoing process of reviewing, clarifying, estimating, and prioritising items in the product backlog to ensure they are ready for selection in upcoming sprints.

In-Depth Explanation

Backlog refinement (formerly called grooming) is the collaborative activity where the product owner and development team review upcoming backlog items to ensure they are well-understood, appropriately detailed, and ready for development.

Refinement activities:

Clarification: Discussing items to ensure shared understanding
Decomposition: Breaking large items (epics) into smaller, deliverable stories
Estimation: Assigning relative size estimates (story points, t-shirt sizes)
Acceptance criteria: Defining clear conditions for completion
Prioritisation: Adjusting the order based on new information
Dependency identification: Recognising and managing inter-item dependencies
Removal: Deleting items that are no longer relevant

Refinement best practices:

Schedule regular sessions (typically once or twice per sprint)
Spend approximately 5-10% of team capacity on refinement
Focus on items 2-3 sprints ahead (not too far into the future)
Include the whole team (not just the product owner)
Use "definition of ready" as a checklist for sufficient detail
Keep sessions time-boxed (typically 1-2 hours)

Definition of ready checklist:

User story follows the "As a..., I want..., So that..." format
Acceptance criteria are defined and testable
Dependencies are identified
The story is estimated
The story is small enough to complete in a single sprint
The team understands the story well enough to start work

Refinement anti-patterns:

Refining items too far in advance (wasted effort on items that may never be built)
Product owner refining alone without team input
Not refining enough (leading to sprint planning delays)
Treating refinement as a design session rather than a clarification session

Business Context

Effective backlog refinement reduces sprint planning time, prevents mid-sprint surprises, and ensures the team always has a pipeline of well-defined work ready to start.

How Clever Ops Uses This

Clever Ops conducts regular backlog refinement sessions for all client projects, ensuring upcoming work is well-defined and understood before sprints begin. We help Australian businesses adopt this practice to improve their sprint predictability and delivery quality.

Example Use Case

"A team holds a weekly one-hour refinement session where they review the top 5 backlog items for the next sprint, splitting large stories, writing acceptance criteria, and estimating effort."