Delivery : Sprint Planning

sprint timeline

 

At the start of sprint planning the development team sits down and the product owner goes through the next approved items in the product backlog and the team agree to add them to the sprint until they believe that is all they can commit to delivering in that sprint.  At this point those backlog items are assigned to the iteration for the sprint and are updated to the status of committed.

The developers in the team then add the technical tasks to the committed product backlog item while monitoring the team’s capacity for that sprint.  At the end of this process they may need to talk to the product owner and either remove or add product backlog items if their total task estimate has varied from their product backlog estimates.

Bugs from work done in previous sprints that also needs to be resolved also need to be added to the sprint. This will reduce the capacity of the team to deliver features and will hence affect their velocity.

When bugs are added to the sprint the default 0.5 day estimate they are given needs to be validated by the team.

Sprint Planning

Sprint Backlog: Backlog Items and Tasks (estimated in hours)  [note real time team capacity levels on the right]