What: Spring Planning is an event where the team decides what user stories from the Product Backlog need to be executed in the upcoming sprint
Who: It is attended by Product Owner, Scrum Master and Dev team.
How: The team discusses the goal of upcoming sprint and selects which user stories would achieve the goal.
When: Before the start of every Sprint
Kit Contents Required:
- Agile Estimation Deck for estimating stories
- Masking Tape as lane dividers
- Removable Color Coding Labels for columns & swim-lanes
- Restickable Glue Stick for sticking User Story cards on the wall
- Post - It ® Notes (3 X 3) for listing tasks
- Product Owner discusses the objective of the sprint and possess a prioritized list of user stories associated with the goal
- Based on velocity, the team sets sprint capacity i.e. how many points can we possibly implement in the sprint
- Product Owner discusses the stories (ordered by priority)
- Team discusses and finalizes the Acceptance Criteria for each story. Product Owner writes the Acceptance Criteria on the backside of User Story card.
- Dev Team uses the Agile Estimation Deck and uses relative estimation technique to size the stories
- Product Owner fills the Size box in the User Story card
- Team forecasts how many stories will be completed in the next sprint
- ScrumMaster ensures there is a task board available with at least 3 columns (a) To Do (b) Doing (c) Done separated by masking tape and appropriate swin-lanes for a Kanban baord.
- Using Restickable Glue Stick a team member sticks story card on the board
- Using Masking tape a team member creates a row for each story card (optional)
- Using Post-It Notes ® Dev team creates tasks for each story and sticks them on the To Do column of task board (Sprint Backlog).
- The Post-It Notes(R) can have the hours listed on it if needed. Team can also use the removable round stickers to indicate each team member or priority of the task.