Tips for Working Effectively with Distributed Team Members

In a few classes I have taught recently, we have had some interesting conversations around working on distributed agile teams.  I always recommend trying to keep your Scrum team co-located whenever possible but in today’s world, distributed teams are unavoidable.  Here are some suggestions to help keep your distributed team members more involved:


1.    If the majority of your team is in one location and a few members are remote, get a large stuffed animal, blow up doll (not the adult variety please), etc to represent your distributed team members.  Bring the doll, stuffed animal, etc to all of your meetings and put them in a chair.  You can even write the names of the people it represents on a sticky note and stick it on the doll. The visual reminder of the people on the phone helps keep the folks in the room aware of the team members on the phone.

2.    Draw a table on a whiteboard where the meeting is initiated.  Write the names of all attendees on the phone around the virtual table.

3.    Use an on-line, real time collaboration tool that all team members can access during meetings. The Scrum Master can then put relevant data here for everyone to see.  If you have a distributed team, a physical card wall may not be a good choice.  Look into using tools like the GreenHopper plug-in for Jira or Rally.

4.    Get a web-cam and use it often.  I know a company that has a webcam running all the time in each office and has it is pointing to the task board.  Everyone can log in and see it whenever they need to.  The web cams are also used for daily stand-ups, etc.

5.    In meetings where the purpose is to gather information and form an action plan such as planning meetings, retrospectives, etc, try using the round robin style of gathering information.  Go around the virtual room and ask each person to contribute.  This way, everyone has a chance to be heard.

6.    Publish any decisions made somewhere where the entire team can see it.  Don’t bury information on an intranet or share point site that no one goes to. 

7.    Create some simple, fun games with prizes that encourage team members to visit the place (intranet, wiki, etc)  where you keep important information (like action items from retrospectives, etc).  For example, put trivia questions from Jeopardy on the site and give a fun award at the end of your stand-up to whoever responds first with the correct answer.  Or, you can track the results each day during the sprint and then give an award at your sprint demo.

8.    Devote a few minutes during each retrospective to discuss remote team issues and to brainstorm on how to make things better.  Follow-up with an action plan and re-visit it after it sprint.

9.    Pick a few times a year where everyone travels to the same location at once.  This gives everyone a chance to meet each other face to face.

10.   If you are not remote, then act like a remote employee for a day every now and then (i.e. work from home).  See first hand what the remote people experience so you can better understand the challenges they may be facing.


The point here is to get creative and go beyond simple conference calls.  Your Scrum Master should own the responsibility of managing effective communication and collaboration with distributed team members.  Make sure you are getting regular feedback from your team members on what is working well and what isn’t.  Collaboration on your distributed teams should be a top priority and you should be willing to make the necessary investments to ensure that all team members feel like they are heard and are part of the team.


9 Responses

  1. […] Posted on June 12, 2008 by Jon Strickler Megan Sumrell has 10 nice tips up on working with remote teams. I like that these tips include a softer side to the remote challenge. To them, I add a few […]

  2. To add to point #3: also check out VersionOne. Our company just recently started to implement / use it and it is in the same camp as Rally and maybe Jira.

    To add to point #9: we had an interesting solution in my last company (very large)- Our scrum team had 10 people in one location and 4 in another overseas. Every few weeks we brought one of them over for a week or two and sent them back. This allowed the culture on both sides to normalize. As the environment on each side changed, there was a person that could see both and cross-pollinate ideas to the other side. When we had our standing meetings or reviews, it felt like one team even though there was an ocean and half of Europe in between us.

    Great post!

  3. Thanks for the post! I find that as our methods for doing agile get better and as the tools for distributed teams improve, the barriers to distribution really begin to fade away.

    I love the idea about representing the remote members with some physical representation at face-to-face meetings (do the distributed members get to pick their own blow-up doll? 😉 )

    A few tools I’ve found absolutely invaluable for distributed teams:

    1. Mikogo (or similar) desktop sharing/remote desktop tool. They’re free and they’ve gotten so fast, it’s like having someone standing looking over your shoulder (or handing them your keyboard/mouse). Make it a habit to always open a session whenever you’re on a phone call. Things are so much clearer when you’re both looking at the same thing. For example, have it point to the project dashboard in Rally or whatever tool you’re using during the Daily Scrum so people can point to their tasks as they talk about them.

    2. Wiki for allowing the team to collectively own, create, and evolve the information & discussions that surround the project – making those decisions visible, as you mention.

    3. IM and/or Skype so you can see who’s around and ping them for quick questions

  4. On online tool you may take a look at TargetProcess ( It has nice UI and many productivity tools.

  5. Very Helpful Site,
    Thank You.

    Please make more Articles Like this…

  6. Why not move off the whiteboard entirely? I love the architectural elegance of this tool for greater insight into where a specific project is directly within your source control tool regardless of location, not to mention the ability to just change the process with a drag and drop. Sweet.

  7. This topic is quite trendy in the net at the moment. What do you pay the most attention to while choosing what to write about?

  8. Honestly, I tend to write about things I am currently working on with customers or talking about with them.

  9. “‘” I am really thankful to this topic because it really gives useful information -.-

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: