MoSCoW Prioritization Tool
Categorize your features into Must Have, Should Have, Could Have, and Won't Have. A simple but powerful way to align your team on priorities.
MoSCoW Categories
Add Features
Continue your workflow
What is MoSCoW Prioritization?
MoSCoW sorts features into four categories: Must Have (non-negotiable for launch), Should Have (important but not critical), Could Have (nice-to-have if time permits), and Won't Have (explicitly out of scope). Unlike scoring frameworks like RICE or ICE, MoSCoW produces categories, not ranked scores. This makes it better for stakeholder alignment sessions. Learn the full method in our MoSCoW framework guide.
How to Use This Tool
- Add your features. Enter every feature, requirement, or user story you're considering for the release.
- Drag to categorize. Sort each item into Must, Should, Could, or Won't Have.
- Validate capacity. Must-haves should not exceed 60% of your team's sprint capacity. Use the sprint planning calculator to check.
- Share with stakeholders. Export your categorized list for alignment meetings.
FAQ
When should I use MoSCoW instead of RICE?
MoSCoW works best in collaborative sessions where you need fast stakeholder buy-in. RICE works better when you need to defend a ranking with data. Many teams use MoSCoW for sprint planning and RICE for quarterly roadmap prioritization. See our comparison guide for details.
What percentage of features should be Must-Haves?
Keep Must-haves under 60% of your total capacity. If everything is a Must-have, the framework isn't working. The value of MoSCoW is forcing the hard conversation about what can wait. For a deeper look at capacity constraints, use the weighted scoring calculator to add effort estimates to your priorities.
For a visual approach to prioritization, try the value-effort matrix. For customer-driven categorization, the Kano analyzer maps features by satisfaction impact.