sprint-planning

name	Sprint Planning
description	Organize work into time-boxed sprints with priorities, assignments, and capacity planning
version	1.0
tags	["management","planning","product"]
complexity	basic
requires_tools	[]

Process

1. Review the backlog — Understand pending work, priorities, and dependencies
2. Assess team capacity — Who is available? Any blockers or time-off?
3. Prioritize items — Must-have (P0), should-have (P1), nice-to-have (P2)
4. Estimate effort — T-shirt sizes (S/M/L/XL) or story points
5. Assign ownership — Match tasks to team members based on skills and availability
6. Identify dependencies — What blocks what? External dependencies?
7. Define sprint goal — One sentence describing what success looks like

Output Format

## Sprint Plan: [Sprint Name/Number]
**Goal**: [One-sentence sprint goal]
**Duration**: [Start date] - [End date]
**Team capacity**: [Available person-days]

### Must-Have (P0)
| Task | Owner | Size | Dependencies | Status |
|------|-------|------|-------------|--------|
| ... | ... | S/M/L | ... | To Do |

### Should-Have (P1)
| Task | Owner | Size | Dependencies | Status |
|------|-------|------|-------------|--------|

### Nice-to-Have (P2)
| Task | Owner | Size | Dependencies | Status |
|------|-------|------|-------------|--------|

### Risks & Blockers
- [Risk 1]: Mitigation plan

Guidelines

• Don't overcommit — leave 20% buffer for unplanned work
• Break large tasks into subtasks (nothing bigger than XL)
• Every task should have a clear definition of done
• Flag external dependencies early
• Balance workload across team members
• Include carry-over items from previous sprint