methodData, experimentation & growth

MoSCoW Prioritization

MoSCoW sorts requirements into Must, Should, Could, and Won’t-have-for-now groups to protect a viable delivery scope.

Download Markdown (.md)

01What it means

MoSCoW is a requirements-prioritization method associated with the Dynamic Systems Development Method. Teams classify work as Must Have, Should Have, Could Have, or Won’t Have this time, making the boundaries of a timeboxed release explicit.[1][2]

Explicit timebox scope boundaries Separate essential outcomes from survivable omissions and deliberate deferral
  1. 01Must HaveWithout it, unsafe, illegal, nonviable, or no core purpose
  2. 02Should HaveImportant, but omission is survivable
  3. 03Could HaveUseful enhancement if capacity remains
  4. 04Won't Have this timeExplicitly outside this timebox

Must Haves should fit comfortably within capacity; categories can change when evidence or constraints change.

02Why it matters

A flat list of “high-priority” requirements gives teams no guidance when time runs out. MoSCoW forces stakeholders to distinguish what is essential for a viable outcome from what is valuable but negotiable, creating room for contingency without hiding trade-offs.

03When to use it

Use MoSCoW when defining a release, project increment, prototype, or other fixed timebox whose scope can vary. It works best when decision-makers agree on the outcome, the deadline, and a strict test for what counts as a Must Have.

04How it works

  1. Define the timebox, intended outcome, constraints, and the decision authority for disputed items.
  2. Classify as Must Have only work without which the outcome would be unsafe, illegal, nonviable, or unable to meet its core purpose.
  3. Classify important but survivable omissions as Should Have and useful enhancements as Could Have.
  4. Put explicitly deferred work in Won’t Have this time so it does not quietly return to the active scope.
  5. Check that Must Haves fit comfortably within capacity, then revisit categories as evidence or constraints change.

05A practical example

Example

For a first release of appointment booking, secure slot selection, confirmation, and cancellation are Must Haves. Calendar export is a Should Have, reminder customization is a Could Have, and family-account management is Won’t Have this time. When integration work expands, the team drops a Could rather than compromising cancellation.

06Where it breaks

Categories can become political labels, and stakeholders may call everything a Must. MoSCoW does not quantify value, sequence dependencies, or compare effort. “Won’t” means excluded from the current timebox, not necessarily rejected forever, so deferred items still need deliberate review.

Common mistakes

  • Allowing most of the scope to become Must Have.
  • Using vague category definitions without a viability test.
  • Interpreting Won’t Have this time as permanently rejected.

07Sources

  1. What is MoSCoW Prioritization?Agile Business Consortium · Institutional guideWhat is MoSCoW Prioritization?
  2. MoSCoW PrioritisationAgile Business Consortium · Official DSDM handbookMoSCoW Prioritisation
View saved topics

Start typing to search titles, definitions, categories, and frameworks.