PR-12
WSJF Score Mismatch — Stored vs Computed
Planning Recommendations
Default severity: medium
Product BacklogPrioritizationBusiness ValueRisk
What it detects
`(BV+TC+RR)/JobSize`; tests; catalogue.
Detection formula
No published identification formula is available yet for this rule.Examples in practice
- A team shows `(bv+tc+rr)/jobsize`; tests; catalogue during analysis.
- Example signal: `(BV+TC+RR)/JobSize`; tests; catalogue.
Suggested response
Use the advisory outputs to tune refinement, WIP, and planning cadence with data.
Coaching playbook
Symptom
The "WSJF Score Mismatch — Stored vs Computed" signal shows a repeatable delivery anti-pattern on the cited issues.
Why it matters
When "WSJF Score Mismatch — Stored vs Computed" 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 "WSJF Score Mismatch — Stored vs Computed" 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.