What is MoSCoW Prioritization?
MoSCoW prioritization groups requirements as Must have, Should have, Could have, or Won't have for the current delivery. It clarifies scope when time or capacity is limited and helps make deferred work explicit.
When to use it
Use it when requirements exceed the time or scope available for a delivery.
How the methodology works
Classify items into Must have (critical), Should have (important), Could have (nice to have), and Won't have this time (future consideration).
- Define the delivery goal, deadline, and capacity. A requirement cannot be prioritized well without a shared release boundary.
- Classify each requirement by its effect on the minimum acceptable outcome, then distinguish important work from optional improvements.
- Check that Must haves fit the available capacity and document Won't haves so stakeholders know what is outside this delivery.
Example: Scoping a first version of an ordering portal
Illustrative situation: A team has limited time for the first release. Secure order submission is essential to the release goal, saved favorites would improve convenience, and personalized recommendations could wait.
How to apply it: The team records which requirements are Must, Should, or Could for this release, and lists recommendations as Won't for now if they are explicitly deferred.
Example limits: This scenario is illustrative, not evidence about a real business. Use evidence relevant to your decision for your own facts, ratings, probabilities, or financial estimates.
How to read the result
Focus delivery on Must Have requirements first, consider Should Have items for a later iteration, and use Won't Have items to set scope expectations.
Questions about MoSCoW Prioritization
Does Must have mean a stakeholder says it is important?
Not by itself. A Must should be necessary for the agreed delivery outcome or a real constraint. If every request is a Must, the categories are not helping manage scope.
Is Won't have the same as never?
No. It means the item is outside the current delivery. Record whether it is deferred for a later release or intentionally excluded.
Next step
Set the goal and capacity for one delivery, then classify requirements against that boundary.
Need a printable resource or a step-by-step method? How to prioritize projects. Compare requirements prioritization with other project methods.