CAPM Business Analysis Frameworks Practice Question
After gathering requirements, the business analyst is prioritizing them based on stakeholder value and implementation complexity. Which tool is commonly used for this purpose?
⚠ Common exam trap
CAPM often tests the confusion between strategic analysis tools (SWOT) and requirements prioritization techniques (MoSCoW), so candidates must recognize that SWOT analyzes organizational position, not requirement value.
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 analysis
MoSCoW analysis (Must have, Should have, Could have, Won't have) is a prioritization technique specifically designed to rank requirements by business value and delivery necessity. It directly addresses the question's need to prioritize based on stakeholder value while considering implementation complexity by forcing stakeholders to categorize requirements into value tiers.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
SWOT analysis
Why it's wrong here
SWOT analysis assesses internal strengths and weaknesses against external opportunities and threats, producing no per-requirement value or complexity ranking. It is tempting because it supports strategic decision-making, and it would be correct when evaluating organisational position before planning, not when prioritising individual requirements on those two criteria.
- ✓
MoSCoW analysis
Why this is correct
MoSCoW analysis classifies requirements as Must, Should, Could or Won't have, forcing stakeholders to weigh value against implementation complexity. This satisfies the stem's prioritisation constraint by producing a ranked, agreed scope rather than an unranked list.
- ✗
Process flow diagram
Why it's wrong here
A process flow diagram maps sequential activities and decision points, capturing no value or complexity ratings for requirements. It is tempting because it clarifies how work currently happens, and it would be correct when modelling as-is or to-be business processes during process analysis, not when ranking requirements on a value-versus-complexity grid.
- ✗
Requirements traceability matrix
Why it's wrong here
A requirements traceability matrix links requirements to their sources, tests and deliverables; it records relationships, not value or complexity scores. It is tempting because it organises requirements, and it would be correct for verifying coverage and managing scope changes, not for plotting requirements against stakeholder value and implementation effort.
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 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.