DG-01
Stage Transition With DoD Below Threshold
DoD Gates
Default severity: medium
ProcessOutputQuality
What it detects
An issue transitioned to the next stage before meeting the configured minimum DoD completion score for the current stage. All stages, fields, and thresholds are fully configurable per organisation.
Detection formula
dod_config = config.dod.stages\[S\] // { fields: \[\...\], threshold: 0.0-1.0 } dod_score = COUNT(dod_config.fields WHERE value = true) / COUNT(dod_config.fields) IF dod_score \< dod_config.threshold AT transition time THEN FLAG Default thresholds: Funnel=1.0, Analysing=0.8, Ready=0.75, Implementing=0.67, Done=1.0Examples 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 an issue transitioned to the next stage before meeting the configured minimum dod completion score for the current stage while stages is set to Map configured per issue type.
Suggested response
Hold stage transitions until DoD evidence is complete and visible for auditors.
Coaching playbook
Symptom
An issue transitioned to the next stage before meeting the configured minimum DoD completion score for the current stage. All stages, fields, and thresholds are fully configurable per organisation.
Why it matters
When "Stage Transition With DoD Below Threshold" 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 "Stage Transition With DoD Below Threshold" 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.