Forums

By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. If you have left the first and last name fields blank on your member profile, your email address will be displayed instead.

All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Daily Scrum not effective due to geographic location of development team
Last Post 17 Jan 2014 07:48 AM by Stacy Venani. 5 Replies.
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
Samridh Arora
New Member
New Member
Posts:9
Samridh Arora

--
15 Jan 2014 04:05 PM
    HI,
    If development team is geographically located at Europe,India and Australia as in case of my project .
    Daily scrum is not effective as it should be .
    As a solution we ask team members to email their update and then we go through the items.
    If someone has better option then please let me know.
    Dave Lochead
    New Member
    New Member
    Posts:5
    Dave Lochead

    --
    15 Jan 2014 04:40 PM
    I have had similar problems in the past, and I have to say that unless your teams have an unusually high commitment to the project and dont mind getting onto a Skype conference call at strange times in the night, then you are probably doing the best you can.

    A possibility might be basing a message thread on network 54 allowing all who are involved, and registered, the chance to see what each team is doing, and comment, which would be good transparency, but may also dissolve into other pointless sideline discussions
    Ian Mitchell
    Veteran Member
    Veteran Member
    Posts:1693
    Ian Mitchell

    --
    15 Jan 2014 05:36 PM
    The point of a Daily Scrum is to ensure that team members spend face-to-face planning time each day with a collaborative focus on the Sprint Goal. If team members are distributed, then everything needs to be thrown at maximizing the quality of the communication channels.

    Video conferencing is the best option because it carries at least some if the non-verbals. Audio is a poor second choice and if this is all you have it should be of excellent quality.

    Charles has a good list of resources on distributed, offshore, and multisite scrum available here: http://www.scrumcrazy.com/My+Prefer...+Resources

    One other option us to change the session format to "walking the board". Each task on the team board, which should be electronic so all can see it, is considered in turn. The team collectively determine what needs to be done, and by whom, in order to progress it. This is a delivery-centric approach used in Kanban. The disadvantage is that some focus on the Sprint Goal is lost. However, the approach can be used with reasonable success even over low bandwidth communication channels.
    VS Chandra Mouli Seelaboyina
    New Member
    New Member
    Posts:27
    VS Chandra Mouli Seelaboyina

    --
    16 Jan 2014 08:19 PM
    How about the time zone differences which are not overlapping?
    Ian Mitchell
    Veteran Member
    Veteran Member
    Posts:1693
    Ian Mitchell

    --
    16 Jan 2014 10:15 PM
    A Development Team are expected to self-organize a suitable time at which all members can attend the Daily Scrum. This expectation applies regardless of whatever time zones they may be in.

    If a distributed team cannot do this then a Daily Scrum cannot be held and they will not be doing Scrum. They can exchange emails. However that will not be a Daily Scrum because the participants will not be engaging with each other in the same 15 minute time box.
    Stacy Venani
    New Member
    New Member
    Posts:1
    Stacy Venani

    --
    17 Jan 2014 07:48 AM
    I had an issue with time zones on a previous project. We did our best to find 15 minutes that worked for everyone - usually early morning for the US (folks often took the call form home, which was fine). For longer meetings, like sprint planning, we rotated who was "inconvenienced" - ie. early morning for the US on time, late night for the US next time, etc. We planned the days/times ahead and kept rotation going, so people who met really late their time knew they would be meeting at a more convenient time next time. It was announced way ahead (so people could make arrangements for their personal life, and very fair, so everyone was on board with it, and it worked well.
    You are not authorized to post a reply.


    Feedback