Skip to content
PrioSmith
All free tools

Prioritize · CSV

MoSCoW Prioritization

Sort scope into Must, Should, Could, and Won't Have buckets.

No account, no server upload, no hidden paywall. Work stays in this browser unless you explicitly copy, download, print, or enter a remote image URL.

Shape one release boundary

Assign every item to make the trade-off visible. Unassigned items stay outside the distribution.

6/100 items · 0/240 characters

Unassigned — choose a category

CSV export
API v2

Must Have

1

The release fails without it.

User authentication

Should Have

1

Important, but the release still works without it.

Dashboard analytics

Could Have

1

Useful if time allows; cut before critical scope.

Dark mode

Won't Have this time

1

Explicitly out of scope for this release.

Custom themes

Distribution

Must Have

1 · 25%

Should Have

1 · 25%

Could Have

1 · 25%

Won't Have this time

1 · 25%

Method guide · reviewed September 2, 2026

Use MoSCoW to set scope for one timeframe.

MoSCoW groups work by how much the current release needs it. Set the release or timebox first. The same item may have a different priority in a later timeframe.

The four groups

Must Have
The release is not viable, safe, or legal without it.
Should Have
Important and painful to leave out, but the release still works with a temporary workaround.
Could Have
Useful but less important. Drop it first when the deadline is at risk.
Won't Have this time
Explicitly outside this timeframe, not rejected forever.

The Must test

Ask what happens if the item is missing. If you would cancel the release because the result is unusable, unsafe, or illegal, it is a Must. If a workable fallback exists, it is usually a Should or Could.

If everything is a Must, the plan has no room to protect its deadline.

Small release example

  • Must: save submitted feedback securely.
  • Should: let the team merge duplicate requests.
  • Could: add custom board colors.
  • Won't this time: send Slack notifications.

What MoSCoW does not do

It does not rank items inside one group, estimate value, or remove dependencies. Use a second comparison method when several Musts or Shoulds still compete for order.