5 common mistakes that should be avoided in the daily scrum meetings

#1 Scrum is not a status meeting.

It's a common mistake by those teams which are very new to Scrum. If we are taking the status individually of the last sprint of the day. so the majority of the time would be wasted in asking the team members about their progress. While the scrum meeting should be boxed under 15 minutes. The daily scrum meeting should not be used as a status meeting, although after a scrum meeting all progress should come automatically in the summary of the meeting.

#2 Scrum meeting is not for micromanagement.

Sometimes scrum master comes up with the issues related to the task which was assigned yesterday and ask individually about the changes or issues related to the task. Scrum team members should be self-managing. all team members should realize their responsibility and the scrum master and product owner should not try to micro-manage the team activity. 

#3 Scrum is not a planning meeting.

Although we can plan about the sprint cycle in the scrum many times it happens when scrum master starts sharing the requirement of the new project and start asking to pick any new requirements to the team. because this team does not get the chance to share their updates and scrum meeting turns into a planning meeting. 

#4 Scrum is not used for technical discussion.

I noticed that one of the team members began his update then he discussed a stuck point, there was a critical issue on a module and he just started a new technical discussion about that issue. same as other members also started discussing technical terms and ticket ID, etc. the scrum meeting should not for any individual technical discussion, these issues should be discussed later on.

#5 A scrum should not be held away from the workstation.

It's a quick meeting so everyone should be available near to the scrum board or in the same building so that everyone can join and start their work immediately after the meeting