Back to all frameworks
prioritization

MoSCoW Method

Classify requirements into Must have, Should have, Could have, Won't have.

Best forSprint or release planningScope negotiation with stakeholdersSetting clear boundaries on what ships
How it works
  1. 1

    List all requirements or features for the release

  2. 2

    For each item, classify it into one of four categories

  3. 3

    Must have: the release is useless without this

  4. 4

    Should have: important, but workarounds exist

Try it now
The trade-offs

What you gain — and what you give up.

MoSCoW is a prioritization technique used in project management and software development. It classifies requirements into four categories: Must have (non-negoti…

Strengths
  • Simple and widely understood
  • Forces explicit scope conversations
  • Won't have category prevents scope creep
  • Great for stakeholder alignment
Limitations
  • No granularity within categories (all Musts are equal?)
  • Doesn't quantify value or effort
  • Can be politically difficult (whose feature is a Won't?)
  • Doesn't account for dependencies
Real-world examples

When to reach for MoSCoW Method.

  • 01

    A scrum team planning what goes into the next sprint

  • 02

    A PM negotiating scope for a fixed-deadline launch

  • 03

    A client project where expectations need clear documentation

Apply this with the AI assistant
Context-aware chat

Ask about MoSCoW Method

The chat starts from this framework, so you can ask how to apply it, when it falls short, or whether another framework fits your situation better.

Open full assistant
Ask the AI

Talk through MoSCoW Method

This chat knows the current page context and starts from MoSCoW Method before recommending alternatives.

Open full chat
TT

You're looking at MoSCoW Method. I can help you apply it to a real problem, explain when it breaks down, or tell you when another framework fits better.

Try one of these
Related frameworks
prioritizationEisenhower MatrixOpen
prioritizationRICE ScoreOpen