How to Prioritize Features with MoSCoW Method (Step-by-Step)
MoSCoW (Must/Should/Could/Will-not) is straightforward and effective for scope management within a release or sprint. It is simpler than RICE and great for stakeholder alignment.
This guide covers correct application for product prioritization.
Step-by-step guide
Step 1: Define Must Have
Non-negotiable. Without them, the release fails. Should be 60% of scope at most. Test: "What happens if we ship without this?"
Step 2: Define Should Have
Important but not critical. First candidates for scope cuts. Plan for 20%.
Step 3: Define Could Have
Desirable but easily deferred. First to be cut when time runs short. Plan for 20%.
Step 4: Define Will Not Have
Explicitly out of scope. Include at least 3 items stakeholders have requested but you chose to defer.
Step 5: Get stakeholder agreement
Present categorization before development. When someone wants to add a feature, ask: "Which Must Have should we drop?"
Common mistakes
Everything is Must Have
Force the ratio: 60% Must, 20% Should, 20% Could. The discipline is in the constraints.
No Will Not Haves
An empty list means scope is not defined. Every exercise should produce at least 3.
MoSCoW for ongoing backlogs
MoSCoW works for time-boxed releases, not ongoing backlogs. Use RICE for ongoing prioritization.
Tips
- Use MoSCoW in sprint planning for sprint items
- Review Will Not Have list at release end for next cycle
- Combine with estimation: Must Haves must fit 60% of capacity
How Vantage helps
Vantage generates requirements with priority levels mapping to MoSCoW: P0 (Must Have), P1 (Should Have), P2 (Could Have), P3 (Will Not Have this release).