Naming it is a reminder that WSJF sequences initiatives against each other, it doesn't score one in isolation.
The value this creates for the business and the user, scored relative to other initiatives, not an absolute figure.
How much that value decays the longer this waits. A 20 here means delay is genuinely costly, not just unwelcome.
The risk this removes or the opportunity it unblocks elsewhere, separate from the direct business value above.
The relative size of the work, the same kind of estimate used for sprint sizing, not a person-days figure.
WSJF Score
—
Select all four scores to see a WSJF value.
Using this tool
When WSJF helps, and where it stops
When to use WSJF
- Sequencing larger, cross-functional investments
- Comparing bets where job sizes vary too much for RICE
- Making cost of delay visible in a prioritisation conversation
When not to rely on WSJF alone
- Scoring small, individual capability items (use RICE)
- Setting scores without the people who own the work in the room
- Treating the number as final rather than a starting point for debate
WSJF is SAFe's standard formula, the industry reference for this method. It supports a sequencing conversation, it doesn't replace the judgement of the person having it.