CO-05
Business Value Carry-Over — Committed BV Not Delivered
Carry-Over
Default severity: medium
PrioritizationOutputRiskEffort
What it detects
The amount of business value that was committed in sprint/PI planning but not delivered (carried over or descoped) exceeds the configured BV threshold. This is the executive-level impact measure of over-planning — it quantifies the value promised but not received.
Detection formula
IF config.workflow.bv_field IS NULL THEN SKIP FOR each_sprint S: committed_bv(S) = SUM(bv, issues committed to S AT sprint.start) delivered_bv(S) = SUM(bv, issues Done IN S) undelivered_bv(S) = committed_bv(S) - delivered_bv(S) bv_carryover_rate(S) = undelivered_bv(S) / max(1, committed_bv(S)) IF bv_carryover_rate(S) > config.co.bv_carryover_threshold // default: 30% THEN FLAG IF bv_carryover_rate(S) > config.co.critical_bv_carryover // default: 50% THEN CRITICAL — majority of committed BV not deliveredExamples in practice
- A team shows the amount of business value that was committed in sprint/pi planning but not delivered (carried over or descoped) exceeds the configured bv threshold while bv field is set to Configured per workspace.
- Example signal: The amount of business value that was committed in sprint/PI planning but not delivered (carried over or descoped) exceeds the configured BV threshold.
Suggested response
Address chronic carry-over by rightsizing sprints and finishing or splitting stuck work.
Coaching playbook
Symptom
The amount of business value that was committed in sprint/PI planning but not delivered (carried over or descoped) exceeds the configured BV threshold. This is the executive-level impact measure of over-planning — it quantifies the value promised but not received.
Why it matters
When "Business Value Carry-Over — Committed BV Not Delivered" 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
Address chronic carry-over by rightsizing sprints and finishing or splitting stuck work.
Facilitation questions
- What system change would stop "Business Value Carry-Over — Committed BV Not Delivered" 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.