| |Three Tips for Your Geographically Distributed Team
Agile has moved past small co-located teams. As much as you and I might prefer that all teams be co-located, it's not going to happen. That's because great people are located all over the world.
And, how you organize the people is important for your success in a geographically distributed agile project.
- 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.
In my workshops, you'll experience many more tips and techniques to make your geographically distributed teams work. Please do join me.
Intrested in a Geographically Distributed Teams Workshop?
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 isMaking 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?