---
description: Categorize requirements as Must, Should, Could, or Won't have
---

# MoSCoW Method

Classify requirements into four priority buckets to reach consensus on scope. Use when negotiating scope with stakeholders or planning a release with limited resources.

## Steps

1. **List all requirements** — gather features, stories, or tasks for the release.
2. **Must Have** — requirements that are non-negotiable; without them the release fails.
3. **Should Have** — important but not critical; painful to leave out but the release still works.
4. **Could Have** — nice-to-have; include only if time and budget allow.
5. **Won't Have (this time)** — explicitly agreed to be out of scope for this release.
6. **Validate** — ensure Must Haves do not exceed ~60% of capacity; adjust if needed.

## Output Format

A four-column table (Must / Should / Could / Won't) listing each requirement, with a summary showing the percentage of effort allocated to each category.