Three Tips for Your Geographically Distributed Agile Teams
NOTE: This post has been taken from Johanna Rothman's terrific newsletter, "The Pragmatic Manager".
Three Tips for Your Geographically Distributed Team
Make sure you organize the people in cross-functional, feature teams. Organizing the people in silos, such as developers or testers, introduces delays into the project.
Call the teams by their feature names, not by their geographic location. It's too easy to call the teams by "Headquarters" or "Cincinatti" or "Paris" or "Bangalore", and any name other than "Headquarters" implies a hierarchy among the teams.
Spread the discomfort of planning times around. If you have team members spread across many timezones, spread the discomfort of the planning times across the entire team, not just the one or two team members who are most dispersed.
I'm delivering a two-day workshop in Tel Aviv, Israel June 19-20. See the course list at Ignite for more details. I'm also delivering an Executive Agile briefing while I'm in Israel.
My post-conference AYE workshop this year is Making Geographically Distributed Projects Work. How do you bring teams and people all over the world together to make a product? It isn't easy, but it is possible. We'll learn how together.
Would you like an on-site workshop? Contact me.
New to the Pragmatic Manager?
I keep my blogs current with my writings: Managing Product Development
Hiring Technical People
and my newest blog (with it's own new mailing list) Create an Adaptable Life
(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)