When everything is "urgent", nothing really is. The MoSCoW method sorts every task into 4 clear categories to settle priorities without endless negotiation.
The MoSCoW method, developed in the 1990s as part of DSDM, sorts every task or feature into 4 categories: Must have (non-negotiable), Should have (important but not blocking), Could have (nice to have if time allows), and Won't have (excluded, for now).
Its value: forcing a real decision. Unlike a "priority 1 to 10" scale where everything ends up at 8 or 9, MoSCoW forces you to pick a precise category — and, crucially, to accept that part of the work won't happen this time.
What the deliverable has zero value or isn't legally/technically viable without. This category should stay the smallest.
Important, but the project stays viable without it. A common rule: Must + Should shouldn't exceed 60% of total effort.
The first tasks to drop if the schedule or budget tightens. Only include them if everything else is on track.
Explicitly noting what's excluded stops it from resurfacing later in the backlog as if the decision had never been made.
Common mistake: putting 80% of tasks in "Must have" means you haven't prioritized at all. If almost everything is essential, the method wasn't applied seriously.
Simple and fast to apply as a team. Great for prioritizing a project charter or a sprint.
Urgent vs. important, better suited to individual time management than a shared product backlog.
More quantitative, useful when several stakeholders need to objectively arbitrate between competing requests.
Reach, Impact, Confidence, Effort: heavier to calculate, reserved for large product roadmaps with lots of data.
The PMI recommends picking the simplest method that fits the context: for most teams, MoSCoW covers the need just fine.
Tag your tasks Must/Should/Could/Won't and stay focused on what matters. Free.