CO-07
Carry-Over Concentration — Same Issues Repeat
Carry-Over
Default severity: medium
PrioritizationOutputRiskEffort
What it detects
The same set of issues appears in carry-over across multiple sprints — over-planning is not random but concentrated on specific items that are never actually planned with sufficient capacity to complete them.
Detection formula
FOR each_issue I: carryover_count(I) = COUNT(sprints WHERE I was carried over) IF carryover_count(I) >= config.co.repeat_carryover_min // default: 2 THEN FLAG repeat_carryover_item repeat_items_sp = SUM(sp, repeat_carryover_items) IF repeat_items_sp / avg_committed_sp > config.co.repeat_concentration_threshold // default: 30% THEN FLAG concentrated_carryover — planning problem is structural, not random Report: top repeat carry-over items ranked by carryover_count descendingExamples in practice
- A team shows the same set of issues appears in carry-over across multiple sprints while repeat carryover min is set to 2.
- Example signal: The same set of issues appears in carry-over across multiple sprints — over-planning is not random but concentrated on specific items that are never actually planned with sufficient capacity to complete them.
Suggested response
Address chronic carry-over by rightsizing sprints and finishing or splitting stuck work.
Coaching playbook
Symptom
The same set of issues appears in carry-over across multiple sprints — over-planning is not random but concentrated on specific items that are never actually planned with sufficient capacity to complete them.
Why it matters
When "Carry-Over Concentration — Same Issues Repeat" 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
Address chronic carry-over by rightsizing sprints and finishing or splitting stuck work.
Facilitation questions
- What system change would stop "Carry-Over Concentration — Same Issues Repeat" 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.