VL-07
Velocity Declining Trend — Sustained Reduction Over Time
Velocity
Default severity: medium
PrioritizationEstimationOutputEffort
What it detects
Completed velocity is decreasing across consecutive sprints in any dimension — the team is delivering less over time, not more. A declining trend that persists for 3+ sprints is a systemic signal, not noise. Common causes: increasing tech debt, team attrition, rising bug ratio consuming capacity, or growing WIP.
Detection formula
FOR each_dimension D: velocity_series(D) = \[completed(D, S) FOR S IN baseline_sprints ORDER BY date ASC\] slope(D) = linear_regression(velocity_series(D)).slope r_squared(D) = linear_regression(velocity_series(D)).r_squared IF slope(D) \< 0 AND r_squared(D) > config.vl.trend_r_squared // default: 0.55 AND COUNT(sprints with negative delta) >= config.vl.declining_min_sprints // default: 3 THEN FLAG velocity_declining in dimension D IF slope(D) \< -(baseline(D).avg * config.vl.critical_decline_rate_per_sprint) // default: 5% per sprint THEN CRITICALExamples in practice
- A team shows completed velocity is decreasing across consecutive sprints in any dimension while trend r squared is set to 0.55.
- Example signal: Completed velocity is decreasing across consecutive sprints in any dimension — the team is delivering less over time, not more.
Suggested response
Plan to historical capacity—avoid repeated over or under-commitment and unstable velocity.
Coaching playbook
Symptom
Completed velocity is decreasing across consecutive sprints in any dimension — the team is delivering less over time, not more. A declining trend that persists for 3+ sprints is a systemic signal, not noise. Common causes: increasing tech debt, team attrition, rising bug ratio consuming capacity, or growing WIP.
Why it matters
When "Velocity Declining Trend — Sustained Reduction Over Time" 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
Plan to historical capacity—avoid repeated over or under-commitment and unstable velocity.
Facilitation questions
- What system change would stop "Velocity Declining Trend — Sustained Reduction Over Time" 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.