BC-08
Business Value Burn-Up — BV Back-Loaded
Burn Charts
Default severity: medium
PrioritizationMetricsOutputEffort
What it detects
Business value is being delivered in the second half of the PI/initiative rather than front-loaded — high-BV items are planned later in the schedule, meaning the organisation receives no value until late in the delivery cycle. bv_series = \[cumulative_bv_delivered per week\] midpoint_week = total_weeks / 2 bv_at_midpoint = bv_series\[midpoint_week\]
Detection formula
IF bv_at_midpoint / total_bv \< config.bc.bv_frontload_threshold // default: 0.35 (less than 35% BV by midpoint) THEN FLAG bv_back_loaded Report: BV delivered by week, highlight which high-BV epics are scheduled lateExamples in practice
- A team shows business value is being delivered in the second half of the pi/initiative rather than front-loaded while bv frontload threshold is set to 0.35 (less than 35% BV by midpoint).
- Example signal: Business value is being delivered in the second half of the PI/initiative rather than front-loaded — high-BV items are planned later in the schedule, meaning the organisation receives no value until late in the delivery cycle.
Suggested response
Re-plan remaining scope when burn charts show late work, scope creep, or stalls.
Coaching playbook
Symptom
Business value is being delivered in the second half of the PI/initiative rather than front-loaded — high-BV items are planned later in the schedule, meaning the organisation receives no value until late in the delivery cycle. bv_series = \[cumulative_bv_delivered per week\] midpoint_week = total_weeks / 2 bv_at_midpoint = bv_series\[midpoint_week\]
Why it matters
When "Business Value Burn-Up — BV Back-Loaded" 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 "Business Value Burn-Up — BV Back-Loaded" 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.