Purpose
All Teams work together on finding solutions for the Stories they had committed to in Sprint Planning Meeting #1. They support each other.
Basics
- All Teams work on their Stories.
- Dependencies are communicated during the Scrum of Scrums (SoS) and noted down.
- Impediments are identified and noted down.
Ingredients
- ScrumMaster, Team and Development Team
- Results from the Sprint Planning Meeting #1: Selected Product Backlog of the teams
- Further information
Insider Tip: For this meeting, it might be helpful to have system architects or information providers from other departments on call. They are only allowed to help out by giving advise.
Output
- A common understanding of the Teams' solutions for the Backlog Items
- ScrumBoard with Tasks, design, architecture information
- Worked upon and solved dependencies and impediments
Don't
- ... send a ScrumMaster to the Scrum of Scrums.
- ... interrupt the meeting for reasons such as lack of access to the code base, architecture diagrams or the like.
Duration/Location
Duration depends on the length of the Sprints, but you should start off with 3 hours.
Procedure
Time 13:00 Duration 5 min
All team members come together and kick off this afternoon's activities.
Time 13:05 Duration 60 min
Team members work on the Stories and find solutions for their implementation.
Time 14:05 Duration 15 min
Scrum of Scrum (SoS) Solve or work on solving the impediments and dependencies that were indentified in the Scaled Sprint Planning Meeting #1. During SoS, Team members report on the Stories that they have found a solution for and on how they will solve the dependencies to other Teams.
Time 14:20 Duration 60 min
The Teams continue working on their Stories.
Time 15:20 Duration 15 min
SoS, see above.
Time 15:35 Duration 60 min
The Teams continue working on their Stories.
Time 16:35 Duration 15 min
All team members come together and exchange information with the other Teams about the stories that have been commited to. All participants end the day together!
Insider Tip: The Company ScrumBoard should be a physical board, with a lot of space. (Brown) Paper is a simple but good idea. A digital tool doesn't generate enough transparency.
Company ScrumBoard
