Multiple teams, cross-team issues, dependencies, multiple-stakeholders, and multiple project timelines! Sounds complicated! Yes, it can be.
I’ve found that many times a scrum of scrums meeting can be a very valuable part of disseminating information across the enterprise as well as getting project leaders and product owners on the same page, especially if it’s a many-to-one relationship (multiple product owners and one development team).
For those who don’t know, a Scrum of Scrums is a scrum team made up of representatives from each of several other teams (usually the product owner). Just like a regular scrum team, the Scrum of Scrums works iteratively to deliver value in the form of removed organizational obstacles. Scrum of Scrum meetings usually are right after a regular scrum meetings in the morning. If we have a scrum meeting for development at 9:00 AM, then the scrum of scrums is at 9:15ish.
The purpose of such a scrum meeting are as follows:
- To remove escalated obstacles or resolve dependencies between teams
- Remind the team of mission/value statements for each project
- Quickly document any necessary follow ups with team members
- And… to remove dependencies between teams!
I’m a big proponent of not having meetings for the sake of meetings, nor am I big on process that bogs down productivity. Remember: Simplicity!
So, for your larger projects or our environment currently, would a Scrum of Scrums be useful or valuable?