WSJF Calculator
Weighted Shortest Job First — the SAFe prioritization method. Calculate Cost of Delay divided by Job Duration to prioritize your backlog.
How WSJF Works
Feature 1
What is WSJF?
Weighted Shortest Job First (WSJF) is the SAFe framework's prioritization method. It calculates Cost of Delay (the business impact of not building something now) divided by Job Duration (how long it takes to deliver). Features with the highest WSJF score deliver the most value per unit of time. WSJF is particularly effective for teams managing dependencies across multiple teams or value streams.
How the WSJF calculator works
It ranks features by economic urgency: items that cost the business the most to delay, relative to how long they take to build, float to the top.
The formula: WSJF equals Cost of Delay divided by Job Duration. Cost of Delay is the sum of three inputs scored 1-10 each: User/Business Value, Time Criticality, and Risk Reduction/Opportunity Enablement.
Worked example: A single sign-on feature scores User/Business Value 7, Time Criticality 8, and Risk Reduction 3, for a Cost of Delay of 18. Sized at 3 relative points of Job Duration, its WSJF is 18 / 3 = 6.0. A feature with the same Cost of Delay but a Job Duration of 9 scores only 2.0, so the calculator pushes the smaller job ahead even though both deliver equal value.
When to use it: Reach for WSJF when items carry different urgency, not just different value, such as regulatory deadlines or closing market windows. Read the Cost of Delay glossary entry or the RICE vs WSJF comparison to decide which framework fits your backlog.
How to Use This Calculator
- Add your features. Enter each feature, epic, or initiative you want to prioritize.
- Estimate Cost of Delay. This combines user/business value, time criticality, and risk reduction/opportunity enablement.
- Estimate Job Duration. Use relative sizing (1-10) rather than absolute time. What matters is the ratio between items.
- Review the ranking. The highest WSJF scores indicate features you should sequence first.
FAQ
When should I use WSJF instead of RICE?
Use WSJF when time criticality matters. WSJF explicitly accounts for the cost of delay, making it ideal for features with deadlines, market windows, or dependency chains. RICE is better when you need to factor in reach and confidence. See our RICE vs WSJF comparison for a detailed breakdown.
Is WSJF only for SAFe teams?
No. WSJF works for any team that needs to sequence work by economic value. SAFe popularized it, but the Cost of Delay / Duration formula applies universally. Even if you don't run SAFe, WSJF is useful when you have items with different urgency levels competing for the same team's time.
For alternative prioritization methods, try RICE for reach-based scoring, ICE for quick ranking, MoSCoW for stakeholder alignment, or weighted scoring for custom criteria. The complete prioritization guide covers when to use each.