Purpose
The method helps clarify scope, ordering, and delivery flow concretely. It makes work, boundaries, and ordering manageable. The result is captured as a prioritized backlog, release scope, and tradeoff notes.
Delivery
MoSCoW
Turns scope, ordering, and flow into a tangible result by collecting items, assigning must/should/could/won't categories, and finalizing the release set.
Which items must be included in the release, which are negotiable, and how much scope remains for stakeholder negotiation?
LowWorkshop + async30-90 min
How it works
The team follows the steps: collect items, assign must, should, could, and won't, validate musts against constraints, negotiate scope, and finalize the release set. Each step is captured visibly. At the end, a prioritized backlog, release scope, and tradeoff notes are available so decisions, tests, or actions can follow directly.
Visual orientation
Method sketch for a quick mental model.
Flow
- 1Collect items
- 2Assign must, should, could, won't
- 3Validate musts against constraints
- 4Negotiate scope
- 5Finalize the release set
The runsheet guides execution with 5 phases, timeboxes, 5 pitfalls, and clear stop criteria.
Open runsheetIdeal for
- Release planning
- Scope control
- Stakeholder alignment
Not good for
- Fine-grained ranking
- Quantitative portfolio scoring
Deep dive
In detail
MoSCoW follows a clear working logic: collecting items, assigning must, should, could, and won't, validating musts against constraints, negotiating scope, and finalizing the release set. This turns the method into a visible thinking process rather than only a conversation. Participants move step by step from raw material, observations, or options toward a shared structure. As a result, a prioritized backlog, release scope, and tradeoff notes support decisions, learning, or further planning.
Facilitation
Prepare a clear guiding question, the right information, and a visible workspace. Plan about 30-90 min with 3-12 people and use the format either in a workshop or asynchronously. The facilitation stays lightweight; short timeboxes, visible intermediate results, and a parking lot for open questions help.
Output artifacts
Prioritized BacklogRelease ScopeTradeoff Notes
Artifact templates
MoSCoW Working TemplateCompact working template for MoSCoW with context, input, output artifacts, and next step.markdown
MoSCoW Working TemplateCompact working template for MoSCoW with context, input, output artifacts, and next step.
markdownmoscow-working-template.md
Compact working template for MoSCoW with context, input, output artifacts, and next step.
MoSCoW Working Template
Goal
Prioritizes scope into Must, Should, Could, and Won't.
Context
When and for what do we use this method?
Input
Which data, observations, decisions, or materials are available?
Execution
Short notes along the runsheet.
Output artifacts
- Prioritized Backlog:
- Release Scope:
- Tradeoff Notes:
Assumptions and open questions
- ...
Decision / Next step
Owner, date, and success signal.
When to choose differently
Short decision aid for existing alternatives.
RICE Scoring
Statt MoSCoW, wenn Reichweite, Wirkung, Confidence und Aufwand als Zahlenvergleich wichtiger sind als Muss- und Kann-Grenzen.
Similar methods
All methodsDelivery
Cost of Delay
Moves scope, order, and delivery flow toward a concrete result through "adopt the initiative list", "clarify value types for each initiative, such as revenue, efficiency, or risk", and "derive a sorted sequence".
Product Strategy
ICE Scoring
Moves target group, value, goals, and priorities toward a concrete result through "prepare the idea backlog", "define scales for I, C, and E", and "select top ideas for testing or building".
Decision Making
Decision Matrix
Turns options, criteria, and risks into a tangible result by listing options, defining criteria, and checking result and sensitivity.
Product Discovery
Kano Model
Turns customer problems, solution ideas, and evidence into a tangible result by collecting features, asking functional and dysfunctional questions, and deriving roadmap decisions.
Product Strategy
RICE Scoring
Turns target groups, value, goals, and priorities into a tangible result by collecting initiatives, estimating reach, and calculating scores.
Statt MoSCoW, wenn Reichweite, Wirkung, Confidence und Aufwand als Zahlenvergleich wichtiger sind als Muss- und Kann-Grenzen.
Agile
WSJF
Turns backlog, sprint work, and team flow into a tangible result by defining the work queue, estimating cost of delay, and pulling highest value first.