A backlog refinement meeting is a collaborative session for adding detail, estimates, and order to upcoming Product Backlog items. Teams clarify features, identify examples and acceptance criteria, split larger features into smaller features or User Stories, and prepare work for implementation and planning. section 5.1
A practical refinement session typically moves from shared understanding toward delivery readiness:
- Review high-level features or Epics that emerged from strategic discovery. section 4.1 section 5.1
- Discuss the feature’s purpose, examples, acceptance criteria, and unresolved assumptions. section 5.0 section 5.1
- Break larger features into smaller features or User Stories that are easier to discuss, estimate, and deliver. section 5.0 section 5.1
- Estimate items at a high level, order them in the Product Backlog, and define upcoming release or iteration goals. section 5.1
From feature to ready backlog items
A high-level feature identified through Impact Mapping or a Pirate Canvas is discussed, divided into User Stories, given examples and acceptance criteria, estimated, and ordered so a team can pick it up during an upcoming sprint or release. section 5.0 section 5.1
Refinement is ongoing rather than a single planning event. Teams may meet weekly, meet shortly before a sprint ends, or prepare requirements in smaller groups between sessions. section 5.1
