 |
| Sprint Planning Checklist Template for Excel |
Download Free Sprint Planning Checklist Template for Excel.
Purpose of Sprint Planning Checklist?
The scrum team establishes and commits to an immediate goal and identifies requirements that support that goal by a set of user stories and supporting tasks that satisfy the team's definition of done for each requirement.
| 1 | Review the Product Backlog with Product Owner and Architecture prior to Sprint Planning (Make sure there is stakeholder alignment, right-size and estimate backlog items) |
| 2 | Stories ready for the sprint are “right-sized” and well understood (Stories taken into a sprint should be small and acceptance criteria known) |
| 3 | Team is invited to the meeting – stakeholders are notified of the sprint planning cycle (Entered into the teams’ sprint calendar) |
| 4 | Entire team participates in the meeting including development, test, product owner, etc. (Stakeholders can be present, but the product owner is a single voice for product decisions) |
| 5 | Meeting is facilitated (not directed) by the Scrum Master (Stories presented by Product Owner and discussed by team) |
| 6 | Expect the Sprint Planning Meeting to be 2-4 hours in length for a two week sprint (This meeting may take longer for teams not familiar with the code or business domain) |
| 7 | Determine number of team hours available for the sprint (Identify any team member absences, % allocation, and other items that reduce from optimal) |
| 8 | Team identifies tasks and estimates hours collaboratively (Each team member can create tasks on post-it notes, they can be entered in a tool later) |
| 9 | Tasks are right-sized from 1 to 18 hours to assure tracking in the sprint (Keep task sizes small to where tracking of progress is obvious) |
| 10 | Tasks are not assigned during the meeting (Allow tasks to be pulled by anyone from the task board during the sprint) |
| 11 | Team determines commitment to the sprint after each story is estimated (Use hours estimated and available, as well as their confidence in the task estimates, and allow the team to determine sprint commitment) |
| 12 | Create the task board with each story and all of its tasks grouped on each row (A task board provides visibility, ownership and tracking of progress during the sprint) |
Related Topics:
Post a Comment