SA-02
Issue Resolved After Sprint End Without Sprint Update
Sprint Anomalies
Default severity: medium
ProcessMetricsQuality
What it detects
An issue was resolved days or weeks after the sprint it belonged to ended, but its sprint field still references the old sprint — the sprint record is incorrect, burndown was wrong, and velocity was miscounted. Distinct from BH-06 (delayed closure) by adding the sprint field accuracy dimension.
Detection formula
FOR each_issue I WHERE sprint IS SET: sprint_end = sprint(I).end_date resolution_date = I.resolutiondate lag = resolution_date - sprint_end IF lag > config.sa.sprint_resolution_lag_days // default: 7d THEN FLAG late_sprint_resolution IF lag > config.sa.critical_lag_days // default: 30d THEN CRITICAL — sprint metric is fictional Report: issue, sprint, sprint_end, actual_resolution_date, lag_daysExamples in practice
- A team shows an issue was resolved days or weeks after the sprint it belonged to ended, but its sprint field still references the old sprint while sprint resolution lag days is set to 7d.
- Example signal: An issue was resolved days or weeks after the sprint it belonged to ended, but its sprint field still references the old sprint — the sprint record is incorrect, burndown was wrong, and velocity was miscounted.
Suggested response
Keep sprint boundaries honest—resolve, replan, or flag anomalies instead of hiding them.
Coaching playbook
Symptom
An issue was resolved days or weeks after the sprint it belonged to ended, but its sprint field still references the old sprint — the sprint record is incorrect, burndown was wrong, and velocity was miscounted. Distinct from BH-06 (delayed closure) by adding the sprint field accuracy dimension.
Why it matters
When "Issue Resolved After Sprint End Without Sprint Update" 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 Resolved After Sprint End Without Sprint Update" 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.