Marcus Andrey Study
Ler em português Library

Framework · Facilitation techniques · 2 min read

MoSCoW

Must / Should / Could / Won't. Scope a release or initiative and make the 'won'ts' explicit.

MMust have

Without it, the release fails or makes no sense. Non-negotiable.

e.g. save a draft order
SShould have

Important and expected, but the release still works without it.

e.g. bulk edit
CCould have

Nice to have. The first thing to drop if time runs out.

e.g. saved filters
WWon't have

Out of scope this time. Written down and shared, so nobody expects it.

e.g. mobile layout, not this release

Musts ≤ about 60% of the effort · the rest is room for Should and Could

MoSCoW sorts scope into four buckets, and the Won't list is as important as the Must list.

Use it when

  • You scope a release or initiative with a product manager and developers, and the list is longer than the time.
  • Stakeholders keep adding "small" items and you need a visible line between in and out.
  • You want to protect UX capacity by agreeing early what the team will not do.

How to use it

  1. List the candidate items. Write each feature, fix or research task on its own sticky, with a rough effort estimate. Output: the full candidate list with effort.
  2. Agree the meaning of Must. A Must is something without which the release fails or makes no sense. Say this out loud before sorting. Output: one shared test for "Must".
  3. Sort into the four buckets. Place each item in Must, Should, Could or Won't. Discuss items people disagree on, one at a time. Output: a first sorted board.
  4. Check the Must line. Add up the effort of the Musts. If it is more than about 60% of the available effort, move items down until it fits. Output: a Must list that leaves room for surprises.
  5. Write down and share the Won'ts. Put the Won't list in the release notes or project page, with "not this time" as the reason. Output: an explicit Won't list. About 30 minutes for the session.
  6. Revisit at each milestone. Check the buckets again when plans change or a milestone ends. Output: an updated board.

Worked example

A UX lead, a product manager and three developers scope the next release of an order editor on an internal operations platform. The team has 20 days of effort.

Bucket Items Effort
Must Save a draft order · validation messages · keyboard entry for the main fields 11 days (55%)
Should Bulk edit · recent orders list 5 days
Could Saved filters · dark mode 4 days
Won't (this release) Mobile layout · custom columns Shared in the release page

The product manager first wanted bulk edit as a Must. The test "does the release fail without it?" moved it to Should.

Watch out for

  • Everything becomes a Must. Without the 60% check, the Must list grows until there is no room for anything else. Add up the effort.
  • The Won'ts stay unspoken. If you don't write them down, people assume their item is still coming. Share the list.
  • Sorting without effort. A bucket means little if you don't know the cost. Estimate roughly before you sort.
  • Sort once and forget. Priorities change. Revisit at each milestone.

Template

Copy this into the project page and fill it with the team.

MoSCoW · Release/initiative: ____________   Available effort: ____ days

Must (release fails without it)     effort: ___ days  (≤ about 60%)
-
Should (important, but it works without it)    effort: ___ days
-
Could (first to drop)                          effort: ___ days
-
Won't (this time; shared with stakeholders)
-

Next review (milestone / date):
Source
Dai Clegg (DSDM)
Saved only on this device.

↑ ↓ to move · Enter to open · Esc to close