BC-01
Sprint Burn-Down — Insufficient Daily Progress
Burn Charts
Default severity: medium
PrioritizationMetricsOutputEffort
What it detects
The sprint burn-down line is not decreasing at the required daily rate across any of the four tracked dimensions. Detected separately for: remaining issue count, remaining story points, remaining estimated time, and remaining business value. A flat or rising burn-down in any dimension indicates the sprint will not deliver as committed.
Detection formula
FOR each_dimension D IN \[issue_count, story_points, estimated_hours, business_value\]: ideal_daily_rate(D) = total_committed(D, sprint) / sprint_duration_days actual_rate(D) = AVG(delta(remaining(D)), last config.bc.burndown_check_window_days) // default: 3d IF actual_rate(D) \< ideal_daily_rate(D) * config.bc.burndown_progress_threshold // default: 0.5 THEN FLAG dimension D as behind IF actual_rate(D) \<= 0 THEN CRITICAL (no progress in checked window)Examples in practice
- A team shows the sprint burn-down line is not decreasing at the required daily rate across any of the four tracked dimensions while burndown check window days is set to 3d.
- Example signal: The sprint burn-down line is not decreasing at the required daily rate across any of the four tracked dimensions.
Suggested response
Re-plan remaining scope when burn charts show late work, scope creep, or stalls.
Coaching playbook
Symptom
The sprint burn-down line is not decreasing at the required daily rate across any of the four tracked dimensions. Detected separately for: remaining issue count, remaining story points, remaining estimated time, and remaining business value. A flat or rising burn-down in any dimension indicates the sprint will not deliver as committed.
Why it matters
When "Sprint Burn-Down — Insufficient Daily Progress" 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
Re-plan remaining scope when burn charts show late work, scope creep, or stalls.
Facilitation questions
- What system change would stop "Sprint Burn-Down — Insufficient Daily Progress" 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.