PL-10
Target or Sprint Oscillation in Planning Window
Pipeline
Default severity: medium
ProcessOutputRisk
What it detects
bidirectional target/sprint thrash inside thrash_window_days; tests; catalogue.
Detection formula
No published identification formula is available yet for this rule.Examples in practice
- A team shows bidirectional target/sprint thrash inside thrash_window_days; tests; catalogue during analysis.
- Example signal: bidirectional target/sprint thrash inside thrash_window_days; tests; catalogue.
Suggested response
Unblock pre-release and carry-over items with clear ownership and planning labels.
Coaching playbook
Symptom
The "Target or Sprint Oscillation in Planning Window" signal shows a repeatable delivery anti-pattern on the cited issues.
Why it matters
When "Target or Sprint Oscillation in Planning Window" 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
Unblock pre-release and carry-over items with clear ownership and planning labels.
Facilitation questions
- What system change would stop "Target or Sprint Oscillation in Planning Window" 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.