RA-08

Resource Velocity — Per-Person Throughput Tracking

Resource Allocation

Default severity: medium
ProcessOutputRiskEffort

What it detects

Computes per-person throughput (issues completed, SP delivered, hours logged) per sprint over the last N sprints. Identifies individuals whose output is declining, individuals whose output is consistently higher than peers (potential burnout risk), and confirms whether the team\'s velocity is uniformly distributed or driven by one or two individuals.

Detection formula

N = config.ra.velocity_baseline_sprints // default: 6 sprints FOR each_person P: FOR each_sprint S: completed_issues(P, S) = COUNT(issues WHERE primary_author_or_assignee=P AND resolved IN S) completed_sp(P, S) = SUM(story_points, above) hours_logged(P, S) = SUM(worklog.time_spent WHERE author=P AND started IN S) velocity_trend(P) = linear_regression(\[completed_sp(P,S) FOR S in last N\]).slope IF velocity_trend(P) \< -config.ra.declining_velocity_threshold // default: -10% per sprint THEN FLAG person_velocity_declining IF completed_sp(P) > team_avg_sp * config.ra.outlier_high_multiplier // default: 2.0x THEN FLAG potential_burnout_risk Report: per-person velocity table, trend direction, comparison to team avg

Examples in practice

  • One person owns a disproportionate share of critical-path or high-WIP work.
  • Delivery risk rises when a single expert becomes the throughput bottleneck.
  • A team shows computes per-person throughput (issues completed, sp delivered, hours logged) per sprint over the last n sprints while velocity baseline sprints is set to 6 sprints.

Suggested response

Reduce single points of failure—spread critical skills and lighten overloaded contributors.

Coaching playbook

Symptom

Computes per-person throughput (issues completed, SP delivered, hours logged) per sprint over the last N sprints. Identifies individuals whose output is declining, individuals whose output is consistently higher than peers (potential burnout risk), and confirms whether the team\'s velocity is uniformly distributed or driven by one or two individuals.

Why it matters

When "Resource Velocity — Per-Person Throughput Tracking" 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

Reduce single points of failure—spread critical skills and lighten overloaded contributors.

Facilitation questions

  • What system change would stop "Resource Velocity — Per-Person Throughput Tracking" 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
RA-08: Resource Velocity — Per-Person Throughput Tracking — FlowAnalyzer