Test Management Featured Article

The temptation to outsource testing or at least take advantage of a globally dispersed workforce is strong for many developers. And while using a globally dispersed team can make sense and deliver lower costs, it is important to get the details right. Not all setups are the same.

In a recent white paper titled “Building Hyper Productive Globally Distributed QA Teams,” test management solutions provider Zephyr outlines six key suggestions that should be considered when building a geographically dispersed team.

First, pay attention to the time difference.

“Time difference is the primary concern and shouldn’t be overlooked in favor of lower rates,” noted the Zephyr paper. “Team cohesion is important for the success of any project and a time difference of 10 hours can stress team leaders who need to maintain communication.”

Look for a time difference of no more than four hours. So if your business is primarily in the U.S., consider Latin American or Canada but not, for example, the Philippines.

Second, have the team work the same hours if there is a big time difference among testing participants. This might not be appreciated by all, but it can keep the cohesiveness of the team even if geographical locations are vastly different.

Third, if 24-hour testing is part of the appeal of a globally dispersed testing group, focus on the hours of contact.

“Someone from the project team will need to be communication on a regular basis and 2 a.m. meetings don’t always go over very well,” noted the paper.

Fourth, a good organization of testing artifacts and work assignments can help flatten geography. With an appropriate system for managing, assigning, verifying and tracking work, time zones don’t become as much of a problem.

Fifth, visit offshore teams if at all possible. It goes a long way toward building cohesiveness and presence, even if these far-flung team members are not visited more than once a year or two.

Finally, a good testing management solution assists with recourse turnover and the addition of new team members. If there is a good structure in place, bringing new team members aboard is relatively easy.

Testing teams that are not all in the same city can work, and they bring benefits. But don’t overlook the time difference and the effect that can have on a team.