When every item screams “priority 1,” a disciplined scoring system can cut through the noise. Weighted Shortest Job First (WSJF) is a simple arithmetic formula that balances value against effort, helping product owners and portfolio managers decide which initiative to ship first.
The Formula
WSJF = Cost of Delay ÷ Job Size
A higher result means the work should be done sooner. The denominator (Job Size) prevents large, high‑value items from monopolizing the queue; a small effort with a decent value can outrank a massive effort with slightly higher value.
Cost of Delay Inputs
Three factors feed the numerator:
- User/Business Value – Direct revenue impact, user adoption, or strategic importance.
- Time Criticality – Deadlines, market windows, or seasonal demand that decay over time.
- Risk Reduction / Opportunity Enablement – How much risk is removed or future capability is unlocked by completing the work now.
Each input is rated on a consistent relative scale (for example, 1‑10) and summed to produce the total Cost of Delay.
Job Size
Job Size is an estimate of effort, typically expressed in the same relative scale used for story points. Smaller jobs receive a lower denominator, which boosts their WSJF score. When two items have identical Cost of Delay, the one that takes fewer resources climbs to the top—creating quick wins that keep momentum high.
When to Use It
WSJF shines at the portfolio or program level where multiple initiatives compete for limited capacity. It is less useful for day‑to‑day sprint backlog grooming, where the granularity of story points already provides sufficient ordering. Applying WSJF to routine, low‑impact tasks can overcomplicate the process without adding value.
Do / Avoid
Do
- Score every item using the same relative scale for all three Cost of Delay inputs.
- Re‑evaluate scores whenever new market data, regulatory changes, or stakeholder feedback alters the perceived cost of delay.
- Reserve WSJF for initiative‑level decisions where trade‑offs between value and effort are significant.
Avoid
- Skipping the Job Size denominator; without it, large items will always dominate the list.
- Letting a single stakeholder’s opinion replace the objective calculation—consensus on the scale keeps the model credible.
- Applying WSJF to tiny, routine backlog items; the overhead outweighs the benefit.
Use WSJF to turn “everything is priority 1” into a transparent, data‑driven order that aligns teams with business outcomes.
Top comments (0)