- A
Kano
Correct: Kano model categorizes requirements based on satisfaction.
- B
SWOT
Why wrong: SWOT is used for strategic analysis, not prioritization.
- C
Fishbone
Why wrong: Fishbone diagram is for root cause analysis.
- D
MoSCoW
Correct: MoSCoW is a prioritization method.
- E
Risk Register
Why wrong: Risk register documents risks, not prioritization techniques.
Quick Answer
The answer is MoSCoW and Kano analysis. MoSCoW, which stands for Must have, Should have, Could have, and Won’t have, is a straightforward prioritization framework that helps stakeholders agree on essential versus nice-to-have requirements, directly supporting scope management. Kano analysis, on the other hand, classifies features based on how they impact customer satisfaction—categorizing them as basic, performance, or excitement attributes—so you can prioritize what delivers the highest satisfaction relative to investment. On the CAPM exam, these two techniques are frequently tested together because they represent both a simple consensus-driven approach and a more customer-centric analytical method. A common trap is confusing Kano analysis with quality metrics or assuming MoSCoW is only for software projects; remember, MoSCoW applies to any project’s requirements prioritization. For a memory tip, think “MoSCoW sorts the musts, Kano maps the joy.”
CAPM Business Analysis Frameworks Practice Question
This CAPM practice question tests your understanding of business analysis frameworks. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Which TWO of the following are commonly used techniques for requirements prioritization?
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 is a technique that categorizes features based on how they affect customer satisfaction, distinguishing between basic, performance, and excitement attributes. This helps prioritize requirements by focusing on features that deliver the highest satisfaction relative to investment, making it a standard tool in business analysis for the CAPM exam.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
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.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
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.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Risk Register
Why it's wrong here
Risk register documents risks, not prioritization techniques.
Common exam traps
Common exam trap: answer the scenario, not the keyword
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.
Detailed technical explanation
How to think about this question
Kano analysis classifies requirements into five categories: Must-be (basic expectations), One-dimensional (performance features that increase satisfaction linearly), Attractive (delighters that greatly increase satisfaction), Indifferent (features that do not affect satisfaction), and Reverse (features that cause dissatisfaction). MoSCoW prioritization (Must have, Should have, Could have, Won't have) is used in agile and iterative development to negotiate scope and manage stakeholder expectations, often applied during backlog refinement. Both techniques rely on stakeholder input and are formally recognized in the BABOK guide for business analysis planning and monitoring.
KKey Concepts to Remember
- Read the scenario before looking for a memorised answer.
- Find the constraint that changes the correct option.
- Eliminate answers that are true in general but not in this case.
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A practitioner preparing for the CAPM exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Business Analysis Frameworks — study guide chapter
Learn the concepts, then practise the questions
- →
Business Analysis Frameworks practice questions
Targeted practice on this topic area only
- →
All CAPM questions
503 questions across all exam domains
- →
Certified Associate in Project Management CAPM study guide
Full concept coverage aligned to exam objectives
- →
CAPM practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related CAPM practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Agile Frameworks and Methodologies practice questions
Practise CAPM questions linked to Agile Frameworks and Methodologies.
Project Management Fundamentals and Core Concepts practice questions
Practise CAPM questions linked to Project Management Fundamentals and Core Concepts.
Predictive Plan-Based Methodologies practice questions
Practise CAPM questions linked to Predictive Plan-Based Methodologies.
Business Analysis Frameworks practice questions
Practise CAPM questions linked to Business Analysis Frameworks.
CAPM fundamentals practice questions
Practise CAPM questions linked to CAPM fundamentals.
CAPM scenario practice questions
Practise CAPM questions linked to CAPM scenario.
CAPM troubleshooting practice questions
Practise CAPM questions linked to CAPM troubleshooting.
Practice this exam
Start a free CAPM practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this CAPM question test?
Business Analysis Frameworks — This question tests Business Analysis Frameworks — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Kano — Kano analysis is a technique that categorizes features based on how they affect customer satisfaction, distinguishing between basic, performance, and excitement attributes. This helps prioritize requirements by focusing on features that deliver the highest satisfaction relative to investment, making it a standard tool in business analysis for the CAPM exam.
What should I do if I get this CAPM question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Same concept, more angles
1 more ways 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.
Last reviewed: Jun 30, 2026
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.