SC-04
PI Scope Injection — Issues Added to PI After Planning
Scope Control
Default severity: medium
PrioritizationProcessRiskEffort
What it detects
Issues were added to the PI (via fixVersion/PI field or sprint assignment to a PI sprint) after PI planning completed. Measured across all four dimensions. Distinguished from normal PI refinement (small SP additions) vs significant scope injection (large SP or high BV items added).
Detection formula
pi_lock_date = config.planning.pi_lock_date\[pi_id\] // date of PI planning event injected_to_pi = changelog.filter(field=config.planning.pi_field, new=pi_id, date > pi_lock_date) injected_sp = SUM(story_points, injected_to_pi) injected_bv = SUM(bv, injected_to_pi) IF injected_sp / pi_committed_sp > config.sc.pi_injection_threshold // default: 10% THEN FLAG IF injected_sp > config.sc.pi_critical_injection_sp // default: absolute SP threshold THEN CRITICAL — report items added, by whom, on which dateExamples in practice
- A team shows issues were added to the pi (via fixversion/pi field or sprint assignment to a pi sprint) after pi planning completed while pi lock date is set to Configured per workspace.
- Example signal: Issues were added to the PI (via fixVersion/PI field or sprint assignment to a PI sprint) after PI planning completed.
Suggested response
Gate sprint and PI scope changes with visible rationale and stable commitments.
Coaching playbook
Symptom
Issues were added to the PI (via fixVersion/PI field or sprint assignment to a PI sprint) after PI planning completed. Measured across all four dimensions. Distinguished from normal PI refinement (small SP additions) vs significant scope injection (large SP or high BV items added).
Why it matters
When "PI Scope Injection — Issues Added to PI After Planning" 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 "PI Scope Injection — Issues Added to PI After Planning" 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.