BC-09
Business Value Burn-Up — Zero BV Delivered in PI
Burn Charts
Default severity: medium
PrioritizationMetricsOutputEffort
What it detects
No business value has been delivered in the current PI period across the entire initiative — all completed items have BV=0 or BV field not set, while high-BV items remain open. The PI is delivering output but not outcome. current_pi_done = issues WHERE status IN done_statuses AND resolved_in_current_pi bv_delivered_pi = SUM(bv
Detection formula
FOR issue IN current_pi_done WHERE bv > 0) IF bv_delivered_pi = 0 AND COUNT(current_pi_done) > 0 THEN FLAG IF bv_delivered_pi = 0 AND COUNT(open_high_bv_issues) > 0 THEN CRITICAL Report: list of open high-BV items still in backlogExamples in practice
- A team shows no business value has been delivered in the current pi period across the entire initiative during analysis.
- Example signal: No business value has been delivered in the current PI period across the entire initiative — all completed items have BV=0 or BV field not set, while high-BV items remain open.
Suggested response
Re-plan remaining scope when burn charts show late work, scope creep, or stalls.
Coaching playbook
Symptom
No business value has been delivered in the current PI period across the entire initiative — all completed items have BV=0 or BV field not set, while high-BV items remain open. The PI is delivering output but not outcome. current_pi_done = issues WHERE status IN done_statuses AND resolved_in_current_pi bv_delivered_pi = SUM(bv
Why it matters
When "Business Value Burn-Up — Zero BV Delivered in PI" 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 — Zero BV Delivered in PI" 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.