CAPM Practice: Determine how to gather requirements

Requirements prioritization ensures that if time or budget runs short, the most important requirements are delivered first. It drives iteration planning in agile and phase planning in predictive, maximizing value delivery within constraints.

**Why not B:** Prioritizing requirements solely by technical complexity focuses on the solution perspective rather than the business perspective. While technical complexity may influence implementation planning, prioritization should primarily consider business value, stakeholder needs, risk, and strategic alignment to ensure the most important requirements are addressed first.

**Why not C:** Determining which stakeholder reviews a requirement is a responsibility assignment activity, not a prioritization technique. Prioritization involves ranking requirements based on their relative importance and urgency to guide development sequencing and resource allocation decisions.

**Why not D:** Ordering requirements alphabetically has no analytical or strategic basis. Effective prioritization requires evaluating each requirement against meaningful criteria such as business value, cost, risk, dependencies, and time sensitivity to make informed trade-off decisions.