Team Workload Fast

Team Workload Fast is a rapid workload analysis command that evaluates how tasks and responsibilities are distributed across team members and surfaces imbalances before they cause burnout or bottlenecks. It examines contribution patterns, current assignments, and individual capacity to produce fast, actionable rebalancing recommendations. Unlike a full workload audit, this command is optimized for speed, delivering results in seconds rather than minutes.

When to Use This Command

Run this command when...

• You notice certain team members consistently working late or carrying disproportionately large backlogs and want data to confirm the imbalance.
• Mid-sprint adjustments are needed because a team member became unavailable and their tasks need to be redistributed quickly.
• A new sprint is starting and you want to ensure the initial assignment distribution accounts for each person's current capacity and expertise.
• You are managing multiple squads or projects and need a fast cross-team view of who has bandwidth for additional work.
• A release deadline is approaching and you need to identify which team members can absorb critical-path tasks without becoming overloaded.

Consider alternatives when...

• You need a deep skill-gap analysis with training recommendations rather than immediate workload rebalancing; a dedicated skills audit is more appropriate.
• The team is a single person or pair working in lockstep, making distribution analysis unnecessary.
• You want long-term capacity planning spanning multiple quarters; use the velocity tracking command instead.

Quick Start

Copy
# .workload-fast.yml
analysis:
  time_window: 14d           # lookback period
  metric: assignments        # assignments | commits | review_load
  include_reviews: true
  burnout_threshold: 1.5     # ratio above team mean triggers alert
output:
  format: summary            # summary | detailed | json

Example invocation:

Copy
team-workload-fast "current sprint rebalance"

Example output:

Workload Distribution (Current Sprint)
---------------------------------------
Team Member       Tasks  Reviews  Load Score  Status
[email protected]       8       3       1.62      OVERLOADED
[email protected]         5       4       1.21      HIGH
[email protected]       3       2       0.72      AVAILABLE
[email protected]        2       1       0.45      AVAILABLE

Recommended Reassignments:
  1. Move TASK-442 (frontend) from alice -> carol [skill match: 92%]
  2. Move TASK-459 (API endpoint) from alice -> dave [skill match: 85%]
  3. Reassign review for PR #287 from bob -> carol [reduce review load]

Projected Load After Rebalancing:
  alice: 1.08 | bob: 1.02 | carol: 0.98 | dave: 0.92

Core Concepts

Concept	Purpose	Details
Load Score	Normalizes workload to a comparable metric	A composite score combining active task count, review responsibilities, and estimated task complexity, normalized against the team mean
Skill Matching	Ensures reassignments respect expertise	Maps each team member's demonstrated skills based on historical contributions to recommend transfers that maintain quality
Burnout Threshold	Flags at-risk individuals early	When a team member's load score exceeds the configured threshold above the team average, they are flagged for immediate attention
Capacity Window	Defines the analysis timeframe	The rolling window of days used to calculate current workload, defaulting to the current sprint duration
Rebalancing Engine	Generates optimal task redistribution	An algorithm that minimizes maximum individual load while respecting skill constraints and task dependencies

            Team Workload Fast Architecture
  +------------------------------------------------------+
  |  INPUT SOURCES                                       |
  |  [Git Commits] [Task Tracker] [PR Reviews]           |
  +------------------------------------------------------+
           |              |              |
           v              v              v
  +------------------------------------------------------+
  |  LOAD CALCULATION                                    |
  |  Per-Member Aggregation --> Normalization --> Scoring |
  +------------------------------------------------------+
           |
           v
  +------------------------------------------------------+
  |  SKILL MATRIX                                        |
  |  Contribution History --> Expertise Mapping           |
  +------------------------------------------------------+
           |
           v
  +------------------------------------------------------+
  |  REBALANCING ENGINE                                  |
  |  Constraint Solver --> Reassignment Proposals         |
  +------------------------------------------------------+
           |
           v
  +------------------------------------------------------+
  |  OUTPUT                                              |
  |  Load Table | Alerts | Reassignment Recommendations  |
  +------------------------------------------------------+

Configuration

Parameter	Type	Default	Description
time_window	string	14d	Lookback period for workload calculation, expressed as days (e.g., 7d, 14d, 30d)
burnout_threshold	float	1.5	Load score ratio above team mean that triggers an overloaded alert for a team member
include_reviews	boolean	true	Whether to include pull request review assignments in the load score calculation
skill_weight	float	0.8	How heavily skill matching influences reassignment recommendations versus pure load balancing
max_reassignments	integer	5	Maximum number of task reassignments to suggest in a single analysis run

Best Practices

1. Run the command at sprint midpoints, not just at the start. Workload distribution changes throughout a sprint as tasks are completed, new issues arise, and team availability shifts. A midpoint check catches imbalances early enough to course-correct before they impact the sprint goal. The speed of this command makes frequent checks practical without disrupting workflow.

2. Calibrate the burnout threshold for your team's culture. The default 1.5x multiplier works for most teams, but high-performing teams with experienced members may tolerate higher loads without stress. Conversely, teams with many junior developers should lower the threshold to account for the additional cognitive load that comes with less experience. Observe and adjust over two or three sprints.

3. Consider review load as a first-class workload component. Code reviews are invisible work that rarely appears on sprint boards but consumes significant mental energy. The command includes reviews in its load calculations by default, and disabling this feature understates the true burden on senior developers who typically review the most code. Keep it enabled for accurate analysis.

4. Use skill matching to grow junior developers deliberately. Rather than always routing reassignments to the person with the highest historical skill match, occasionally assign tasks to someone with a moderate match score who would benefit from the learning opportunity. Use the skill weight parameter to loosen the matching constraint when development goals are a priority.

5. Pair the output with a brief team conversation. Algorithmic recommendations cannot capture context like personal preferences, learning goals, or interpersonal dynamics. Present the rebalancing suggestions to the team as a starting point for discussion rather than a mandate. This preserves team autonomy while still grounding the conversation in objective data.

Common Issues

Load scores seem inaccurate for part-time team members. The command calculates load scores assuming full-time availability by default. Part-time contributors will appear to have artificially low load scores relative to their actual capacity. Fix this by configuring per-member capacity multipliers in the YAML file so that a half-time developer's three tasks are correctly weighted as equivalent to a full-time member's six.

Reassignment suggestions ignore task dependencies. The rebalancing engine considers skill match and load balance but may not detect that two tasks must be handled by the same person due to shared context or sequential dependencies. Review each suggestion against your sprint board before acting on it. If this happens frequently, add dependency annotations to your task metadata so the command can account for them.

Command reports all members as equally loaded despite visible imbalance. This occurs when the analysis relies solely on task count without factoring in task complexity or size. A team member with two large epics is far busier than someone with two small bug fixes, but they appear equal by count. Switch the metric to a weighted mode that incorporates story points or estimated hours for a more accurate picture.