Daily Scrum: Neither status meeting nor ad hoc discussion
„The Daily Scrum is a 15-minute event for the Developers of the Scrum Team. To reduce complexity, it is held at the same time and place every working day of the Sprint.“
The Daily Scrum Meeting is a meeting where the Developers get together to talk about what they have achieved since the last meeting, what they have planned for today, and if there were any obstacles or problems. During this meeting, only the Developers get to speak. If there were impediments, then at the end of the meeting, the Scrum Master has created a list with the items that he needs to deal with. In addition, the work of the Developers is synchronised - everyone is on the same level as their colleague and ideally the whole team is a little closer to the Sprint Goal than before.
Often the term stand-up meeting is used synonymously with Daily Scrum. But there are some differences. In the stand-up meeting, which originally comes from Extreme Programming, not only the Developers exchange experiences, but also clients or the Agile Coach can be actively involved. In contrast to the Daily Scrum, the stand-up meeting is not an official Scrum Event, it is not described in the Scrum Guide and it is not time-boxed. Nevertheless, this meeting should also be kept short and not take up too much time - the fact that the participants should stand during this meeting helps to keep it short.
Well-intentioned, but poorly executed
How can you get to the Daily Scrum the way it should be?
- Not only the Developers participate, but also other stakeholders. This means that there are no longer eight or fewer participants, but more people.
- Due to the increasing number of participants, the meeting does not last 15 minutes anymore, but longer - the timebox will be exceeded.
If the Daily Scrum is not held as it should be, then the Scrum Master is called upon. He is responsible for ensuring that the Scrum framework is implemented, adhered to and lived, and usually not only at the project level, but throughout the entire organisation. Likewise, the Developers should approach him if they are of the opinion that something needs to be changed in the project.
Ad-hoc meetings instead of Daily Scrum?
If you consult ad hoc only with the colleagues involved in your problem, you don't have the opportunity to hear the opinion of other colleagues - and maybe exactly these opinions would be important for your further work? In addition, the Daily Scrum Meeting offers a good start to the day: everyone is informed about what will happen today. This way, no one is excluded, and everyone can pull together to work towards the Sprint Goal.
However, it can also be a disadvantage that the Daily Scrum is only held once a day. If problems suddenly arise that need to be solved immediately, then the participants can additionally meet spontaneously and talk about them, or, depending on the issue, approach the Scrum Master, which may possibly be the better decision. But don't forget to address this problem the next day anyway to update all Developers.
And what's wrong with additional ad hoc meetings? Basically, you and your team are self-organised. You should know best yourself whether ad hoc meetings suit your team and whether everyone benefits from them. However, one major drawback is that any spontaneous meeting can break in on your colleagues' thoughts, he may lose his focus or get out of the flow. Perhaps your colleague is busy programming, reflecting, or researching, and any interruption can contribute to them taking longer to complete their current work process. It's best to agree with your colleagues what ad hoc meetings might look like: For example, if all colleagues have turned off their email program's push notifications so they can work undisturbed, you could send out an email in advance letting them know you need to talk - if your colleague responds, you can seek them out, otherwise not.