Sprint Backlog Refinement | Grooming Best Practices
Conduct effective backlog refinement sessions with Definition of Ready, story sizing, and team estimation. GitScrum tracks ready items and health metrics.
6 min read
Refinement Goals
| Goal | Indicator | Benefit |
|---|---|---|
| Ready for sprint | Meets DoR | Faster planning |
| Well-estimated | Team consensus | Predictable velocity |
| Right-sized | 1-3 day tasks | Manageable work |
| Prioritized | Stack-ranked | Clear focus |
| Understood | Questions answered | Less mid-sprint confusion |
Refinement Process
BACKLOG REFINEMENT WORKFLOW
BEFORE SESSION (Product Owner + Tech Lead):
┌─────────────────────────────────────────────────┐
│ 1. Review incoming requests │
│ 2. Draft user stories with acceptance criteria │
│ 3. Identify items needing technical input │
│ 4. Pre-prioritize items to discuss │
│ 5. Flag items with dependencies or risks │
│ │
│ Time: 1-2 hours before weekly session │
└─────────────────────────────────────────────────┘
│
▼
REFINEMENT SESSION (Full Team):
┌─────────────────────────────────────────────────┐
│ Duration: 1 hour per week │
│ │
│ Agenda: │
│ 1. Review new items (15 min) │
│ └── PO presents, team asks questions │
│ │
│ 2. Clarify existing items (20 min) │
│ └── Answer open questions, update stories │
│ │
│ 3. Estimate ready items (20 min) │
│ └── Planning poker or similar │
│ │
│ 4. Identify risks/dependencies (5 min) │
│ └── Flag for follow-up │
└─────────────────────────────────────────────────┘
│
▼
AFTER SESSION (Ongoing):
┌─────────────────────────────────────────────────┐
│ 1. Update stories with clarifications │
│ 2. Research flagged technical questions │
│ 3. Resolve dependencies │
│ 4. Split stories if too large │
│ 5. Keep backlog prioritized │
└─────────────────────────────────────────────────┘
Definition of Ready
DEFINITION OF READY (DoR)
BEFORE ENTERING SPRINT, ITEM MUST HAVE:
CLARITY:
☐ User story follows format (As a... I want... So that...)
☐ Acceptance criteria are specific and testable
☐ UI designs attached (if applicable)
☐ Technical approach understood
SIZE:
☐ Estimated by team
☐ Can be completed in 1-3 days
☐ If larger, broken into sub-tasks
DEPENDENCIES:
☐ No blocking dependencies, OR
☐ Dependencies scheduled to complete first
☐ External dependencies have timeline
PRIORITY:
☐ Product Owner has prioritized
☐ Stakeholder alignment confirmed
TESTABILITY:
☐ Test scenarios identified
☐ Edge cases documented
Story Sizing Guidelines
STORY SIZING REFERENCE
1 POINT - Trivial
┌─────────────────────────────────────────────────┐
│ • Configuration change │
│ • Text update │
│ • Simple bug fix with known cause │
│ Time: < 4 hours │
└─────────────────────────────────────────────────┘
2 POINTS - Small
┌─────────────────────────────────────────────────┐
│ • Add field to existing form │
│ • Simple API endpoint │
│ • Basic UI component │
│ Time: 4-8 hours (half day to full day) │
└─────────────────────────────────────────────────┘
3 POINTS - Medium
┌─────────────────────────────────────────────────┐
│ • New feature with known pattern │
│ • Moderate complexity │
│ • Some testing/edge cases │
│ Time: 1-2 days │
└─────────────────────────────────────────────────┘
5 POINTS - Large
┌─────────────────────────────────────────────────┐
│ • New feature with some unknowns │
│ • Multiple components involved │
│ • Integration with external system │
│ Time: 2-3 days │
│ Consider: Can this be split? │
└─────────────────────────────────────────────────┘
8 POINTS - Very Large
┌─────────────────────────────────────────────────┐
│ • Complex feature │
│ • Significant unknowns │
│ • Cross-team coordination │
│ Time: 3-5 days │
│ Action: Should definitely be split │
└─────────────────────────────────────────────────┘
13+ POINTS - Epic
┌─────────────────────────────────────────────────┐
│ Too large for single sprint │
│ Action: MUST be broken down │
└─────────────────────────────────────────────────┘
Refinement Session Template
REFINEMENT SESSION AGENDA
OPENING (2 min):
┌─────────────────────────────────────────────────┐
│ • Review session goals │
│ • Check: How many items need refinement? │
│ • Time-box reminder │
└─────────────────────────────────────────────────┘
ITEM REVIEW (50 min for ~5 items):
┌─────────────────────────────────────────────────┐
│ For each item (10 min max per item): │
│ │
│ 1. PO reads story and acceptance criteria │
│ 2. Team asks clarifying questions │
│ 3. Technical discussion if needed │
│ 4. Estimate (if ready) │
│ 5. Mark as ready or note follow-ups │
│ │
│ If not resolvable in 10 min: │
│ └── Park for offline follow-up │
└─────────────────────────────────────────────────┘
WRAP-UP (5 min):
┌─────────────────────────────────────────────────┐
│ • Recap items refined and estimates │
│ • List follow-up actions with owners │
│ • Confirm enough ready for next sprint │
│ • Note: Ready backlog should be 2 sprints deep │
└─────────────────────────────────────────────────┘
Backlog Health Metrics
BACKLOG HEALTH DASHBOARD
READINESS:
┌─────────────────────────────────────────────────┐
│ Items meeting Definition of Ready: │
│ │
│ Ready for next sprint: 35 points ✓ │
│ (Target: 1.5x sprint capacity of 30) │
│ │
│ Ready for sprint after: 28 points ⚠ │
│ (Target: 1x sprint capacity) │
│ │
│ Needs refinement: 45 points │
│ (Pipeline for future) │
└─────────────────────────────────────────────────┘
ESTIMATION COVERAGE:
┌─────────────────────────────────────────────────┐
│ Top 20 items: │
│ ├── Estimated: 18 (90%) ✓ │
│ └── Unestimated: 2 (10%) ✓ │
│ │
│ All items: │
│ ├── Estimated: 45 (65%) │
│ └── Unestimated: 24 (35%) │
│ (Lower backlog items can wait) │
└─────────────────────────────────────────────────┘
STORY SIZE DISTRIBUTION:
┌─────────────────────────────────────────────────┐
│ Ready items breakdown: │
│ 1-2 points: 8 items ████████ │
│ 3 points: 5 items █████ │
│ 5 points: 4 items ████ │
│ 8+ points: 1 item █ (needs splitting) │
│ │
│ Health: Good (most items < 5 points) │
└─────────────────────────────────────────────────┘
Best Practices
Anti-Patterns
✗ Refinement only during sprint planning
✗ No Definition of Ready
✗ 3+ hour refinement meetings
✗ Estimating without understanding
✗ PO works alone on all items
✗ Never splitting large stories