7.2 Value Prioritization Techniques

7.2 Value Prioritization Techniques

In traditional project management, scope is often treated as fixed, while time and cost are variable. In agile project management, time and cost are fixed (via timeboxed iterations and stable cross-functional teams), while scope is variable. Therefore, the order in which backlog items are developed dictates project success.

Value Prioritization is the process of ranking Product Backlog items to maximize return on investment (ROI), minimize risk, and deliver early business value. The Product Owner holds ultimate accountability for prioritization, but relies on quantitative models and stakeholder collaboration tools to make objective decisions.

---

1. MoSCoW Prioritization

Originally developed as part of the Dynamic Systems Development Method (DSDM), MoSCoW Prioritization categorizes requirements into four distinct levels of priority:

PMI-ACP EXAM TIP: MoSCoW acts as a risk buffer. By capping "Must Haves" at 60% of capacity, the team builds in a 40% contingency (Shoulds + Coulds) to absorb unexpected complexity without missing the hard release deadline.

---

2. Noriaki Kano Model

Created by Professor Noriaki Kano, the Kano Model maps customer preference against feature execution to understand what truly drives user satisfaction.

The model classifies requirements into five distinct categories:

1. Basic / Must-Be Quality: Mandatory baseline expectations (e.g., a hotel room having clean hot water or a banking app allowing logins). Their presence does not increase satisfaction, but their absence causes severe customer dissatisfaction.
2. Performance / One-Dimensional Quality: Features with linear satisfaction response (e.g., smartphone battery life or processing speed). More is directly better.
3. Delighters / Attractive Quality: Unexpected, novel features (e.g., free high-end noise-canceling headphones with a hotel booking). Absence causes zero dissatisfaction (users didn't expect it), but presence creates high satisfaction and delight.
4. Indifferent: Features that users simply do not care about regardless of implementation quality.
5. Reverse: Features that actively annoy users when present (e.g., intrusive auto-playing video popups).

Feature Decay Dynamics

Over time, features migrate downward through Kano categories. Yesterday's Delighter (e.g., Wi-Fi on an airplane) becomes today's Performance expectation and tomorrow's Basic Must-Be requirement.

---

3. Weighted Shortest Job First (WSJF)

Popularized by Don Reinertsen and integrated into the Scaled Agile Framework (SAFe®), WSJF is a quantitative prioritization algorithm designed to sequence jobs to achieve the maximum economic benefit.

$\text{WSJF} = \frac{\text{Cost of Delay (CoD)}}{\text{Job Size (Duration)}}$

Calculating Cost of Delay (CoD)

Cost of Delay is calculated by adding three relative business components (typically scored on a Fibonacci scale: 1, 2, 3, 5, 8, 13, 20):

$\text{Cost of Delay} = \text{User-Business Value} + \text{Time Criticality} + \text{Risk Reduction / Opportunity Enablement (RR/OE)}$

WSJF Calculation Example

Key Insight: Feature A delivers a higher WSJF score than Feature B because Feature B's massive job size (13) dilutes its return rate, whereas Feature A delivers rapid value quickly.

---

4. Karl Wiegers' Relative Weighting Method

Software engineering expert Karl Wiegers introduced a relative prioritization matrix that balances business value against development effort and technical risk.

$\text{Priority Score} = \frac{\text{Relative Value \%}}{\text{Relative Cost \%} \times \text{Cost Weight} + \text{Relative Risk \%} \times \text{Risk Weight}}$

Operational Steps:

1. List proposed features.
2. Estimate Relative Benefit (value to customer if present) and Relative Penalty (negative impact if absent) on a scale of 1 to 9.
3. Calculate Total Value = Benefit + Penalty.
4. Estimate Relative Cost (1-9 scale) and Relative Technical Risk (1-9 scale).
5. Convert Values, Costs, and Risks into percentage contributions of the column totals.
6. Divide Value % by the combined weighted Cost % and Risk % to calculate the final priority index.

---

5. Collaborative Group Prioritization Methods

When managing divergent opinions across business executives, Product Owners leverage consensus-building prioritization games:

100-Point Method (Monopoly Money)

Each stakeholder is given a fixed budget of 100 points (or $100 in fake "Monopoly money") to distribute across a list of candidate user stories.

• Stakeholders can allocate all 100 points to a single critical feature or spread them across multiple stories.
• Summing points across all stakeholders exposes true organizational priorities and prevents the common trap where stakeholders mark every request as "High Priority".

Pairwise Comparison (Analytic Hierarchy Process)

When ranking items is highly contentious, the team conducts a systematic pairwise tournament. Every backlog item is compared directly against every other item in a one-on-one comparison:

$\text{Total Comparisons} = \frac{N(N - 1)}{2}$

For 5 items (A, B, C, D, E), 10 head-to-head comparisons are made. The item winning the highest number of pairwise choices ranks #1 on the backlog.