Your ScrumMaster has become the Master of Ceremonies and is speaking WAY too much: When the ScrumMaster puts on a glitter jacket and or has a bedazzled microphone, this is your sign that they have taken things WAY too far. It is important that the SM work closely with the Development Team to drive value, but they also must be in control without saying many words.
Monologues Over Dialogues: Are team members simply reporting their updates, or are they engaging in a discussion? The Daily Scrum should encourage interaction, not just broadcasting.
Problem-Solving Takes a Backseat: The Daily Scrum is a platform to highlight and assign ownership to problems, not necessarily to solve ALL of them completely. If it can be solved in 30 seconds or less, do not call for another meeting... Solve the freaking problem! If issues are merely reported but not addressed, the meeting isn’t serving its purpose.
Attendance and Engagement Dwindles: If team members are regularly missing the meeting or not actively participating, it’s an indication that they don’t see value in it, signaling that changes are needed.
Misconception of the Meeting’s Purpose: If the Daily Scrum has turned into a status report to the Product Owner or the Scrum Master, it’s a clear sign that the meeting has strayed from its purpose. The Daily Scrum is for the Development Team to synchronize their efforts and plan their work, not to report progress to the Product Owner or the Scrum Master.
The Agile Daily Standup - AgileDad