What is the daily meeting in the SCRUM methodology for?
To my superficial look at Agile methodologies and based on management books, a recurring or fixed meeting followed by short intervals are useless. The question is: What differentiates the daily meeting of the SCRUM from other existing meetings in a company/business?
3 answers
When I started studying the SCRUM methodology and saw that I had such a daily meeting some questions of the following kind popped up in my head: - Isn't this meeting a waste of time? - What the hell are you gonna have to discuss every day?
So I went to research a little more about what the Daily SCRUM meeting is really about in various blogs and what its due importance is. Even the following blogs helped me write this post:
Http://www.mountaingoatsoftware.com/agile/scrum/daily-scrum / http://www.mountaingoatsoftware.com/blog/weighty-matter-daily-scrum http://www.effectivemeetings.com/teams/teamwork/scrum.asp
I presented it to my teammates, and we decided to implement the daily during a phase of the project that we are on a tight deadline and this technique really helped us to stay focused and be able to deliver the software on the agreed deadline.
A daily meeting should last around 15 minutes, so it is not about those prolonged meetings and if that drag on 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 member of the team is in trouble, it can signal to everyone present and ‘ask for help’.
The typical questions to be answered on a daily basis are as follows: "What did you do yesterday?" "What will you do today?" "Is there any impediment to the execution of your task?"
It is recommended that participants be as brief as possible in their answers. If someone faces an impediment should signal in the daily so that it can be resolved outside of it. Typical assertive signals to signal that you need help are:
" I'm having trouble debugging the problem with the xpto program."
" I am having difficulty learning certain technology and would like to pair with someone."
" the VP Department asked me to work on something else for a day or two."
Although it requires a team with a certain seniority in software development, when done in the right way, the daily meeting can help any type of team to keep the focus and the members cooperate with each other for the delivery of the software with quality and in due time.
The "Daily Scrum" is an event (meeting) whose duration is necessarily limited to 15 minutes. It serves so that the development team can synchronize their activities and create the planning for the next 24 hours.
This is done by inspecting the work since The Last "Daily Scrum" and generating the forecast of the work that can be carried out until the next meeting.
The "Daily Scrum" is kept at the same place and time every day to reduce its complexity. During the meeting, each developer explains:
- What did I do yesterday that helped the development team achieve sprint's goal?
- What am I going to do today to help the development team achieve sprint's goal?
- Do I see any impediments that get in the way of me or that get in the way of the development team achieving sprint's goal?
Briefly that's it. With information from this meeting both the" Scrum Master " and the "Product Owner" may or may not take actions.
Dude, this meeting basically details what steps each team member will take, which have already been completed and what difficulties they are encountering on their way, the goal is to follow up and identify delays and difficulties in the delivery of the project, not to mention that with the culture of collaboration Scrum can help people help themselves in some specific demand by developing new skills.