When I started to study the SCRUM methodology and saw that I had such a daily meeting a few questions of the following kind popped up in my head:
"Is not this meeting a waste of time?"
"What the hell's the matter for you to discuss every day?"
So I went to research a bit more about what the SCRUM daily meeting is really about in various blogs and how important it is. Even the following blogs helped me write this post:
link
link
link
I introduced to my teammates, and we resolved to implement the diary during a phase of the project that we are tight deadline and this technique really helped us stay focused and able to deliver the software on time.
A daily meeting should last around 15 minutes, so it's not about those long meetings and they crawl for hours. The main idea of this meeting is not to solve problems, but to identify if the team is on the right track, or if any team member is in trouble, the team can signal to all those present and 'ask for help'.
The typical questions to be answered in a daily rate are as follows:
"What did you do yesterday?"
"What are you going to do today?"
"Is there any impediment to performing your task?"
It is recommended that participants be as brief as possible in their responses. If someone faces an impediment should signal in the daily so that it can be resolved outside of it. Typical assertions to signal that you need help are:
"I'm having trouble debugging the problem with the xpto program."
"I'm having trouble learning a particular technology and would like to partner with someone."
"The VP department asked me to work on something else for a day or two."
While requiring a staff with a certain seniority in software development, when done right, the daily meeting can help any team stay focused and members cooperate with each other to deliver quality software and in due time.