PlayInfoBox

Home /Utilities /MoSCoW Prioritization: Sorting Requirements Into Must, Should, Could, and Won't

MoSCoW Prioritization: Sorting Requirements Into Must, Should, Could, and Won't

When a project has more requested features than time to build them, MoSCoW gives everyone a shared, simple language for what actually has to ship.

Must have: non-negotiable for this release

Requirements the project genuinely cannot succeed or ship without. If a single Must-have item is missing, the release is considered a failure by definition, which is why this category should be kept small and genuinely essential.

Should have: important but not fatal if delayed

Requirements that add real, significant value and are painful to leave out, but the project can still succeed without them for this specific release if time runs short.

Could have: desirable, first to be cut

Nice-to-have improvements that would be welcome if time and resources allow, but have a comparatively small impact if left out entirely. These are the first items dropped when a project needs to reduce scope.

Won't have (this time): explicitly out of scope

Items deliberately agreed to be excluded from this particular release, which is different from simply forgetting or ignoring them -- naming them explicitly prevents the same debate from resurfacing later and sets clear expectations for a future release.

Why the lowercase letters

The lowercase "o"s in MoSCoW exist purely to make the acronym pronounceable as a word, rather than standing for anything themselves -- the four real categories are Must, Should, Could, and Won't.

Where it comes from and why it's useful

MoSCoW originated in software development and agile project management as a way to have a fast, shared conversation about priority without a lengthy scoring system. Its main strength is forcing an explicit, negotiated decision about what "must" actually means, since teams often disagree the most on where the line between Must and Should belongs.

A common rule of thumb for balance

A commonly cited (though not universal) guideline suggests keeping Must-have items to roughly 60% or less of total project effort, leaving meaningful room for Should- and Could-have items -- if everything gets labeled a Must-have, the categorization has stopped doing its job of forcing real trade-offs.

Frequently Asked Questions

What's the difference between MoSCoW and just ranking tasks 1, 2, 3...?

A numbered ranking implies every item is different from every other by exactly one degree of priority, while MoSCoW groups items into a small number of meaningfully different tiers, which tends to produce clearer, faster team agreement than debating fine-grained rankings.

Who decides what counts as a Must-have?

Ideally it's negotiated among stakeholders together rather than decided unilaterally by any one person, since the most common failure mode of MoSCoW is everyone privately treating their own item as a Must-have without ever testing that claim against the others.