Sprint Planning
Agile Development¶
Scrum Meetings!¶
Sprint Planning¶
- Frequency: 2 Week Development Cycle
Goal of Sprint Planning Meeting
- Set expectations.
- Review the backlog, and cover upcoming tasks for the 2-week sprint.
- Teams should highlight any potential roadblocks that could delay progress.
Minimum set of Sprint Planning Questions
- What did we learn at sprint review and sprint retrospective that needs to be considered in our planning conversations today?
- What is at the top of the product backlog?
- What do we need to know about these backlog items in order to fully commit to getting them done in the upcoming sprint?
- How much of the product backlog do we think we can complete in the upcoming sprint?
- Do we need more clarification on this feature?
- What is our confidence level regarding this (sprint backlog) as a reasonable plan for this sprint?
- How is this yet-to-build backlog item similar/relative to other known/completed work we have done in the past? How does this comparison help us estimate the relative size of the new work?
- What outside help will we need to succeed with our plans?
- What’s the biggest risk that may prevent us from completing this sprint?
- Who is taking time off during the next sprint? How should we plan differently given the team’s (adjusted) capacity?
Daily Stand-Up¶
- Frequency: Daily Development Work
Goal of Daily Stand-Up Meeting
- Each team member shares what they are working on and how it contributes to sprint goals
- Set the expectations for what will be worked on and if there is overlap
- Allows team members to request and get help on blockers
Minimum set of Daily Stand-Up Questions
- Are we on track with the sprint goal?
- Are we working on the most important items?
- Do we have any new requests?
- What do we still need to learn in this sprint?
- Have we identified any new risks?
- Who would benefit from another pair of eyes on something?
- Who could use some help?
- Who has some time available to help?
Sprint Review¶
- Frequency: End of 2 Week Sprint
Goal of Sprint Review Meeting
- Discuss what the team has accomplished
- Collect actionable feedback to improve next sprints
Minimum set of Sprint Review Questions
- What questions do you have?
- How would you use this product?
- What excites you about the product increment we reviewed? Why is that?
- How do you feel about the product increment we reviewed? Why is that?
- If you could change one thing about the product we’ve built, what would you change? Why is that?
- Let’s say one feature should be eliminated. Which feature gets your vote? Why did you choose this one?
- What’s your favorite feature or characteristic about this product? Why is it your favorite?
- What do you really hate about this product? Why is that?
- What other product on the market should we learn from? Why is that?
- How can we improve future sprint reviews?
Sprint Retrospective¶
- Frequency: End of 2 Week Sprint, after Sprint Review
Goal of Sprint Retrospective Meeting
- How the team accomplished sprint items (i.e. what worked, what didn’t)
- Improve future sprint planning and process using sprint review feedback
Minimum set of Sprint Retrospective Questions
- What did we do well—that if we don’t discuss we might forget?
- What didn’t go so well?
- What are we feeling about the upcoming sprint now that we have identified these issues?
- What have we learned?
- What still puzzles us?
- What are the most important things we learned today?
- Does anyone have an “appreciation” to share with another team member?
- Where are we confused or unclear on any of the items we discussed today?
- Are we in agreement on what action item(s) we will take from this sprint retrospective into the upcoming sprint planning?
Example 14 Day Sprint Diagram¶
