DG-03
Readiness Stage DoD Bypass
DoD Gates
Default severity: medium
ProcessOutputQuality
What it detects
Issue entered the configured development stage with the readiness stage DoD score below threshold. Fields and threshold configurable.
Detection formula
ready_stage = config.dod.ready_stage_name IF score(ready_stage) \< config.dod.stages\[ready_stage\].threshold // default: 0.75 AND issue.status IN config.dod.development_stages THEN FLAGExamples 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 issue entered the configured development stage with the readiness stage dod score below threshold while ready stage name is set to 0.75.
Suggested response
Hold stage transitions until DoD evidence is complete and visible for auditors.
Coaching playbook
Symptom
Issue entered the configured development stage with the readiness stage DoD score below threshold. Fields and threshold configurable.
Why it matters
When "Readiness Stage DoD Bypass" 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 "Readiness Stage DoD Bypass" 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.