Friday, July 15, 2011

Remote team building on distributed Agile projects

Team camaraderie is important on any projects, but it is critical on Agile projects because Agile process requires close interactions. If you have distributed teams, it becomes challenging. It is important that you spend some time to make sure the teams gel together to get the best result for your Agile project.
 
Ideally, you would want to bring the teams together at one location for a sprint at the start of the project. The team members will get an opportunity to know each other while they start working on the project. You may want to do some explicit team building activities. Then you want to bring the teams together every so many sprints, maybe rotating the locations where they come together. Here is a nice case study on this.
 
Yes, it increases the cost of your project. Given how the economy is, you may not get the budget approved for the travel and associated costs. This is what happened to the project I'm working on as an Agile coach. As an alternative, we came up with a remote team building activity, which truned out to be very helpful.
 
Some backgorund on the teams
We wanted to faciliate a team building activity between two teams- one located in the West coast, and another in the East coast. The two teams did not know each other. This is the first time they are working together. One team was staffed by people from the client, and the other was by the vendor. As a result, there were some work culture differences. The teams were communicating through Scrum Masters and Proxy Product owners. Developers did not know each other and shyed away from communicating directly. Also getting in the way was the 3-hour time differences between the two teams. Overall, annonimity resulted in lack of trust and was contributing to the overall frustration between the teams.
 
Remote team building
We decided to faciliate a remote team buidling session using a vedio conferencing session. Prior to the event, we did the following:
 
1. We created a team profile for each team. It included some intro info about each person with a picture.
 
2. We paired each member of one team with another from the other team.
 
3. We sent them a list of questions and asked each pair to interview each other over the phone prior to the team event. A sample set of questions that we used to help prime the conversation:
 
                  1) What is your role on the project?
 
                  2) What is (are) your domain(s) of expertise?
 
                  3) What new capabilities are you learning on the project?
 
                  4) What are your pet peeves at workplace?
 
                 5) Tell us one interesting thing about you that no one knows.
 
                6) What is your favorite hobby? Why do you like it?
 
               Additonally we asked everyone to pick a question to ask their buddies.
 
4. The team event was divided into two parts. In the first part, we asked each pair to introduce their buddies to the whole team. In the second part, we made it free form (quizzed the team on what they learned about each other) with a deliberate effort to instigate conversations about things that the teams are struggling with.
 
Overall, everybody found the team building activity helpful. At the least, it broke the ice between the two teams, got them talking about issues (as you would expect in "storming stage" of a team/goup development), and opened up the communication. Some norms are starting to form from the storming.
 
I do not expect the trust to be built overnight. Still we need to continue to make deliberate efforts in making that happen. But, it was a good start. We plan to do this on a regular interval.
 
Some of the fun facts about these two teams
  •  One team is a all-women team.
  •  Eleven languages are spoken between the two teams.
  •  Six countries represented based on birth places.
Do you have a similar experience of team building?

5 comments:

  1. Organizations need to be assured the individuals that manage their projects can integrate methods to achieve sustainability goals and still achieve project specific objectives. Project Managers need credentials that validate their proficiency with these specialized qualities. PMP Certified and scrum certified project managers can learn, apply, and validate mastery of sustainability based project methods to meet these demands.

    ReplyDelete
  2. To manage the risk successfully one should have scum in their projects .With high competition, companies have to develop products fast and innovatively always adding value and greater customer satisfaction. In Scrum, it is important to learn agile through one of the Agile Training Providers and practice its basic principles which collectively and naturally help in effective management of risk. As a project manager i follow SBOK guide of http://www.scrumstudy.com

    ReplyDelete
  3. Team building activities are stimulating problem-solving tasks designed to help group members develop their capacity to work effectively together. Many team building and initiative tasks are like kids games, others are novel, complex tasks and designed for specific needs. More elaborate initiative tasks can involve ropes courses, night-time activities, and exercises lasting over several days.

    ReplyDelete

  4. I love team games, especially as a team-building
    Richard Brown best virtual data rooms

    ReplyDelete
  5. Thank you for sharing information. it is new and useful to me....click here now

    ReplyDelete