IA-04
Age Pyramid — Team-Level Aging Profile
Issue Age
Default severity: medium
Product BacklogPrioritizationRiskEffort
What it detects
Computes per-team age profiles across all active issues to identify which teams carry the oldest in-flight work. A team with many items aged above the portfolio average cycle time is effectively overloaded and under-delivering.
Detection formula
FOR each_team T: active_issues(T) = issues WHERE assignee.team=T AND status IN config.workflow.active_statuses avg_age(T) = AVG(today - issue.start_date, active_issues(T)) pct_above_ucl(T) = COUNT(active_issues WHERE age > UCL) / COUNT(active_issues(T)) IF avg_age(T) > portfolio_avg_cycle_time * config.ia.team_age_threshold // default: 1.3x THEN FLAG team_overloaded Report: ranked table of teams by avg active issue age; pyramid chart per teamExamples in practice
- A team shows computes per-team age profiles across all active issues to identify which teams carry the oldest in-flight work while active statuses is set to Configured per workspace.
- Example signal: Computes per-team age profiles across all active issues to identify which teams carry the oldest in-flight work.
Suggested response
Age down old items: shorten time-in-status, clear blockers, and focus high-value ageing work.
Coaching playbook
Symptom
Computes per-team age profiles across all active issues to identify which teams carry the oldest in-flight work. A team with many items aged above the portfolio average cycle time is effectively overloaded and under-delivering.
Why it matters
When "Age Pyramid — Team-Level Aging Profile" 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
Age down old items: shorten time-in-status, clear blockers, and focus high-value ageing work.
Facilitation questions
- What system change would stop "Age Pyramid — Team-Level Aging Profile" 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.