Tuesday, September 1, 2009

How do Teams Become Distributed?

Many companies without a formal distributed work program may still find themselves needing and wanting to support distributed teams. Here are some ways that a team may become distributed:

* your company decides to delegate some specific chunks of work to a group in another location; e.g., programming to India, QA to Colorado. However, you still want to make sure these groups stay in sync with the rest of the team.

* the company acquires a new company, and is eager to integrate a newly acquired employee (and their skills) into an existing team or project

* a person with required skills is found in a different location, and no one with the required skills is available in the same location as the rest of the team

* two or more teams merge, with each team in a different location

* the company may decide to close a campus for real estate or other reasons, and may not want to relocate all of the employees (nor lay them off)

* a local or national government, for pandemic reasons, orders all offices within the city limits to close for two weeks to stop the spread of a flu or other disease. How can you keep your company still working?

There are more examples of this, so I’ll continue this list in a future post. I’ll also discuss how to approach the issues and finding best practices to help these teams.

Posted via web from dianaf's posterous

No comments: