Monday, August 12, 2013

The Sprint Planning Meeting

Today I will present you some information about the planning meeting in Scrum

So to start, you need the product backlog, and by the way, in the Exam you will find some questions about who fills it up and who is in charge for the product backlog.
Back to the sprint planning meeting.
In discussions, the team together with the product owner, decides what goes from the product backlog to the sprint backlog. Once this is done, the team discusses who will do what and makes their planning plan for the sprint. So for each story the team identifies the tasks and makes estimates how long it will take. And so you see at this activities, the team is doing planning. So this old argument, in Agile there is no, or less planning, than in waterfall projects, is not correct, there is even more planning.

So what is done during this meeting:

  • the team reviews the backlog to identify tasks for the next sprint
  • the team discusses them and makes estimates for the tasks (estimates for the story are existing at this moment but they are on a higher level)
  • they define the goal for the upcoming sprint
  • they make the commitment, yes, this is what we will deliver

So for the exam you should know:

  • the complete team takes part with the product owner and the scrum master
  • the product owner presents the features / user stories with the highest priority
  • the team decides what will go into the sprint
  • the team asks questions about the user stories so that they can estimate the tasks
  • the team creates a sprint backlog
  • the team and the product owner define together the definition of done for the sprint
Once this is done, we come to the second part of this meeting.
In the second meeting the team and only the team brings the user story down into the tasks and talks about the how these tasks should be done. The goal is, that each task should not take longer than one day for development.
The team discusses, but they do not start with the development. At the end of this discussions the team has the tasks, the estimates for these tasks and who will handle them.

Some time frames:
the complete meeting should not take more than 8 hours, so each part should last not more than 4 hours.

Good Luck!

Thomas Schneider
PMI SFBAC chapter

Upcoming PMI San Francisco Bay Area Chapter events/training's can be found on our calendar at

No comments:

Post a Comment