FI-08
Parent Issue Flag Concentration
Flags
Default severity: medium
ProcessOutputRisk
What it detects
The flag rate per sprint is increasing across consecutive sprints — impediments are accumulating faster than they are being resolved. A rising flag trend is one of the strongest leading indicators of sprint collapse and delivery failure. flag_rate_series = \[flag_rate(sprint=S)
Detection formula
FOR S IN last config.fi.trend_window_sprints\] // default: 5 sprints IF linear_regression(flag_rate_series).slope > 0 AND r_squared > config.fi.trend_r_squared // default: 0.55 AND n_sprints >= 3 THEN FLAG increasing_impediment_trend IF slope > config.fi.critical_slope_per_sprint // default: 0.05 (5% more flags each sprint) THEN CRITICAL Report: flag rate per sprint as time series chart; projected flag rate at current trendExamples in practice
- Per sprint per team
- A team shows the flag rate per sprint is increasing across consecutive sprints while trend window sprints is set to 5 sprints.
- Example signal: The flag rate per sprint is increasing across consecutive sprints — impediments are accumulating faster than they are being resolved.
Suggested response
Close the loop on flags—link blockers, set owners, and clear impediments with traceability.
Coaching playbook
Symptom
The flag rate per sprint is increasing across consecutive sprints — impediments are accumulating faster than they are being resolved. A rising flag trend is one of the strongest leading indicators of sprint collapse and delivery failure. flag_rate_series = \[flag_rate(sprint=S)
Why it matters
When "Parent Issue Flag Concentration" 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
Close the loop on flags—link blockers, set owners, and clear impediments with traceability.
Facilitation questions
- What system change would stop "Parent Issue Flag Concentration" 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.