How to Increase Your Distributed Team's Flow
In the absence of ongoing collaboration, even the most talented distributed software team can slow down. Agile principles and practices show how a regular rhythm can maximize flow.
In forming distributed software development teams, some managers will gather the most skilled professionals across the globe to form the teams, work with them to set up processes to follow, then ensure that work flows into the teams and that value flows out. Good managers also work to remove impediments. All well and good, but can these teams keep up a rhythm?
For instance, on many distributed software teams, team members and managers alike will seek to reduce collaboration time in preference to individual work time. However, without regular collaboration on your distributed software team, your team can slow down even if you have the best developers and testers on the planet. Agile principles and practices show how a regular rhythm can help. Let’s look at a couple of examples…
An example of how one broadly distributed team struggled
One out-of-rhythm distributed team consisted of a product manager on the U.S. west coast and developers on the U.S. east coast. The team decided to improve the quality of its software by adding a tester in India.
Since members all worked for the same organization, the team assumed the tester was familiar with the product line. This was not
Please log in or sign up below to read the rest of the article.