technical-planning

# Technical Planning Skill

Patterns for sprint planning and technical roadmaps.

## Sprint Planning

### Story Point Estimation

```markdown
## Fibonacci Scale (Recommended)

| Points | Description | Examples |
|--------|-------------|----------|
| 1 | Trivial | Config change, copy update |
| 2 | Simple | Bug fix, small feature |
| 3 | Medium | Standard feature, API endpoint |
| 5 | Complex | Multi-component feature |
| 8 | Large | Cross-service feature |
| 13 | Very Large | Should be broken down |

## T-Shirt Sizing (Alternative)

| Size | Points | Description |
|------|--------|-------------|
| XS | 1 | < 2 hours |
| S | 2-3 | < 1 day |
| M | 5 | 1-2 days |
| L | 8 | 3-5 days |
| XL | 13+ | > 1 week, break down |
```

### Sprint Capacity

```markdown
## Team Capacity Calculation

Team Size: 5 developers
Sprint Length: 2 weeks (10 working days)
Ceremonies: 1 day equivalent
PTO/Holidays: 2 days
Buffer (bugs, support): 20%

Available Days: (5 × 10) - (1 × 5) - 2 = 43 days
Effective Capacity: 43 × 0.8 = 34.4 days

At 6 points/dev/day:
Sprint Capacity: ~35-40 points
```

### Sprint Backlog

```markdown
## Sprint 12 - User Management

### Sprint Goal
Enable users to manage their profiles and preferences.

### Committed Stories

| ID | Title | Points | Owner |
|----|-------|--------|-------|
| US-101 | Profile page UI | 5 | @alice |
| US-102 | Update profile API | 3 | @bob |
| US-103 | Profile image upload | 5 | @alice |
| US-104 | Email preferences | 3 | @carol |
| US-105 | Password change | 3 | @bob |
| BUG-45 | Login redirect issue | 2 | @dave |

**Total Points:** 21
**Team Capacity:** 35

### Stretch Goals
| ID | Title | Points |
|----|-------|--------|
| US-106 | Two-factor setup | 5 |
| US-107 | Session management | 3 |
```

## Technical Roadmap

### Quarterly Planning

```markdown
# Q1 2024 Technical Roadmap

## Theme: Foundation & Scale

### January
- [ ] Database migration to PostgreSQL 15
- [ ] Implement connection pooling
- [ ] Set up monitoring (Datadog)

##