MoSCoW Prioritization Explained: Must, Should, Could, Won't

May 24, 2026

When everything is a priority, nothing is. MoSCoW is a prioritization technique that forces clarity by sorting every requirement into four categories. It is one of the most widely used frameworks in business analysis because it is fast, intuitive, and stakeholder-friendly.

What the letters mean Must Have — the project fails or is not viable without these. If you cannot launch without it, it is a Must. Be ruthless here; if everything is a Must, you have not prioritised.

Should Have — important and painful to leave out, but the project still works without it for now. These are the first things added once Musts are done.

Could Have — desirable but with a smaller impact. Included only if time and budget allow. These are the first to drop when deadlines tighten.

Won't Have (this time) — explicitly out of scope for this release. Writing these down is the secret weapon against scope creep, because it documents what everyone agreed to exclude.

Why the "Won't Have" matters most Most teams skip the Won't Have category, and that is a mistake. Naming what you are deliberately not doing prevents the slow drift of "can we just add one more thing." When a new request appears mid-project, you point to the agreed Won't Have list and have a calm, documented conversation instead of an argument.

How to run a MoSCoW session Gather your stakeholders, list every requirement on cards, and sort them together. The discussion itself is the value — it surfaces disagreements about what really matters before a single line of code is written. Aim for no more than 60 percent of effort in the Must category, leaving room for the inevitable changes.

Our AI Document Studio applies MoSCoW automatically when generating a BRD. Try it free.