PR-16
WSJF Finalised in DoD but WSJF Data Incomplete or Inconsistent
Planning Recommendations
Default severity: medium
PrioritizationProcessQualityRisk
What it detects
DoD checklist vs WSJF fields; tests; catalogue.
Detection formula
No published identification formula is available yet for this rule.Examples in practice
- A team shows dod checklist vs wsjf fields; tests; catalogue during analysis.
- Example signal: DoD checklist vs WSJF fields; tests; catalogue.
Suggested response
Use the advisory outputs to tune refinement, WIP, and planning cadence with data.
Coaching playbook
Symptom
The "WSJF Finalised in DoD but WSJF Data Incomplete or Inconsistent" signal shows a repeatable delivery anti-pattern on the cited issues.
Why it matters
When "WSJF Finalised in DoD but WSJF Data Incomplete or Inconsistent" 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 Finalised in DoD but WSJF Data Incomplete or Inconsistent" 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.