7 Steps to Transform Daily Scrum from Status Report to Decision-Making

Emily, a new Scrum Master, noticed a peculiar dynamic in her team's Daily Scrums. The meeting would start with Chris (the Project Manager) asking each Developer, 'What did you do yesterday? What will you do today? Do you have any blockers?' Developers would then report sequentially to Chris. Alice, for instance, would say, 'I finished that task yesterday, and today I'll work on X,' her eyes constantly seeking Chris's approval. The Sprint Goal was relegated to a forgotten corner of the board, and team members conversed with the manager, not with each other. This situation hindered team conflict resolution, stifled the Developers' self-planning, and went against the spirit of servant leadership.

Many Scrum Masters, facing such a situation, might quickly suggest, 'The manager shouldn't be in the Daily Scrum!' However, this often fails to address the root cause. Chris's intentions might not be malicious; perhaps he genuinely wants to stay informed or help. Or the team might be accustomed to reporting to management due to long-standing habits. Simply enforcing a rule can create resistance, make Chris feel excluded, and doesn't help the team develop its self-management capabilities. This requires a delicate balance in stakeholder management.

Transforming such a situation demands Agile coaching skills and Scrum Master skills beyond those of a typical facilitator. It requires the ability to have difficult conversations at work, foster team self-organization, and educate stakeholders. A Scrum Master's role isn't just to enforce rules but to embody and promote Scrum values and principles. This is a core aspect of servant leadership examples. You must take an active role in empowering the team to make its own decisions, remove impediments, and focus on the Sprint Goal. This sometimes necessitates initiating uncomfortable but essential dialogues.

The first step is to understand not just the surface symptoms but the underlying causes. Who is talking to whom in the Daily Scrum? Are team members interacting with each other? What's the energy level like? What might be Chris's intentions behind his questions? Why does the team maintain this dynamic? These observations will help you understand the reasons behind potential Sprint Planning problems or the team's impediments to self-organization. Perhaps the team is accustomed to reporting to management from past experiences.

The Daily Scrum is for Developers to synchronize their plan for the next 24 hours to achieve the Sprint Goal. If Chris's presence overshadows this purpose, talk to the Developers one-on-one or during a Sprint Retrospective. Use coaching questions for Scrum Masters like, 'What's the real purpose of the Daily Scrum?' or 'When is this meeting most useful for you?' Remind them that they own the meeting. Ask, 'This is your meeting, how can you help each other?' Encourage them to speak to each other, not to Chris.

Arrange a private meeting with Chris outside the Daily Scrum. Start by acknowledging his good intentions. 'Chris, thank you for attending the Daily Scrum. I know you want to stay updated on the team's progress. However, I'd like to remind you that the primary purpose of the Daily Scrum is for Developers to plan among themselves. Your questions sometimes seem to hinder the team's internal communication and self-organization.' Explain the situation. Offer him alternative ways to track the team's progress (e.g., attending the Sprint Review, reviewing the Product Backlog, or speaking with you at a specific time). This falls under Scrum Master interview scenario questions about handling difficult stakeholders and is critical for effective stakeholder management in Agile.

During the Daily Scrum, exhibit active facilitation skills for Scrum Masters. When you notice conversations drifting or a tendency to report to the manager again, gently intervene. Use guiding questions like, 'Developers, how will you help each other achieve the Sprint Goal today?' or 'Can this topic be discussed after the Daily Scrum?' Write the Sprint Goal in a visible place and reiterate it at the beginning of each meeting. Ensure each team member answers the 'What did I do yesterday, what will I do today, and do I have any impediments?' questions addressing each other, within the context of the Sprint Goal. This is an approach that can also be used in retrospective facilitation.