The Right Way to Do Backlog Refinement (and What to Avoid)

Published on 21 May 2025 by Arjan Franzen
If you’ve ever found yourself thinking, “I sit through 90% of backlog refinement waiting for something relevant to me,” you’re not alone — but you’re also not doing refinement right.

How not to refine
Backlog refinement should never feel like a marathon meeting where only one or two people talk and the rest silently zone out. It’s not about working through the entire backlog or listening to a two-hour monologue. Instead, refinement is about creating a shared understanding of the right work, with the right people, in an engaged and collaborative way.
What Not to Do
❌ Don’t treat refinement as a status update.
❌ Don’t invite the entire team if only a few people are involved.
❌ Don’t go through the backlog item by item “just in case.”
❌ Don’t let the meeting drag on without timeboxing.
What to Do Instead
Great refinement sessions are:
-
Prepared: The Product Owner (PO) comes in with selected, prioritised items.
-
Focused: You go through one item at a time — no scattershot discussions.
-
Time-boxed: Set a 10-minute timer per item to keep momentum.
-
Collaborative: Everyone contributes. If nobody speaks, nobody learns.
-
Clarifying: For each item, you clarify:
✅ Why are we doing this?
✅ What needs to happen?
✅ How might we build it?
✅ How big is it?
The Result
When done right, refinement sessions are energising, not exhausting. They create clarity, spark good questions, and move the team forward with confidence.
Done wrong? You’re just wasting everyone’s time.
Refinement is a tool, not a chore. Use it well — and your team will feel the difference.
Supercharge your Software Delivery!
Implement DevOps with Agile Analytics
Implement Site Reliability with Agile Analytics
Implement Service Level Objectives with Agile Analytics
Implement DORA Metrics with Agile Analytics