MoSCoW Prioritization

Definition

MoSCoW Prioritization is a method to prioritize stories (or other elements) in incremental and iterative approaches. MoSCoW (must have, should have, could have, won't have) is used for scope management and provides a way to reach a common understanding on relative importance of delivering a story or other piece of value in the product.

Inputs

• A backlog or list of candidate requirements, stories, or features to be prioritized
• Stakeholder input on business value, urgency, and constraints (time, budget, regulatory)

Outputs

• Each item categorized as Must Have, Should Have, Could Have, or Won't Have (this time)
• A shared, negotiated understanding among stakeholders of what's truly essential versus what's negotiable

When to Use

• Scope negotiation under a fixed timeline or budget, where not everything can be delivered
• Iterative or incremental delivery models (Agile, SAFe) where releases need a clear "must-ship" boundary
• Resolving stakeholder disagreement about relative importance early, before development begins

When Not to Use

• Projects where all requirements are genuinely mandatory (e.g. hard regulatory compliance with no negotiable scope)
• Very small backlogs where simple rank-ordering is clearer than four categories