SP-02
Velocity Reporting Gap
Sprint / Planning
Default severity: critical
PrioritizationEstimationOutputEffort
What it detects
Ratio of reported spent time to expected effort (based on velocity and configured hours-per-SP) falls below the configured threshold. expected_effort = velocity * config.sprint.hours_per_sp // default: 8h/SP
Detection formula
IF reported_spent_time / expected_effort \< config.sprint.min_reporting_ratio // default: 0.6 THEN FLAGExamples in practice
- Sprint commitments, velocity, or late scope changes tell conflicting planning stories.
- Committed scope shifts materially after the sprint lock point.
- A team shows ratio of reported spent time to expected effort (based on velocity and configured hours-per-sp) falls below the configured threshold while min reporting ratio is set to 0.6.
Suggested response
Reconcile sprint commitments, velocity signals, and late scope changes with the team.
Coaching playbook
Symptom
Ratio of reported spent time to expected effort (based on velocity and configured hours-per-SP) falls below the configured threshold. expected_effort = velocity * config.sprint.hours_per_sp // default: 8h/SP
Why it matters
When "Velocity Reporting 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
Reconcile sprint commitments, velocity signals, and late scope changes with the team.
Facilitation questions
- What system change would stop "Velocity Reporting 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.