CBAP · Question #241
Your organization uses the MoSCoW approach to requirements prioritization. What does MoSCoW mean?
The correct answer is B. Must, Should, Could, Won't. MoSCoW is a requirements prioritization technique that categorizes requirements into four priority levels to help teams and stakeholders agree on what to deliver.
Question
Your organization uses the MoSCoW approach to requirements prioritization. What does MoSCoW mean?
Options
- AMust, Should, Could, Would
- BMust, Should, Could, Won't
- CMission, Schedule, Cost, Willingness
- DMust not, Should not, Could not, Will not
How the community answered
(35 responses)- A17% (6)
- B71% (25)
- C9% (3)
- D3% (1)
Why each option
MoSCoW is a requirements prioritization technique that categorizes requirements into four priority levels to help teams and stakeholders agree on what to deliver.
'Would' is not a valid MoSCoW category - the correct final term is 'Won't have,' which captures intentional deferral rather than a conditional desire.
MoSCoW stands for Must have, Should have, Could have, and Won't have (this time) - these four categories allow stakeholders to separate non-negotiable requirements from desirable ones and those intentionally excluded from the current scope. The 'Won't have' category is critical because it explicitly defers items rather than permanently eliminating them, managing stakeholder expectations.
Mission, Schedule, Cost, and Willingness is a fabricated set of terms with no relation to the MoSCoW prioritization framework.
MoSCoW categories represent affirmative priority levels for inclusion or deferral, not a set of prohibitions - inverting each term contradicts the framework's purpose entirely.
Concept tested: MoSCoW requirements prioritization technique
Source: https://www.agilealliance.org/glossary/moscow/
Topics
Community Discussion
No community discussion yet for this question.