LEARN. PRACTICE. GROW.Concept and mechanism
WSJF offers a way to discuss sequencing through relative cost of delay divided by relative duration. For comparable items, A at 15/3 has ratio five and B at 20/5 has four. The result favors A in that model; it does not authorize ignoring dependencies or mandatory deadlines. Explain scales and revisit estimates when new data emerge. Ordering by size alone ignores delayed value, time criticality, and risk reduction or opportunity. Use comparison to make trade-offs discussable. Do not change numbers merely to produce a choice someone already wants imposed. A constraint should appear as a constraint, not a manipulated score.
Guided application
During PI Planning, teams and stakeholders need shared understanding of objectives, capacity, and dependencies. The RTE facilitates coordination; a board does not itself create a supplier team’s commitment. Confirm dates and conditions with those doing the work. If known L3 support exists, include it in capacity. Of 100 days, 35 already committed leave at most 65 as a starting point before other constraints. Express objectives in outcome language: enabling recovery within the agreed operating condition is more informative than a ticket list. The intent is to coordinate an adaptable transparent plan without turning an initial forecast into certainty about the entire PI.
An API expected in iteration two supports the plan only after its dependency is discussed with the responsible team.
Common pitfalls
WSJF as a context-free rule; unilateral date as agreement; double-counted capacity; objective as a task list.
Related topics: Integrated execution, release, and improvement · Portfolio, hypotheses, and funded capacity
Make choices and dependencies explicit before consolidating commitments.
Reference: PI Planning · AI-Empowered SA; official study guide May 27 2026; current product page publishes different ranges in three domains