BH-06
Delayed Sprint Closure
Backlog Health
Default severity: medium
Product BacklogPrioritizationRiskEffort
What it detects
Issues are closed in Jira more than the configured grace period after the sprint they belonged to ended — sprint records are inaccurate. closure_lag = resolution_date - sprint.end_date
Detection formula
IF issue.sprint = S AND closure_lag > config.backlog.sprint_closure_grace_days // default: 7d THEN FLAG IF closure_lag > config.backlog.critical_closure_lag_days // default: 30d THEN CRITICALExamples in practice
- A team shows issues are closed in jira more than the configured grace period after the sprint they belonged to ended while sprint closure grace days is set to 7d.
- Example signal: Issues are closed in Jira more than the configured grace period after the sprint they belonged to ended — sprint records are inaccurate.
Suggested response
Refine or prune ageing, imbalanced, or inconsistently closed backlog items.
Coaching playbook
Symptom
Issues are closed in Jira more than the configured grace period after the sprint they belonged to ended — sprint records are inaccurate. closure_lag = resolution_date - sprint.end_date
Why it matters
When "Delayed Sprint Closure" 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
Refine or prune ageing, imbalanced, or inconsistently closed backlog items.
Facilitation questions
- What system change would stop "Delayed Sprint Closure" 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.