# Sprint Planning Quick Reference

## The Two Parts

| Part | Focus | Who |
|------|-------|-----|
| **What** | Sprint goal, selected items | Product Owner + Team |
| **How** | Tasks, approach | Development Team |

## Sprint Goal Template

```
Sprint [X]: [One-sentence outcome]
Success: [2–3 concrete outcomes]
Out of scope: [What we're NOT doing]
```

## Estimation Cheat Sheet

| Technique | When to Use |
|-----------|-------------|
| Story points | Backlog refinement, sprint planning |
| T-shirt sizing | Quick triage, non-technical stakeholders |
| Planning poker | New or complex stories, alignment needed |

**Fibonacci:** 1, 2, 3, 5, 8, 13, 21

## Velocity vs Capacity

| Term | Formula / Meaning |
|------|-------------------|
| Capacity | Team size × Days × Hours × (1 − overhead) |
| Velocity | Avg points completed (last 2–3 sprints) |
| Forecast | Pull ~80–90% of velocity |

## Definition of Ready (Example)

- [ ] Acceptance criteria defined
- [ ] Dependencies identified
- [ ] Sized by team
- [ ] Technically feasible

## Anti-Patterns to Avoid

| Anti-Pattern | Better Practice |
|--------------|-----------------|
| Over-commit (100%+) | 80–90% of velocity |
| No sprint goal | One outcome-focused goal |
| Estimate in hours | Story points (complexity) |
| Skip "how" | Break into tasks |
| Stakeholder dictates scope | Team decides |

## Remote Planning Tips

1. **Async prep** — Send items 24–48h ahead
2. **Shared boards** — Miro, FigJam, Jira, Linear
3. **Timebox** — 15-min chunks
4. **Document live** — Capture goal + decisions in shared doc
5. **Cameras on** — For goal agreement, voting

## Capacity Example

```
5 devs × 10 days × 6 hrs × 0.85 = 255 person-hours
Velocity: 45 pts → Forecast: 38–40 pts this sprint
```

## Mermaid: Sprint Planning Flow

```mermaid
flowchart LR
  A[Product Owner: goal + items] --> B[Team: capacity]
  B --> C[Select items]
  C --> D[Break into tasks]
  D --> E[Sprint backlog]
```