frameworkData, experimentation & growth

Weighted Shortest Job First (WSJF)

WSJF sequences work by dividing a relative Cost of Delay estimate by relative job size, favoring valuable short-duration items.

Download Markdown (.md)

01What it means

Weighted Shortest Job First is a sequencing heuristic used in the Scaled Agile Framework and influenced by product-development-flow economics. It compares a relative Cost of Delay with relative job size; a higher ratio indicates more estimated economic value delivered per unit of capacity.[1][2][3]

Relative economic urgency divided by relative job size Higher WSJF favors more estimated Cost of Delay per unit of capacity
WSJF = relative Cost of Delay ÷ relative job size
User or business value
Relative contribution to desired outcomes
Time criticality
Relative loss from waiting
Risk reduction or enablement
Relative future risk removed or opportunity opened
Job size
Relative effort across all work needed for the outcome

WSJF is a sequencing heuristic, not an objective truth. Review dependencies, service classes, uncertainty, and non-economic obligations after ranking.

02Why it matters

Large, valuable initiatives can block a flow system while smaller opportunities wait. WSJF brings urgency, value, risk reduction, and size into one explicit comparison, encouraging teams to split oversized work and examine the economics behind queue order.

03When to use it

Use WSJF to sequence a set of reasonably comparable jobs competing for the same constrained capacity, especially at portfolio or program boundaries. Apply it during a shared estimation session and revisit it when job size, urgency, or evidence changes.

04How it works

  1. Define a comparable set of jobs and a consistent relative scale.
  2. Estimate user or business value, time criticality, and risk reduction or opportunity enablement for each job.
  3. Combine those components into a relative Cost of Delay estimate, following the organization’s documented scoring convention.
  4. Estimate relative job size across all work needed to reach the outcome.
  5. Divide relative Cost of Delay by relative job size, rank higher ratios first, then review dependencies, classes of service, and non-economic obligations.

05A practical example

Example

A platform group compares a small authentication upgrade, a medium analytics capability, and a large migration. The upgrade has strong time criticality and risk reduction with low job size, producing the highest WSJF ratio. It goes first, while the migration is split into smaller independently valuable slices.

06Where it breaks

WSJF inherits uncertainty from all of its estimates and can be gamed by inflating urgency or shrinking stated size. Adding ordinal components and dividing the result does not create objective economics. The method also needs explicit overrides for safety, compliance, fairness, and essential maintenance.

Common mistakes

  • Comparing scores produced by teams using different scales.
  • Scoring a large initiative without first looking for smaller valuable slices.
  • Treating the ratio as binding when dependencies or mandatory work intervene.

07Sources

  1. Extended Guidance: WSJFScaled Agile, Inc. · Official framework guidanceExtended Guidance: WSJF
  2. Weighted Shortest Job First (WSJF)Scaled Agile, Inc. · Official glossaryWeighted Shortest Job First (WSJF)
  3. Second Generation Lean Product DevelopmentReinertsen & Associates · Foundational practitioner sourceSecond Generation Lean Product Development
View saved topics

Start typing to search titles, definitions, categories, and frameworks.