CAPM Practice: Determine how to gather requirements

MoSCoW categorizes requirements by priority: Must have (non-negotiable), Should have (high value but not essential), Could have (nice to have), Won't have (out of scope for this release). This helps teams make scope decisions when constrained by time or budget.

**Why not A:** "Monthly, Sometimes, Occasionally, When needed" is a fabricated expansion of the MoSCoW acronym. The actual letters stand for Must have, Should have, Could have, and Won't have (this time). This incorrect option confuses the technique with a scheduling or frequency concept, which is unrelated to requirements prioritization.

**Why not C:** MoSCoW prioritization has nothing to do with the Russian city of Moscow. The name is a mnemonic acronym created by Dai Clegg while working at Oracle, designed to categorize requirements by priority: Must have, Should have, Could have, and Won't have. The capitalized letters M, S, C, and W form the framework, with the lowercase "o"s added for readability.

**Why not D:** "Measure, Order, Select, Consider, Omit, Worth it" is an invented expansion that does not correspond to the MoSCoW technique. The actual framework has four priority categories (Must, Should, Could, Won't), not six. This fabricated version also suggests a sequential process, whereas MoSCoW is a classification scheme for prioritizing requirements.