The following article is a sample from the full BVOP™ Ultimate Guide and is part of the preparation for the BVOP™'s modern Agile Project Management Certification Program.
The Daily Scrum is a limited-time event during which each member of the Development Team presents to the others very briefly what they did the previous day, what they will do today, and what problems and obstacles they have encountered or anticipated.
This event is typical of the Scrum framework and is mainly used by Scrum teams.
During the event, the members of the Development Team answer the following sample questions:
- What did I do yesterday that helped the Development Team meet the Sprint Goal?
- What will I do today to help the Development Team meet the Sprint Goal?
- Do I see any impediment that prevents the Development Team or me from meeting the Sprint Goal?
Team members can ask their own questions. They invent and configure the questions themselves. To achieve team balance, every day, a different team member can be a conductor and ask the questions. It is common practice asking the questions to be performed by the Scrum Master role, but not necessarily.
Participants tell short stories. Discussion may also take place. All details, however, which require more detail and will take time, are held after the meeting.
The purpose of the Daily Scrum
The purpose of this event, in theory, is to increase transparency, efficiency, better inspection of the work and allow easier solutions to potential problems.
Participants share with others what they are working on, making their work transparent to others. Transparency makes it easy to inspect work, identify any problems, and find appropriate solutions with the help of other members of the Development Team.
After discussing all development issues and obstacles, the team reviews their Sprint progress to see how the team is doing. Burndown Chart is a traditional chart that shows work progress by visualizing the work done and the work remaining.
According to the data in the chart, plans can be modified if necessary to meet the Sprint Goal.
The team is entirely self-organized. No one outside the Development Team interferes with the inspection and adaptation processes of the team.
Features of the Daily Scrum event
All members of the Development Team are present.
The meeting is held daily at the same time and place.
The meeting has a maximum time of 15 minutes.
The time limit is intended to promote efficiency and prevent loss of focus.
The Scrum Master role should take care of the focus of the meeting, the brevity, and at the same time, sharing the answers to all three questions by everyone.
It is a common practice among the Scrum teams to keep the team members straight during the meeting. Because of this, sometimes the unofficial event name is the Daily Standup Meeting.
The idea of participating in a meeting without sitting in a chair is that if the participants are not so comfortable, they will not want to extend the length of their meeting.
The Daily Scrum event is not a report
Many teams just share a brief report of their work and what they will do today. Quite often, however, among many teams, this meeting is no more than simple reporting.
The Scrum Master role must support the idea of self-organization and the achievement of the sprint goal. If the team is not very proactive, the Scrum Master role should provoke them to look carefully at the situation and understand what others are sharing. The Sprint Goal must be achieved. If this means a work review or an immediate change in tasks, the team should do it.
The business value and the work of the team
Scrum mentions the topic of business value pretty much, though no specifics are given. However, all Scrum participants must strive to deliver business value because this is the most important thing the entire Scrum team has to provide for the product.
In the process, the Development Team not only has to strive to complete Product Backlog Items but also strive to deliver business value for the product. As Scrum proclaims the team to choose their way of working and how exactly they will do their job, there remains the risk of not enough value for the tasks completed.
The development team must be provoked to do the best job it can do. Business value can be found in any initiative.
Tidy code can provide easier maintenance in the future and save time. Being diligent in one web-based user registration form can provide more customers and fewer repelled users. Business value can also be delivered through communication, where the team asks important questions about the essence of the product idea.
Who are the participants in the Daily Scrum event
Participants in the Daily Scrum event are the Development Team and the Scrum Master role.
The presence of the Product Owner role is not required, but this role may be present if the team wishes and needs his / her knowledge and advice.
Any detailed discussion of a task should take place after the meeting. The Product Owner role should in no way attempt to influence the Development Team through its presence or to make its presence mandatory.
The Development Team conducts its meeting, inspects its work and progress. No one questions the Development Team about the tasks completed and the tasks remaining. The Burndown Chart chart is not a reporting tool to Scrum Master, Product Owner, or outsiders.
The Scrum Master role does not put any pressure on the Development Team related to work progress, nor does the Product Owner role when attending the meeting.
Exteriors and any business stakeholders are not allowed in the event.
The Scrum Master role ensures that the Development Team executes the event, that the 15-minute limit of the event is respected, and that no external pressure is exerted on the Development team. These are the only formal responsibilities of the Scrum Master role related to the Daily Scrum event.
Informal responsibilities of the Scrum Master role related to the Daily Scrum event
A team meeting can have many obvious or hidden issues. These problems are sometimes not resolved and continue to exist.
If during a Daily Scrum event, Development Team members look in the eye of a Scrum Master, Product Owner role, or some designated senior member as they speak, this may be an indicator of anxiety, anxiety, lack of calm, or expecting others to be leaders. These factors are signs of impaired self-organization, cohesion, proactivity.
As many teams and organizations exist, so many possible problems live on in the day-to-day work of teams. Even a business person, or even a customer, may require a member of the Development Team to report in writing or receive orders without anyone else in the team knowing.
Whatever problems are noticed inside the team or its meetings concerning all Scrum principles, it is the informal duty of the Scrum Master role to resolve them in some way. Sometimes these problems may not be solved due to stronger factors than the influence of the Scrum Master role.
BVOP recommends that in any Agile-oriented organization, there is an Agile Director position that addresses the problems of Agile teams that the Scrum Master role lacks the authority and power to solve.
The Agile Director should be seen as part of senior management, not as part of the Scrum team.
Potential sensitive situations related to the Daily Scrum event
You are receiving an email from the upstairs marketing department. Since they do not know where the Daily Scrum is located, they ask you to indicate it in advance so that they are not late for the meeting.
Members of other teams or departments should not attend the Daily Scrum event. It is up to the Scrum Master to explain these details to outsiders and to deny access to the event.
Your client's representative is on a business trip to your office, but only for a short time. Tomorrow he will leave early in the morning. Fifteen minutes before your meeting, a member of the Development Team asks the Scrum Master role to invite him to provide as much relevant information as possible while he is here.
In theory, the event should not be attended by external participants. However, since a member of the Development Team is willing to do so, it is unlikely that this will be a problem, and the Scrum Master role can assist and ensure the involvement of the client representative.
However, since only one team member presents this desire, it is appropriate that the other members of the Development Team are aware of this idea and request and also do not mind. The Scrum Master role must understand the views of all team members before inviting the representative.
A member of the Development Team was late for the Daily Scrum meeting and sent the following email with answers to common questions typical of the event:
"Yesterday, I worked on password recovery. The functionality is not yet ready, and today I am still working on it. I think by the end of the day, I will succeed. I encountered a few problems, but I got around them quite flexible."
At first glance, such information seems commonplace, as it indicates what your colleague worked on and what he will do today. It is also explained that problems have occurred. However, the information cannot be considered as exhaustive and satisfactory for other participants in the Development Team, who may need to understand what specific problems their colleague has experienced.
It is up to the Scrum Master role to request additional information as soon as possible after the Daily Scrum event. The Scrum Master role then shares information with the entire team.
The Product Owner role comes to the Daily Scrum meeting just before the end of the event and asks everyone to kindly repeat what they shared because in a short while Product Owner role will meet with a customer representative. The client has requested up-to-date development status, and the Product Owner role wants to satisfy the client's desire.
There are many possible reactions to this situation, but the most important result is keeping the Development team calm. The Product Owner role of theory should not be present at this meeting, nor should it require such information and ask the Development Team whatsoever.
However, such a situation is delicate and, in some way, needs to be addressed to satisfy all parties. An easy way out is to provide the necessary information to the Product Owner role. The development team shares specific information with the Scrum Master role. The Scrum Master role then passes the information to the Product Owner role.
It is strongly recommended that the Scrum Master role has daily clarity on the status of the work so that it can more easily participate in such reports while the Development team simply works undisturbed.
Scrum Master and Product Owner roles can play a part in customer satisfaction while the Development team continues to work peacefully to meet the Sprint Goal.
Just before the Daily Scrum meeting, your Director sent the following email to the Scrum Master role:
"Can colleagues from another department come to your daily team meeting to monitor your Scrum events and gain valuable experience. I guarantee that they will not interfere in any way."
Again an interesting and real situation. Outsiders should not attend the Daily Scrum event. However, to deliver business value to the entire organization, the Scrum Master role may consider facilitating the training of other teams as they attend real Scrum events.
Discussion between the Scrum Master role and the Development team can take place. If the Development Team doesn't mind, then the Scrum Master role may invite an external new team to watch from the side.
A member of the Development team asked the Product Owner role to attend the Daily Scrum event to share important information. Other members of the Development Team are strongly opposed as they believe that your Product Owner role will understand essential details about how they will implement the increment, and they do not want this to happen.
Since there is no complete consensus from the entire Development Team on the idea of inviting the Product Owner role, it is appropriate to reject this request. However, an important and hidden issue may be why some members of the Development team do not want their Product Owner to understand the details of implementing the increment. Transparency is lost, and technical questions are kept in secret. A good response would be the Scrum Master role to understand the real reason why the Development team has concerns.