Weighted Shortest Job First
In continuation of the series on the many benefits of SAFe, we will be discussing micro-post number 3; Weighted Shortest Job First.
In general, Agile methods recommend that the highest priority items to the customer are built first, which is an excellent idea in and of itself, but Agile in general, provides no support for how the customer determines what the highest business value is. So, most customers either go by their gut instincts or utilize suboptimal ways of determining business value using ROIs, NPV, IRR and other metrics that have proven to be problematic. SAFe, on the other hand, does not leave its users stranded, it leverages Don Reinersten’s WSJF (Weighted Shortest Job First) job prioritization model, which is an objective, data-based system that helps leaders deliver the most value in the shortest time and supports the economic principles of Lean product development flow. The technique is used to help organizations determine the order in which Epics, Features, and other work items would be scheduled and implemented.
The WSJF formula takes into account several factors to prioritize work items based on their relative value and cost. The formula for WSJF is as follows:
WSJF = Cost of Delay (User Business Value + Time Criticality + Risk Reduction/Opportunity Enablement) / Job Size
Here’s a brief explanation of the components:
Cost of Delay (CoD): The Cost of Delay represents the economic impact of delaying the implementation of a particular work item. It takes into account factors like potential revenue loss, customer dissatisfaction, market opportunities, and other relevant business considerations. The higher the CoD, the more urgent it is to implement the work item.
Job Size: Job Size represents the size or effort required to complete the work item. It can be estimated using various Agile estimation techniques like Story Points, T-Shirt sizing, or other relative sizing methods.
By calculating the WSJF for each work item, teams can prioritize their backlog based on the economic and business impact, ensuring that the most valuable and time-sensitive work items are addressed first. Remember that Agile prioritizes early and continuous delivery of value.
WSJF is often used in SAFe’s Planning Interval (PI) event to determine which Features, Capabilities or Epics to include in the upcoming PI, and it helps teams and organizations make informed decisions about where to allocate their resources to maximize value delivery. This prioritization technique is particularly useful when dealing with multiple features or projects with competing priorities in a large-scale Agile environment.
Having seen that SAFe, in addition to all the other benefits it provides to an organization that wishes to grow and improve, also provides a mechanism by which you can deliver the most value in the shortest duration and provide the best economic return, any right thinking organization is sure to go SAFe!
Feedback and contributions are welcome. Thank you.
#ThingsThatMakeYouGoSAFe #TheManyWhysOfSAFe #ItIsSafeToBeSAFe