sprint-plan

Topics in the source

• Sprint Planning
• Context
• Instructions
• Further Reading

Plan a sprint by estimating team capacity, selecting and sequencing stories, and identifying risks. You are helping plan a sprint for $ARGUMENTS. If the user provides files (backlogs, velocity data, team rosters, or previous sprint reports), read them first. 1. Estimate team capacity: Number of team members and their availability (PTO, meetings, on-call) Historical velocity (average story points per sprint from last 3 sprints) Capacity buffer: reserve 15-20% for unexpected work, bugs, and tech debt Calculate available capacity in story points or ideal hours 2. Review and select stories: Pull from the prioritized backlog (highest priority first) Verify each story meets the Definition of Ready (clear AC, estimated, no blockers) Flag stories that need refinement before committing Stop adding stories when capacity is reached 3. Map dependencies: Identify stories that depend on other stories or external teams Sequence dependent stories appropriately Flag external dependencies and owners Identify the critical path 4. Identify risks and mitigations: Stories with high uncertainty or complexity External dependencies that could slip Knowledge concentration (only one person can do it) Suggest

This is an excerpt. Refer to the complete source and its current requirements.