Teams & projects
WSJF calculator
Rate one backlog item on the modified Fibonacci scale; get its cost of delay and WSJF score to rank it against the rest of the backlog.
Score each factor relative to the other items in the same backlog: give the smallest item a 1 and rate the rest against it.
How WSJF is calculated
Weighted Shortest Job First is the prioritization method used in the Scaled Agile Framework (SAFe), based on Don Reinertsen's work on the economics of product flow. It ranks work by how much value is lost per unit of time while it waits, divided by how long it takes. Cost of delay is the sum of three relative scores: user or business value, time criticality (does the value fall off if it ships later, is there a deadline) and risk reduction or opportunity enablement. WSJF = cost of delay ÷ job size. Each factor uses the modified Fibonacci scale 1, 2, 3, 5, 8, 13, 20, whose widening gaps reflect the growing uncertainty of large estimates.
Example: a feature with business value 8, time criticality 5 and risk reduction 3 has a cost of delay of 16. With a job size of 5, WSJF = 16 ÷ 5 = 3.2. The same cost of delay on a job of size 2 would score 8, so a smaller job with the same urgency jumps ahead.
| Item | Value | Time criticality | Risk reduction | Cost of delay | Size | WSJF |
|---|---|---|---|---|---|---|
| Payment retry | 8 | 5 | 3 | 16 | 5 | 3.2 |
| Regulatory report | 5 | 20 | 8 | 33 | 8 | 4.1 |
| Redesigned dashboard | 13 | 3 | 1 | 17 | 13 | 1.3 |
| Logging cleanup | 2 | 1 | 8 | 11 | 2 | 5.5 |
| Partner API | 20 | 8 | 13 | 41 | 20 | 2.1 |
Ranked by WSJF, the logging cleanup goes first and the redesigned dashboard last, although the dashboard has the second-highest value on its own.
Scoring WSJF well
The scores are relative, not absolute. The usual practice is to score one column at a time across all items: find the item with the lowest business value, give it a 1, and rate the others against it, then do the same for time criticality, risk reduction and size. Scoring a single item in isolation produces numbers that cannot be compared.
Job size is a proxy for duration. If a large job can be split so that the most valuable part ships first, its WSJF usually rises, which is exactly the behavior the method is meant to encourage. Be careful with time criticality: inflating it for every item flattens the ranking. Reserve high values for real deadlines, contracts or market windows. Re-score the backlog every planning cycle, because cost of delay changes as deadlines approach and as other work lands.
Frequently asked questions
What is the formula for WSJF?
WSJF = cost of delay ÷ job size, where cost of delay = user/business value + time criticality + risk reduction/opportunity enablement. Each part is scored on the 1, 2, 3, 5, 8, 13, 20 scale.
Is a higher WSJF score better?
Yes. A higher score means more value is lost for every unit of time the job waits, relative to its size, so it should be done earlier. Only compare scores from the same backlog and scoring session.
Why does WSJF use Fibonacci numbers?
The growing gaps between 1, 2, 3, 5, 8, 13 and 20 stop teams from debating small differences in large, uncertain estimates and force a clear choice between relative sizes.