Prioritization tools

Free MoSCoW Prioritization Calculator

Sort a complete release into Must, Should, Could, and Won't. Free, no signup, works in your browser.
Need team input and customer evidence? See the ProductLift workflow →

Interactive release board

Classify your release, not one isolated feature

Start with the examples, add your own requests, then move each item to the category your team can defend.

Must have

Release fails without it

1

Should have

Important, with a workaround

1

Could have

Valuable if capacity remains

1

Won't have

Explicitly outside this release

1

Use the menu on a card to move it between categories.

Must is a test

Ask whether the release still works without the item. If it does, it is not a Must.

Need the method?

Read the practical MoSCoW guide for category tests, workshops and failure modes.

Prefer a spreadsheet?

Download the Excel template for a release review outside the browser.

Other Prioritization Methods

RICE Calculator ICE Calculator WSJF Calculator Kano Model Opportunity Scoring
View all tools →

Frequently Asked Questions

When should I use MoSCoW prioritization? ▼
MoSCoW works best for timeboxed projects where you need to quickly categorize what's essential vs. optional. It's commonly used in Agile sprints, MVP planning, and when you need stakeholder alignment on priorities without complex scoring.
How is MoSCoW different from RICE? ▼
MoSCoW is categorical (4 buckets) while RICE is numerical (scores). MoSCoW is faster and more intuitive but less precise. Use MoSCoW for quick decisions and stakeholder discussions; use RICE when you need data-driven prioritization with clear rankings.
What percentage should each category have? ▼
A common guideline: Must Have should be around 60% of effort, Should Have about 20%, and Could Have the remaining 20%. Won't Have items are explicitly out of scope. If everything is a "Must Have," you need to reassess priorities.
Who created MoSCoW? ▼
MoSCoW was developed by Dai Clegg at Oracle in 1994 and later refined as part of the Dynamic Systems Development Method (DSDM). It's now widely used across Agile methodologies and project management.
What's the difference between "Could Have" and "Won't Have"? ▼
"Could Have" items might get done if time permits - they're desirable nice-to-haves. "Won't Have" items are explicitly agreed to NOT be done in this iteration, though they might be considered for future releases. The distinction helps manage expectations.

Prioritization library

Choose a method, calculate a score, then apply it

This library connects every ProductLift prioritization guide, calculator, template, and product workflow. Start with the framework guide if you do not know which method fits your decision.

Learn the prioritization frameworks Prioritize inside ProductLift

Start and compare

Pick the right route before committing to a scoring model.

RICE

Balance reach, impact, confidence, and effort.

ICE

Score ideas quickly with impact, confidence, and ease.

MoSCoW

Classify requirements by what a release must, should, could, or will not include.

Other methods and tools

Use a visual matrix or a specialized model when simple scoring is not enough.

The faster, easier way to capture user feedback at scale

Join over 5,204 product managers and see how easy it is to build products people love.

from 124+ reviews
ProductLift dashboard preview

Did you know 80% of software features are rarely or never used? That's a lot of wasted effort.

SaaS software companies spend billions on unused features. In 2025, it was $29.5 billion.

We saw this problem and decided to do something about it. Product teams needed a better way to decide what to build.

That's why we created ProductLift - to put all feedback in one place, helping teams easily see what features matter most.

In the last five years, we've helped over 5,204 product teams (like yours) double feature adoption and halve the costs. I'd love for you to give it a try.

Ruben Buijs, Founder
Ruben Buijs

Founder & Digital Consultant