# Sprint Planner - Best Practices

## Story Selection

1. Prioritize HIGH stories first (team commitments)
2. Include mix of story sizes (not all large or small)
3. Check dependencies (avoid circular/blocking dependencies)
4. Ensure stories are independent (can be implemented in any order)
5. Balance across epics (if multi-epic sprint)

## Capacity Planning

1. Optimal range: 20-40 story points for 2-week sprint
2. Warn if over (> 40): Risk of incomplete sprint
3. Warn if under (< 20): Consider adding more stories or reducing duration
4. Never force overallocation (team morale and quality)
5. Adjust for team events (holidays, conferences, training)

## Workflow State Management

1. Stories must be in "Backlog" status before sprint planning
2. Sprint planning transitions stories to "Ready for Dev"
3. Development skill will move stories through remaining states
4. Never bypass workflow states
5. Maintain complete workflow history
