Sprint Prioritizer

---
name: sprint-prioritizer
description: "Use when an org role acts as sprint prioritizer and must decide what enters the next sprint from a groomed backlog by value, effort, risk and dependencies. Covers RICE scoring before planning, sprint goals, cross-functional estimates and capacity limits. For writing stories and backlog ownership see agile-product-owner."
tags: ["product","planning","strategy"]
tools: []
license: Apache-2.0
source: https://github.com/monoes/monomind
---
# Sprint Prioritizer — Best Practices

## Focus
Decides what enters the next sprint from a groomed backlog, balancing value, effort, risk, and dependencies so each sprint delivers the highest-impact work that's actually feasible.

## Best practices
- Score backlog items with RICE (Reach × Impact × Confidence ÷ Effort) during backlog grooming, before sprint planning starts — don't score live in the planning meeting.
- Get cross-functional input on the score components: engineering validates Effort, growth/marketing informs Reach and Impact, stakeholders stress-test Confidence assumptions.
- Anchor every sprint to one or two explicit sprint goals; use those goals as a secondary filter when RICE scores are close.
- Apply multiple prioritization lenses depending on context — risk-based (de-risk unknowns early), value-based (RICE/MoSCoW), dependency-based (unblock other work first).
- Keep the backlog groomed continuously (not just right before planning) so prioritization decisions aren't rushed under deadline pressure.
- Protect sprint capacity: don't overcommit by ignoring known velocity — pulling in "one more high-value item" that blows the sprint undermines the whole exercise.
- Re-validate priority when new information arrives mid-sprint rather than rigidly sticking to a stale ranking.

## Common pitfalls
- Scoring Effort without engineering input, producing RICE numbers that look objective but are fictional.
- Letting the loudest stakeholder's request jump the queue without re-running it through the same framework as everything else.
- Treating the backlog as a strict, permanent priority queue instead of re-scoring as reach/impact/confidence assumptions change.
- Packing a sprint to 100%+ of known velocity "just this once," which becomes every sprint.
- No sprint goal — a bag of unrelated tickets that individually score well but don't add up to a coherent outcome.

## Tools & techniques
- RICE scoring (Reach, Impact, Confidence, Effort) as the default objective ranking method.
- MoSCoW (Must/Should/Could/Won't) for scope-cut conversations within a sprint.
- Backlog grooming sessions separated in time from sprint planning, so prioritization isn't rushed.
- Dependency mapping to sequence work that unblocks other high-value items first.