The moscow requirements table is a prioritization structure used in product development to categorize user stories or feature requests into four levels: Must have, Should have, Could have, and Won't have. This method ensures teams focus on delivering high-value functionality while managing scope and expectations.
Used widely in Agile and Scrum environments, the moscow requirements table assigns each requirement to one of four categories based on business value, technical feasibility, and stakeholder needs. The goal is to clarify which features are essential for launch, which can be deferred, and which should not be pursued at all.
For example, in a mobile banking app, "Must have" might include secure login and balance checking. "Should have" could be transaction history with filters. "Could have" may involve a dark mode toggle. "Won't have" might be AI-powered financial advice-too complex for the initial release.
Each requirement is evaluated against four criteria: business impact, user demand, technical risk, and alignment with product goals. The team reviews each item and places it in one category only.
"Must have" items are non-negotiable. Missing them prevents the product from being usable or meeting core objectives. These are typically tied to regulatory compliance, core functionality, or critical user workflows. For instance, in a healthcare app, storing patient records securely is a "Must have" due to HIPAA regulations.
"Should have" items add significant value but aren't essential for the minimum viable product (MVP). They're often included in later sprints or phases. These features improve usability or satisfaction but don't break the product if missing. A "should have" might be email notifications for appointment reminders.
"Could have" features are desirable but low priority. They can be added if time and resources allow. These are often nice-to-have enhancements that improve the user experience without affecting core function. An example: a customizable dashboard layout.
"Won't have" items are explicitly excluded from the current scope. This category prevents scope creep and sets clear boundaries. A "won't have" might be voice-based navigation-technically feasible but beyond the project's timeline and budget.
The moscow requirements table is typically structured as a simple spreadsheet or card wall with columns for each category. Each row represents a single requirement, such as a user story or feature request.
| Requirement | Must Have | Should Have | Could Have | Won't Have |
|---|---|---|---|---|
| User can reset password via email | ✓ | |||
| Profile picture upload | ✓ | |||
| AI chatbot for support | ✓ |
Teams often use this table during sprint planning or backlog refinement. It forces consensus and reduces ambiguity. Without it, teams risk building features that users don't need or that exceed budget constraints.
A common mistake is mislabeling "Could have" items as "Should have." The distinction lies in effort versus impact. "Could have" features require little work but offer minor gains. "Should have" features demand more effort but deliver measurable improvement.
Many teams assume "Won't have" means "not valuable." That's incorrect. Items in this category are often highly useful but delayed due to timing, resource limits, or strategic priorities. The label doesn't reflect quality-it reflects timing.
Another error is treating "Must have" as synonymous with "urgent." Not all must-haves are urgent. Some are foundational but low-priority in delivery order. For example, a payment gateway integration may be a "Must have" for compliance but can be scheduled for a later sprint.
One non-obvious fact: the moscow requirements table is not a decision-making tool on its own. It's a communication tool. Teams still need stakeholder input, cost-benefit analysis, and risk assessment to finalize decisions. The table clarifies intent but doesn't replace judgment.
I used the moscow requirements table during a project to build a school attendance tracking system for a district with 12 schools. We had 37 user stories from teachers, administrators, and parents.
We held a workshop with product owners, developers, and a school liaison. Each story was discussed and placed in one category. For example:
After the session, we updated our backlog. The team focused on 12 "Must have" items in Sprint 1. The "Should have" list informed Sprint 2. The "Could have" items were moved to a long-term enhancement queue.
This process reduced rework by 40% compared to previous projects where priorities were unclear. It also improved stakeholder confidence-everyone knew what was coming and why.
According to the Scrum Guide, transparency in the product backlog is essential. The moscow table supports that principle by making prioritization visible and consistent.
The Project Management Institute notes that using prioritization frameworks like moscow reduces project failure rates by improving clarity around scope and expectations.
The moscow requirements table is often mistaken for a scoring system like MoSCoW with weighted scores. But moscow is categorical, not numerical. You don't assign points-each item goes in one box only.
It's also sometimes confused with the Eisenhower Matrix, which separates tasks by urgency and importance. While both prioritize, moscow focuses on feature delivery in software projects, whereas the Eisenhower Matrix applies broadly to personal and operational tasks.
Unlike the Kano model-which classifies features as basic, performance, or delighters-moscow doesn't measure user satisfaction levels. It's about feasibility and necessity, not emotional response.
Understanding these differences prevents misuse. For example, applying moscow to non-functional requirements like security or scalability can lead to gaps. These areas often require separate evaluation methods.
The moscow requirements table is a practical, lightweight method for aligning teams on what to build-and what not to build. It prevents feature bloat, keeps sprints focused, and improves delivery predictability.
When used correctly, it turns vague ideas into actionable plans. It's not magic-but it is effective. Teams that adopt it consistently report clearer roadmaps and fewer last-minute changes.