How do you prioritize when everything is marked critical?
47 of 52 tickets marked critical is not a priority list, it is a queue. The MoSCoW method on one page: the four buckets, the 60% rule that keeps Musts honest, one test per bucket, and the 45-minute meeting script.
Get the free PDF
One page, print-ready, free to share. No signup needed.
The backlog says 47 of 52 tickets are critical. That is not a priority list, it is a queue with better vocabulary, and the sprint will decide the real priorities by accident.
The four buckets
| bucket | definition | test |
|---|---|---|
| Must | release is pointless or illegal without it | "What happens if we ship without it?" Silence = not a Must. |
| Should | painful to skip, workaround exists | "What is the workaround?" None = promote it. |
| Could | improves life, cut first | "Who notices if it slips?" Nobody = say so now. |
| Won't | explicitly out, this release | "Are we agreed, in writing?" |
The letters are easy. The discipline is in the tests, because every stakeholder's Should is presented to you as a Must, and the only defense is a question with a falsifiable answer.
The 60% rule
Cap Musts at roughly 60% of delivery effort. The Shoulds and Coulds are not decoration: they are the shock absorber. When a Must overruns, a Could gets dropped and the date survives. If everything is a Must, the first overrun breaks the release, and the prioritization meeting reconvenes as a crisis meeting.
Prioritize effort, not ticket count. Ten tiny Musts can weigh less than three big ones; a count-based split hides that entirely.
Phrases that give the bucket away
- "Legal asked for it": Must, and check the deadline.
- "Customers keep churning over it": Must or high Should, get the numbers.
- "It would be embarrassing": Should. Embarrassment is a workaround.
- "While we are at it": Could at best. Scope creep in a trench coat.
- "The CEO mentioned it once": ask the CEO. Do not guess the bucket.
The 45-minute version
- 0-10 — restate the release goal, one sentence, on screen.
- 10-30 — bucket everything fast; any debate over 60 seconds gets parked.
- 30-40 — run the Must test on every Must. Demote freely.
- 40-45 — read the Won't list out loud and get the nods on record.
The last five minutes are the ones people skip and regret. A Won't that was never said out loud is a Must waiting to ambush week three.
The takeaway
Four buckets, one test each, a 60% cap measured in effort, and a written Won't list. The print-ready PDF above is the whole method on one page.
Frequently asked questions
What does MoSCoW stand for in prioritization?
How many requirements should be Must have?
How do you tell a Must from a Should?
Why does the Won't list matter so much?
Get the free PDF
One page, print-ready, free to share. No signup needed.