# Sprint Planning Walkthrough — Learn by Doing ## Before We Begin **Diagnostic:** What is a sprint, and why plan one? In one sentence: what should a team have at the end of sprint planning that they didn't have at the start? **Checkpoint:** You can distinguish "a list of work" from "a committed plan with a shared goal"—and explain why the latter matters. --- ## Step 1: Draft a Sprint Goal **Task:** Pick a product area (e.g., "password reset," "search," "notifications"). Write a one-sentence sprint goal that describes the *outcome* the team is aiming for, not the list of features. **Question:** If someone asked "Why does this matter?" could you answer in terms of user or business value? Or are you describing output (features) instead of outcome? **Checkpoint:** The goal is outcome-focused and could guide trade-off decisions mid-sprint. --- ## Step 2: Estimate Three Stories **Task:** Take three backlog items (real or hypothetical): "Add email validation to signup form," "Refactor payment module for testability," "Design and implement dark mode toggle." Estimate each using story points (1, 2, 3, 5, 8). Write one sentence justifying your estimate for each. **Question:** What makes one story "bigger" than another? Is it effort, uncertainty, or both? How might two teammates disagree—and what would that discussion surface? **Checkpoint:** Estimates are relative (the 5 is bigger than the 2) and justified. --- ## Step 3: Calculate Capacity and Forecast **Task:** For a 5-person team, 2-week sprint, with 20% of time in meetings: calculate capacity in person-hours. If last sprint's velocity was 38 points, how many points would you forecast for this sprint? What if 2 people have 2 days of PTO each? **Question:** Why might you pull *fewer* points than your velocity even when no one is out? What buffers do you want? **Checkpoint:** Capacity math is correct; forecast is justified and conservative. --- ## Step 4: Apply Definition of Ready **Task:** Write a Definition of Ready (3–5 criteria) for your team. Then take one backlog item and score it: does it meet each criterion? If not, what's missing? **Question:** What happens to sprint planning when half the items aren't ready? Who owns getting items ready—Product Owner, team, or shared? **Checkpoint:** DoR criteria are testable; at least one gap is identified for the sample item. --- ## Step 5: Spot Anti-Patterns **Task:** Read this scenario: "The stakeholder asked the team to add 5 more stories to 'fill the sprint.' The team added them. Sprint goal: 'Complete all backlog items.'" List 2–3 anti-patterns. Rewrite the sprint goal to be outcome-focused. **Question:** Why do teams often accept pressure to over-commit? What would you say to the stakeholder to protect the team's ownership of the sprint? **Checkpoint:** Anti-patterns are named; the goal is rewritten to focus on outcome. --- ## Step 6: Plan a Remote Sprint Planning Agenda **Task:** Design a 2-hour remote sprint planning agenda. Include: async prep, Part 1 (what), Part 2 (how), timeboxes, and how decisions will be captured. **Question:** What typically goes wrong in remote planning? How does your agenda address those risks? **Checkpoint:** Agenda has clear sections, timeboxes, and an outcome (sprint goal + backlog) documented.