MoSCoW

MoSCoW is a prioritization technique that sorts requirements into four groups: Must have, Should have, Could have and Won't have (this time). Created by Dai Clegg in 1994 and later built into the Dynamic Systems Development Method (DSDM), it is mainly used to agree the scope of a fixed-time release, minimum viable product or project with stakeholders.

How MoSCoW Works

Each requirement is placed in exactly one group. The lowercase o's carry no meaning; they only make the acronym pronounceable.

• Must have: requirements without which the release has no point, is unsafe or is not legal. DSDM describes this group as the Minimum Usable SubseT, the part the team guarantees to deliver. A useful test: if this is missing, would we cancel the release?
• Should have: important but not vital. The release still works without them, perhaps with a workaround.
• Could have: desirable but less important. These form the main contingency, the first items dropped if time runs short.
• Won't have (this time): items explicitly agreed to be out of scope for this timeframe. Recording them prevents them from quietly creeping back in, and they may return in a later release.

DSDM adds an effort rule that makes MoSCoW more than a labeling exercise: Must haves should take no more than about 60% of the planned effort, with around 20% in Could haves as contingency. That buffer is what lets a team hit a fixed date while protecting what matters most.

Why MoSCoW Matters

MoSCoW is fast and uses plain language, so non-technical stakeholders can take part. Its real strength is forcing an honest conversation about what is truly non-negotiable, which is exactly the decision that matters when scoping an MVP or a deadline-driven release.

Its weakness is subjectivity. Without discipline, almost everything becomes a Must have, and the method does not rank items within a group. Teams often pair it with a quantitative method such as RICE scoring to order items inside the Should and Could groups.

MoSCoW Example

A startup has eight weeks to launch a payroll minimum viable product for small businesses:

• Must have: calculate gross and net pay, apply tax withholding, run payroll for up to 20 employees.
• Should have: downloadable payslips, email notifications to employees.
• Could have: dark mode, custom report filters.
• Won't have (this time): multi-currency payroll, contractor payments.

When the tax module runs two weeks late, the team drops the Could haves and keeps the launch date. Deciding what to build, defer or cut at this stage is explored further in protecting pre-seed runway from feature over-engineering.

MoSCoW vs. Out of Scope

The Won't have group is close to an out-of-scope list, with one difference: "this time" signals a deferral, not a permanent rejection. Items marked Won't have are still valid ideas that may be reconsidered for a later release.