facebooktwittergoogle_plusredditpinterestlinkedintumblrmailby feather

Scrum of Scrum

To coordinate the different Scrum Teams “Scrum of Scrum”-Meetings can be used. It is similar to the Daily Scrum but the focus here is on team-level. The meeting takes place every day and should be limited to e.g. 15 minutes. Each team sends out one member to participate and answer the following questions:

  • What did the team finish?
  • What does the team plan to finish today?
  • Are there any impediments?

The answers should concentrate on the things that impact any other team.

The Chief Scrum Product Owner should moderate the meeting. Participate should not only the Scrum Master of the teams, one approach could also be to shift participation on a daily base within the team.

Common Sprint Reviews

Instead of multiple small Sprint Review meetings a common Sprint Review with all teams could also be used. This will show everyone what has been done within the Sprint and what the status of the project is.

Common Sprint Retrospectives

For the Sprint Retrospective there are two possibilities. The first possibility is that each team has their own Sprint Retrospective meeting followed by a Common Sprint Retrospective where all results are discussed that concern multiple teams. Another possibility is that topics are collected, selected and then worked on in smaller groups with members of all teams. This approach will take more time but the advantage is that members from multiple teams are closely working together.

Multi-Team Planning – Scrum Product Backlog

Even when working with multiple teams it is important to keep only one common Scrum Product Backlog for all teams. The Scrum Product Backlog shall be maintained by the Chief Scrum Product Owner but is filled by all Scrum Product Owners. If necessary the items in the Scrum Product Backlog can be broken down into more team-specific stories and maintained in a team-specific Scrum Product Backlog, e.g. only the relevant parts for an infrastructure team. In this case references between these Scrum Product Backlogs shall exist

Shared Metrics

A combined product backlog is an essential part of monitoring the process.  This means that all the important metric terms must have a common definition:

  • Velocity
  • Story points
  • Definition of done

Sprint Reviews

The sprint review for the product can initially occur at the team level.  However it is essential that there is an overall sprint review to demonstrate the product and review overall progress.

Sprint Retrospectives

Each team must hold its own sprint retrospective to  ensure that people are confident in sharing problems.  The lessons can then be shared with the other teams through another mechanism.