CAPM Business Analysis Frameworks Practice Question
Which TWO of the following are commonly used techniques for requirements prioritization?
⚠ Common exam trap
PMI often tests the distinction between tools used for analysis versus prioritization, so candidates may confuse SWOT (a strategic analysis tool) or Fishbone (a root cause analysis tool) as valid prioritization techniques because they are also used in business analysis contexts.
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
✓
Kano
Kano analysis categorizes features based on how they affect customer satisfaction (basic, performance, excitement) to prioritize by impact. MoSCoW (Must have, Should have, Could have, Won't have) classifies requirements by necessity and stakeholder agreement. Both are standard prioritization techniques in business analysis for the CAPM exam.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Kano
Why this is correct
Correct: Kano model categorizes requirements based on satisfaction.
- ✗
SWOT
Why it's wrong here
SWOT is used for strategic analysis, not prioritization.
- ✗
Fishbone
Why it's wrong here
Fishbone diagram is for root cause analysis.
- ✓
MoSCoW
Why this is correct
Correct: MoSCoW is a prioritization method.
- ✗
Risk Register
Why it's wrong here
Risk register documents risks, not prioritization techniques.
Go deeper
Related to this question
About these practice questions
One of 487 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 →
Same concept, more angles
1 more way this is tested on CAPM
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. 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?
medium- ✓ A.MoSCoW
- B.Interview
- C.Brainstorming
- D.Observation
Why A: 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.
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.