MoSCoW Method
Prioritization Framework Template

The simplest method to sort tasks with only one criterion — mark each idea or task with just one label: Must, Should, Could, or Won't.

Use Template

One criterion. Four labels.

MoSCoW skips scoring entirely. Every idea or task gets exactly one label, so the debate is short: is it Must, Should, Could, or Won't for this delivery timebox?

Must

Critical to the current delivery timebox to be a success.
Without it, the release is considered a failure.

Should

Important but not necessary in the current delivery timebox.
Painful to leave out, but the release still ships without it.

Could

Desirable but not necessary.
Could improve customer satisfaction with little cost if time allows.

Won't

Agreed as the least-critical, lowest-payoff items — or not appropriate at this time.
Not planned for this delivery timebox.

// the scores

Must · Should · Could · Won't — one score per item

Just one label per idea or task, agreed with stakeholders before the timebox starts.

Ducalis keeps the label attached to every idea or task, so the whole backlog sorts itself by delivery priority.

┌─ MOSCOW · LABEL THIS BACKLOG ──────────────────┐
│  Fix checkout crash                      Must  │
│  Add CSV export                        Should  │
│  Custom themes                          Could  │
│  Legacy API v1 support                  Won't  │
│                                                │
│  ▸ one label, no debate                        │
└────────────────────────────────────────────────┘

// sorted output

Labels that travel with your tickets

The Must/Should/Could/Won't label isn't locked inside Ducalis — push it straight back to your task tracker as a field, label, or board column, so the priority travels with the ticket.

Learn how scores sync back to your task tracker.

┌─ DUCALIS → TASK TRACKER ───────────────────┐
│  "Fix checkout crash"                      │
│  MoSCoW                              Must  │
│                                            │
│  synced as a priority field                │
│                                            │
│  ▸ pushed on every label change            │
└────────────────────────────────────────────┘

Example: labeling a real backlog

Four items, one label each, one sorted delivery timebox — this is what a MoSCoW-labeled backlog looks like in practice.

Idea / Task	Label
Fix checkout crash	Must
Add CSV export	Should
Custom themes	Could
Legacy API v1 support	Won't

// native scoring

Label with MoSCoW natively in Ducalis

MoSCoW is a built-in framework — no setup, no custom fields to wire up. Open a board, pick MoSCoW, and start labeling.

Prefer RICE, WSJF, Eisenhower Matrix, or your own criteria? Switch frameworks anytime — the same backlog carries over.

┌─ LABEL THIS ITEM ──────────────────────────┐
│  "Fix checkout crash"                      │
│                                            │
│  Must                               [ ✓ ]  │
│  Should                             [   ]  │
│  Could                              [   ]  │
│  Won't                              [   ]  │
│                                            │
│  ▸ one click, auto-saved                   │
└────────────────────────────────────────────┘

Where teams use MoSCoW

MoSCoW fits anywhere a team needs a fast, low-friction call on scope — here's where it shows up most.

┌─ RELEASE SCOPE ──────────────────────────┐
│  Must                           4 items  │
│  Should                         6 items  │
│  Could                          9 items  │
│                                          │
│  ▸ ship Must, cut the rest if late       │
└──────────────────────────────────────────┘

Release Scoping

Lock the Must list before the timebox starts — Should and Could stay negotiable if the schedule slips.

┌─ STAKEHOLDER REVIEW ─────────────────────┐
│  PM proposes: Should                     │
│  Eng counters: Must                      │
│                                          │
│  ▸ one label, agreed in the room         │
└──────────────────────────────────────────┘

Stakeholder Alignment

Settle scope disagreements with a single label per item instead of a multi-criteria scoring debate.

┌─ MVP BUILD ──────────────────────────────┐
│  Must-labeled items               = MVP  │
│                                          │
│  everything else waits                   │
└──────────────────────────────────────────┘

MVP Definition

Filter a backlog down to Must and the MVP scope defines itself — no separate exercise required.

┌─ CONTRACT SCOPE ─────────────────────────┐
│  In scope                 Must + Should  │
│  Change order                     Could  │
│                                          │
│  ▸ Won't excluded, in writing            │
└──────────────────────────────────────────┘

Vendor / Contract Scoping

Spell out Must/Should/Could/Won't in a statement of work so scope creep has a clear label to point at.

Ducalis—The Decision-Making Toolkit

Ducalis helps companies capture user requests, estimate job size, and prioritize the backlog with MoSCoW — or any framework your team prefers.
No credit card required. Unlimited users. No time limit.

Use MoSCoW Template View pricing

┌─────────────────────────┐
│  MUST · SHOULD          │
│  COULD · WON'T          │
│  = ONE LABEL            │
└─────────────────────────┘