Which technique uses Must Have, Should Have, Could Have, and Won’t Have to prioritize requirements?

Which technique uses Must Have, Should Have, Could Have, and Won’t Have to prioritize requirements?

• A. MoSCoW prioritization
• B. Gantt chart analysis
• C. Risk Register review
• D. RACI matrix

Answer: (A)

The main idea here is prioritizing what the project must deliver by classifying requirements into four categories that guide scope and decisions under constraints. This structured approach, MoSCoW prioritization, helps teams decide what is essential (Must have), what is highly desirable but not critical (Should have), what could be included if time allows (Could have), and what will not be included in the current delivery (Won’t have). Must have items are the minimum set needed for the product to be viable or for the release to be acceptable; without them the project risks failure or an unusable result. Should have items add meaningful value and are important to user needs, but the project can proceed without them if necessary, though with some impact to quality or user satisfaction. Could have items are nice-to-have features that improve the offering but are not essential, and Won’t have items are explicitly out of scope for the current stage, clarifying what will not be built to prevent scope creep. This approach is particularly useful because it surfaces trade-offs early and aligns stakeholders on what’s truly necessary versus optional, helping teams manage time, budget, and resources more effectively. The other options aren’t about prioritizing requirements in this way: a Gantt chart analyzes schedule and sequencing, a Risk Register review focuses on identifying and tracking risks, and a RACI matrix clarifies roles and responsibilities.

The main idea here is prioritizing what the project must deliver by classifying requirements into four categories that guide scope and decisions under constraints. This structured approach, MoSCoW prioritization, helps teams decide what is essential (Must have), what is highly desirable but not critical (Should have), what could be included if time allows (Could have), and what will not be included in the current delivery (Won’t have). Must have items are the minimum set needed for the product to be viable or for the release to be acceptable; without them the project risks failure or an unusable result. Should have items add meaningful value and are important to user needs, but the project can proceed without them if necessary, though with some impact to quality or user satisfaction. Could have items are nice-to-have features that improve the offering but are not essential, and Won’t have items are explicitly out of scope for the current stage, clarifying what will not be built to prevent scope creep.

This approach is particularly useful because it surfaces trade-offs early and aligns stakeholders on what’s truly necessary versus optional, helping teams manage time, budget, and resources more effectively. The other options aren’t about prioritizing requirements in this way: a Gantt chart analyzes schedule and sequencing, a Risk Register review focuses on identifying and tracking risks, and a RACI matrix clarifies roles and responsibilities.