Refinement is the ongoing process of preparing backlog items so the team can actually work on them without constant interruption. It's not a formal Scrum event — but the Scrum Guide acknowledges it as necessary work, and teams that skip it pay for it in broken sprints.
"Backlog Refinement is a technique that can include Story Decomposition and Story Elaboration along with prioritization and sequencing." — IIBA Agile Extension
The outcome of refinement is a common understanding of what is required to deliver a backlog item. Not a perfect specification — a shared understanding.
In practice, refinement includes:
- Clarifying what the story is actually asking for
- Splitting large items into something a sprint can absorb
- Writing or reviewing acceptance criteria
- Estimating effort
- Surfacing dependencies before they become surprises in Sprint Planning
The key people in a refinement session: the PO owns the what and why, developers own the how and how much. Neither should dominate. The best refinement sessions feel like a conversation, not a presentation.
On the LPT project I introduced regular grooming sessions — before that, the team was trying to estimate and clarify stories during Sprint Planning itself, which burned half the planning meeting just getting everyone on the same page. Moving that work earlier changed the quality of every sprint.
Refinement is complete when there's sufficient information for the team to execute — not more, not less. Over-refining is waste.
Exam tip: The Scrum Guide says refinement consumes no more than 10% of the Developers' capacity per sprint. This number appears directly in PSPO and PSM exam questions.