HY-02
Story Point Coverage Gap
Hygiene
Default severity: critical
ProcessMetricsQuality
What it detects
A configured feature area has spent time percentage exceeding its story point percentage by the configured multiplier — effort is invisible in planning.
Detection formula
IF (spent_time_pct\[area\] / sp_pct\[area\]) > config.hygiene.coverage_gap_multiplier // default: 5x THEN FLAG as invisible effort Report: area, sp_pct, spent_time_pct, gap_ratioExamples in practice
- Baseline fields or story data are edited outside agreed roles or left incomplete.
- Changelog sparsity makes it hard to trust historical metrics.
- A team shows a configured feature area has spent time percentage exceeding its story point percentage by the configured multiplier while coverage gap multiplier is set to 5x.
Suggested response
Reduce silent edits—enforce who may change baselines and keep story data complete.
Coaching playbook
Symptom
A configured feature area has spent time percentage exceeding its story point percentage by the configured multiplier — effort is invisible in planning.
Why it matters
When "Story Point Coverage Gap" 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
Reduce silent edits—enforce who may change baselines and keep story data complete.
Facilitation questions
- What system change would stop "Story Point Coverage Gap" 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.