There is a secret to successfully distributed Agile development, and it has nothing to do with AJAX, Java, .NET or perfect hours. In cases where English is a second (or third) language and employees have different cultural morals and religious affiliations, successful communication is the key issue. Challenges, such as working over multiple time zones, or simply working with a new colleague for the first time, can also present communication problems. The keys to successful communication are cultural awareness and team building.
Cultural Differences and how to Anticipate Friction
Distributed Agile projects with multinational team locations are becoming the norm. The primarily reason for this is cost reduction, but skill set is another driver. Each geographic region has its own cultural subtleties that must be taken into consideration. For example, in the Indian and Chinese cultures, it is considered impolite to say no or to disagree with someone in too strong a manner, while in the Russian and Baltic cultures, voicing strong opinions are expected. As you can imagine, both reactions can cause friction if a team is not used to these cultural nuances.
The manner in which team members feel comfortable communicating is another common source of friction, often English is the second or third language for a team member. Perhaps their writing skills are more advanced than their verbal, or vise versa. Typically, Baltic and Indian cultures feel more adept with writing than they do with speaking English. Conversely, the French and Latin American cultures are often more comfortable with the spoken English word.
Another issue to be aware of when working with diverse teams is that each culture has its own work ethic, holiday schedule and accepted office behaviours. These seemingly harmless differences can lead to a lot of friction. For example, the French believe strongly in a 35-hour working week, while Americans often work more than 50 hours each week. Holidays are another planning issue that needs attention. Each country has its own set of national holidays, and different religions observe different Holy days. Finally, in regards to all planning, it is always important to be aware of daylight savings issues for the different locations.
Fortunately, these are all fairly consistent, easy to decipher differences. But, there are other issues that do not stand-out like these. Differing cultures have varying senses of urgency, such as the British and French. Their cultural norm varies greatly from that in China, India, Russia and the Baltic nations. What is considered appropriate conversation and behavior can also vary widely between geographies.
Team Building from the Start to Avoid Animosity
Much of the animosity and friction that can grow between members in any team, whether globally dispersed or crammed into one small office, can be avoided through strong, repetitive team building activities.
It is strongly recommended to arrange face-to-face meetings at the start of any release plan that involves, multi-site distributed teams. It is also best, if possible, to have periodic follow-up meetings after the launch. It is true that planning can be done over the phone using collaboration tools such as WebEx or NetMeeting. However, even though the output may look the same, there is a distinct lack of chemistry and familiarity within teams that never meet face-to-face and rely solely on collaboration technologies. Developers are people, and they won’t bond with programs – personal rapport goes a long way. Face-to-face meetings are ideal for hammering out how to communicate within the team.
The travel costs involved in setting up these face-to-face meetings can easily run into thousands, and management will almost always refuse at first. Simply remind them of what the cost could be if the development team delivers the wrong functionality or the accrued cost of developer run-rate if they have to start over, which often happens when a team doesn’t meet regularly. In this case, the financial impact could be much greater than the cost of a few flights! If you have a team of developers doing the "wrong" thing for a period of time and then getting into a blame situation with a product owner and vice versa, the cost can often be the entire sprint or even the project.
Plan to have team-wide meetings every week via audio or video conference where every sub-team reports on what they’ve done, issues they’re facing and something non-work related to share. The more conversation the team members can have that does not involve work, the closer they will grow to each other. Team member familiarity goes a long way to relieving tension, and letting each others know you have a sense of humour will help during the inevitable stressful moments. Be considerate of the team’s time zone issues too. Rotate meetings to share the burden of off-hours meetings so that the same geographic region isn’t always inconvenienced with a late or early meeting.
Distributed Agile success is dependent on developing good communication skills between team members. Keeping an open mind, watching out for cultural differences and working to build kinship beyond the project at hand can be the difference between failure or success. This is not a hard process, but it does take effort from everyone. And, the likelihood is if your company has decided to try distributed Agile through outsourcing or its own distributed locations, you’ll end up working with these coworkers on further project. Working to improve inter-cultural communication is an important investment that will continue to benefit your company throughout many future endeavors.
About the Author
Clive Jenkins currently serves as Delivery and Assurance Manager for Exigen Services. A certified Prince2 Practitioner and Product Owner, he has been working with distributed Agile teams for more than four years, with more than 20 years of development experience in total. Clive lives in Wiltshire, England and works in London.
