CO-04
Cross-Sprint Issue Transfer — Intentional Replanning
Carry-Over
Default severity: medium
PrioritizationOutputRiskEffort
What it detects
Issues were moved from one sprint to another sprint that is not the immediate next sprint — a deliberate skip-sprint reassignment. This indicates the team knows the item will not be done soon but is papering over the commitment by assigning it to a future sprint without descoping.
Detection formula
FOR each_issue I: sprint_changes = changelog.filter(field=\'sprint\').sort(date) FOR each_change (old_sprint, new_sprint): IF sprint_index(new_sprint) > sprint_index(old_sprint) + 1 // not next sprint AND I.status NOT IN done_statuses AT change.date THEN FLAG skip_sprint_transfer Report: issue, from_sprint, to_sprint, sprints_skipped, sp, bvExamples in practice
- A team shows issues were moved from one sprint to another sprint that is not the immediate next sprint during analysis.
- Example signal: Issues were moved from one sprint to another sprint that is not the immediate next sprint — a deliberate skip-sprint reassignment.
Suggested response
Address chronic carry-over by rightsizing sprints and finishing or splitting stuck work.
Coaching playbook
Symptom
Issues were moved from one sprint to another sprint that is not the immediate next sprint — a deliberate skip-sprint reassignment. This indicates the team knows the item will not be done soon but is papering over the commitment by assigning it to a future sprint without descoping.
Why it matters
When "Cross-Sprint Issue Transfer — Intentional Replanning" 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 "Cross-Sprint Issue Transfer — Intentional Replanning" 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.