Course contentsShow
← Software Engineering
Lesson 153 of 1,9334. Requirements EngineeringFree lesson

MoSCoW Method

Using Must-have, Should-have, Could-have, and Won't-have categories to classify requirements by necessity.

MoSCoW Method

You'll learn: How to classify requirements by importance using four simple categories that help teams decide what to build first.

What is MoSCoW?

The MoSCoW Method is a prioritization technique that sorts requirements into four categories based on necessity. The name is an acronym (with vowels added for pronunciation):

  • Must have
  • Should have
  • Could have
  • Won't have (this time)

Understanding Each Category

Must-Have

These are non-negotiable. Without them, the system fundamentally doesn't work or solve the core problem. If you're building a login system, authentication itself is a Must-have.

Should-Have

Important but not critical for launch. The system works without them, but they significantly add value. Think of password reset functionality—valuable, but users can contact support if needed.

Could-Have

Nice-to-haves that improve the experience but can easily be dropped if time runs short. Maybe a profile picture feature in your login system.

Won't-Have (This Time)

Explicitly out of scope for the current release. This prevents scope creep and manages stakeholder expectations. Perhaps social media login integration is interesting, but not now.

Why This Helps

MoSCoW forces honest conversations about priorities. When stakeholders say everything is critical, you can challenge them: "If we only have two weeks, which features literally prevent the system from working?" It creates a shared understanding of trade-offs.

Think of building a house: walls and a roof are Must-haves, insulation is Should-have, a fireplace is Could-have, and a pool is Won't-have (this year).

Key Takeaway: The MoSCoW Method helps teams prioritize requirements by forcing honest categorization into Must/Should/Could/Won't, making scope and trade-off decisions transparent and manageable.