DG-07
Stage Flip-Flop
DoD Gates
Default severity: medium
ProcessOutputQuality
What it detects
An issue moved forward then backward then forward again within the configured flip-flop detection window.
Detection formula
flip_flop_window = config.dod.flip_flop_window_days // default: 7d flip_flops = COUNT(S->S+1->S->S+1 patterns within flip_flop_window) IF flip_flops >= 1 THEN FLAG IF pattern occurs within config.dod.same_day_threshold // default: 24h THEN CRITICAL (same-day reversal)Examples 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 moved forward then backward then forward again within the configured flip-flop detection window while flip flop window days is set to 7d flip_flops = COUNT(S->S+1->S->S+1 patterns within flip_flop_window).
Suggested response
Hold stage transitions until DoD evidence is complete and visible for auditors.
Coaching playbook
Symptom
An issue moved forward then backward then forward again within the configured flip-flop detection window.
Why it matters
When "Stage Flip-Flop" 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 Flip-Flop" 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.