SA-03
Issue Removed From Sprint Without Completion or Flag
Sprint Anomalies
Default severity: medium
ProcessMetricsQuality
What it detects
An issue was removed from a sprint (sprint field cleared or changed to a different sprint) while in a non-Done status, with no flag raised and no comment explaining the removal — a silent, unacknowledged descope event. Goes deeper than SC-02 by tracking individual issue-level governance. removals = changelog.filter(field=\'sprint\', old=sprint.id, new=NULL OR different_sprint, date BETWEEN sprint.start AND sprint.end)
Detection formula
FOR each_removal R: issue = R.issue IF issue.status NOT IN done_statuses AT R.date AND no_flag_before_removal AND no_comment_within config.sa.removal_comment_window_hours // default: 24h THEN FLAG silent_removal Report: issue, sprint, removal_date, sp, bv, actor (who made the change)Examples in practice
- A team shows an issue was removed from a sprint (sprint field cleared or changed to a different sprint) while in a non-done status, with no flag raised and no comment explaining the removal while removal comment window hours is set to 24h.
- Example signal: An issue was removed from a sprint (sprint field cleared or changed to a different sprint) while in a non-Done status, with no flag raised and no comment explaining the removal — a silent, unacknowledged descope event.
Suggested response
Keep sprint boundaries honest—resolve, replan, or flag anomalies instead of hiding them.
Coaching playbook
Symptom
An issue was removed from a sprint (sprint field cleared or changed to a different sprint) while in a non-Done status, with no flag raised and no comment explaining the removal — a silent, unacknowledged descope event. Goes deeper than SC-02 by tracking individual issue-level governance. removals = changelog.filter(field=\'sprint\', old=sprint.id, new=NULL OR different_sprint, date BETWEEN sprint.start AND sprint.end)
Why it matters
When "Issue Removed From Sprint Without Completion or Flag" 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
Keep sprint boundaries honest—resolve, replan, or flag anomalies instead of hiding them.
Facilitation questions
- What system change would stop "Issue Removed From Sprint Without Completion or Flag" 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.