Back to Docs
Recipe

MoSCoW Method

Prioritize features by Must-have, Should-have, Could-have, and Won't-have.

Overview

The MoSCoW method is a prioritization framework that helps teams decide which features to ship first. It splits requirements into four buckets, forcing hard conversations about what truly matters.

The Four Buckets

  • Must-have (M) — Non-negotiable. The product fails without these. Ship-stoppers.
  • Should-have (S) — Important but not critical. Painful to omit, survivable.
  • Could-have (C) — Nice-to-have. Include only if time and budget allow.
  • Won't-have (W) — Explicitly out of scope for this cycle. Not "never" — just not now.

How to Run It

  1. List every feature, task, or requirement on sticky notes.
  2. Force-rank each item into one of the four buckets. No "everything is a must-have."
  3. Cap Must-haves at 60% of total effort. If you exceed that, renegotiate scope.
  4. Share the board with stakeholders. Make the trade-offs visible.
  5. Revisit weekly — a Should-have today may become a Must-have tomorrow.

Why It Works

MoSCoW forces clarity. When every feature feels urgent, the framework creates a shared language for saying no. It aligns engineering, product, and leadership around a single source of truth.

Pro tip: Treat Won't-have as a parking lot, not a graveyard. Revisit it during the next planning cycle.