CAPM Business Analysis Frameworks Practice Question
During a project, multiple stakeholders have conflicting requirements for a new software feature. The business analyst needs to prioritize the requirements to ensure the most critical ones are delivered first. Which technique is most appropriate for prioritizing requirements?
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
✓
MoSCoW
MoSCoW (Must have, Should have, Could have, Won't have) is a prioritization technique that helps categorize requirements based on importance. Brainstorming, interviews, and observation are elicitation, not prioritization, techniques.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
MoSCoW
Why this is correct
MoSCoW sorts requirements into Must have, Should have, Could have and Won't have categories, letting the business analyst rank conflicting stakeholder demands by delivery criticality. This directly satisfies the stem's need to identify which requirements are most critical and deliver them first.
- ✗
Interview
Why it's wrong here
Interview gathers qualitative information from individuals and produces no ranking mechanism, so conflicting stakeholder requirements remain unresolved. It is tempting because it is a core elicitation technique, but it would be correct for understanding needs and context, not for ordering requirements by value, risk or urgency.
- ✗
Brainstorming
Why it's wrong here
Brainstorming generates a broad pool of candidate ideas from participants; it produces no agreed ranking mechanism, so conflicting stakeholder requirements remain unresolved. It is tempting because brainstorming is a legitimate elicitation technique for gathering diverse requirements early, and would be correct when the goal is idea generation rather than prioritisation.
- ✗
Observation
Why it's wrong here
Observation records how users actually perform tasks, yielding behavioural data rather than comparative value judgements, so it cannot rank conflicting requirements by business priority. It is tempting because observation genuinely surfaces unstated needs and workarounds during elicitation, and would be the right choice when validating documented requirements against real practice.
Go deeper
Related to this question
About these practice questions
One of 451 original CAPM practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.