Delivery Decision method
Shapes a time-bound release with clear must, flexibility, and deferral decisions.
MoSCoW classifies requirements as Must, Should, Could, and Won’t Have this time. The classification is checked against the goal, dependencies, risks, and available capacity.
Which requirements must be in this release, which are negotiable, and what is deliberately left for later?
The four categories apply to this timeframe. They are not a permanent ranking or point total.
Frame
Set goal, timeframe, capacity, and what Must means for this release.
Classify
Classify comparable items by their importance for this release.
Constraints
Test whether Musts are deliverable and which dependency or risk threatens the release.
Trade-offs
Decide which important and desirable items fit the remaining flexibility.
Commit
Record Musts, committed Shoulds, optional Coulds, and Won’t Have this time as a time-bound decision.
MoSCoW applies to a defined period. Revisit categories when date, capacity, or risk changes; Won’t is not permanent exclusion.
Use it to plan a release or fixed work period and agree a boundary for variable scope.
Each item has a reasoned category for the current period.
Must core, flexibility, capacity, and dependencies are visible.
Deferrals, risks, and later review points remain traceable.
Fictional neighborhood tool-lending pilot
Time-bound release categories with visible flexibility.
Fictional: Record lending
Without a record, safe return is not possible.
Fictional: Reminder message
Important; a manual reminder is possible.
Fictional: Wishlist
Useful; first to drop under time pressure.
Fictional: Second pickup point
Deliberately deferred for this pilot period.
Name release, goal, fixed time, and available capacity. Agree the Must test: without this item delivery is not viable, safe, or legal.
When a release carries too many demands and priorities are only ever negotiated, MoSCoW creates clear boundaries for the next cut. Must, Should, Could, and Won't make commitment, room for maneuver, and trade-off logic visible to everyone involved.
The classification separates mandatory from deferrable points and weighs them against time, risk, and dependencies. This creates a shared weighting picture on which commitments, compromises, and a solid release boundary can be built cleanly.
MoSCoW helps because it translates prioritization into degrees of commitment, making the scope of an initiative starkly visible. The approach becomes effective when every classification is checked against goal, risk, dependency, and actual deliverability. The prioritization stays clean when the number of Must items remains tight, edge cases are negotiated openly, and the Won't category doesn't quietly creep back in, so scope doesn't grow again uncontrolled.
Before sorting, fix the release or planning horizon under consideration and clarify who shares the consequences of the classification. The prioritization usually tips where too many points slide into Must; then the group has to resharpen the core of the initiative. Close with an explicit release boundary and visible trade-off decisions for later discussions.
The method guide walks execution through 5 phases, timing, 5 pitfalls, and clear stop criteria.
Open method guideYour perspective
Your feedback helps shape the next improvements to methodatlas.
Prepare a time-bound release decision with visible trade-offs.
To be confirmed
To be confirmed
Shape a release Time: 30 to 90 minutes for the first sort
Complete this worksheet on paper or in your own document during the work.
...
...
...
...
Must test ...
Time bound ...
Trade-off rule ...
Agile Business Consortium / DSDM
Expected artifact: Prioritization frame
Without time and capacity, the category loses force.
Entry:
...
Expected artifact: Categorized backlog
Won’t describes a deliberate deferral in the current period.
Entry:
...
Expected artifact: Checked core scope
MoSCoW does not create false precision; rough sizes are enough for the boundary.
Entry:
...
Expected artifact: Negotiated flexibility
Coulds are not promised scope.
Entry:
...
Expected artifact: Time-bound release decision
Reassess categories when constraints change.
Entry:
...
...
Method guide: https://methodatlas.meierhoff-systems.de/en/methods/moscow/run-sheet
Fitting alternatives with decision guidance, followed by other related methods.
Instead of MoSCoW, when reach, impact, confidence, and effort matter more as a numeric comparison than must- and could-boundaries.
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".
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".
Weighs options against criteria so comparison, scoring rationale, and selection are documented traceably.
Classifies features by their effect on satisfaction, showing which expectations create basic, performance, or delight response.
Splits items into A, B, and C by value or effect and directs focus to the most impactful ones.
