Weighed Shortest Job First (WSJF)

Optimised software backlog prioritisation

WSJF is a form of software backlog prioritisation.  It helps inform teams and managers, the ideal sequencing of delivering capabilities based value vs cost.  All software backlog prioritisation depends on the following three factors:

  1. Value.  How valuable is a capability (what is the cost to the business of this being delayed).
  2. Dependencies.  Are other capabilities dependent on this one
  3. Cost. How hard (cost) is this capability to deliver

Value.  A common technique for assessing value is the cost of delay, or specifically what is the monthly cost of delay (MCOD) of each particular capability.  In other words,  what would the business suffer each month that this capability is delayed in being delivered.

Dependency. Each capability may unlock other capabilities.  In other words, if other capabilities depend on this one being delivered first, then the value of delivering this one is enhanced.

Cost. The cost of delivering a capability (backlog functional user story or epic) is typically aligned to it’s size in COSMIC function points.

Weighted Shortest Job First (WSJF).

A useful formula for prioritising backlog items is the the value/cost equation.  This is known as the weighted shortest job first as is calculated as the Monthly cost of delay (value) / Functional size (cost).

WSJF Automated

Since ScopeMaster autocalculates the size, it is just up to you to add the value (MCOD) for each item to obtain a weighted shortest job first prioritised backlog.  ScopeMaster makes this so easy to do.

ScopeMaster Value Tracer

Requirements Traceability – to business value

Class Diagram auto-generated by ScopeMaster

ScopeMaster encourages Capability based planning, whilst ensuring Capabilities are aligned to quantifiable business outcomes.

ScopeMaster automates the cost half of the equation.   Backlog prioritisation is then achieved by assigning a value for Monthly Cost of Delay to each item.

ScopeMaster also accelerates value traceability,  ensuring that all backlog items are traceable to actual business value.  This is performed using a 3-tier model and simply dragging and dropping items to establish the links:

Outcomes to Capabilities to Functional User stories

Just Drag and Drop

Requirements traceability board

Using the Kanban-like metaphor,  all you have to do is

  • drag and drop user stories onto capabilities
  • drag and drop capabilities onto outcomes

All the while ScopeMaster tracks the functional size (implied cost) of each capability and hence each outcome.

Requirements Traceability Visualisations

Class Diagram auto-generated by ScopeMaster

See these other features of ScopeMaster that help to automate traceability:

Use Case Modelling – automated

CRUD Analysis Automated

User and Objects, Auto-detection