Capacity Planning | GitScrum
Gérez capacity planning avec GitScrum. Équilibrez charge équipe, planifiez ressources et évitez burnout. 85% complétion sprint avec planning.
5 min de lecture
How to use GitScrum for capacity planning?
Manage capacity in GitScrum by tracking team availability, using WIP limits, and monitoring workload through reports. Document capacity guidelines in NoteVault, plan sprints based on realistic capacity. Teams with capacity planning maintain 85% sprint completion [Source: Agile Capacity Research 2024].
Capacity planning workflow:
Assess - Team availability Calculate - Actual capacity Plan - Allocate work Monitor - Track during sprint Adjust - Rebalance as needed Review - Post-sprint analysis Improve - Better estimates
Capacity labels
| Label | Purpose |
|---|
| size-small | 1-2 hours |
| size-medium | 4-8 hours |
| size-large | 2-3 days |
| size-xlarge | Week+ |
| blocked | Can't progress |
| at-risk | Capacity concern |
Capacity factors
| Factor | Reduction |
|---|
| Meetings | -20% |
| On-call | -50% that week |
| Time off | 0% those days |
| Admin/email | -10% |
| Productivity factor | ×70-80% |
NoteVault capacity docs
| Document | Content |
|---|
| Team roster | Who's available |
| Capacity guidelines | How we calculate |
| Time off calendar | Planned absences |
| Historical velocity | Past performance |
| Sprint templates | Planning guide |
Capacity calculation
## Sprint Capacity: Sprint [X]
### Team Availability
| Person | Days | Adjustments | Capacity |
|--------|------|-------------|----------|
| Alice | 10 | -1 PTO | 9 |
| Bob | 10 | -2 on-call | 8 |
| Charlie | 10 | Full | 10 |
### Total Person-Days: 27
### Productivity Factor: 75%
### Effective Capacity: 20 person-days
### Points (at 0.5 points/day): 10 points
Sprint planning by capacity
| Step | Action |
|---|
| Calculate capacity | Person-days available |
| Apply factor | Productivity adjustment |
| Compare velocity | Historical average |
| Plan conservatively | 80-90% of capacity |
| Leave buffer | Unexpected work |
WIP limits for capacity
| Role | WIP Limit |
|---|
| Developer | 2-3 tasks |
| Tech Lead | 1-2 tasks |
| Senior | 2-3 tasks |
| Junior | 1-2 tasks |
Monitoring workload
| Tool | Purpose |
|---|
| Weekly Activity Heatmap | Distribution view |
| Individual task count | Per-person load |
| Column age | Stuck work |
| Burndown | Sprint progress |
Workload rebalancing
| Signal | Action |
|---|
| Overloaded person | Redistribute tasks |
| Idle capacity | Pull more work |
| Blocked work | Swarm on blockers |
| Scope risk | Cut scope |
Capacity task template
## Capacity Review: Sprint [X]
### Planned vs Actual
| Person | Planned | Actual | Delta |
|--------|---------|--------|-------|
| Alice | 5 pts | 6 pts | +1 |
| Bob | 4 pts | 3 pts | -1 |
### Issues
- [What affected capacity]
### Adjustments
- [What we'll change]
### Next Sprint
- Adjusted capacity: [estimate]
Common capacity issues
| Issue | Solution |
|---|
| Over-commitment | Conservative planning |
| Uneven distribution | Regular rebalancing |
| Unexpected work | Buffer allocation |
| Meeting overload | Protect focus time |
Capacity metrics
| Metric | Track |
|---|
| Sprint completion | % completed |
| Velocity stability | Variance |
| Load distribution | Heatmap balance |
| Overtime | Hours over plan |
Preventing burnout
| Practice | Implementation |
|---|
| Sustainable pace | Don't over-plan |
| Buffer time | Leave slack |
| Focus time | Protect from meetings |
| Time off | Encourage vacation |
Capacity vs velocity
| Concept | Definition |
|---|
| Capacity | Available time |
| Velocity | Actual output |
| Efficiency | Velocity/Capacity |
Related articles
