Weighted Shortest Job First (WSJF)

https://ik.imagekit.io/beyondpmf/frameworks/weighted-shortest-job-first-wsjf.png
Weighted Shortest Job First (WSJF) primarily addresses operational friction by providing a framework to prioritize jobs. It focuses on sequencing tasks to maximize economic benefit, streamlining the workflow and improving coordination of work.

Weighted Shortest Job First (WSJF) is a decision-making framework used in Agile software development and product management to prioritize projects, features, or other work items. It calculates the cost of delay and divides it by the job duration, helping teams to prioritize tasks that deliver the highest value in the shortest time. This framework is particularly useful in environments where the work backlog exceeds the available development capacity, helping to maximize economic outcomes and improve efficiency.

Score your
Weighted Shortest Job First (WSJF)
Measure my
Operational
Friction

Steps / Detailed Description

  • Identify and list all jobs or features to be prioritized.
  • Estimate the Cost of Delay (CoD) for each item.
  • Estimate the duration or job size for each item.
  • Calculate the WSJF score for each item by dividing the CoD by the job size.
  • Prioritize the jobs based on the highest WSJF scores.

Best Practices

  • Regularly review and update the estimations as project progresses.
  • Involve diverse team members in the estimation process to ensure accuracy.
  • Balance WSJF with other considerations like risk and strategic alignment.

Pros

  • Promotes economic value-driven decision-making.
  • Helps prioritize tasks that deliver quick benefits.
  • Reduces time wasted on less critical tasks.

Cons

  • Estimation of Cost of Delay can be subjective and complex.
  • May not account for dependencies and interactions between tasks.
  • Can lead to short-term focus, neglecting long-term strategic goals.

When to Use

  • When managing a large backlog with limited resources.
  • In fast-paced environments where quick delivery is critical.

When Not to Use

  • For projects where all tasks have similar importance and urgency.
  • When long-term strategic projects are more important than immediate returns.

Related Frameworks

Feature Bucket Framework
IPA Matrix
Buy-a-Feature Prioritization
Feature Adoption Matrix
Risk-Adjusted Backlog

Categories

Prioritization

Lifecycle

Launch
Growth

Scope

Scope not defined

Maturity Level

Maturity level not specified

Time to Implement

2–4 Weeks
3–6 Months
1–2 Weeks
3–6 Months
1–2 Months
3–6 Months
1–2 Weeks
Less Than 1 Day
1–2 Weeks
Longer Than 6 Months
1–2 Weeks
Longer Than 6 Months
1–2 Weeks
3–6 Months
1–2 Weeks
1–2 Weeks
1–2 Weeks
1–2 Weeks
1–2 Days
1–2 Weeks
1–2 Weeks
1–2 Weeks
1–2 Weeks
1–2 Weeks
1–2 Weeks
3–6 Months
1–2 Weeks
1–2 Weeks
1–2 Weeks
3–6 Months
1–2 Weeks
1–2 Weeks
2–4 Weeks
1–2 Weeks
1–2 Days
1–2 Weeks
Longer Than 6 Months
Longer Than 6 Months
3–6 Months
Longer Than 6 Months
Longer Than 6 Months
Longer Than 6 Months
1–2 Weeks
Longer Than 6 Months
3–6 Months
Less Than 1 Day
3–6 Months
1–2 Months
3–6 Months
Longer Than 6 Months
3–6 Months
Less Than 1 Day
1–2 Weeks
3–6 Months
3–6 Months
1–2 Weeks
3–6 Months
1–2 Weeks
1–2 Weeks
1–2 Days
1–2 Weeks
1–2 Months
Longer Than 6 Months
1–2 Weeks
Longer Than 6 Months
1–2 Weeks
3–6 Months
1–2 Weeks
Less Than 1 Day
1–2 Weeks
3–6 Months
1–2 Weeks
3–6 Months
1–2 Weeks
1–2 Weeks
Longer Than 6 Months
Less Than 1 Day
3–6 Months
Longer Than 6 Months
1–2 Months
1–2 Weeks
Longer Than 6 Months
1–2 Weeks
3–6 Months
1–2 Weeks
1–2 Weeks
3–6 Months
Less Than 1 Day
1–2 Weeks
1–2 Weeks
3–6 Months
3–6 Months
Less Than 1 Day
1–2 Weeks
Longer Than 6 Months
1–2 Months
1–2 Weeks
1–2 Weeks
1–2 Weeks
Longer Than 6 Months

Copyright Information

Autor:
Dean Leffingwell and Don Reinertsen
2015
Publication:
Scaled Agile Framework
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
© 2025 vallenstone LLC. All rights reserved
Copyright and
Attribution PolicyPrivacy Policy