CC-10

Team Rolling Avg Divergence From Portfolio

Control Chart

Default severity: medium
ProcessMetricsOutputRisk

What it detects

A team\'s rolling average exceeds the all-teams rolling average by more than the configured percentage. delta(T) = rolling_avg(T) - rolling_avg(ALL)

Detection formula

IF delta(T) > rolling_avg(ALL) * config.cc.team_divergence_threshold // default: 30% THEN FLAG Rank teams by delta descending

Examples in practice

  • Rolling averages, control limits, or band width diverge from expected statistical bounds.
  • Recent control-chart windows show drift, clusters, or missing limit configuration.
  • A team shows a team\'s rolling average exceeds the all-teams rolling average by more than the configured percentage while team divergence threshold is set to 30%.

Suggested response

Treat the metric as a control signal: confirm limits, windows, and cross-team spread before acting.

Coaching playbook

Symptom

A team\'s rolling average exceeds the all-teams rolling average by more than the configured percentage. delta(T) = rolling_avg(T) - rolling_avg(ALL)

Why it matters

When "Team Rolling Avg Divergence From Portfolio" 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

Treat the metric as a control signal: confirm limits, windows, and cross-team spread before acting.

Facilitation questions

  • What system change would stop "Team Rolling Avg Divergence From Portfolio" 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.

Product tourSign in
CC-10: Team Rolling Avg Divergence From Portfolio — FlowAnalyzer