Who is required to attend the Daily Scrum?
Introduction
Scrum is probably the most widely practiced agile framework in software development (and some other domains too, though that isn’t necessarily a good thing I think). There are five events in the Scrum framework and the most widely known and used is the Daily Scrum. This article will explain what the Daily Scrum (not Standup!) is really about, and explain that (and why) the Daily Scrum is actually just for the Developers.
Understanding the Daily Scrum
The Daily Scrum is a 15-minute event for the Scrum team to synchronize activities and create a plan for the next 24 hours. It plays an important role in fostering transparency, inspection, and adaptation, which are the core pillars of Scrum.
How does it do these things?
- Transparency: the developers get together and communicate openly.
- Inspection: the developers inspect their progress towards the Sprint Goal.
- Adaptation: the developers update the Sprint Backlog (plan for the sprint) based on their progress so far.
Key Participants of the Daily Scrum
The Role of Developers
In the Scrum context, ‘Developers’ refer to professionals responsible for creating the product increment. Not just software developers! Their active participation is crucial in the Daily Scrum, as they discuss progress and challenges related to the Sprint Goal.
Involvement of the Scrum Master and Product Owner
While the meeting is primarily for developers, the Scrum Master and Product Owner might be involved, depending on the context.
The developers might find it helpful to have a Scrum Master facilitate the event, ensuring it iss productive and positive. The Product Owner may attend under certain conditions, especially if they are actively involved in the development, or the team have questions about changing priorities during the sprint.
Just make sure that it doesn’t become the dreaded “status update” meeting, where the developers report the status of their tickets to the Scrum Master. That is not what the Daily Scrum is for! The team should already have some kind of tool or board (physical or digital) that provides a transparent view of what the team is working on.
So it is of no use for people to mindlessly report what they worked on yesterday and what they are working on today and what blockers they are facing – that should already be visible to everyone. It is for the developers to inspect their progress and discuss their plan for the day.
Distinction between Mandatory and Optional Attendees
The mandatory attendees are the Developers, as they are the ones doing the work. The Scrum Master and Product Owner’s attendance is optional but can be beneficial, depending on context. I recommend the Scrum Master attends and silently observes every now and then. Just make sure the developers are not “giving a report” to the Scrum Master.
The Role of Developers in the Daily Scrum
Developers in Scrum are not limited to software developers; they encompass all team members contributing to the Sprint Goal. They are collectively accountable for creating Done increments each sprint. The Daily Scrum is an event by and for the developers, for them to discuss and coordinate their work.
The Scrum Master’s Contribution
The Scrum Master can ensures the Daily Scrum happens, it sticks within its timebox, and remains a positive experience. They coach the team towards self-management and protect the team’s focus from outside disruptions. Over time, the Scrum Master should be needed less and less at the Daily Scrum.
The Product Owner’s Involvement
The Product Owner might want to attend the Daily Scrum to gain insights into the team’s progress and to provide clarity if needed. They are not a mandatory attendee but many teams invite them to the Daily Scrum and let the Product Owner choose if they want to go or not.
Conducting an Effective Daily Scrum
Running an effective Daily Scrum involves sticking to the timebox, focusing on the Sprint Goal, and addressing impediments. It’s about maintaining engagement and adapting the backlog as necessary.
Common Formats and Techniques
Teams may use the traditional three-question format or other approaches that suit their dynamics. I actually don’t love the “three questions”, since it can quickly become a status report, it assumes developers are all working independently, and it does not at all involve the sprint goal.
The key is to adapt the format to meet the team’s needs while focusing on the Sprint Goal and progress towards it.
Tools for Running a Daily Scrum
Teams can use various tools, both virtual and physical, to enhance communication and collaboration during the Daily Scrum. The choice of tools should align with the team’s preferences and needs.
Daily Scrum vs. Daily Standup
While often used interchangeably, the Daily Scrum and Daily Standup have subtle differences. The Daily Scrum is specific to the Scrum framework and focuses on the Sprint Goal, whereas the Daily Standup is a more general Agile practice.
In fact, the concept of a “Daily Standup” comes from Extreme Programming (also called XP), not Scrum. The terminology crept into the Scrum domain.
Common Mistakes to Avoid
Common pitfalls include turning the Daily Scrum into a status report, solving problems during the meeting, and not respecting the timebox. Teams should continuously inspect and adapt their approach to the Daily Scrum to avoid these mistakes.
Daily Scrum for Remote or Distributed Teams
For remote or distributed teams, the Daily Scrum can be adapted to accommodate different time zones and work environments. Using video meetings and visual tools can enhance the effectiveness of the Daily Scrum in a remote setting. I do really recommend teams try to keep it in the morning, since it is an event where the team discusses work for the upcoming day.
Continuously Improving Scrum Team Practices
The Daily Scrum is a tool for continuous improvement. It helps teams inspect their progress and adapt their approach, leading to better coordination and efficiency.
FAQ Section
- What is the main purpose of the Daily Scrum?
The main purpose of the Daily Scrum is to synchronize the activities of the development team and plan for the next 24 hours. This meeting helps in identifying any impediments to progress, discussing what work has been completed, and what work needs to be done next. The focus is on ensuring that the team is on track to meet the Sprint Goal and facilitating quick decision-making and problem-solving.
- Who should attend the Daily Scrum?
The Daily Scrum is primarily for the development team members, who are the individuals actively working on the Sprint Backlog. Attendance by the Scrum Master and the Product Owner is optional but beneficial. The Scrum Master typically facilitates the meeting to ensure it stays focused and within the timebox, while the Product Owner may attend to provide clarity on the product backlog items and understand the team’s progress and challenges.
- How long should the Daily Scrum last?
The Daily Scrum should last no longer than 15 minutes. This timebox is set to keep the meeting brief yet effective. The short duration encourages the team to discuss only the most critical items and maintain a high level of focus and energy.
- Can the Daily Scrum format be adapted?
Yes, the Daily Scrum format can be adapted to suit the needs of the team. While the traditional format involves answering three questions (What did I do yesterday? What will I do today? Are there any impediments?), teams are encouraged to find a format that works best for them. The key is to ensure that the meeting remains focused on progress towards the Sprint Goal and that it facilitates effective collaboration and problem-solving.
Conclusion
Understanding who attends the Daily Scrum and how to conduct it effectively is crucial for the success of Agile projects. The Daily Scrum is not just a meeting; it’s a fundamental practice that enhances team dynamics, fosters transparency, and drives progress towards the Sprint Goal.
