WSJF Prioritization

Purpose

WSJF (Weighted Shortest Job First) helps teams sequence work by economic value. By dividing the Cost of Delay by the Job Size, the highest-scoring items deliver the most value per unit of time, optimizing the portfolio for flow and ROI.

At a glance

How to run

1. Explain the formula (5 min) — WSJF = Cost of Delay / Job Size. Cost of Delay = User-Business Value + Time Criticality + Risk Reduction/Opportunity Enablement.
2. Score Cost of Delay components (30 min) — For each item, use relative scoring (Fibonacci) to rate:

• User-Business Value: How much does the user or business benefit?
• Time Criticality: How much does delay cost?
• Risk Reduction / Opportunity Enablement: Does it reduce risk or unlock future opportunities?

1. Score Job Size (10 min) — Estimate the relative effort using the same Fibonacci scale.
2. Calculate WSJF (5 min) — Sum the three Cost of Delay components, divide by Job Size.
3. Rank and discuss (10 min) — Sort by WSJF descending. Discuss surprises. Adjust if strategic context demands.

Materials needed

• WSJF scoring spreadsheet template
• List of features/epics to prioritize
• Fibonacci cards for relative scoring
• Calculator or spreadsheet

Pitfalls & common mistakes

• Absolute instead of relative scoring — Always use relative scales; the smallest item gets a 1 and others are compared to it.
• Ignoring time criticality — Some features have deadlines (regulatory, seasonal); this dimension captures that.
• Job Size = 0 — Avoid division by zero; the smallest job is 1, not 0.
• HiPPO override — The score should inform the conversation, not be overridden without documented rationale.

Inclusion & accessibility

• Share feature descriptions in advance.
• Use a shared spreadsheet everyone can edit.
• Use simultaneous reveal (as in card-based estimation) for each scoring dimension to prevent anchoring.

Variations

• WSJF with confidence — Add a confidence multiplier to the Cost of Delay.
• Simplified WSJF — Use only Cost of Delay / Job Size without breaking CoD into sub-components.
• WSJF + RICE — Cross-reference WSJF ranking with RICE scoring for validation.

When NOT to use this

• For a single team with a small backlog — simpler methods like dot voting suffice.
• If the organisation lacks data on business value and urgency — the scores will be arbitrary.

Source & further reading

• Reinertsen, D. (2009). *The Principles of Product Development Flow*. Celeritas.
• Leffingwell, D. (2020). *SAFe Reference Guide*. Scaled Agile Press.