DG-02
Analysis Stage DoD Bypass
DoD Gates
Default severity: medium
ProcessOutputQuality
What it detects
Issue entered the configured post-analysis stage with the configured analysis stage DoD score below the configured threshold. The specific DoD fields for the analysis stage are configurable.
Detection formula
analysis_stage = config.dod.analysis_stage_name // e.g. \'Analysing\' analysis_fields = config.dod.stages\[analysis_stage\].fields // configurable field list analysis_threshold = config.dod.stages\[analysis_stage\].threshold // default: 0.8 IF score \< analysis_threshold AND issue.status IN config.dod.post_analysis_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 post-analysis stage with the configured analysis stage dod score below the configured threshold while analysis stage name is set to Configured per workspace.
Suggested response
Hold stage transitions until DoD evidence is complete and visible for auditors.
Coaching playbook
Symptom
Issue entered the configured post-analysis stage with the configured analysis stage DoD score below the configured threshold. The specific DoD fields for the analysis stage are configurable.
Why it matters
When "Analysis 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 "Analysis 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.