Scrum Master doing daily huddle with multiple teams together

This sounds a little self serving to me. Do the teams feel they're able to inspect their work and plan for the next 24 hours being intermingled with other (non dependent) teams? 

If no, what evidence can be provided to the Scrum Master to show the impact of their actions on the teams ability to have a successful Daily Scrum? 

I have observed that some of the Scrum Masters facilitates daily huddle with multiple teams together to save their time.

@upasana chaudhary, How exactly does it save time? I am assuming each Development Team of the different Scrum Teams discuss their progress independently and that they don't all talk at once.

Is the Scrum Master able to attend each team's Daily Scrum separately?

If not, given the choice of having multiple teams together, or having it without the Scrum Master present, what does each Development Team consider more effective?

Yeah, if it works for the teams to see each other's work...then I see a viable reason to merge the standup. If they are saying it saves them time, then they are warping one of the core elements of agile. The point is for a team to speak briefly and align goals for the a short period of time. 



It's also 10-15 minutes tops. 



If your scrum master doesn't have time for up to 30 minutes, then they are not prioritizing their time correctly. It's an essential part of the process. I'd ask you team if you would benefit from breaking this standup apart by teams.

I have observed that some of the Scrum Masters facilitates daily huddle with multiple teams together to save their time.

To save whose time? A Scrum Master, who does not need to be there, or the time of a Development Team?

A Daily Scrum is a Development Team's opportunity to take 15 minutes out of a busy day to stand aside and refocus their efforts on meeting the Sprint Goal. Is that too much to ask?

I'm with Ian on this.

The Stand-up is mandatory for the Development Team. It isn't mandatory for the Scrum Master to attend, only to ensure that it has happened.

The simplest answer is - both teams hold their own at the current time and the scrum master goes to the one they're needed at. 

It may be they need to stop trying to be the PM holding a status update meeting.

Scrum master is also a project lead in this case. So the scrum master who is the project lead wants to save his time of going to 2-3 projects daily huddle.

Scrum master is also a project lead in this case. So the scrum master who is the project lead wants to save his time of going to 2-3 projects daily huddle

@upasana chaudhary, As Ian Mitchell has mentioned above, the Daily Scrum is an event for the Development Team. There is nothing in the Scrum Guide that mandates that the Scrum Master has to be there at the Daily Scrum. So, the concern about saving time becomes questionable.

Scrum master is also a project lead in this case. 

This it the root of the problem.  The Scrum Master is not having two teams join their events.  The Project Lead is doing it.  This goes back to having a Project Manager gather all of the project team members together to have a 2.5 hour status meeting every week.  

As many have said, the Daily Scrum is for the Development Team to plan their day, not to give status updates to anyone.  The Project Lead should be able to see the progress by viewing the teams Sprint Backlog.  If the Development Team needs help from the Scrum Master, Project Lead, Human Resource Representative or the Front Office Receptionist, they will ask.  Otherwise everyone should trust the Development Team to be doing the work that is needed in order to meet the Sprint Goal that the Scrum Team has agreed upon.