4 min leitura • Guide 434 of 877
How to Manage Pair Programming Sessions in Sprints?
How to manage pair programming sessions in sprints?
Manage pair programming by scheduling dedicated pairing time, assigning pairing tasks on the board, rotating partners regularly, documenting patterns in NoteVault, and tracking outcomes. Use labels to identify pairing tasks, include pairing in sprint capacity planning, and treat it as investment in quality and knowledge sharing.
Pairing labels
| Label | Purpose |
|---|---|
| pairing | Pair programming task |
| pair:required | Must be paired |
| pair:optional | Pairing recommended |
| pair:knowledge | Knowledge transfer focus |
| pair:onboarding | Onboarding pairing |
| pair:complex | Complex problem solving |
Pairing task template
## Task: [Task Name] (Pair Programming)
### Pairing Assignment
- Driver: @developer-a
- Navigator: @developer-b
- Duration: 2-hour sessions
### Why Pairing
- [x] Complex problem
- [ ] Onboarding
- [x] Knowledge transfer
- [ ] High-risk code
### Session Log
#### Session 1 - 2025-01-27
- Duration: 2 hours
- Focus: Architecture design
- Outcome: Agreed on approach
#### Session 2 - 2025-01-28
- Duration: 2 hours
- Focus: Core implementation
- Outcome: Main feature complete
### Outcomes
- [ ] Task complete
- [ ] Knowledge shared
- [ ] Code reviewed (inherently)
- [ ] No follow-up bugs
Pairing schedule template
## Sprint [X] Pairing Schedule
### Weekly Pairing Slots
| Day | Time | Pair | Focus |
|-----|------|------|-------|
| Monday | 10-12 | A+B | Complex feature |
| Tuesday | 14-16 | C+D | Onboarding |
| Thursday | 10-12 | A+C | Knowledge transfer |
| Friday | 14-16 | B+D | Debt payoff |
### Pairing Rotation
Week 1: A-B, C-D
Week 2: A-C, B-D
Week 3: A-D, B-C
(Rotate to spread knowledge)
When to pair program
| Pair | Don't Pair |
|---|---|
| Complex algorithms | Routine tasks |
| Critical path code | Simple bug fixes |
| Onboarding new dev | Deep focus work |
| Learning new tech | Documentation writing |
| Breaking blockers | Meetings, admin |
| High-risk changes | When tired |
NoteVault pairing documentation
# Pair Programming Guide
## When to Pair
- Complex problems needing two perspectives
- Onboarding new team members
- Knowledge transfer for bus factor
- High-risk or critical code
- Learning new technologies
## How to Pair
### Driver-Navigator Model
- **Driver**: Types code, focuses on tactics
- **Navigator**: Reviews, thinks ahead, spots issues
- **Switch**: Every 15-30 minutes
### Remote Pairing Tools
- VS Code Live Share
- Tuple
- Screen sharing + voice
## Pairing Etiquette
- Agree on duration upfront
- Take breaks every hour
- Driver controls keyboard
- Navigator guides, doesn't dictate
- Switch roles regularly
## Measuring Success
| Metric | Solo | Paired |
|--------|------|--------|
| Bug rate | Baseline | 15% lower |
| Onboarding time | 4 weeks | 2 weeks |
| Knowledge spread | 1 person | 2+ people |
Pairing capacity adjustment
When two developers pair:
- Velocity: ~1.5x solo (not 2x)
- Quality: Higher (fewer bugs)
- Knowledge: Shared (bus factor improved)
Sprint planning:
- Pairing task: Assign both developers
- Estimate: Slightly less than 2 solo tasks
- Value: Include quality and knowledge benefits