Team Capacity Planner

The Challenge

Sprint planning often ignores real capacity. PTO, recurring meetings, and on-call duties reduce available time, leading to overcommitment and missed targets.

The AI Desk Solution

AI Desk calculates true team capacity by analyzing calendars, PTO, and historical patterns.

The Workflow

Step 1: Sprint Planning

Trigger: Sprint planning meeting
Sources: Calendars, PTO, velocity history

Step 2: Capacity Calculation

• Available hours per person
• Meeting load analysis
• Historical accuracy

Step 3: Capacity Report

📊 Sprint 25 Capacity Plan

SPRINT DATES: Apr 22 - May 5, 2026
WORKING DAYS: 10

TEAM CAPACITY

Jamie Chen
├── Available days: 8 (2 days PTO)
├── Meeting load: 25%
├── Effective capacity: 48 hours
├── Historical velocity: 18 pts
└── Recommended: 14 points

Alex Rivera
├── Available days: 10
├── Meeting load: 15%
├── On-call: 2 days
├── Effective capacity: 58 hours
└── Recommended: 20 points

Dana Kim
├── Available days: 9 (1 day training)
├── Meeting load: 30%
├── Effective capacity: 50 hours
└── Recommended: 16 points

TEAM SUMMARY
├── Total capacity: 156 hours
├── Recommended points: 50
├── Historical avg: 52 pts/sprint
├── Last sprint: 48 pts (93% of plan)
└── Stretch target: 55 points

RISKS
├── ⚠️ Jamie's PTO overlaps with deadline
├── ⚠️ Alex on-call may impact velocity
└── ✓ No major dependencies this sprint

RECOMMENDATIONS
├── Plan for 50 points (conservative)
├── Keep 5-point buffer for unknowns
├── Front-load Jamie's work
└── Assign on-call-friendly tasks to Alex

Value Proposition

• Time Saved: 1 hour per sprint
• Realistic Plans: True capacity
• Fewer Surprises: Risks surfaced early