Definition
WSJF (Weighted Shortest Job First)
WSJF is a prioritization model from SAFe that sequences work for maximum economic benefit by dividing the Cost of Delay by the job's duration or size. The shortest jobs with the highest cost of delay rank first. Cost of Delay itself sums user/business value, time criticality, and risk reduction or opportunity enablement, each scored on a relative scale.
Key takeaways
- WSJF = Cost of Delay ÷ Job Duration (or Size); the highest-CoD, shortest jobs rank first.
- It comes from SAFe and exists to sequence work for maximum economic benefit under limited capacity.
- Cost of Delay sums User-Business Value + Time Criticality + Risk Reduction/Opportunity Enablement, each on a relative scale.
- Dividing by duration surfaces small enabling work that pure value ranking would bury — but estimates must share a consistent baseline.
WSJF answers a sequencing question: given limited capacity, which work delivers the most value soonest? It comes from the Scaled Agile Framework (SAFe) and is computed as Cost of Delay ÷ Job Duration (or Size). Dividing by duration is the key move — it favors short, high-value work over long, high-value work, because finishing a cheap item now frees capacity sooner than committing it to a large one.
Cost of Delay is estimated as the sum of three components, each typically scored on a relative scale: User-Business Value (importance to users and revenue), Time Criticality (how fast the value decays or how urgent the deadline is), and Risk Reduction & Opportunity Enablement (work that de-risks the future or unlocks later options even if it brings no immediate revenue). Job Duration approximates how long the item takes once started, often in story points or ideal days.
Because every term is relative rather than absolute, WSJF works well with the same estimation scales agile teams already use, and it deliberately surfaces small enabling work that pure value ranking would bury. Its risks are the usual ones for any scored model: garbage-in estimates produce a confident but wrong order, and the relative scoring needs a consistent baseline across the items being compared.
Planoda can capture the WSJF components as structured fields on backlog items and compute the score automatically, so a SAFe-style backlog re-ranks itself as cost-of-delay and size estimates are updated.
Related terms
- RICE PrioritizationRICE is a prioritization framework that scores each initiative by Reach (how many people it affects), Impact (how much it moves the needle per person), Confidence (how sure the estimates are), and Effort (the work required). The score is Reach × Impact × Confidence ÷ Effort, producing a comparable number that ranks competing ideas by expected value per unit of work.
- ICE ScoringICE is a lightweight prioritization framework that scores each idea on three factors — Impact (how much it will move the goal), Confidence (how sure you are in the estimate), and Ease (how simple it is to implement) — usually on a 1–10 scale. The ICE score is Impact × Confidence × Ease, giving a fast, comparable number for ranking competing experiments.
- MoSCoW PrioritizationMoSCoW is a prioritization method that sorts requirements into four categories — Must have, Should have, Could have, and Won't have (this time). The capitalized letters form the name; the lowercase o's make it pronounceable. It forces a team to agree explicitly on what is essential versus deferrable, rather than treating every request as equally urgent.
- Story Points (Estimation)Story points are a relative, unitless measure of how much effort an issue will take, accounting for complexity and uncertainty rather than raw hours. Teams estimate in points — often using a Fibonacci-like scale — to compare items against each other quickly. Summed across a cycle, points feed velocity and burndown without false precision about clock time.
- Relative EstimationRelative estimation sizes work by comparing items to each other rather than guessing absolute hours. Teams use techniques like story points, t-shirt sizing (S/M/L), and planning poker to ask 'is this bigger than that?' — a question humans answer more reliably than 'how long will this take?' The sized values then feed velocity and forecasting.