Purpose
Metaphor for this meeting: Design.
The Team decides on HOW the committed Backlog Items will be implemented in this Sprint.
At the end of this meeting, the Team knows HOW to develop the planned functionalities. ( see Sprint Planning Meeting #1).
Basics
Only the Development Team defines the solution. If necessary, architects and other persons not included in the Team are invited for consultation. However, they are not allowed to make decisions for the Team. They remain guests at this meeting.
Ingredients
- People who consult the Team i.e. experts or specialists from other Teams Teams
- Selected Product Backlog
- Flip charts, marker pens, scissors, glue, sticky notes, whiteboards, pencils, crayons...
Don't
- ... estimate Tasks.
- ... assign Tasks.
Output
- Design of the application
- Architecture diagrams, charts, drawings, descriptions
- Some written-down Tasks
- Drawing upon the code basis, the Team has a clear understanding of how it will implement each Backlog Item.
Procedure
- Start with the first Backlog Item.
- Recapitulate the Team's understanding of what is actually wanted by looking at the flip charts from Sprint Planning Meeting #1.
Run a result-oriented discussion on how the Backlog Item could be implemented. These questions may help you:
Which interfaces do we need to write?
- Which databases will be needed?
- Which architecture is necessary?
- Which components do we need to update or create?
Once the Team has a clear understanding of the way it wishes to build a feature, it can move to the next Backlog Item.
In the last 10 minutes of the meeting, the Team members use sticky notes to write initial Tasks. This helps the Team members to know where to start their work on the next day. Do not estimate these Tasks.
Duration/Location
60 mins per week of Sprint. If possible, run this meeting right after the Sprint Planning Meeting #1.