BC-05
Burn-Up — Completion Rate Insufficient for Target Date
Burn Charts
Default severity: medium
PrioritizationMetricsOutputEffort
What it detects
The current completion slope, if sustained, will not reach the total scope by the configured target date or PI end date — across any tracked dimension. Provides projected completion date vs committed date gap.
Detection formula
FOR each_dimension D: completion_rate(D) = done_slope(D) // units per day remaining_units(D) = total_committed(D) - total_done(D) days_to_done(D) = remaining_units(D) / max(0.01, completion_rate(D)) projected_end(D) = today + days_to_done(D) IF projected_end(D) > config.planning.target_date THEN FLAG gap_days = projected_end(D) - config.planning.target_date IF gap_days > config.bc.critical_date_gap_days // default: 14d THEN CRITICALExamples in practice
- A team shows the current completion slope, if sustained, will not reach the total scope by the configured target date or pi end date while target date is set to Configured per workspace.
- Example signal: The current completion slope, if sustained, will not reach the total scope by the configured target date or PI end date — across any tracked dimension.
Suggested response
Re-plan remaining scope when burn charts show late work, scope creep, or stalls.
Coaching playbook
Symptom
The current completion slope, if sustained, will not reach the total scope by the configured target date or PI end date — across any tracked dimension. Provides projected completion date vs committed date gap.
Why it matters
When "Burn-Up — Completion Rate Insufficient for Target Date" 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 "Burn-Up — Completion Rate Insufficient for Target Date" 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.