Free tool

WSJF calculator

Score any backlog item by Weighted Shortest Job First — Cost of Delay ÷ Job Size. Rank by what delivers the most value soonest per unit of effort.

Score each input on the same relative scale (Fibonacci-style). WSJF is only meaningful when you score the whole backlog this way.

Cost of Delay

16

WSJF score

3.2

High priority

Where it lands

low medium high
WSJF is blind to revenue. A job for one paying enterprise account can score the same as a nice-to-have. Ground value and time-criticality in the accounts and revenue actually asking, and the ranking sharpens.
Prioritize on real demand, not guesses See revenue-weighted prioritization

Beyond the number

A WSJF score is only as good as its inputs.

Value is usually estimated. When demand and revenue live on the spine, "user/business value" stops being a vibe — it's the accounts and money behind the request.

Time criticality has a source. Tie each item to the deal, contract, or deadline driving it, and urgency stops being asserted.

WSJF lives next to delivery here. Score on the same board that runs your Scrum, Shape Up, or experiment work — no separate spreadsheet to keep in sync.

FAQ

WSJF scoring questions

What is WSJF (Weighted Shortest Job First)?
WSJF is a SAFe prioritization model: WSJF = Cost of Delay ÷ Job Size. Cost of Delay sums three relative scores — user/business value, time criticality, and risk reduction or opportunity enablement. Dividing by job size favors the work that delivers the most value soonest per unit of effort.

How do I calculate a WSJF score?
Add the three Cost-of-Delay components, then divide by job size. For example, 8 value + 5 time-criticality + 3 risk/opportunity = 16 Cost of Delay, ÷ 5 job size ≈ 3.2.

Why use relative Fibonacci-style numbers for WSJF?
WSJF scores are only meaningful relative to the rest of the backlog, so most teams score each input on a Fibonacci-ish scale (1, 2, 3, 5, 8, 13, 20). The absolute number doesn't matter — what matters is the ranking it produces when you score every item the same way.

WSJF vs RICE — which should I use?
RICE multiplies reach, impact, and confidence over effort; WSJF divides Cost of Delay over job size and adds an explicit time-criticality input. WSJF is stronger when timing and risk matter (deadlines, dependencies); RICE leans on reach. Neither weighs revenue directly — feed both the actual revenue behind each request to fix that.

What is WSJF missing?
WSJF captures urgency and effort but, like RICE, it's blind to the money behind a request — a job for one paying enterprise account can score the same as a nice-to-have. The fix is to ground value and time-criticality in the real accounts and revenue asking for the work, not a guess.

More free tools: CAC payback · RICE prioritization · MRR & ARR · Rule of 40 · churn rate · stack cost.