SC-07
Sprint Assignment Thrash
Scope Control
Default severity: medium
PrioritizationProcessRiskEffort
What it detects
non-monotonic sprint ping-pong; tests; catalogue. AKVI-1677 / AKVI-1666.
Detection formula
No published identification formula is available yet for this rule.Examples in practice
- A team shows non-monotonic sprint ping-pong; tests; catalogue during analysis.
- Example signal: non-monotonic sprint ping-pong; tests; catalogue.
Suggested response
Gate sprint and PI scope changes with visible rationale and stable commitments.
Coaching playbook
Symptom
The "Sprint Assignment Thrash" signal shows a repeatable delivery anti-pattern on the cited issues.
Why it matters
When "Sprint Assignment Thrash" 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
Gate sprint and PI scope changes with visible rationale and stable commitments.
Facilitation questions
- What system change would stop "Sprint Assignment Thrash" 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.