It happens that engineers call into question the importance of daily scrum meeting, especially those ones who have a lack of experience of working in a team. Their most common argument against this meeting is that it distracts them from the actual work, and it is just a waste of time.
If you as a project manager faces this issue, you should find the right words and arguments to explain your team mates the usefulness of a daily scrum meeting and to persuade them not only to attend it but also to be an active participant at it.
In this article I try to put together some arguments to support the idea of a daily team meeting, regardless of whether you use Scrum or any other process framework. From my point of view, the main purpose of the daily meeting is to encourage team collaboration, however, there are also a number of other benefits. Let’s get a look at this inforgrafic to define them:
If you have used all kinds of these arguments and it still doesn’t work for your team mate, it’s time to ask yourself a couple of questions. Can a troubled employee bring a value to the project working in an isolated environment? Is he/she really so autonomous that can coordinate and synchronize the work with other team members on his/her own? Does the rest of the team accept such kind of collaboration? If the answer at least to one of those questions is “No”, maybe it’s time to put the reasonability of having this person in the team under the concern.
Please, share in comments if whenever someone in your team questioned a daily team meeting. How did you resolve this problem?