Weighted Shortest Job First
Weighted Shortest Job First
Let’s break down Weighted Shortest Job First (WSJF) with a real-life example to help
explain how it works.
Real-Life Example:
Imagine you're managing the development of an e-commerce website, and your team has a backlog
of features to implement. These features include:
Now, your challenge is to prioritize these features to maximize value while minimizing the cost of
delay. This is where WSJF comes in.
o Feature A (Loyalty Rewards): High value as it encourages repeat purchases, but not
immediately critical.
o Feature C (AI Recommendations): Medium value, improves user experience but not
essential for all customers.
2. Estimate Effort/Complexity:
o Feature D: High effort, since it involves translating content and adapting the UI for
different languages.
o Feature A: Low risk, it’s a self-contained system with little impact on other features.
o Feature B: Medium risk, as any error in the checkout process could disrupt
payments.
o Feature C: High risk, AI development can be unpredictable and hard to get right.
You would assign relative scores for cost of delay (based on value, risk, and urgency) and effort for
each feature.
Feature B (One-Click Checkout) has the highest value, moderate risk, and low effort, so it
gets the highest WSJF score.
Feature A (Loyalty Rewards) has a medium WSJF score—high value but moderate effort.
Feature D (Multi-Language Support) has a lower WSJF score—high value but high effort and
risk.
Feature C (AI Recommendations) has the lowest WSJF score—medium value but very high
effort and risk.
Effort/Complexity: Features that are easier and quicker to implement but provide high value
(Feature B) should be prioritized.
Risk: Tackling risky features earlier ensures the team mitigates potential problems before
they affect other work.
Dependencies: If one feature (like Feature B) relies on another system (payment integration),
it should be prioritized to unblock other features.
1. Maximizing Value: It helps a project manager ensure that the team is working on tasks that
deliver the most value relative to the time and effort required.
2. Reducing Delays: By considering the cost of delay, the project manager can prioritize work
that minimizes disruptions and bottlenecks.
3. Balancing Risk: WSJF enables the project manager to address high-risk features early,
preventing unexpected challenges later in the project.
WSJF works well in Agile environments where features evolve, and rapid feedback is crucial. It
ensures that development aligns with business value while optimizing resource usage.
4o
You said:
but there are no numberical value assigned to this ''Cost of Delay''. How do we divide without
numbers and with High, medium and low
ChatGPT said:
ChatGPT
To apply WSJF effectively, you can use a relative scoring system to quantify the Cost of Delay. Here’s
how to assign numerical values to High, Medium, and Low ratings for each feature's cost of delay:
Step-by-Step Approach
1. Define Scoring Scale: Establish a numerical scale for value, effort, and risk. A common
approach is to use a scale from 1 to 10.
High: 8-10
Medium: 4-7
Low: 1-3
2. Assign Scores:
o For each feature, assign scores for Cost of Delay, Job Duration (Effort), and include
factors like risk and urgency.
Example Scoring
Calculating WSJF
Final Prioritization
Key Takeaways
Numerical Values: Assigning numerical values helps you quantify abstract concepts like cost
of delay.
Relative Assessment: You assess features relative to each other, helping prioritize effectively
based on overall impact.
Flexibility: You can adjust scoring scales or criteria based on project context and stakeholder
feedback.
Using a systematic approach helps keep the process objective and grounded in measurable criteria.
This makes it easier for stakeholders to understand and agree on prioritization decisions.