DG-15
DoD Completion Rate Declining Across Periods
DoD Gates
Default severity: medium
ProcessOutputQuality
What it detects
Average DoD completion rate across issues closed in the current period is lower than in the prior period by more than the configured decline threshold. dod_rate(period) = AVG(total_dod_score, all_issues_closed_in_period)
Detection formula
IF dod_rate(current) \< dod_rate(previous) * config.dod.min_rate_retention // default: 0.9 THEN FLAG trend IF dod_rate(current) \< config.dod.critical_rate_floor // default: 0.5 THEN CRITICAL systemic_bypassExamples in practice
- Issues advance workflow stages without meeting the configured Definition of Done score.
- Stage transitions occur before required DoD evidence is present.
- A team shows average dod completion rate across issues closed in the current period is lower than in the prior period by more than the configured decline threshold while min rate retention is set to 0.9.
Suggested response
Hold stage transitions until DoD evidence is complete and visible for auditors.
Coaching playbook
Symptom
Average DoD completion rate across issues closed in the current period is lower than in the prior period by more than the configured decline threshold. dod_rate(period) = AVG(total_dod_score, all_issues_closed_in_period)
Why it matters
When "DoD Completion Rate Declining Across Periods" 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
Hold stage transitions until DoD evidence is complete and visible for auditors.
Facilitation questions
- What system change would stop "DoD Completion Rate Declining Across Periods" 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.