MoSCoW Prioritization Tool

MoSCoW is an acronym: Must Have, Should Have, Could Have, and Won't Have. The lowercase 'o's are just there to make the word pronounceable. Each category represents a different commitment level for the current release or planning window.

MoSCoW originated in the Dynamic Systems Development Method (DSDM) in the 1990s and has since become one of the most widely used prioritization frameworks in product and project management. It is popular because it is simple to explain and surfaces hard tradeoffs quickly.

Ask: if we removed this item, would the release still ship and still deliver its core promise? If yes, it is at most a Should Have. Must Have means the release fails without it — true minimum viable functionality. Most teams over-stuff the Must Have column the first time they try MoSCoW; recategorizing forces healthy debate.

Disagreement here is the point of the exercise. The fastest way through is to ask each person to defend why removing the item would make the release fail — not just be worse, but actually fail. If they can articulate that, it is a Must. If the worst case is 'launch without it but ship in a follow-up,' it is a Should. Capture the rationale in the notes field so the decision survives the meeting.

Won't Have means 'not in this release / planning window' — not 'never.' It is an explicit deferral that prevents the item from sneaking back in mid-release. Document Won't Have items so you can revisit them in the next planning round; it is one of the most underused MoSCoW categories.

Use MoSCoW for release scope decisions where the question is 'does this go in or not?' — particularly for fixed-date releases. Use RICE when you need to compare and rank a long backlog against each other on a continuous score. Many teams use both: RICE to rank candidates, then MoSCoW to draw the line for what makes the release.