Prioritisation
WSJF
Prioritise by Cost of Delay (User & Business Value, Time Criticality, Risk Reduction & Opportunity) against Job Size.
What the framework is
Weighted Shortest Job First orders work by its cost of delay divided by its job size. You do first whatever loses most by waiting and takes least time. It's the prioritisation method of the Scaled Agile Framework (SAFe). There, cost of delay combines business value, time criticality, and risk reduction or opportunity enablement.
When it earns its place
Use it in PI planning, on portfolio backlogs, or whenever several teams must sequence many features or epics. The trap is estimating in absolute numbers nobody can defend. SAFe itself recommends relative estimation, comparing items with each other, which is exactly what comparing two at a time does.
How to run it with a group
- List six to ten features or epics.
- Participants compare them two at a time on each part of cost of delay, and on job size, on their own phones, with no account. A smaller job ranks higher.
- Invite business owners to judge value and time criticality, and the teams who'll do the work to judge job size.
- Sequence from the top of the ranking, and run it again each planning cycle.
What the result looks like
| Rank | Option |
User & Business Value
25%
|
Time Criticality
25%
|
Risk Reduction & Opportunity
25%
|
Job Size
25%
|
Points
(unweighted)
|
Win Rate
(weighted)
|
|---|---|---|---|---|---|---|---|
| 01 | Checkout redesign |
64
|
67%
|
||||
| 02 | Audit logging |
49
|
51%
|
||||
| 03 | Partner API |
31
|
32%
|