Daily Scrum Meetings occurrence

WOW.  Six teams per SM.  That is a challenge all by itself. 

Are all teams working on the same product, or on different products?  If the former, then you might wish to look into implement one or two Nexus's. 

All three of you SMs should be considering the following issues that will arise if the frequency of the Daily Scrum is reduced: 

• If you have remote teams, their feeling of being disconnected from the other teams will increase
• The opportunities to update the sprint plan will be reduced, thus preventing the teams from organising work to achieve their sprint goals will be slowed
• A inaccurate sprint plan reduces transparency
• Opportunities to inspect and adapt the sprint backlog will be reduced, causing re-alignment to become more difficult

When I received this request some questions came up to my mind: What is the value to do this? What exactly are we measuring and for what?

The ability of the Developers on each team to agree a plan for the next working day which takes them closer to their Sprint Goal.

Are you able to help each team focus on its Sprint Goal, given you have so many?

Since this request came from the implementation leads and they really want to have this info available, then, what would be the best way to do this

What are "implementation leads", and what would they use this information for in regards to each team?

Thank you for the comments!

Scott, yes, they are going through the same "enablement process". I mean, the user stories are the same ones for all the teams, these are intended for them to understand the scrum framework, but each one have different products. At this point we are trying to avoid reducing the daily scrum meeting frequency for the reasons you described. But there were some particular occurrences which had to cancel because the team had been double booked. These particular cases are what the executives want to start measuring. The goal is to have zero cancellations if possible.

Ian, I do my best to keep each one of the teams focused on achieving their goal every Sprint.This organization has recently implemented Scrum (mid last year). I've joined as Scrum Master last January, so I work closely with these implementation leads. Their role is to provide the company's view on what is expected from the teams and clarify questions, especially to the product owners, since they have received some training on this role on the last few months. Everything is new to them, so it is a great challenge for the Scrum Masters.

Forgive for being blunt but I saw a couple Scrum terms but nothing I read sounded like Scrum. You have passed the PSM I so I ask if this sounds remotely like you understand Scrum to be?  For example, what meetings are described in the Scrum Guide? I know of 5 events, but no meetings. Implementation Leads are not one of the 3 Scrum roles and the work you say they do doesn't sound like an environment that promotes self-organization. 



As a Scrum Master I would stop trying to find a way to make this information available and start educating people on how their interactions, and this case demands, are interfering with the teams' ability to self organize and produce valuable increments. I would also be helping the teams realize the importance and benefits of having the Daily Scrum event. You have responsibilities to the Scrum Team and the organization. With 6 teams you do not have the time to spend producing unnecessary reports. With 6 teams and an organization that is new to Scrum, but claims to want to use the framework, the 3 Scrum Masters need to concentrate on the responsibilities described for you in the Scrum Guide.