scrum phases‎ > ‎

sprint planning

Inputs for Sprint Planning:
- A groomed product backlog (sliced into appropriately sized, estimated and prioritised stories) 
- Estimates for new stories: Estimates for all newly identified stories
Burn Up Chart: Chart showing above status showing completed and remaining scope to help the product own make trade-offs
- Metrics related to the previous iteration: Velocity / Throughput: # of story points "done done" (with 0 critical defects)
- Updated product backlog / story list: Updated backlog showing new estimates and updated total number of story points for release
- Updated product backlog priorities: Based on progress to date, what is the priority of the remaining stories in the release, especially new stories: Product owner should update the backlog by swapping stories out to meet the deadline or extend the deadline

Sprint planning (single part style)
  1. Determine team capacity: how many team capacity days are available accounting for sprint meetings, other commitments, holidays and leave. Leave a buffer of capacity. 
  2. Product owner: with the team define the goal for the sprint that includes some wiggle room
  3. Team: Select the next story in the backlog that supports the goal
  4. Task breakdown: identify tasks for the story, track the team capacity used up by each task
  5. Capacity check: Do we have left-over capacity? If so go to step 3
  6. Commit: Team understands the work in the sprint and commits to completing the stories they have selected.


Subpages (1): Burn Up Chart
Comments