The team is given the authority to determine what they are capable of completing in the duration of the sprint. Each story is evaluated by its complexity, size, and dependencies. The sprint is fed one story at a time until the points approximately add up to the velocity.
For this planning to be successful, the team should have everything that is needed to properly estimate the functionality, including design, needed architectural runway, and business definition.
There are 5 steps to a successful Sprint Planning:
- Establish velocity: Each team member should call out any time off they are planning for. This is factored into the team velocity.
- Iteration goals: Typically, the product owner will discuss the goals of the sprint with the team.
- Estimate stories: The scrum master will open up planning poker and start pulling stories from the backlog. The team is given an opportunity to ask questions and raise flags in regard to the complexities and acceptance criteria for the story. Once the team feels they understand the story completely, a group vote is made to point the story. If anyone’s vote contrasts the rest of the teams, they are given an opportunity to articulate why they feel that way. The team is given an opportunity to recast their votes or adjust in consideration of team member(s) articulation.
- Tasks: Each story will require work from one or more team members. This work can be broken down into sub-tasks to help each team member know where and when they’re expertise should apply to the story.
- Commit: Once the team’s capacity has been reached with backlog stories, there is a final sign-off from the team. The product owner and team should have one last chance to consider the work that will be done for the current sprint. Once everyone gives a ‘thumbs up,’ the work is set in stone for the remaining two weeks.