Here are some things we do to make distributed agile testing work:
- Make the best use of the overlap hours. In our case, we have at least three overlap hours between Poland and the eastern US. These hours are precious. During this time, we have stand-up scrum meetings and we work on test team projects.
- Invest in the right tools. This means buying or building tools that enable everyone on all teams to have the same advantages. For example, we migrated to Quality Center when we opened the Poland office. QC is just about as responsive in Poland as it is in the US.
- Communicate! We use video conferencing, collaboration software, and instant messaging everyday. Cheap tools can erase the miles and bring your teams together. We have started using Adobe Connect for video conference and collaboration. One cool feature of this is the ability to record meetings. This gives the abilty for programmers to pass along a quick recorded demo of the day's work to the tester on the other side. User acceptance test sessions can be recorded -- in fact, a UAT performed during off hours can be reviewed later in another office.
- Travel between sites. New hires in our Poland office spend several months in the US working the development and testing teams. A big success factor is building strong relationships. It is difficult to really get to know and to trust someone if you only talk on the phone or communicate through email. The benefits to people traveling and to the people being visited outweight the costs of traveling.
- Find the right projects. Regression test analysis and many test automation-related projects are easily done in Poland. Most new functionality projects are more easily done in the other office where there is better access to programmers and business users.
- Hire the right people. This is always important, but it is really important when you have to rely on trust and communication with people that you don't see on a regular basis.
What I have found so far is that the issues related to distributed agile testing are common with distributed agile development. If you are looking for more information on distributed agile development, here is a great resource: