WSJF
The formula
WSJF = Cost of Delay / Job Size
Features with the highest WSJF are implemented first, because they generate the most relative value per unit of effort.
Cost of Delay (CoD)
The Cost of Delay represents the negative impact of postponing the implementation of a feature. It is calculated by combining three factors:
- Business or user value: how much is this feature worth to those who need it?
- Time criticality: is there a deadline, a market opportunity, or a penalty for not doing it now?
- Market opportunity: does losing this feature to competitors or market conditions carry a specific cost?
Job size
The effort required to implement the feature, measured in whatever unit the team uses (story points, ideal days, T-shirt sizing).
How to apply it
- Identify the features or user stories to be prioritized.
- Estimate the cost of delay of each one, combining the three factors (a relative scale such as Fibonacci can be used).
- Estimate the job size of each one.
- Calculate the WSJF by dividing CoD by job size.
- Sort from highest to lowest WSJF: the first ones are those that generate the most value per unit of effort.
- Review iteratively as business needs change.
Practical example
A development team prioritizes the following features of an e-commerce application:
| Story | Business Value | Time Criticality | Market Opportunity | CoD | Job Size | WSJF |
|---|---|---|---|---|---|---|
| Implement cryptocurrency payments | 8 | 5 | 6 | 19 | 5 | 3.8 |
| Improve loading speed | 7 | 8 | 7 | 22 | 7 | 3.1 |
| Add reviews and ratings | 5 | 6 | 5 | 16 | 4 | 4.0 |
| Integrate customer service chatbot | 6 | 7 | 8 | 21 | 6 | 3.5 |
After the calculation, the team decides to prioritize the user story with the highest WSJF, ensuring the most efficient delivery of business value.
Limitations
- Difficulty estimating CoD: quantifying the impact of not doing something requires business information that is not always available.
- Does not consider dependencies: two features with similar WSJF but with a dependency between them must also be ordered according to that dependency.
- May favor small stories: if size dominates the formula, smaller stories will always come first even when their value does not justify doing them before larger, more strategic ones.
Common mistake
Treating WSJF as an objective truth rather than a conversation tool. The values that go into the formula are estimates, not precise measurements. The value of WSJF lies not in the number it produces but in the conversation it sparks: it forces the team and the Product Owner to state explicitly how much waiting costs, which usually uncovers hidden assumptions and aligns expectations.
Resources
🔧 WSJFTool · Scrum Manager
References
- Reinertsen, Donald G. (2009). The Principles of Product Development Flow: Second Generation Lean Product Development. Celeritas Publishing.
- Scaled Agile, Inc. "Weighted Shortest Job First (WSJF)". SAFe Framework.
See also
Want to advance in agility? You can search for course and exam calls or go at your own pace by becoming a member of the Agile Club. This membership includes exclusive resources, e-learning classrooms, and access to Skill Arena: a space to practice and measure your agile skills at your own pace.