PL-05
WSJF or PI Baseline Changed After Planning Lock
Pipeline
Default severity: medium
ProcessOutputRisk
What it detects
WSJF/Tempo Account recalc after PI lock; tests; catalogue. AKVI-1530.
Detection formula
No published identification formula is available yet for this rule.Examples in practice
- A team shows wsjf/tempo account recalc after pi lock; tests; catalogue during analysis.
- Example signal: WSJF/Tempo Account recalc after PI lock; tests; catalogue.
Suggested response
Unblock pre-release and carry-over items with clear ownership and planning labels.
Coaching playbook
Symptom
The "WSJF or PI Baseline Changed After Planning Lock" signal shows a repeatable delivery anti-pattern on the cited issues.
Why it matters
When "WSJF or PI Baseline Changed After Planning Lock" 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 "WSJF or PI Baseline Changed After Planning Lock" 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.