MoSCoW prioritization

noun

MoSCoW prioritization classifies requirements as Must have, Should have, Could have or Won't have this time, making clear what is essential and what can wait.

We use MoSCoW prioritization to decide which features the first version must include.

MoSCoW stands for Must have, Should have, Could have and Won't have this time. The lowercase o's have no separate meaning; they make the abbreviation pronounceable as Moscow. Teams use the method to prioritize requirements, features or tasks for an agreed phase or Glossary · In briefreleaseA release is an identifiable software version prepared to be made available to users. It brings together one or more checked changes.Read more.

The four categories

  • Must have: essential for a usable result. Without a must-have, the version is not ready.
  • Should have: important and valuable, but can temporarily be handled another way or postponed.
  • Could have: desirable if time and budget allow, without the result depending on it.
  • Won't have this time: deliberately excluded from the current Glossary · In briefscopeScope defines the boundaries of a project or assignment: which goals, activities and results are included and which are excluded.Read more. This does not mean the idea will never be implemented.

Each category applies to a particular period or version. A feature classified as a won't-have now can become a must-have in the next phase.

Prioritizing a feasible scope

Start with a shared understanding of the goal and minimum outcome. For each item, discuss what would happen if it were missing. This helps distinguish genuine must-haves from strong preferences. Record the category on the Glossary · In briefbacklogA backlog is an ordered, evolving list of work for a product or project. Its order helps a team decide what to investigate or implement first.Read more and check dependencies: a small technical prerequisite may be essential for a visible feature.

MoSCoW prioritization does not automatically identify the best choice. The team and client must justify the categories and reconsider them when schedules, budgets or insights change. Clear Glossary · In briefacceptance criteriaAcceptance criteria are agreed, testable conditions that a product, feature or change must meet to be accepted.Read more then help determine when a must-have or should-have is actually complete.