A daily stand-up is a meeting that is commonly used in agile software development as a way for team members to quickly communicate their progress and any obstacles they are facing.
Today in this post we will share with you all the details about Daily Scrum Call or Daily Scrum Meeting.
What is Daily Stand Up Or Daily Scrum Call:
Daily Scrum Meeting is also called can Daily Scrum call or Standup meeting. This meeting owned by the Scrum team happens mostly at the beginning of every day.
The meeting is typically held in a standing position and is kept to a time box of 15 minutes or less.
During the meeting, each team member answers three questions:
- What did you do yesterday?
- What will you do today?
- Are there any blockers or issues that are preventing you from making progress? The purpose of the daily stand-up is to promote accountability, ensure that everyone is on the same page, and identify and address any issues or blockers that may be impeding progress as soon as possible.
For a co-located team all the participants stand in front of the physical scrum board (ideally the task board) and talk story by story or person by person, Scrum Master facilitates and takes ownership of any impediments or provides updates with the presence of the PO. Though its majorly known as the daily scrum call, both Scrum and Kanban teams ideally conduct this agile ceremony.
We will discuss in detail the daily stand up in each and every part of it this article.
Basic Rules Of Daily Scrum Calls:
- This meeting own by the Team not by Scrum Master or Product Owner.
- It’s not a Status update meeting
- This meeting should not exceed 15 minutes.
- This meeting should be conducted every working day, at beginning of the day
- This meeting should place at the same place and same time every day.
- All development team members must attend the meeting, even if they don’t have any pending work. Scrum Master and Product owner are optional. But it’s good to have the presence of the entire Scrum team.
- If the team (or the majority of the team member) is co-located, all team members should stand up for 15 minutes.
- The team should talk about
- Rules: Follow and stick to the Rules of the daily stand up as mentioned above
- State Your Name: Everyone Please state your name before you start talking about your tasks.
- Speak Loud: So everyone can pay attention to who is physically present near the speaker or on the Phone.
- Working from Home? : Please attend the bridge
- Task Remaining Hours: Update the task remaining hours before starting your DSM. To have the board populated properly and actually burn down.
- Burndown Chart: Scrum Master please check the burn-down after the end of DSM every day, and take action if required
- Long discussion items: Park the long discussion at the sidebar for the core hour discussion (After DSM). its also called the 16th Minute discussion item
- Team member on Planned Leave: Is any team member on Plan Leave? Please send the information to peers by end of your last working day.
- Distributed team: Open a bridge and screen sharing: Share your screen with ALM open and point your mouse to the task you are talking about.
- DSM Duration: Try to complete the Scrum call/standup meeting in 15 Minutes.
- After the Scrum call: a quick check on individual load, and take appropriate action in case of overloading to avoid risk.
- Keep a note: Keep a quick Note for all the tasks you want to talk about, that will help you quickly discuss the points. Instead of spending time to remember it during DSM or searching the entire board
- Impediments: Talk about all the impediments and resolution, and the risk to meeting the commitment.
- Cell Phone: Please get yourself detached from your cell phone for 15 minutes.
- Avoid interference from anyone outside of the scrum team during that 15 minutes.
- Use of the term “Status” or “Update”. It’s Not a Status update meeting.
- Avoid technical discussion during DSM – Park it for Core Hour discussion.
- Avoid Requirement Clarification that may take a long time – Park it for Core Hour Discussion, or the next grooming session. Or conduct an immediate grooming session
- Avoid Side discussions, focus on the active discussion for daily stand up
- Avoid change of the meeting time
- Provide your update to the entire team. Avoid giving updates to the Scrum Master or Product Owner or any limited number of team members.
- Avoid losing focus or being distracted, even if you don’t have anything to contribute. If you are part of the meeting put your 100% to listen and understanding (if not speaking). Stay on top on the ALM tool (may on a shared screen), or Physical board
Benefits Of Daily Stand-Up Meetings:
Participants In Daily Scrum Calls or Daily Stand Up:
Scrum calls are primarily owned by the development team. so it’s very important all the development team should participate in this meeting very religiously.
However, The participation of the Scrum Master and product owner make the meeting more fruitful and effective. So having the presence of all three roles (as mentioned below) is definitely good practice.
Participants in daily scrum calls or stand-up meetings (In Moscow)
- All development team members (must attend)
- Scrum Master (should attend)
- Product Owner (Could attend)
- one (Won’t)
Let’s try to understand the basic responsibility of the three primary Scrum roles during daily scrum calls.
Scrum Roles & Responsibilities During Daily Scrum Calls or Daily Stand-Up Meetings:
1. Development Team Responsibility during Daily Scrum Calls or Stand-up Meetings
- Talk about the three agenda
- What did you do yesterday
- What are you planning to do today
- Are there any impediments, blocking your progress
- Join the call on time, without delay. every day
- Give the task updates to all team members, not to the scrum master or any selective team member
- Give your task update to your peer, in case you feel that you will not able to attend the daily stand-up on time, or will be on leave or vacation. You don’t need to give updates every day when you are on vacation. give the update on your last working day before vacation.
- Give the task updates of any peer member in case they or on leave or vacation.
- Update remaining hours against each task before the daily scrum call. So that you can utilize the scrum call time effectively.
- Make small notes of all the tasks that you want to talk about, or any other associated details. In the 15-minute time box, if you spend time searching for information, people may lose focus, and the team will waste time on unnecessary activity. And if you are having your daily scrum call in front of the physical board, you may not have your PC or notebook accessible.
- Refer to individual remaining work and days remaining in the sprint. Raise your voice if you think it’s getting difficult to complete the task within the sprint. consult with your peer members and find out the best possible solution. take preventive action rather than corrective.
- Move your task card in your task board, from one column to another based on your scrum board workflow and the task’s story card.
- Ask the Product Owner related to any small question regarding requirement understanding. Remember If the discussion takes a longer time, park it for your core hour discussion or 16th-minute discussion.
As a Team
- Check the burn-down chart, and find out if the team’s progress is at risk. make a strategy for the day and the rest of the sprint duration.
- Re-assign tasks to normalize overloading. and keep a balance between task effort allocation and the remaining days of the sprint
- Think together, plan and act accordingly to complete the story as a whole, not the individual task. Even if one task remains incomplete, the story will be treated as incomplete. So when you are making a strategy of which task will work when being careful of the sequential tasks. A testing task can start when the development task is completed, So if you only think about only your task of development and think you can complete the task before the end of the sprint’s last day, then the tester will not be able to get time to test your change. And if there are any defects raised by the tester, the developer needs to fix them and followed them by re-verification.
2. Scrum Master’s Responsibility During Daily Scrum Calls or Daily Stand Up:
The Scrum Master is treated as a local coach for the team. till the time team is not getting mature enough to run in a self-organized fashion, Scrum Master drives the daily scrum call and continuously focuses on maturing the team, so that they can become self-organized. Along with that, a Scrum Master also has the below-mentioned responsibilities.
- Based on team composition, and distribution, find the best time and place to conduct this 15-minute discussion and schedule a recurring meeting with the scrum team including the product owner. preferable morning time of developers’ time zone.
- Facilitate the scrum call, and let the team drive it by them. Make sure the team is following the scrum call rules.
- protect the call from outsider interference
- stop the long-running discussion and park it for a 16th-minute discussion. Also, let those open discussions happen after daily scrum calls.
- Enforce on-time start and end of the meeting.
- Make sure the team is covering all the items in progress. And if any story can come in progress.
- Check if anyone is overloaded or under-occupied and ask the team to balance it.
- Have a quick look at the burndown chart and identify potential slippage of commitment. and take proactive action.
- Take ownership of impediments and give updates on them every day Daily scrum call or daily stand up
- Ask the product owner to verify the completed stories (if any) to mark them done.
- Ensure the team is following the definition of Done.
- Ensure the story cards and task cards in the scrum board represent the right states of the sprint progress.
3. Product Owner’s Responsibility during Daily Scrum Calls or Stand-up Meetings.
Products Owners are not mandatory for daily scrum calls; However, I encourage having Product Owners present in daily scrum calls. That will help him to understand what is happening during the sprint. And also, the team members can give heads up on the doubts they have and needs to discuss in detail. Mainly to remove any gap in requirement understanding.
Scrum Master or team can update the stories to the product owner that are completed and ready to review.
The product owner can update about any impediments that he/she is resolving.
Purpose Of Daily Scrum Call or Daily Stand-up Meeting:
- Increase Team coordination, and work together to meet a common goal.
- Increase transparency of Sprint’s progress, dependencies, and Risks.
- Increase the opportunity to take proactive decisions.
- Increase Team bonding and self-organization
- Identify road blockers in advance and act accordingly.
- Make a strategy for the day.
Why Stand up?
The daily stand-up meeting is also known as a “daily scrum”, a “daily huddle”, and a morning roll-call”. is practically a quick synchronization meeting with an individual team. Traditionally the scrum team mostly used to be collocated. where the team used to gather together at one place during the morning time for 15 minutes for a daily stand-up meeting in front of the physical board. They used to keep standing and share their updates within the team.
The main reason for conducting this meeting standing up is to keep the focus on the main agenda of the daily stand-up. The team avoids long discussions and restricts external interference. Now in modern days, Scrum teams started working from distributed locations, they refer to digital scrum boards and rarely get a chance to meet with each other in person. So standing up does not make much sense from their own desk.
The name of the meeting is changing from “Daily Stand-up-meeting” to Daily Scrum Call” or “Daily Huddle”. I will still emphasize conducting this Scrum called, Standing up if your team members are co-located, or mostly co-located.
Scrum Call Approach for Distributed & Co-located Team?
You may be part of a co-located agile team, or distributed agile team. In both cases, the overall rules, roles, and responsibilities will remain the same. The co-located team gets the advantage of gathering physically for daily hurdles, most of the time they use a Physical Scrum Board or Kan-ban Board.
Nowadays all teams are getting digital, by using ALM tools like Rally, Jira, Version, etc. and the use of the Physical board is fading out eventually. During Daily Scrum, these team members used to stand up for 15 min. These teams can easily plan their Daily call during the morning Time.
On the other hand, If the team is distributed, the Physical board does not add value to everyone, as it is not accessible to everyone. However, the availability Digital board within the ALM tools fills the gap of a Physical board and works out pretty well. However, the team lacks the physical presence of its members.
And it does not need to be stood up, as every one is referring to a small screen rather than a big physical board. The team meets through Screen sharing apps like Webex, Skype, Blue Jeans, etc. Many teams prefer to make a video to get to see each other. If the distribution of the team is within the same time zone, it’s good.
But if there are different time zone evolved. It’s practically not possible to schedule the meeting for everyone in the morning. So mostly the team mutually decides to have the Daily Scrum Call in the morning time, when the majority of the Development team is there.
Because of the different time zone. many times, the Daily scrum call get extended, as the team members from two different time zones generally get this time to share their thoughts, Ideas, and sprint progress.
However in that case try to complete the Scrum Call, identify the long-running discussion, and park them for later. Once the main agenda of the Daily scrum call is over, make a logical end of the daily sprint progress. and start the discussion you have parked for, here the only required member can stay, the rest can drop off.
The Outcome Of The Daily Scrum Call:
Common Understanding of Team Progress:
Meeting with the team to share what they are working on, and what they are planning to do today to meet the common goal of the sprint, improves the common understanding of the team about the progress on their commitment for the sprint.
Execution Strategy for the Day:
Based on the current state and progress, the team makes the strategy for the day, who will work on what task, which task needs to be finished first, and how to utilize the sprint time in the most optimized way.
An Updated Sprint Backlog:
Continuous acceptance and progress on Task and sprint level update the sprint backlog on daily basis. Gives better visibility to the team, or management level. It also contributes to consolidated reports to reflect real-time states.
And Updated Scrum Board or Sprint Board:
The teal also updates the task Remaining hours, Task card, and Story Cards placement in the sprint board. and make the Sprint board or Scrum Board up-to-date.
Challenges Of Daily Stand-Up:
Time for distributed time zone:
Apart from not being able to follow the basic rules of Scrum Call, the biggest challenge is to define a time when the team is distributed, and the team is located in two different time zone. As it is good to have in the morning time, it becomes difficult to identify, the morning of which time zone. So in that situation, plan the Daily Scrum call in the morning of the time zone where the majority of the development teams are working.
Reaching a mature mindset that, this 15-minute discussion is not a status update meeting, that you need to update your Product Owner or Scrum Master or anyone about the progress. The team just needs to discuss within themselves and prepare a strategy for the day.
If the team (Dev Team + Scrum Master + Product Owner) doesn’t utilize time for the purpose it is meant for, or even if they were forced to do so. The Agile team will not get the real expected outcome of the meeting and it will impact the overall performance of the team and also the agile value. The team will eventually lose interest in the daily stand-up. And for the team, the Daily Scrum Call becomes just a formality or burden.