CAPM Business Analysis Frameworks Practice Question
A business analyst is using the MoSCoW technique to prioritize requirements. A feature is determined to be important but not critical for the first release. How should it be categorized?
⚠ Common exam trap
CAPM often tests the confusion between 'Should have' and 'Could have'—candidates must remember that 'Should have' is important but not critical, while 'Could have' is merely desirable.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Should have
In MoSCoW prioritization, 'Should have' represents requirements that are important but not critical for the first release; they can be worked around if omitted, but are high priority. 'Must have' is reserved for critical, non-negotiable features. Therefore, a feature that is important but not critical is categorized as 'Should have'.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Could have
Why it's wrong here
Could have denotes desirable but optional items, lower than important-but-not-critical features, which fall under Should have. It is tempting because Could have sounds like a reasonable middle ground, but MoSCoW places importance above mere desirability.
- ✓
Should have
Why this is correct
MoSCoW's Should-have category covers requirements that are important and expected but not vital for the first release. This matches the stem exactly: the feature matters yet can be deferred without breaking the initial delivery, unlike Must-have items.
- ✗
Must have
Why it's wrong here
Must have denotes requirements critical for the first release; an important-but-not-critical feature belongs in Should have. It is tempting because Must have sounds like the strongest priority, yet MoSCoW reserves it for items whose absence makes the release unviable.
- ✗
Won't have
Why it's wrong here
The MoSCoW technique reserves "Won't have" for features explicitly excluded from the current delivery timeline, not merely deferred. This feature is important for the first release, meaning it must be delivered then, so "Won't have" incorrectly removes it from scope. It is tempting because "Won't have" genuinely applies to low-priority items deliberately omitted from a release; if the feature were truly optional and could be dropped without affecting the minimum viable product, this category would be correct.
Go deeper
Related to this question
About these practice questions
Courseiva writes every CAPM question from scratch — 451 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official PMI exam blueprint
This CAPM practice question is part of Courseiva's free PMI certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CAPM exam.