The Agile Pocket Guide: A Quick Start to Making Your Business Agile Using Scrum and Beyond

Chapter 10

Sprint Planning Meeting

The Product Owner and you are now ready to set out the schedule of work for the upcoming iterations. The sprint planning meeting is the perfect place to start setting the pace for work. Remember, the team has a good grasp on the vision and purpose of the project, and you are now ready to commit to stories and the work at hand. Now, the Product Owner, you, the entire team, and any other interested members of the business work together to understand how many user stories they can to commit to completing within a given sprint. These sprints hold a certain point value, as we discuss in Chapter 11. At this point the team answers the questions, “What needs to be built first, and can we commit to completing it?” (See Figure 10.1.) These user stories are generally locked in place and committed to by the team. The Product Owner can change some stories and requirements as long as the team commits to completing them or you help the Product Owner understand that some features may be added to the sprint, which may mean that other features will be removed. We then estimate the work as detailed in Chapter 11. It's “go” time. Let's get started.

Figure 10.1 Sizing Stories with Story Points into Tasks with Task Hours

Note: Many Agile coaches do not have a backlog grooming session prior to a first sprint for a new Agile Team as depicted in Chapter 9. That is absolutely ...