Weighted Shortest Job First (WSJF)

Every delivery team has more work than it can do, and the order in which it does that work has a large effect on how much value it delivers. Ranking by gut feel, by who shouts loudest or by business value alone often puts large, valuable projects first, while smaller jobs that could deliver value quickly wait behind them. Weighted shortest job first gives a more economic answer. It asks two questions about each job: how much does it cost to delay it, and how long will it take? Dividing the first by the second gives a score, and jobs with the highest scores go first.

The method comes from Don Reinertsen's work on product development economics, especially his 2009 book The Principles of Product Development Flow, where it appears as a way to sequence jobs to minimize the total cost of delay. The Scaled Agile Framework (SAFe) adopted it as its main prioritization method for features and epics, with a simplified scoring approach that teams can apply without detailed financial models. For product managers, portfolio managers and business owners, WSJF provides a consistent, transparent way to decide what to do next. It works at several levels, from ranking features for a single team to ranking epics across a whole portfolio.

Definition of Weighted Shortest Job First (WSJF)

Weighted shortest job first is a sequencing model in which each job's cost of delay is divided by its job duration, or a proxy such as job size, and jobs are scheduled in descending order of the resulting score to maximize economic benefit over time.

It is the main prioritization method in the Scaled Agile Framework (SAFe), is used to prepare for PI planning and is related to other approaches such as the weighted scoring model.

Cost of Delay

Cost of delay is the value lost by not having a job finished, often expressed per week or month.

In SAFe, it is estimated as the sum of three parts. User and business value reflects how much customers and the business want the job.

Time criticality reflects how quickly value decays, such as a regulatory deadline or a market window.

Risk reduction and opportunity enablement reflects whether the job reduces risk or makes other valuable work possible.

Calculating WSJF

Each part of cost of delay and the job size are scored relative to the other jobs being compared, usually with a modified Fibonacci scale such as 1, 2, 3, 5, 8, 13 and 20.

The smallest job in each column gets a 1, and others are scored relative to it. This keeps scoring fast and comparable.

WSJF equals the total cost of delay divided by job size. Jobs are then ranked from highest to lowest score.

Job size is used as a proxy for duration because it is easier to estimate, though in principle duration is what matters. Because scores are relative, they are only meaningful within the set of jobs being compared at the same time.

Importance of WSJF in Delivery and Engineering Operations

WSJF maximizes value delivered over time. Doing small, valuable jobs first produces more total value than starting with large ones of similar value.

It makes prioritization transparent. Stakeholders can see why one job ranks above another and argue about specific scores rather than about overall preferences.

It also considers time. Including time criticality and risk reduction stops urgent or enabling work from being crowded out by work that only looks valuable.

WSJF and Financial Management

WSJF is built on economics. Ranking by cost of delay per unit of size directs capacity to the work with the best return per unit of effort.

Thinking explicitly about cost of delay helps leaders see the real cost of waiting, which is often larger than the cost of doing the work.

Where possible, teams can replace relative scores with financial estimates of cost of delay for the largest decisions.

Consistent prioritization reduces money spent on work that is started, paused and restarted as priorities change. At the portfolio level, WSJF scores for epics can feed decisions in lean portfolio management about which initiatives to fund next.

Common Challenges

Relative scores can be gamed by stakeholders who inflate value or time criticality for their own work. Scoring together in a group helps keep estimates honest.

Very large items, such as big epics, will rarely rank highly unless split into smaller pieces, which is often the right outcome.

WSJF compares jobs at a point in time. Scores should be refreshed as conditions change, rather than treated as permanent. Some work, such as urgent security fixes or legal obligations, may need to bypass WSJF altogether, and teams should agree on these exceptions in advance.