Get certified - Transform your world of work today


Effective Ways to Conduct Daily Scrums for Distributed Teams

1 March 2016

As we all know, daily stand-up meetings, also referred to as Daily Scrums, are one of the most important sprint ceremonies, leading to the completion of committed user stories. I prefer to think of the Daily Scrum as a synchronization meeting. Team members are synchronizing their work: Here's what I did yesterday and what I think I'll do today. A Daily Scrum will feel energizing. Team members will leave the meeting feeling enthusiastic about the progress they and others have made.

Despite the sixth principle of the Agile Manifesto, "The most efficient and effective method of conveying information to and within a development team is face-face conversation," for distributed teams this is not possible. Conducting Daily Scrums when team members are in the same time zone and speak the same language is much simpler than for a team with members spread across multiple countries and time zones, having many different languages and cultures. Distributed Agile teams require a different level of attention, especially when they are newly forming.

Distributed Scrum teams can be classified into three major types:
  1. Scrum teams in the same time zone
  2. Scrum teams with overlapping time zones
  3. Scrum teams with no overlapping time zones

Techniques for driving Daily Scrums

Below are the various techniques that you can follow to drive more effective Daily Scrums for cases a and b above.
  1. Deal with the time zone, choosing the most convenient time for all teams that is possible.
  2. Identify and attack blockers between Scrums.
  3. Use any Agile planning tool (Altassian JIRA, IBM Rational Team Concert, Hewlitt Packard ALM, Visual Studio Team Foundation Server, Rally, or VersionOne). The advantages of using an Agile planning tool are that everybody is on the same page, and during the stand-up meeting members can walk through each of the tasks or user stories with everybody being well aware of where they are. Everyone can see the status information across time zones as soon as it is entered.
  4. Educate the team about the importance of muting the telephone while another distributed team member is updating.
  5. Make stand-ups a topic of the team's retrospectives.
  6. Consider the logistics for Daily Scrums that are directly related to communication. Good communication can be achieved by teleconference, with a computer screen shared with all attending team members who can view the team progress by using the Agile planning tool, as mentioned above, or by video conferencing, which will be little bit more difficult because of setting up and securing a room within the facility every day.
  7. The team and the ScrumMaster (SM) should strive to understand all the blockers. The SM makes sure that all these blockers are addressed straight away after the Daily Scrum, in case another meeting is required to remove the blockers.
  8. Take Daily Scrum notes.
  9. This helps distributed team members to overcome language problems and to plan and learn. Chat tools and Wiki help distributed teams facilitate Daily Scrums in this way.
Make sure that if you are implementing any Agile planning tool, the information in it is up to date prior to the stand-up meeting, irrespective of whether the team is distributed or colocated.

Teams with no overlapping time zones

The above points hold good for the Scrum teams within the same time zone and overlapping time zones (e.g., India and Europe), but not for teams with no overlapping time zones (e.g., Asia and U.S.). So, how do you handle distributed Daily Scrums with no overlapping time zones?
  1. Hold the Daily Scrum each day at an hour that is inconvenient for one side or the other. Rotate the burden of the inconvenience from one location team to the other every month or so, based on the Scrum teams' receptiveness.
  2. If it is difficult to hold the meeting according to the above conditions, identify one team member and request that he or she write down the updates and share them with the other location team.
  3. (This one will be costly:) Record the Daily Scrum at every location and share the recording with the other team. Before the start of the Daily Scrum, your team can walk through the other team's updates.
  4. Conduct Daily Scrum through documentation.


Opinions represent those of the author and not of Scrum Alliance. The sharing of member-contributed content on this site does not imply endorsement of specific Scrum methods or practices beyond those taught by Scrum Alliance Certified Trainers and Coaches.

Article Rating

Current rating: 4.1 (7 ratings)


Tim Baffa, CSM, 3/1/2016 3:32:29 PM
Agree with the "share the pain" approach, but I don't agree with taking notes during daily stand-up meetings.

They are opportunities for the team to touch base. The content of these discussions isn't intended to be captured like a status report. Perhaps the team can rotate one "time zone" team member to attend other daily stand-ups. Again, share the pain.
Kevin Normand, CSP,CSM, 3/2/2016 8:16:20 AM
Great summary. From our experience I think the important points are all covered.

I also do not think taking notes at daily scrum is necessary; and maybe not such a great idea. It costs time for the team, and changes the daily scrum experience significantly for the poor note-taker.
Upputuri Srikanth, CSM, 3/3/2016 12:40:59 AM
Thank you Tim and Kevin.
Yes that is a good idea, we can rotate one "time zone" team member to other other daily stand-ups.
Will follow from now onwards :)

You must Login or Signup to comment.

The community welcomes feedback that is constructive and supportive, in the spirit of better understanding and implementation of Scrum.


Newsletter Sign-Up