OI-06
Operational Issue Crossing Sprint Boundaries
Operational Issues
Default severity: medium
Product BacklogProcessMetrics
What it detects
An operational tracker issue has been assigned to multiple sprints consecutively — it is being carried over as a permanent sprint fixture, disguised as sprint-committed work. This inflates committed issue count and SP every sprint, distorts carry-over metrics, and creates phantom velocity.
Detection formula
IF issue flagged by OI-01: sprint_count = COUNT(DISTINCT sprints WHERE issue was present) IF sprint_count >= config.oi.max_sprints_for_operational // default: 2 THEN FLAG sprint_boundary_operational IF sprint_count >= config.oi.critical_sprint_count // default: 4 THEN CRITICAL — issue has been a permanent sprint fixture for 4+ sprints Report: list of all sprints the issue appeared in, SP included each sprint, committed BV included each sprintExamples in practice
- A team shows an operational tracker issue has been assigned to multiple sprints consecutively while max sprints for operational is set to 2.
- Example signal: An operational tracker issue has been assigned to multiple sprints consecutively — it is being carried over as a permanent sprint fixture, disguised as sprint-committed work.
Suggested response
Separate operational trackers from product flow or exclude them consistently from delivery metrics.
Coaching playbook
Symptom
An operational tracker issue has been assigned to multiple sprints consecutively — it is being carried over as a permanent sprint fixture, disguised as sprint-committed work. This inflates committed issue count and SP every sprint, distorts carry-over metrics, and creates phantom velocity.
Why it matters
When "Operational Issue Crossing Sprint Boundaries" 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
Separate operational trackers from product flow or exclude them consistently from delivery metrics.
Facilitation questions
- What system change would stop "Operational Issue Crossing Sprint Boundaries" 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.