What is MoSCoW Prioritisation?
MoSCoW prioritisation is a technique that sorts requirements into four categories: Must have, Should have, Could have and Won't have (this time). It forces explicit agreement on what a release genuinely depends on, what would improve it, what is optional, and what is consciously excluded from scope.
Reviewed by Gensudo Team · 23 July 2026
In more depth
The method was devised by Dai Clegg and became a core practice of the DSDM agile framework. Its discipline lies in the definitions: a Must have is something without which the release fails or is not viable — not merely something important. Should haves are painful to omit but survivable; Could haves are desirable if capacity allows; Won't haves are recorded exclusions, which prevents them silently re-entering scope. A common rule of thumb is to keep Must haves to a minority of the total effort, so there is genuine room to flex when estimates prove optimistic.
Why it matters
Most scope arguments happen because everything has been labelled high priority. MoSCoW replaces a meaningless ranking with a contract: stakeholders agree in advance which items the release stands or falls on, and which get dropped first under pressure. That makes de-scoping a planned manoeuvre rather than a crisis, and gives teams a defensible answer when new requests arrive mid-build.
A product example
For the first release of an invoicing feature, creating and sending an invoice is a Must have; recurring invoices are a Should have; customisable templates are a Could have; and multi-currency support is recorded as a Won't have this time. When testing overruns, the team drops the Could have without renegotiating the whole release.
Documents where this shows up
Prioritisation Framework for Heads of Product · Product Requirements Document (PRD) for Product Managers · Product Roadmap for Product Managers
Related terms
RICE Scoring · Product Backlog · Acceptance Criteria · Stakeholder Alignment