In 30 seconds
- Prioritization is choosing what not to do yet.
- Common methods: MoSCoW, value vs effort, RICE, WSJF, Kano.
- Pick one method and use it consistently.
Five common methods
| Method | How it works | Best for |
|---|---|---|
| MoSCoW | Must, Should, Could, Won't | Fixed deadlines |
| Value vs effort | 2x2 grid; do high value, low effort first | Quick team sessions |
| RICE | (Reach x Impact x Confidence) / Effort | Product teams with usage data |
| WSJF | Cost of delay / job size | Economic sequencing, used in SAFe |
| Kano | Basic, performance and delight features | Understanding customer satisfaction |
Choosing a method
Small teams usually do well with value vs effort. If delay is expensive, WSJF makes the trade-off explicit. MoSCoW comes from DSDM and suits time-boxed releases.
Common traps
- Everything labelled high priority
- Scores treated as precise truth
- The loudest stakeholder overriding the method
The output should be a single ordered Product Backlog.
Myth vs reality
Myth · A scoring formula removes judgment.
Reality · Scores inform judgment; they don't replace it.
Myth · Prioritize once per quarter.
Reality · Revisit as you learn, at least every few sprints.
Myth · High priority means do it now.
Reality · Order matters more than labels.
FAQ
What is cost of delay?
The value lost for each week a feature isn't available.
Who owns prioritization in Scrum?
The Product Owner, informed by stakeholders and the team.
Can we combine methods?
Yes, such as Kano to understand features and WSJF to sequence them.