Weighted Shortest Job First (WSJF)
Weighted Shortest Job First (WSJF) is a prioritization model that sequences work by dividing its cost of delay by the duration or size of the job. Work that is both valuable to deliver soon and quick to finish rises to the top. It comes from Don Reinertsen's economics of product development flow and is best known today as the prioritization method of the Scaled Agile Framework (SAFe).
How WSJF Works
The core formula is simple:
WSJF = Cost of Delay ÷ Job Duration
Cost of delay is the value lost for each unit of time the work is not delivered. When a team can only do one thing at a time, doing the job with the highest cost of delay per unit of duration first minimizes the total value lost while everything else waits in the queue. Reinertsen made this argument in The Principles of Product Development Flow (2009), and the same calculation is often called CD3 (cost of delay divided by duration).
SAFe turned the idea into a relative scoring exercise that teams can run without financial models:
- Cost of delay is the sum of three relative scores: user-business value, time criticality, and risk reduction and/or opportunity enablement.
- Job size is used as a proxy for duration, because size is easier to estimate.
- Each input is scored relative to the other items, commonly on a modified Fibonacci scale (1, 2, 3, 5, 8, 13, 20).
Dividing the summed cost of delay by job size gives each item its WSJF score.
Why WSJF Matters
WSJF shifts the question from "what is most valuable?" to "what is most valuable per unit of time?" That change has two practical effects. It stops large, high-value items from blocking a stream of smaller wins, and it rewards teams for splitting big pieces of work, because a smaller job with the same urgency scores higher.
It also makes urgency explicit. Two features can have the same business value, but if one supports a regulatory deadline, time criticality separates them.
The method has critics. Practitioners such as Joshua Arnold of Black Swan Farming argue that SAFe's relative scores and the job-size proxy lose much of the economic meaning of cost of delay, and recommend estimating cost of delay in money per week where possible. Either way, WSJF depends on honest inputs: inflated value scores produce confident but wrong rankings.
WSJF Example
A team ranks three epics using SAFe-style relative scores:
| Epic | Value | Time criticality | Risk/opportunity | Cost of delay | Job size | WSJF |
|---|---|---|---|---|---|---|
| A: Partner API | 8 | 13 | 3 | 24 | 8 | 3.0 |
| B: New reporting suite | 13 | 3 | 5 | 21 | 13 | 1.6 |
| C: Audit log export | 5 | 8 | 8 | 21 | 3 | 7.0 |
Epic B has the highest business value, yet Epic C goes first: its cost of delay is almost as high and it can be finished far sooner.
WSJF vs. RICE Scoring
RICE scoring also divides value by effort, but it has no explicit urgency factor. WSJF treats time sensitivity as a core input, which makes it better suited to sequencing work with deadlines, market windows or dependencies. RICE is usually easier to explain for feature-level decisions.