Workload Balancing Across Team Members | Capacity
Distribute work fairly and prevent burnout. GitScrum shows tasks per person and capacity utilization for informed assignment decisions.
8 min read
Balanced workloads mean better quality and healthier teams. GitScrum provides visibility into team capacity so work can be distributed fairly.
Why Balance Matters
Unbalanced Team Problems
SIGNS OF WORKLOAD IMBALANCE:
┌─────────────────────────────────────────────────────────────┐
│ │
│ OVERLOADED MEMBER: │
│ │
│ @alex: 45 points assigned │
│ │ │
│ ├─ Working late consistently │
│ ├─ Quality slipping │
│ ├─ Skipping documentation │
│ ├─ Missing meetings │
│ └─ Burnout risk HIGH │
│ │
│ UNDERUTILIZED MEMBER: │
│ │
│ @jordan: 12 points assigned │
│ │ │
│ ├─ Finishing early │
│ ├─ Taking on unrelated work │
│ ├─ Not growing skills │
│ └─ Feeling undervalued │
│ │
│ ─────────────────────────────────────────────────────────── │
│ │
│ TEAM IMPACT: │
│ │
│ • Single point of failure (only Alex knows X) │
│ • Resentment builds │
│ • Knowledge silos form │
│ • Predictability suffers │
│ • Quality becomes inconsistent │
│ • Team velocity masked by individual overtime │
│ │
│ THE MATH: │
│ Overloaded person works 60h → burns out → leaves │
│ Cost: Hiring + training + lost knowledge │
│ Better: Balanced 40h/person → sustainable team │
└─────────────────────────────────────────────────────────────┘
Measuring Workload
Visibility into Capacity
GITSCRUM WORKLOAD DASHBOARD:
┌─────────────────────────────────────────────────────────────┐
│ TEAM CAPACITY - Sprint 24 │
├─────────────────────────────────────────────────────────────┤
│ │
│ CAPACITY TARGET: 25-30 pts/person │
│ │
│ @alex [██████████████████████████████░░░] 38 pts ⚠️ │
│ @maria [█████████████████████████░░░░░░░░] 28 pts ✅ │
│ @jordan [████████████░░░░░░░░░░░░░░░░░░░░░] 14 pts ⬇️ │
│ @chen [████████████████████████░░░░░░░░░] 26 pts ✅ │
│ @taylor [███████████████████████████████░░] 34 pts ⚠️ │
│ │
│ LEGEND: │
│ ✅ On target (25-30 pts) │
│ ⚠️ Over capacity (>30 pts) │
│ ⬇️ Under capacity (<25 pts) │
│ │
│ ─────────────────────────────────────────────────────────── │
│ │
│ ACTIONS NEEDED: │
│ │
│ • Move 8 pts from @alex to @jordan │
│ • Review @taylor assignments │
│ • Consider @jordan for stretch assignment │
│ │
│ UNASSIGNED: 12 pts │
│ [View unassigned tasks] │
└─────────────────────────────────────────────────────────────┘
Capacity Factors
CALCULATING REAL CAPACITY:
┌─────────────────────────────────────────────────────────────┐
│ │
│ STANDARD CAPACITY ≠ ACTUAL CAPACITY │
│ │
│ FACTORS THAT REDUCE CAPACITY: │
│ │
│ TIME OFF: │
│ @maria: PTO Mon-Wed = -3 days = -12 pts │
│ @chen: Sick day = -1 day = -4 pts │
│ │
│ MEETINGS: │
│ @taylor: Sprint lead duties = -20% = -5 pts │
│ @alex: Interview loop = -4 hrs = -2 pts │
│ │
│ SUPPORT ROTATION: │
│ @jordan: On-call this week = -25% = -6 pts │
│ │
│ ONBOARDING: │
│ @newdev: Still learning = 50% capacity = 12 pts max │
│ │
│ ─────────────────────────────────────────────────────────── │
│ │
│ ADJUSTED CAPACITY THIS SPRINT: │
│ │
│ Person Base Adjustments Available │
│ ────────── ───── ─────────── ───────── │
│ @alex 28 -2 (interviews) 26 pts │
│ @maria 28 -12 (PTO) 16 pts │
│ @jordan 28 -6 (on-call) 22 pts │
│ @chen 28 -4 (sick) 24 pts │
│ @taylor 28 -5 (lead) 23 pts │
│ │
│ Total available: 111 pts (vs 140 standard) │
│ │
│ Plan for actual capacity, not theoretical │
└─────────────────────────────────────────────────────────────┘
Balancing Strategies
Task Assignment
FAIR ASSIGNMENT PRINCIPLES:
┌─────────────────────────────────────────────────────────────┐
│ │
│ 1. MATCH SKILL TO TASK │
│ │
│ Complex auth work → @alex (security expert) │
│ UI polish → @maria (frontend specialist) │
│ Learning opportunity → @jordan + mentor │
│ │
│ 2. CONSIDER GROWTH │
│ │
│ Senior always gets complex work? │
│ → Junior never learns │
│ │
│ Better: Pair junior on complex, solo on moderate │
│ │
│ 3. ROTATE UNDESIRABLE TASKS │
│ │
│ Bug duty, on-call, legacy code │
│ → Rotate fairly, track in spreadsheet │
│ │
│ 4. AVOID THE "EXPERT TRAP" │
│ │
│ "Only Alex knows payments" │
│ → Alex gets all payment work │
│ → Alex is overloaded, single point of failure │
│ │
│ Solution: Pair others with Alex to spread knowledge │
│ │
│ 5. RESPECT PREFERENCES │
│ │
│ @chen dislikes meetings → fewer sync-heavy tasks │
│ @taylor loves complexity → give hard problems │
│ Balance challenge and comfort │
└─────────────────────────────────────────────────────────────┘
Sprint Planning Balance
BALANCED SPRINT PLANNING:
┌─────────────────────────────────────────────────────────────┐
│ │
│ STEP 1: CALCULATE ADJUSTED CAPACITY │
│ │
│ Total capacity: 111 pts (see adjustments) │
│ │
│ STEP 2: SET INDIVIDUAL TARGETS │
│ │
│ @alex: 26 pts available → Assign 24-26 pts │
│ @maria: 16 pts available → Assign 14-16 pts │
│ @jordan: 22 pts available → Assign 20-22 pts │
│ @chen: 24 pts available → Assign 22-24 pts │
│ @taylor: 23 pts available → Assign 21-23 pts │
│ │
│ STEP 3: ASSIGN WITH VISIBILITY │
│ │
│ During planning: │
│ "This 8-point task - who has capacity?" │
│ [Show workload board] │
│ "@jordan at 14, @chen at 16 - either can take it" │
│ │
│ STEP 4: CHECK BEFORE FINISHING │
│ │
│ Before ending planning: │
│ • Anyone over capacity? │
│ • Anyone significantly under? │
│ • Rebalance if needed │
│ │
│ STEP 5: BUFFER │
│ │
│ Leave 10-15% capacity unassigned │
│ → Room for emergent work │
│ → Prevents overload from unknowns │
└─────────────────────────────────────────────────────────────┘
Monitoring Balance
During Sprint
MID-SPRINT BALANCE CHECK:
┌─────────────────────────────────────────────────────────────┐
│ │
│ WEDNESDAY CHECK-IN (Mid-Sprint): │
│ │
│ BURNDOWN BY PERSON: │
│ │
│ @alex [█████████░░░░░░░] 60% done, on track │
│ @maria [████████████░░░░] 75% done, ahead │
│ @jordan [███░░░░░░░░░░░░░] 20% done, behind ⚠️ │
│ @chen [█████████░░░░░░░] 55% done, on track │
│ @taylor [████████░░░░░░░░] 50% done, on track │
│ │
│ ACTION FOR @jordan: │
│ │
│ Investigate: │
│ □ Blocked on something? │
│ □ Task harder than estimated? │
│ □ Need help? │
│ │
│ Options: │
│ □ Pair with @maria (ahead) │
│ □ Move task to someone else │
│ □ Reduce scope │
│ │
│ DON'T WAIT UNTIL END OF SPRINT │
│ Catch imbalance early → easier to fix │
└─────────────────────────────────────────────────────────────┘
Long-term Patterns
TRACKING WORKLOAD OVER TIME:
┌─────────────────────────────────────────────────────────────┐
│ │
│ 3-MONTH TREND ANALYSIS: │
│ │
│ S21 S22 S23 S24 Avg │
│ ───────────────────────────────────────────── │
│ @alex 32 35 38 38 36 ⚠️ │
│ @maria 28 26 28 16 25 ✅ │
│ @jordan 18 16 14 22 18 ⬇️ │
│ @chen 30 28 26 24 27 ✅ │
│ @taylor 26 30 34 34 31 ⚠️ │
│ │
│ PATTERN IDENTIFIED: │
│ │
│ @alex: Consistently overloaded │
│ → Action: Actively limit assignments │
│ → Share expertise with team │
│ │
│ @jordan: Consistently under capacity │
│ → Action: Give stretch assignments │
│ → Pair on complex work to grow │
│ │
│ @taylor: Trending toward overload │
│ → Action: Monitor closely │
│ → Review if lead duties are too much │
│ │
│ RETROSPECTIVE TOPIC: │
│ "How is our workload distribution?" │
│ "Is anyone consistently stressed or bored?" │
└─────────────────────────────────────────────────────────────┘
Team Self-Balancing
Empowering the Team
TEAM-DRIVEN BALANCE:
┌─────────────────────────────────────────────────────────────┐
│ │
│ MANAGER COMMAND: │
│ "Alex, take this task" │
│ "Jordan, you're underutilized" │
│ → Creates resentment, misses context │
│ │
│ TEAM SELF-ORGANIZATION: │
│ │
│ Make workload visible to all │
│ ↓ │
│ Team sees imbalance │
│ ↓ │
│ Team discusses in standup │
│ ↓ │
│ Team rebalances themselves │
│ │
│ STANDUP EXAMPLE: │
│ │
│ @alex: "I'm swamped with this integration" │
│ @maria: "I finished early, can I help?" │
│ @jordan: "I can take the smaller task from Alex" │
│ │
│ FACILITATING SELF-BALANCE: │
│ │
│ ✅ Visible workload data │
│ ✅ Culture where asking for help is normal │
│ ✅ No blame for being over/under │
│ ✅ Skills matrix (who can do what) │
│ ✅ Safe to say "I'm overloaded" │
│ ✅ Safe to offer help │
│ │
│ MANAGER ROLE: │
│ Enable visibility, facilitate discussion, step in rarely │
└─────────────────────────────────────────────────────────────┘