4.3 Prioritize Requirements

4.3 Prioritize Requirements

Core Purpose and BABOK v3 Context

In any non-trivial business analysis initiative, stakeholders generate far more requirement requests than available time, budget, or engineering capacity can fulfill. Task 13: Prioritize Requirements is the process of evaluating and ranking requirements based on their relative importance, value, cost, risk, and delivery urgency.

Prioritization is not a one-time event conducted at project kickoff; it is an iterative, dynamic activity. As technical feasibility is uncovered, market conditions evolve, or regulatory deadlines shift, BAs must continuously re-evaluate requirement priorities to ensure the implementation team builds the highest-value capabilities first.

---

Eight Fundamental Prioritization Factors

BABOK v3 specifies eight foundational factors that BAs must evaluate when establishing requirement priorities. Exam questions frequently test your ability to select the dominant factor in a given scenario:

---

Deep-Dive into Prioritization Techniques

A CBAP must be proficient in applying multiple formal prioritization frameworks depending on methodology (Agile vs. Waterfall) and organizational context:

1. MoSCoW Method

Categorizes requirements into four distinct buckets based on strict operational rules:

• Must Have: Non-negotiable capabilities without which the solution is completely non-viable or unsafe for production use. If a Must Have is omitted, the release fails.
• Should Have: High-value capabilities that are critical, but a manual workaround or temporary alternative exists for short-term release.
• Could Have: Desirable features ("nice-to-haves") that are included only if time and budget permit after all Must and Should haves are satisfied.
• Won't Have (this time): Valid requirement requests explicitly agreed to be out of scope for the current release baseline, reserved for future iterations.

⚠️ MoSCoW Rule of Thumb: A balanced project baseline should allocate no more than 60% of total team capacity to Must Haves, leaving 40% buffer for Should and Could Haves to absorb velocity fluctuations.

2. Weighted Shortest Job First (WSJF)

Derived from SAFe (Scaled Agile Framework), WSJF prioritizes requirements based on economic value flow by calculating: $\text{WSJF Score} = \frac{\text{Cost of Delay (CoD)}}{\text{Job Size / Duration}}$ Where Cost of Delay = User/Business Value + Time Sensitivity + Risk Reduction/Opportunity Enablement Value. Requirements yielding the highest WSJF score are scheduled first, optimizing ROI and minimizing economic loss.

3. Kano Model Analysis

Classifies requirements based on customer perception and satisfaction impact:

• Basic / Must-Be Attributes: Dissatisfiers if missing, but taken for granted if present (e.g., brakes on a car, login button working). Adding more does not increase satisfaction.
• Performance / One-Dimensional Attributes: Linear relationship—more is better (e.g., battery life, processing speed).
• Excitement / Attractive Attributes: Unexpected delights that create high customer delight (e.g., AI auto-completion of expense receipts). Absence does not cause dissatisfaction.

4. Timeboxing and Voting

• Dot Voting: Stakeholders are given a fixed number of dots (e.g., 5 dots) to allocate across displayed requirement cards.
• 100-Dollar Allocation: Stakeholders spend a hypothetical $100 budget across competing requirements, revealing true monetary preference.

---

Managing Stakeholder Friction & Prioritization Conflicts

Prioritization inevitably uncovers conflicting stakeholder agendas. The Business VP wants revenue features, the Chief Risk Officer demands compliance controls, and the CTO demands technical debt refactoring. To resolve friction:

1. Establish Objective Criteria Beforehand: Agree on weighted prioritization factors (e.g., 40% Benefit, 30% Compliance, 30% Cost) before evaluating individual features.
2. Expose Trade-Off Transparency: Use visual models showing how adding a new "Must Have" automatically pushes lower-ranked items into "Won't Have".
3. De-escalate HiPPO Dominance: Prevent the "Highest Paid Person's Opinion" from overriding data by applying quantitative scoring frameworks (WSJF or Cost-Benefit Analysis).

---

BACCM Connections in Prioritization

• Change: Determines the sequence of solution capabilities delivered over time.
• Need: Prioritizes requirements that address the most urgent or severe business gaps.
• Solution: Shapes the incremental release architecture of the solution.
• Stakeholder: Balances competing priorities across diverse stakeholder groups.
• Value: Directly aligns development effort with maximum business value realization.
• Context: Adjusts priorities in response to shifting economic, regulatory, or technical environments.

---

Worked Example: E-Commerce Mobile App Prioritization

Scenario: An online retailer has a 3-month release window before Black Friday. The product team has 5 major feature requests but capacity to build only 3.

Prioritization Evaluation Matrix:

Outcome: Using WSJF, the team selects PCI Patch (WSJF 10.0), Apple Pay (WSJF 4.5), and Order Tracking (WSJF 3.0), deferring AR Preview to Q1. This delivers high compliance protection and $1.4M in holiday mobile conversion growth.

---

CBAP Exam Tips & Common Pitfalls

💡 Exam Tip: When a regulatory mandate with explicit financial penalties is present in a scenario, Regulatory/Penalty almost always overrides commercial benefit when determining the top priority item.

⚠️ Common Trap: Watch out for scenarios where stakeholders mark every requirement as "Must Have." On the exam, the correct BA response is to facilitate a re-evaluation using formal trade-off techniques (like 100-Dollar Allocation or forced ranking), not to accept 100% Must Have scope.