Skip to main content
← All guides
Tool + guide · September 2026 · 6 min read

MoSCoW prioritization

Must, should, could, won't. Four words everyone knows — and one rule about proportions that almost nobody applies, which is the difference between a plan and a list of labels.

Short answer

What is MoSCoW prioritization?

A way of agreeing what is in and out of a release under a fixed deadline. Items go into Must have, Should have, Could have, or Won’t have this time — and the method works only if no more than about 60% of the effort sits in Must.

The short version

  1. From DSDM, an agile delivery framework, designed for fixed-length timeboxes rather than open-ended backlogs.
  2. Guidance: at most 60% of effort in Must, roughly 20% in Could. Could items are the contingency you drop when you run long.
  3. The rule is about proportions of effort, not counts of items — twenty small Coulds and one huge Must is not a balanced plan.
  4. The Won’t column earns its place by being written down: it is how an excluded idea stops coming back every fortnight.
Check your shares ↓

Free · No signup · Nothing leaves your browser

Sort the list, then check the shares

Put an effort figure on every item — days, points, whatever you use — because MoSCoW is a rule about proportions of effort, and counting cards instead of hours flatters the plan in exactly the direction you would like it to.

Must have
Without it the release has no point. If it slips, the date slips.
Should have
Painful to leave out, but the release still works. There is a workaround.
Could have
Wanted, and the first thing dropped when time runs short. This is the contingency.
Won't have, this time
Agreed out loud, in writing, for this release. Saying it here is what stops it coming back.

Share of the 62 days you plan to spend

56%
23%
21%
Must have · 35 daysShould have · 14 daysCould have · 13 daysWon't: 40 days, deliberately outside the plan

The method asks for Must under 60% and Could around 20%.

Shares are within the method's own guidance: there is contingency behind the commitments, and something is written down as out of scope.

Paste into the scope conversation.

What this cannot know. The four labels are a negotiation, not a measurement — anyone can move an item into Must by saying so, and the effort figures are estimates nobody checked. MoSCoW records a decision about scope; it has nothing to say about whether the scope is worth building.

For ordering within a bucket, RICE scores the candidates. For which kinds of feature belong in Must at all, the Kano model separates what people miss when it is absent from what they merely enjoy.

Test the idea behind it →

MoSCoW argues about scope and takes the goal as settled. A 15-minute session ends with a written GO / WAIT / NO-GO and the reasoning behind it. Free tier, no card.

The rule everyone forgets

MoSCoW is usually taught as four labels, which makes it feel like a vocabulary exercise. The part that makes it work is a constraint on proportions: no more than about 60% of the effort in Must, and roughly 20% in Could.

The logic is mechanical. A timebox has a fixed end. Estimates are wrong, usually in one direction. So the plan needs work in it that can be removed without anyone renegotiating a commitment — and that is precisely what Could means. Not “nice to have”, but the part we have already agreed to lose.

A plan that is 95% Must has no such part. When it runs long — and it will — the team is forced into an emergency conversation about breaking promises, at the worst possible moment to have it. The 60% ceiling is what moves that conversation to today, when it is cheap.

And the shares must be measured in effort. A board with four Musts and twenty Coulds looks well balanced and can still be 90% Must by the only measure that matters. This is why the planner above will not compute anything until every item has an effort figure.

Four ways MoSCoW goes wrong

❌ Everything is a Must

The most common outcome of a MoSCoW session, and the exact opposite of prioritising. It usually happens because Must gets read as "important" rather than "the release is pointless without it".

✓ Instead: Ask of each Must: if this were missing on launch day, would we delay the launch? If the honest answer is no, it is a Should.

❌ Counting items instead of effort

Twenty small Coulds and one enormous Must look like a well-balanced board and give you no contingency at all. The rule is about proportions of work, and the board does not show work.

✓ Instead: Put an effort figure on every item before you look at the shares. The planner above refuses to compute anything without them for this reason.

❌ Leaving the Won’t column empty

The value of Won’t is not the list — it is that somebody said no out loud and it was written down. An empty column means every excluded idea is still quietly in play.

✓ Instead: Name the things you have decided against for this release, with "this time" attached. It ends the same conversation happening every fortnight.

❌ Sorting once and never revisiting

MoSCoW describes a release under a deadline. When the deadline or the understanding moves, the labels are stale — and stale labels are worse than none, because they carry authority.

✓ Instead: Re-sort when the date changes or when something you called Must turns out to be harder than believed. That second case is the one people avoid.

What MoSCoW cannot do

It cannot rank within a bucket. Four Musts are four Musts; the method has nothing to say about which to start. That is what RICE is for.

It cannot stop a label being political. Anyone can put an item in Must by saying so with enough conviction. The proportion rule is the only defence, and it works by making the cost of the claim visible to everyone at once.

It cannot fix a Must list that does not fit. If dropping the entire contingency still leaves you over the deadline, the problem is not prioritisation — the planner above says so in those words rather than pretending the ordering helped.

It says nothing about whether the release is worth building. MoSCoW assumes the goal and argues about scope.

Scope is an argument about a goal

Every MoSCoW session takes the goal as settled and argues about the route. That is the right way round — as long as somebody checked the goal.

A 15-minute session works through seven criteria, including whether the problem is real and whether anyone will pay, and ends with a written verdict and the reasoning.

Test the idea behind the release →

15 min · free tier, no card

Frequently asked questions

What does MoSCoW stand for?+
Must have, Should have, Could have, and Won’t have this time. The lowercase o’s are just there to make the acronym pronounceable. It comes from DSDM, an agile delivery framework, and was designed for timeboxed releases — which is why the fourth category is "won’t have this time" rather than "never".
What is the 60% rule in MoSCoW?+
DSDM’s guidance is that no more than 60% of the effort in a timebox should sit in Must, with roughly 20% in Could. The reason is not aesthetic: Could items are the contingency you drop when the work runs long. If everything is a Must there is nothing to drop, so the first delay turns into a fight with your own commitments instead of a planned reduction in scope.
What is the difference between Should and Could?+
A Should hurts to leave out and has a workaround — the release still functions, someone is just inconvenienced. A Could is wanted and its absence is barely noticed. The practical test is what you do under pressure: Coulds go first, without a meeting; dropping a Should is a decision someone has to make and communicate.
Why bother with the Won’t column?+
Because the value is the act of saying no in writing. An empty Won’t column means every idea that did not make the release is still informally alive, and the same suggestions return every couple of weeks. Writing them down with "this time" attached both closes the conversation and promises it can be reopened later.
Is MoSCoW better than RICE?+
They answer different questions. MoSCoW decides what is in and out of a release under a fixed date — it is a scope negotiation with four vocabulary words. RICE produces an order within a set of candidates using estimates of reach, impact, confidence and effort. Using MoSCoW to rank and RICE to decide scope makes both worse.
Is this planner free, and does my data leave the browser?+
It is free and requires no account. Everything is computed in your browser — nothing you enter is sent to us or stored anywhere.

Related guides