CA-05
Testing Stage Bypass
CFD Advanced
Default severity: medium
PrioritizationProcessMetricsOutputRisk
What it detects
Configured testing stages have average band share below the configured minimum threshold — items are not flowing through testing in practice.
Detection formula
testing_stages = config.workflow.testing_stages // configurable list of testing stage names min_share = config.ca.testing_min_band_share // default: 5% of total WIP FOR each_stage T IN testing_stages: avg_share = AVG(band_height(T) / total_wip, all_days) IF avg_share \< min_share THEN FLAG bypass Verify via changelog: COUNT(issues with T in status_history) / total_issuesExamples in practice
- A team shows configured testing stages have average band share below the configured minimum threshold while testing stages is set to 5% of to.
- Example signal: Configured testing stages have average band share below the configured minimum threshold — items are not flowing through testing in practice.
Suggested response
Use planning-event context when interpreting advanced CFD bottlenecks, spikes, and ageing WIP.
Coaching playbook
Symptom
Configured testing stages have average band share below the configured minimum threshold — items are not flowing through testing in practice.
Why it matters
When "Testing Stage 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
Use planning-event context when interpreting advanced CFD bottlenecks, spikes, and ageing WIP.
Facilitation questions
- What system change would stop "Testing Stage 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.