Daily Scrum Meeting
Teamplay is what it is. I bet you are sick and tired of this comparison, but to tell the truth, it gives us the most correct understanding of Scrum. In lots of team games the players form a tight ring and quickly discuss the most important moments of the game. It usually happens either during a timeout or before the beginning of the match. But it shouldn’t be confused with a planned discussion several days before the game. This will be similar to Planning meeting.
Such a discussion goes on really quick, because the players don’t have much time. Because of the time limit, they discuss only the most important points, paying extreme attention, then they produce their battle-cry and enter the field, rejuvenated and full of energy.
The coach could say something like this: "their forward runs the same trajectory almost any time, your position is too far to intercept him, so move here and stay there till the next timeout" or "I’ve noticed that you have difficulties in covering this distance during attacks, what’s the problem?". Daily Scrum Meeting is almost the same, though maybe with less tension. The goal of such a meeting is to understand and adjust the teamwork, learn about current problems and suggest the possible solutions. In order to have a structured system, we use three simple question during Daily Scrum Meetings.
Three main Daily Scrum Meeting questions
- What have you done yesterday?
- What are you going to do today?
- What problems do you have?
These questions are asked by a Scrum Master. He should write down all the answers. As for the problems, they could be absolutely different. For example, let’s see what they could be within a Development Team (though Scrum can be applied to any sphere).
- I need help with debugging;
- The tech-support of the office software doesn’t call us back for the second day;
- We haven’t received the software we ordered yet;
- My chair is broken and I have to work in standing position!
Of course, the Scrum Master can solve some of these problems himself, but he has to find some solution for the others. But anyway, he is completely responsible for all the problems and solutuions.
Who participates in Daily Meeting?
Of course, anyone can. A postman, for example, or the owner of a nightclub. But none of them are necessary during meetings. And not because their positions, but because they cannot affect the work of the Team in any way. They will be of help only if a problem is connected to them directly.
The same applies to a Daily Meeting. The whole Development Team, the Scrum Master and the Product Owner must participate during the 15-minutes meeting. As for anybody else, be it a client, a marketer, a designer or anybody else – they are allowed to be present, but they don’t have a right to express their opinion.
Ways to hold a Daily Scrum Meeting
There are plenty of ways to hold such a meeting. Each Team chooses the one that suits them best.
- Sometimes a Scrum Master speaks loudly in order to be heard by everyone and asks one person at a time. Such an approach makes all the problems known to everybody and each team member can react to any of it. But there is always a psychological aspect, which can be treated as a con: someone can keep silence if he thinks his problem is caused by other member of the team.
- Another approach: the Scrum Master discusses each problem individually but it takes place in one room. It is important to tell about any problem.
- The third variant: using any other means of communication besides voice. It could be sheets of paper, which the team members use to write their answers or any sort of technical means, such as our service, for example.
Possible problems during Daily Scrum Meeting
The most common problem is discussing unrelated themes during the meeting. I don’t mean discussing the yesterday’s hockey or soccer match, but, let’s say, the budget of the project. Any other distractions, such as checking your email are also unacceptable during meetings.