BH-04
Zero or Near-Zero Estimation Coverage
Backlog Health
Default severity: medium
Product BacklogPrioritizationRiskEffort
What it detects
More than the configured percentage of in-scope issues have no story points — velocity and forecasting are impossible. unestimated = COUNT(issues WHERE story_points IS NULL OR = 0 AND type IN config.estimation.required_estimate_types)
Detection formula
IF unestimated / total_in_scope > config.backlog.critical_unestimated_pct // default: 80% THEN CRITICAL IF unestimated / total > config.backlog.warning_unestimated_pct // default: 60% THEN FLAGExamples in practice
- A team shows more than the configured percentage of in-scope issues have no story points while critical unestimated pct is set to 80%.
- Example signal: More than the configured percentage of in-scope issues have no story points — velocity and forecasting are impossible.
Suggested response
Refine or prune ageing, imbalanced, or inconsistently closed backlog items.
Coaching playbook
Symptom
More than the configured percentage of in-scope issues have no story points — velocity and forecasting are impossible. unestimated = COUNT(issues WHERE story_points IS NULL OR = 0 AND type IN config.estimation.required_estimate_types)
Why it matters
When "Zero or Near-Zero Estimation Coverage" 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
Refine or prune ageing, imbalanced, or inconsistently closed backlog items.
Facilitation questions
- What system change would stop "Zero or Near-Zero Estimation Coverage" 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.