WSJF is a division, and both halves are relative
Weighted Shortest Job First (WSJF) sequences work for maximum economic benefit. In SAFe it is estimated as the relative cost of delay divided by the relative job duration — so a job rises in the order by being valuable *or* by being short.
Why it is like this
Prioritising by value alone starves quick wins; prioritising by size alone starves the valuable. Dividing one by the other produces a sequence that maximises value delivered per unit of time, which is the only thing a queue can actually optimise.
Not to be confused with
A scoring system whose absolute numbers mean something. Both terms are relative estimates across the items being compared — a WSJF of 14 is meaningless on its own and comparable only within the same estimation session.
In practice
The most common abuse is re-running WSJF per item as it arrives. Scores are only comparable within a set, so an item scored alone against remembered numbers is not prioritised, just numbered.
Source: SAFe Glossary (Scaled Agile, Inc.) — Weighted Shortest Job First (WSJF). Read on .
SAFe® and Scaled Agile Framework® are registered trade marks of Scaled Agile, Inc. ytyk.org is not affiliated with, endorsed by or licensed by Scaled Agile, Inc. These cards are independent commentary written in our own words; no SAFe text, graphic or Big Picture is reproduced here.
Predict Check yourself
Two features have the same cost of delay, but one takes a quarter of the time. What does WSJF say?
Show the answer
The shorter one is sequenced first — with cost of delay equal, dividing by job duration puts the shorter job ahead.
This is the whole point of the formula, and the thing a value-only ranking gets wrong every time.