Weighted Shortest Job First

02 / Application

When to Use WSJF

WSJF works any time you have a backlog that needs prioritizing and limited capacity to do everything at once. Here are the most common scenarios where it delivers immediate value.

Roles and Responsibilities

NOTE: Recommended headcount is 5-10 participants. Additional attendees typically slow down the process without meaningfully improving scoring quality or outcomes.

Scheduling and Timing

WSJF should run when no prioritization exists, or when there are concerns about whether the right work is being delivered first.

• Conduct WSJF at least 4 weeks before the first PI Planning event when launching a new program or ART.
• Run on a regular but infrequent cadence — quarterly, semi-annually, or annually — to refresh scores as markets and strategy shift.
• Ideally, WSJF precedes execution by 2-4 weeks. Top-priority items often need additional technical and product review before teams begin the work.

04 / Facilitation

Running the Workshop

Facilitation is about guiding the group toward shared understanding and collaborative decisions — not presenting. Your role is to hold the space, surface the right voices, and keep the process moving toward a clear, prioritized outcome.

Duration: Most WSJF workshops are completed in 2-4 hours. Lengthy backlogs or high-complexity items may require multiple sessions. Build in buffer time for discussion — that is where alignment really happens.

Presenting the WSJF Process

1. Introduction

   • What is WSJF?
   • Why does prioritization matter in Agile?
2. The WSJF Formula

   • Cost of Delay: Business Value, Time Criticality, RR/OE
   • Job size (duration)
   • Formula: WSJF = CoD / Job Size
3. Application

   • Identifying high-value features or tasks
   • Balancing effort against payoff across items
4. Benefits

   • Faster delivery of high-impact work
   • Improved alignment on business goals
   • Transparent, defensible prioritization decisions
5. Example Scenarios

   • Use real-world or hypothetical examples to illustrate WSJF in action
6. Implementation Tips

   • Tools and frameworks: SAFe boards, Miro, Excel templates
   • Common challenges and how to overcome them
7. Q&A or Interactive Exercise

   • Let participants practice using the WSJF formula with a real or sample backlog

Common Anti-Patterns to Avoid

1. Ignoring Relative Estimation

   Using absolute dollar values instead of relative Fibonacci scoring skews prioritization and makes cross-item comparison unreliable.
2. Overemphasis on One Factor

   Focusing too heavily on business value while neglecting time criticality or risk reduction produces an incomplete and misleading WSJF score.
3. Static Prioritization

   Not updating WSJF scores as markets shift or new information arrives leads to outdated priorities that no longer reflect business reality.
4. Misinterpreting Job Duration

   Over- or underestimating job size distorts WSJF scores and can invert the correct priority order for major initiatives.
5. Factoring in Sunk Costs

   Including sunk costs in WSJF calculations violates Lean principles and leads to inefficient prioritization of work that should be deprioritized or stopped.
6. Lack of Collaboration

   Running WSJF without the right team voices results in biased scores and weak stakeholder buy-in. Broad inclusion is part of what makes the outcome trustworthy.
7. Overcomplicating the Process

   Making the WSJF calculation overly complex or academic deters teams from adopting it consistently. Keep the scoring model simple and repeatable.