Overview
WSJF prioritises work by dividing Cost of Delay by job size (duration). It ensures short, high-value items are completed before long, lower-value ones. In SAFe, CoD is scored as Business Value + Time Criticality + Risk Reduction.
When to Use
SAFe environments and PI planning. Also useful for sequencing any large backlog with mixed urgency and size.
How to Apply It
- Score BUSINESS VALUE (1-10): How much value does this deliver?
- Score TIME CRITICALITY (1-10): How much does waiting cost? Hard deadline?
- Score RISK REDUCTION (1-10): Does this reduce risk or unlock future work?
- Cost of Delay = Business Value + Time Criticality + Risk Reduction
- Estimate JOB SIZE using relative sizing (Fibonacci: 1, 2, 3, 5, 8, 13)
- WSJF = Cost of Delay ÷ Job Size — rank by descending score
Examples in Practice
🎵 Spotify
Fixing a free-tier ad load bug: BV=7, TC=9, RR=5. CoD=21. Size=2. WSJF=10.5. Building a new podcast discovery feed: BV=8, TC=3, RR=4. CoD=15. Size=8. WSJF=1.9. The bug fix has 5x the WSJF score despite feeling less strategically important. It goes first.
📊 Trade Surveillance
Please contact the author for more information on these examples at linkedin.com/in/kshitijrege
Common Pitfalls
- Score inflation — teams score everything 10/10 to promote their favourite item
- Ignoring dependencies — WSJF alone doesn't account for sequencing constraints
- Using it mechanically without qualitative discussion about the assumptions behind scores
Origin
Don Reinertsen, implemented in SAFe
2009
Further Reading
- Principles of Product Development Flow — Reinertsen
- SAFe Distilled — Knaster & Leffingwell
Related Frameworks