Understand how to plan a sprint from the product backlog
Now it is time for the team to build a commitment to a product increment based on a sprint goal or set of user stories from the prioritized product backlog.
The team is responsible for the sprint plan. The team with the product owner identify which stories to put into the sprint backlog. The team chooses the sequence of the stories and how many they take into the sprint backlog. This allows the team to moderate their commitment based on a number of factors including but not limited to team availability, difficulty and/or size of the work and/or their available skills.
The sprint backlog contains the following
- User stories from the product backlog
- Task break-downs of each user story
- Estimates in ideal hours of how long it will take the team to complete each task
- A place to sign up for a task as team members become available to work on a task
 |
What is a sprint goal? The sprint goal is a way to summarize what the team is planning to accomplish. For example, the product owner may suggest a sprint goal of, “hardening user security.” This sprint goal allows the team to help the product owner prioritize the product backlog and sequence the user stories to best achieve that sprint goal. |
