MoSCoW Scoring Model: Must, Should, Could, and Won't Prioritisation

What is the MoSCoW scoring model?

MoSCoW is a prioritisation framework used to classify requirements by delivery necessity. It is especially helpful in release planning when scope pressure is high.

MoSCoW categories

• Must have: non-negotiable requirements for release viability.
• Should have: important but not critical for initial release.
• Could have: desirable enhancements if capacity allows.
• Won't have (for now): explicitly deferred items.

How to run MoSCoW prioritisation

1. Define release goals and constraints.
2. List all candidate features or requirements.
3. Classify each item into Must, Should, Could, or Won't.
4. Validate category decisions with stakeholders.
5. Review before each planning cycle.

MoSCoW example

For an MVP launch, authentication and payment processing are Must have, onboarding walkthrough is Should have, custom themes are Could have, and enterprise role permissions are Won't have for the first release.

Common mistakes

• Putting too many items in Must have.
• Not defining objective criteria for categories.
• Failing to revisit Won't have items over time.
• Using MoSCoW alone without effort or risk context.

How DecisionGrid turns MoSCoW into delivery decisions

DecisionGrid complements MoSCoW by translating release-priority discussions into a ranked execution view. Teams can move selected initiatives into the platform and manage them with consistent economic and risk signals across the portfolio.

• Capture each project's economic and delivery inputs, including budget, timeline, and complexity fields.
• Use predicted risk level and model confidence to complement category-based planning decisions.
• Track project completion status and realised outcomes after release decisions are made.