DG-08
Excessive Planning Event Transfers
DoD Gates
Default severity: medium
ProcessOutputQuality
What it detects
An issue has been transferred across planning events (PI, quarter, release) more than the configured maximum number of times.
Detection formula
planning_field = config.planning.pi_field // configurable: fixVersion, PI custom field, sprint pi_transfers = COUNT(changelog WHERE field = planning_field AND value changes to different PI) IF pi_transfers >= config.dod.max_pi_transfers // default: 2 THEN FLAG IF pi_transfers >= config.dod.critical_pi_transfers // default: 3 THEN CRITICALExamples in practice
- Issues advance workflow stages without meeting the configured Definition of Done score.
- Stage transitions occur before required DoD evidence is present.
- A team shows an issue has been transferred across planning events (pi, quarter, release) more than the configured maximum number of times while pi field is set to fixVersion.
Suggested response
Hold stage transitions until DoD evidence is complete and visible for auditors.
Coaching playbook
Symptom
An issue has been transferred across planning events (PI, quarter, release) more than the configured maximum number of times.
Why it matters
When "Excessive Planning Event Transfers" 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
Hold stage transitions until DoD evidence is complete and visible for auditors.
Facilitation questions
- What system change would stop "Excessive Planning Event Transfers" 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.