Recently, I did a small research on Scrum of Scrums and how it could be applied in the organization I am working in. I decided to share the major findings with the community in this post. I hope you will find it useful.
What is Scrum of Scrums?
... each Scrum team proceeds as normal but each team also contributes one person who attends Scrum of Scrum meetings to coordinate the work of multiple Scrum teams. These meetings are analogous to the Daily Scrum Meeting, but do not necessarily happen every day.
The decision of who to send should belong to the team. Usually the person chosen should be a technical contributor on the team—a programmer, tester, database administrator, designer, and so on—rather than a product owner or ScrumMaster. Being chosen to attend the scrum of scrums meeting is not a life sentence. The attendees should change over the course of a typical project.
If a problem is identified and the right people to address that problem are together, they should address it then and there. A problem that has risen to the attention of the scrum of scrums meeting participants is often a significant problem that could be affecting the work of up to 100 people. It deserves to be addressed and, if possible, resolved in that meeting.
- What has your team done since we last met?
- What will your team do before we meet again?
- Is anything slowing your team down or getting in their way?
- Are you about to put something in another team’s way?
No user story should have a lower confidence level than a user story with lower priority.
In the Scrum of Scrums, you only visualize stories. You create the “Scrum of Scrums storyboard” where every story that is currently open is visualized, with the team that has it and the current status indicated.
There are only two columns: “Story” and “Status”. Each story has a little magnet indicating which team is working on it.
... it helps us to get a feel of what happens to the system by the other teams; it helps identify situations where we can help each other; it helps identify situations where the teams need to coordinate; and it simply helps in keeping up the feeling that we are in the same boat and in keeping people connected by making sure that at least one member from each team sees one from every other team once a day.