Linda is the business analyst for her organization and she's working with Joe, a new business analyst, to prioritize requirements. Joe doesn't understand why requirements need to be prioritized; as all requirements are required, they should carry equal weight in the analysis. What should Linda tell Joe as to why requirements must be prioritized?

Prioritization is essential because resources (time, budget, personnel) are finite. It provides a framework for making trade-offs and sequencing work. The goal is to ensure the team focuses on the most critical requirements first (D), maximizing the value delivered at each stage of the project. This ranking is often achieved by evaluating requirements against a set of criteria, such as benefit, penalty, cost, risk, and dependencies, which can be organized into a weighted scale (B). This structured approach helps stakeholders reach a consensus on what is most important and why, moving beyond the assumption that all requirements are equal.

A. This is too narrow. Prioritization considers many factors beyond just cost and schedule, such as value, risk, and dependencies.
C. While stakeholder importance is a consideration, prioritization ranks requirements based on their value and criticality, not solely on who requested them.

- IIBA

A Guide to the Business Analysis Body of Knowledge (BABOK Guide)

version 3

2015

Section 5.3.1

"The purpose of Prioritize Requirements is to rank requirements in order of relative importance."

- IIBA

A Guide to the Business Analysis Body of Knowledge (BABOK Guide)

version 3

2015

Section 5.3.4

"Basis for Prioritization: Benefit

Penalty

Cost

Risk

Dependencies

Time Sensitivity

Stability..."