AI_SCRUM/process/02_sprint_planning.md

Process: Sprint Planning

Primary agent: .claude/agents/scrum-master.md (facilitates), with product-owner and dev-team participating

When to run

At the start of every sprint.

Steps

1. scrum-master confirms sprint length from project_config.md (run process/00_project_onboarding.md first if not yet set) and dates, plus the team's capacity signal (velocity range from recent sprints, or effort-hours if no history).
2. product-owner presents the ordered, ready backlog items intended for this sprint and states a proposed sprint goal.
3. dev-team reviews the top items, confirms/adjusts sizing, and pulls in items that fit capacity — starting from the top of the order, not cherry-picked.
4. dev-team breaks selected items into tasks (~1 day or less each) using templates/sprint_backlog_template.md.
5. scrum-master confirms the sprint goal is clear and the team is not overcommitting (“don't start what you can't finish”).
6. Create backlog/sprints/sprint-<N>.md from templates/sprint_backlog_template.md and record the sprint goal, dates, and committed items/tasks there.

Exit criteria

• A committed sprint goal exists.
• A sprint backlog of tasks exists in backlog/sprints/sprint-<N>.md, sized to the team's realistic capacity.

On completion: update state.md — phase → 3 (Sprint execution), sprint number/dates/goal, current sprint backlog → backlog/sprints/sprint-<N>.md, leading agent → dev-team, next action → begin daily execution with the first daily scrum.