How to explain to the team why to conduct a daily scrum?

Question

Agile

I'm starting to implement scrum in the development team. In fact, scrum is perfect for us in all respects. However, many developers do not understand some things, for example, "Why do we need to waste 15 minutes every day on empty chatter. Anyone who wants to know who is doing what will ask at any time."
In this case, how can the team be motivated to start holding such rallies?
Thank you!

Answer 1

The Daily Scrum Meeting is very important! The main task that he solves is the forced synchronization of developers in the team. It is foolish to hope that a developer will take the initiative every day and go around asking his colleagues for help or who can help him. Therefore, a mandatory procedure is introduced.
In general, Scrum is about the rhythm of the team's work. At the top level, the rhythm is set by iterations, at the level below it is set by the DSM.
To get the maximum benefit from DSM, you need to hold it every day at the same time, it is forbidden to shift, you can not come, but only for good reasons. The main thing is not to go beyond 3 questions, all discussions are taken out of the rally, then the meetings will be short.
And yet, it is better to conduct DSM standing in the stand-up meeting format, this will also limit its duration and increase efficiency.

Answer 2

I will not answer your question specifically, but it seems that holding daily rallies is not very effective. It is better to use weekly scrum, of course, in conjunction with issue tracking (Redmine, Jira, etc.) and a smart manager that will help distribute tasks for a weekly sprint. And all the small questions, if an employee has an issue as the task is solved, you can really ask, for example, in a chat or go directly to the right person.

Answer 3

In my opinion, the need for such rallies disappears in a team that has been working together effectively for a long time. In addition, with the right tools, such rallies only take time. After all, this synchronization, in fact, is forcing the dependency graph. If the tool highlights these dependencies ("I'm waiting", "I'm waiting", "dependency X"), then people become informed through the tool. I observe the effect that adult, mature developers, if necessary, organize a "rally" for synchronization. Also, if you remove the role of "nanny" from the adult team, productivity invariably increases. For high-level synchronization, "steering meetings" are useful, but this is clearly not every day and sometimes more than once a week, but less often.

Answer 4

Remove the "blank talk" as you put it and bring in more constructiveness and decision making.