WSJF Calculator - Prioritize Work with Weighted Shortest Job First

What is WSJF (Weighted Shortest Job First)?

WSJF stands for Weighted Shortest Job First. It is an economic prioritization model originally developed by Don Reinertsen in his 2009 book The Principles of Product Development Flow, and later adopted by the Scaled Agile Framework (SAFe) as its default backlog prioritization method for features, capabilities, and epics.

The core idea is simple: given limited team capacity, you should always work on the job that delivers the most value per unit of time. WSJF quantifies that trade-off by dividing an item's Cost of Delay by its Job Size. Higher WSJF scores get scheduled first.

The WSJF Formula

SAFe's canonical WSJF formula is:

Where Cost of Delay is itself made up of three components:

Cost of Delay = User-Business Value + Time Criticality + Risk Reduction & Opportunity Enablement

Each of the four inputs (three CoD components plus Job Size) is scored on a relative scale, typically a modified Fibonacci sequence (1, 2, 3, 5, 8, 13) or a simple 1 to 10 scale as used in this calculator. The absolute numbers don't matter as much as the relative ranking across the backlog.

How to Calculate WSJF: Step by Step

1. Score User-Business Value (1 to 10). How much does this deliver to customers or the business? Higher revenue potential, larger user impact, or stronger competitive advantage all raise the score.
2. Score Time Criticality (1 to 10). Does the value decay if you delay? A regulatory deadline, a competitor launch, or a seasonal window all push this number up. Evergreen features score low.
3. Score Risk Reduction & Opportunity Enablement (1 to 10). Does the work de-risk a future initiative, unblock a dependency, or open a new market? Enablers and de-risking work often score high here even when the direct value is modest.
4. Sum the three above to get Cost of Delay. CoD = UBV + TC + RR/OE. Range is 3 to 30 on a 1 to 10 scale.
5. Score Job Size (1 to 10). This is your team's estimate of relative effort. Bigger, more complex, or more coordination-heavy jobs score higher. In WSJF, a bigger denominator means a lower final score, so large jobs are naturally deprioritized.
6. Divide CoD by Job Size. WSJF = (UBV + TC + RR/OE) / Job Size. That's your final score. Do this for every candidate feature in the backlog.
7. Sort descending. The item with the highest WSJF score is next up. Re-score whenever new information changes any component (typically each Program Increment or sprint planning cycle).

WSJF Worked Example: SAFe Program Increment Backlog

Say a SAFe Agile Release Train is planning the next Program Increment and has three candidate features on the table. Here's how WSJF ranks them:

The checkout race condition wins with a WSJF of 12.5 despite having the lowest User-Business Value in isolation. Why? It's small (Job Size 2), highly time-critical (revenue is leaking on every failed checkout), and reduces significant risk (customer trust). The mobile redesign, despite having the highest raw value, ranks last because the job is huge and there's no urgency. This is exactly the trade-off WSJF is designed to surface.

WSJF vs RICE vs ICE: Which Prioritization Method Should You Use?

WSJF is one of several popular quantitative prioritization frameworks. Here's how it compares to RICE and ICE:

Rule of thumb: use WSJF if you're operating inside SAFe or if delay costs are the dominant factor (regulatory windows, revenue leak, competitor pressure). Use RICE when you have real user-reach data. Use ICE for early-stage or growth-team decisions when speed matters more than precision. For a side-by-side breakdown of all major frameworks, see the prioritization framework comparison.

Frequently Asked Questions