DV-16
Team Capacity Not Updated After Significant Change
Discipline
Default severity: medium
ProcessMetricsQuality
What it detects
Sprint velocity has changed by more than the configured threshold compared to the previous period, but team capacity configuration has not been updated — capacity-based rules (DV-12, SP-01) will compute incorrect baselines. velocity_change = ABS(velocity_current - velocity_prev) / velocity_prev
Detection formula
IF velocity_change > config.discipline.capacity_update_velocity_threshold // default: 25% AND config_last_updated \< sprint_start_date THEN WARN capacity_config_staleExamples in practice
- Assignee, field, hierarchy, or sprint hygiene rules are violated on active work.
- Issues miss mandatory fields or ownership while still in progress.
- A team shows sprint velocity has changed by more than the configured threshold compared to the previous period, but team capacity configuration has not been updated while capacity update velocity threshold is set to 25%.
Suggested response
Enforce assignee, field, hierarchy, and sprint hygiene rules your team agreed on.
Coaching playbook
Symptom
Sprint velocity has changed by more than the configured threshold compared to the previous period, but team capacity configuration has not been updated — capacity-based rules (DV-12, SP-01) will compute incorrect baselines. velocity_change = ABS(velocity_current - velocity_prev) / velocity_prev
Why it matters
When "Team Capacity Not Updated After Significant Change" 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
Enforce assignee, field, hierarchy, and sprint hygiene rules your team agreed on.
Facilitation questions
- What system change would stop "Team Capacity Not Updated After Significant Change" 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.