Purpose

Metaphor for this meeting: Analysis.

Its goal is to understand exactly what functionalities the End User wants.

At the end of this meeting, the Team will be able to decide what it will be able to deliver during the Sprint.

Basics

Only the Development Team members decide how many Backlog Items are taken into the Sprint.

Ingredients

• Estimated and prioritised Product Backlog
• Flip charts, marker pens, scissors, glue, sticky notes, whiteboards, pencils, crayons etc.
• Vacation planner, contact details of important persons in case of enquiries

Insider Tip for the Product Owner: Sometimes these meetings get off to a slow start.

Create a sense of urgency by asking the Team to synchronise their watches or telling them where the emergency exits are.

Duration/Location

60 mins per week of Sprint.

Ideally, this meeting is held in the morning, so that the Sprint Planning Meeting #2 can take place on the same day.

Output

• Selected Product Backlog
• Requirements for each Backlog Item
• User Acceptance Test for each Backlog Item

Procedure

1. Start with the first Product Backlog Item (Story).
2. The Team questions & discusses the requirements of the Story.
3. The Team draws up the User Acceptance Test(s).
4. Write down the Constraints.
5. Define the Acceptance Criteria.
6. Determine the Level of Done for the Story.
7. Draw sketches of the Story's functionalities.
8. For the next Backlog Item, start again at Step

Prozess-Check

After a few Stories, the ScrumMaster addresses the Team: "Do we wish to deliver the Stories that we have just discussed within this upcoming Sprint?"

Take a 5 minute Break.

Continue with the process for the next Backlog Item.

Ending the Process

1. Stop approx. 20 mins before the end of Sprint Planning Meeting #1.
2. The ScrumMaster asks again – only this time more seriously: "Do we wish to commit ourselves to delivering the first Backlog Item, ... the second, ... ?"
3. Once the Team no longer explicitly agrees upon delivering a Story, stop. The previous Story is the last one that the Team has committed itself to for this Sprint.
4. Now – an important step: Send out the Product Owner. The Team must be able to make an uninfluenced decision. Everyone (Customer, End User etc.), except the Team and the ScrumMaster, leaves the room.
5. Once the Team is on its own, ask again: "Is this the list you believe you can commit to delivering?"
6. Hopefully, a short, open discussion will ensue on the contents of the upcoming Sprint.
7. The result is communicated to the Product Owner and End User.This is not up for discussion!

Don't

1. ... estimate Stories or Tasks.
2. ... ask the question by addressing the Team's ability: "Can you deliver these Stories?"