PR-13
WIP Inversion — Lower WSJF Active While Higher WSJF Waits
Planning Recommendations
Default severity: medium
PrioritizationProcessRiskEffort
What it detects
full WSJF score; suppress PR-10 when active; tests; catalogue.
Detection formula
No published identification formula is available yet for this rule.Examples in practice
- A team shows full wsjf score; suppress pr-10 when active; tests; catalogue during analysis.
- Example signal: full WSJF score; suppress PR-10 when active; tests; catalogue.
Suggested response
Use the advisory outputs to tune refinement, WIP, and planning cadence with data.
Coaching playbook
Symptom
The "WIP Inversion — Lower WSJF Active While Higher WSJF Waits" signal shows a repeatable delivery anti-pattern on the cited issues.
Why it matters
When "WIP Inversion — Lower WSJF Active While Higher WSJF Waits" keeps appearing, the team is signalling a repeatable process gap. Left unexamined, the pattern hides where work really stalls and makes improvement metrics harder to trust.
What you can achieve
Use the advisory outputs to tune refinement, WIP, and planning cadence with data.
Facilitation questions
- What system change would stop "WIP Inversion — Lower WSJF Active While Higher WSJF Waits" from firing again?
- What do the cited issues have in common — same root cause or same workaround?
- Who owns the two-week experiment and how will we verify on the next import?
Run this rule against your own tracker data with Flow Analyzer.