MoSCoW Prioritization: The Complete Guide for Product Managers

What is MoSCoW Prioritization?

MoSCoW is a prioritization framework that helps product teams categorize features and requirements into four distinct groups. The acronym stands for:

• Must Have
• Should Have
• Could Have
• Won't Have (this time)

Originally developed by Dai Clegg at Oracle for use in rapid application development, MoSCoW has become one of the most widely-used prioritization methods in product management and agile development.

The Four MoSCoW Categories

Must Have (Mo)

These are non-negotiable requirements. Without them, the product won't work or won't be legally compliant. They represent the minimum viable product (MVP).

Criteria for Must Have:

• The product is unusable without this feature
• There's no workaround available
• It's required for legal/compliance reasons
• The release would be pointless without it

Example: For an e-commerce app, payment processing is a Must Have.

Should Have (S)

Important features that add significant value but aren't critical for launch. The product can work without them, but they're high priority.

Criteria for Should Have:

• High business value but not critical
• Painful to leave out but possible
• Can be delayed to a later release
• Workarounds exist (even if inconvenient)

Example: Saved payment methods or order history features.

Could Have (Co)

Nice-to-have features that would improve user experience but have minimal impact if omitted. First to be cut when time or budget runs short.

Criteria for Could Have:

• Nice to have but not essential
• Small impact on user satisfaction
• Easy to add later
• Low development priority

Example: Product recommendations or wishlist functionality.

Won't Have (W)

Features explicitly excluded from the current scope. This category is crucial for managing stakeholder expectations and preventing scope creep.

Criteria for Won't Have:

• Out of scope for this release
• May be reconsidered for future releases
• Not aligned with current goals
• Resource constraints make it impossible

Example: Multi-currency support in an initial domestic launch.

How to Implement MoSCoW Prioritization

Step 1: Gather All Requirements

List all features, user stories, or requirements that need prioritization. Include input from stakeholders, customers, and the development team.

Step 2: Define Your Constraints

Understand your limitations:

• Time: Sprint deadline or release date
• Budget: Development resources available
• Team capacity: Skills and bandwidth

Step 3: Categorize Each Item

For each requirement, ask:

1. Is the project a failure without this? → Must Have
2. Is it painful to exclude but survivable? → Should Have
3. Is it nice to have with low impact? → Could Have
4. Is it explicitly out of scope? → Won't Have

Step 4: Validate with Stakeholders

Review the categorization with key stakeholders. Ensure alignment on what constitutes "must have" vs "should have."

Step 5: Allocate Resources

A common rule of thumb:

• 60% of effort on Must Haves
• 20% on Should Haves
• 20% on Could Haves

Best Practices

1. Keep Must Haves Minimal

If everything is a Must Have, nothing is. Limit this category to true essentials—aim for no more than 60% of your backlog.

2. Be Explicit About Won't Haves

Document why items are excluded. This prevents repeated discussions and manages expectations.

3. Revisit Regularly

Priorities shift. Review your MoSCoW categorization at the start of each sprint or release cycle.

4. Use Data to Support Decisions

Back up prioritization with:

• User research findings
• Usage analytics
• Customer feedback
• Business metrics

MoSCoW vs Other Frameworks

When to Use MoSCoW

Ideal scenarios:

• Fixed timeline projects
• MVP definition
• Stakeholder alignment sessions
• Scope negotiation
• Sprint planning

Less ideal for:

• Continuous discovery
• Research prioritization
• Strategic roadmap planning

Common Pitfalls to Avoid

1. Everything is a Must Have - Be ruthless in categorization
2. Ignoring Won't Haves - Explicit exclusion prevents scope creep
3. Static prioritization - Revisit as conditions change
4. Skipping stakeholder alignment - Get buy-in on criteria

Template: MoSCoW Workshop

Run a 90-minute session with your team:

1. Setup (10 min): Explain MoSCoW, set context
2. Silent brainstorm (15 min): Each person categorizes independently
3. Share & discuss (40 min): Review disagreements, find consensus
4. Finalize (15 min): Lock in priorities, document rationale
5. Next steps (10 min): Assign owners, set review cadence

Conclusion

MoSCoW prioritization is a powerful tool for product managers navigating competing priorities and stakeholder demands. Its simplicity makes it accessible, while its categorical structure forces clear decisions.

The key to success? Discipline in the Must Have category and transparency about Won't Haves. Combined with regular reviews, MoSCoW can transform how your team makes prioritization decisions.

---

Ready to master prioritization? Join the Product Leader Academy community for frameworks, templates, and peer learning.