PR-07
Business Value Delivery Rate Advisory
Planning Recommendations
Default severity: medium
PrioritizationEstimationOutputBusiness Value
What it detects
If BV field is configured, advises the Product Owner on the expected BV delivery rate per sprint and PI, and how many high-BV items to include per sprint to hit the PI BV target. Helps avoid BC-08 (BV back-loading) through proactive sprint composition guidance.
Detection formula
IF bv_field NOT configured THEN SKIP pi_bv_target = SUM(bv, all_items_in_pi_scope) sprints_remaining = config.planning.sprints_remaining_in_pi required_bv_per_sprint = pi_bv_target / max(1, sprints_remaining) high_bv_items_needed = CEIL(required_bv_per_sprint / avg_bv_per_high_bv_item) current_sprint_planned_bv = SUM(bv, issues IN current_sprint) IF current_sprint_planned_bv \< required_bv_per_sprint * 0.8 THEN FLAG underscheduled_bv FORMAT: \'BV advisory: this sprint should include at least {required_bv_per_sprint} BV points to stay on track for PI BV target. Currently planned: {current_sprint_planned_bv} BV. Include {high_bv_items_needed} high-BV items.\'Examples in practice
- A team shows if bv field is configured, advises the product owner on the expected bv delivery rate per sprint and pi, and how many high-bv items to include per sprint to hit the pi bv target while sprints remaining in pi is set to Configured per workspace.
- Example signal: If BV field is configured, advises the Product Owner on the expected BV delivery rate per sprint and PI, and how many high-BV items to include per sprint to hit the PI BV target.
Suggested response
Use the advisory outputs to tune refinement, WIP, and planning cadence with data.
Coaching playbook
Symptom
If BV field is configured, advises the Product Owner on the expected BV delivery rate per sprint and PI, and how many high-BV items to include per sprint to hit the PI BV target. Helps avoid BC-08 (BV back-loading) through proactive sprint composition guidance.
Why it matters
When "Business Value Delivery Rate Advisory" 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
Use the advisory outputs to tune refinement, WIP, and planning cadence with data.
Facilitation questions
- What system change would stop "Business Value Delivery Rate Advisory" 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.