Fast, effective, and reliable prioritisation is a critical skill in any business striving for success in agile environments. Understanding the impact, effort, dependencies, and risks associated with implementing new business capabilities can be challenging, especially when managing complex projects with limited resources. At McKenna Agile Consultants, we have helped numerous organisations navigate these challenges by introducing a robust prioritisation framework known as Weighted Shortest Job First (WSJF).
Whether coaching Agile Release Trains (ARTs) to sequence their program backlog of features more effectively or transforming portfolios using lean economics, the first question we always ask is: “How do you prioritise today?” Common answers often include models like MoSCoW, Kano, 9 Box, and RICE, or even complex internal spreadsheets. However, the follow-up question, “And how is that working out for you?” frequently reveals frustrations such as “everything ends up being top priority, so nothing is priority,” “the loudest voice wins,” or “the boss just decides.” Sound familiar? This is where WSJF shines by bringing objectivity, alignment, and consistency to the prioritisation process. WSJF supports continuous prioritisation and job sequencing within a flow based system, enabling organizations to adapt to changing priorities and maximize efficiency, which leads to the best economic outcomes.
What is Weighted Shortest Job First?
Weighted Shortest Job First, popularised by the Scaled Agile Framework (SAFe), is a prioritisation model designed to help organisations prioritise and sequence work to maximise economic value and business agility. At its core, WSJF helps teams sequence jobs—such as features or epics—by calculating a priority score that balances the economic impact of delay against the job size or duration.
The fundamental WSJF formula is:
WSJF Score = Cost of Delay / Job Size
After introducing the formula, it’s important to note that calculating WSJF and performing a WSJF calculation allows teams to objectively rank and prioritise work items by quantifying their value and urgency.
Here, the Cost of Delay (CoD) is an estimate of the economic impact of not completing a job sooner, encompassing three key components: user business value, time criticality, and risk reduction or opportunity enablement. To calculate the WSJF score, you first estimate the relative cost of delay by summing the user business value, time criticality, and risk reduction/opportunity enablement. Then, you divide this sum by the relative job size. When prioritising tasks, it’s important to consider a job’s size and its relative value to the business as some methods focus solely on size while others focus solely on value. This approach inherently favours jobs that deliver higher immediate value and can be completed quickly, thus promoting faster value delivery and better flow in development processes.
When assessing Cost of Delay, teams consider delay cost (the cost of not doing this right now), to quantify the economic impact of postponing a task. These components represent the relative importance of delivering the job promptly, with criticality risk reduction being a key factor in the calculation. The job size, often estimated as job duration or relative effort, reflects the time or resources required to complete the work. These scores directly influence how work is prioritised.
When estimating duration, teams use job size as a proxy for duration in the WSJF calculation.
In practice, the development team (or whomever is executing the work) plays a crucial role in estimating work effort, and the program or product backlog is prioritised using WSJF value to ensure the most valuable items are addressed first. WSJF automatically ignores sunk costs since it focuses on future economic outcomes rather than past investments, ensuring that prioritisation decisions are forward-looking and strategic.
What Are The Benefits of WSJF?
WSJF is more than just a prioritisation tool; it is a skill that fosters collaboration, alignment, and consistency across agile teams and stakeholders. When implemented effectively, WSJF offers several key benefits as a robust prioritisation framework. As a systematic prioritization framework used by product teams, WSJF helps maximize value delivery by ranking work items based on economic value.
- Alignment: WSJF workshops encourage stakeholders to discuss each job’s value levers in detail, fostering shared understanding and consensus on priorities. This collaborative approach helps align product managers, development teams, product teams, and business professionals accountable for value delivery.
- Consistency: Organisations that adopt WSJF consistently use the same definitions for value, risk, and job size, creating a common language for prioritisation. This consistency reduces ambiguity and allows teams to prioritise backlogs and user stories more effectively across complex projects.
- Flow: By dividing the cost of delay by job size, WSJF naturally prioritises smaller jobs that deliver significant value quickly. This bias towards the shortest job first supports lean principles by encouraging smaller batch sizes and limiting work in progress, which enhances flow-based systems and accelerates value delivery.
- Better Economic Outcomes: WSJF’s fundamental principle is to maximise economic value by sequencing work to minimise delay costs and optimise resource allocation. This prioritisation model leads to improved customer satisfaction, strategic alignment, and more effective utilisation of constrained resources.
Understanding the WSJF Formula
The WSJF formula is the heart of the Weighted Shortest Job First prioritization model, widely adopted in agile environments and especially within the Scaled Agile Framework (SAFe). This formula enables teams to make objective, data-driven decisions about which tasks or features to tackle next, ensuring that the highest value work is delivered as quickly as possible.
The WSJF formula is straightforward:
WSJF Score = Cost of Delay / Job Size
Here’s how it works: the Cost of Delay represents the combined impact of user business value, time criticality, and risk reduction or opportunity enablement. Job Duration, sometimes referred to as job size, is an estimate of how long it will take to complete the work. By dividing the Cost of Delay by the Job Duration, the WSJF formula produces a priority score for each item in the backlog.
A higher WSJF score means a job should be prioritized sooner, as it delivers greater business value, reduces risk, or addresses time-sensitive needs in the shortest possible time. This approach, known as weighted shortest job first, helps agile teams optimize value delivery, improve flow, and make the best use of limited resources. By consistently applying the WSJF prioritization model, organizations can ensure that their development process is focused on the work that will have the greatest economic impact.
How to Lead Effective Prioritisation Workshops?
Successfully applying WSJF requires more than understanding the formula—it demands careful facilitation and preparation. Based on our experience facilitating hundreds of WSJF workshops, here are five top tips to help you lead effective prioritisation sessions:
Prioritise Preparation
Preparation is essential. Prioritisation workshops bring together multiple stakeholders, making them expensive and time-consuming. To ensure value:
- Brief Epic/Feature Owners Ahead of Time: Ensure owners prepare their content, including lean business cases and feature descriptions. Coaching them on expectations prevents wasted time on unready items. If an item isn’t ready, consider excluding it from the session to maintain focus.
- Share Content in Advance: Distribute the backlog or list of epics or features before the workshop. Make pre-reading a prerequisite and start meetings by addressing questions from the pre-reading. If attendees come unprepared, consider postponing the session to avoid ineffective prioritisation.
- Educate Participants on WSJF: Ensure everyone understands WSJF’s purpose and mechanics. We recommend experiential learning, such as the “SAFe City” game, to help participants grasp WSJF nuances before prioritising real work.
Understand What Your Value Is
User business value is often the easiest yet most misaligned lever in WSJF. Start by aligning stakeholders on what “value” means in your context. For product companies, value might be revenue or market share, but for non-profits or environmentally conscious organisations, value could include impact metrics or user satisfaction.
Clarify whether value is driven by growth, cost savings, regulatory compliance, or other factors. This alignment leads to deeper conversations and more accurate WSJF calculations. Be cautious about adding too many levers, as this complicates prioritisation and can dilute focus.
Take Your Time With Time Criticality
Time criticality measures how urgent it is to deliver a job. This lever is often rushed but deserves careful consideration. Reflect on fixed deadlines, regulatory deadlines, market events, and how value deteriorates over time.
Some organisations use a simple scale where jobs without a fixed deadline score low, while those with a fixed deadline—specific, non-negotiable time points that determine urgency—score higher relative to their urgency. Consistency in scoring time criticality ensures reliable WSJF prioritisation.
Balancing Risk Reduction and Opportunity Enablement
Risk reduction and opportunity enablement represent future risks and business opportunities that a job addresses. Many find it challenging to size these levers simultaneously. We suggest plotting jobs on a two-dimensional graph with risk reduction on one axis and opportunity enablement on the other. This visual aid helps stakeholders assign relative sizes more objectively.
Strong, Impartial Facilitation
WSJF is a skill requiring practice. A confident, impartial facilitator ensures discussions stay focused, definitions are adhered to, and stakeholders remain aligned. Facilitation includes clarifying which lever is being discussed, distinguishing between immediate value and opportunity enablement, and managing competing priorities diplomatically.
In remote settings, virtual collaboration tools like Mural can recreate the tactile experience of moving index cards, supporting interactive prioritisation sessions.
Normalising Scores in WSJF
Achieving consistency in WSJF scoring is essential for reliable prioritization and better economic outcomes. Normalising scores ensures that all team members interpret and apply the scoring system in the same way, reducing subjectivity and bias in the process.
One effective method is to use a standardised scale, such as the Fibonacci sequence, when estimating both the Cost of Delay and Job Duration. This approach helps teams avoid false precision and encourages relative comparisons between jobs. Regular calibration sessions, where team members discuss and align on what different scores mean, further enhance consistency and understanding.
Leveraging WSJF templates and calculators can also streamline the scoring process, making it easier to compare jobs and calculate WSJF scores accurately. By normalising scores, teams can trust that their WSJF prioritization reflects a shared understanding of value, urgency, and effort—leading to more effective decision-making and improved prioritization outcomes.
Common Challenges in WSJF Prioritisation
While WSJF prioritization offers a robust framework for sequencing work, it is not without its challenges—especially in complex projects with diverse stakeholders and shifting priorities. One frequent hurdle is reaching consensus when estimating the Cost of Delay and Job Duration. These estimates can be influenced by personal bias, incomplete information, or differing interpretations of business value and risk reduction.
Another challenge is ensuring that everyone involved fully understands the WSJF formula and how to apply it. Without a shared understanding, the prioritization process can become inconsistent, undermining the reliability of WSJF scores. Additionally, external factors such as regulatory deadlines, urgent customer requests, or legacy system fragility can complicate the process, sometimes requiring teams to adjust their approach or make exceptions.
To address these challenges, teams should invest in regular training, open discussions, and calibration exercises. By fostering transparency and continuous learning, organizations can strengthen their WSJF prioritization and ensure it remains effective, even in the face of complex projects and evolving business needs.
How Often Should You Run WSJF Workshops?
The frequency of WSJF workshops depends on your organisation’s context and market dynamics. Prioritisation should be fluid, reflecting current knowledge rather than outdated assumptions.
At the program (ART) level, some clients conduct WSJF prioritisation every sprint or week during backlog refinement to accommodate new features. Others prefer quarterly sessions aligned with Program Increment planning. At the portfolio level, WSJF sessions are typically less frequent due to the larger scope and effort involved in building lean business cases.
Regularly reviewing priorities allows agile teams to adapt to changes in time criticality, risk factors, and economic value, ensuring the backlog remains optimally sequenced for maximum business agility.
Customising WSJF for Your Organisation
The WSJF formula provides a solid foundation for prioritization, but it’s important to remember that one size does not fit all. Customising WSJF allows organizations to tailor the model to their unique context, strategic goals, and business environment.
Customisation might involve adjusting the scoring system, introducing new criteria, or modifying how Cost of Delay and Job Duration are estimated. For example, some organizations may place greater emphasis on customer satisfaction, business opportunities, or strategic alignment, in addition to traditional levers like business value, risk reduction, and time criticality. Others may adapt the scales used for scoring to better reflect their team’s experience or the complexity of their work.
By thoughtfully customising the WSJF formula and prioritization process, organizations can ensure that their approach aligns with their specific objectives and delivers the best possible economic outcomes. This flexibility empowers teams to prioritize effectively, respond to changing business needs, and maximize value delivery.
Add WSJF to Your Skill Set
While WSJF is a powerful prioritisation model, it is not a silver bullet. The final decision remains with the business owners, executives, product manager and stakeholders (or whomever is accountable for the backlog in question), who may consciously override WSJF scores based on strategic alignment or other considerations.
To unlock WSJF’s full potential, organisations must treat it as a skill to develop rather than just a tool. Practising WSJF prioritisation refines the team’s ability to prioritise effectively, enhances collaboration, and drives better economic outcomes.
If you’re interested in advancing your team’s WSJF skills, McKenna Agile Consultants offers tailored training and consultancy to support your journey towards mastering this essential prioritisation framework.
By integrating WSJF into your development process, you can prioritise backlogs more effectively, balance competing demands, and deliver value faster—boosting customer satisfaction and business agility in today’s fast-paced markets.
Conclusion
In summary, the WSJF prioritization model stands out as a powerful approach for optimising workflow and maximising value delivery in agile environments. By mastering the WSJF formula, normalising scores across teams, and customising the model to fit organizational needs, teams can create a prioritization process that is both effective and reliable.
While challenges such as applying the WSJF formula and managing complex projects at the same time are real, awareness, transparency and training can help teams overcome this obstacle. By focusing on business value, risk reduction, and time criticality, and by continuously refining their approach, organizations can achieve better economic outcomes, higher customer satisfaction, and greater agility.
Ultimately, WSJF is more than just a prioritization tool—it is a fundamental principle for sequencing work in agile environments. When embraced as a skill and integrated into the development process, the WSJF model empowers teams to make smarter decisions, deliver value faster, and drive sustained business success.
