Some estimates say that 80% of Software development projects are now global. According to these trends, if you work in or manage a co-located team, it will not last long. There are two approaches to global projects: outsourcing and distributed teams. My concern is distributed teams, where team members can work from a location of their choice.
There are benefits and reasons behind the trend of projects getting global. When your team is not co-located in an office, but is scattered around the world, certain issues arise like communication, reliability and motivation, to name just a few. This video shares 10 lessons learned while working in and managing a globally distributed team of developers which release code regularly.
Video Producer: Smidig Conference
Interesting vblog. I would like to challange two ideas proposed in the post. Our organization works with teams in two different countries, India and the US. It would be both a disservice and a challange to our teams to not communicate via teleconference on a routine basis. Developers need to have the ability to ask questions and receieve feedback in a efficient manner for elements not captured in the user stories. Doing so via email or some other method would slow the process. We do recognize the time issues between the two locations and have adjusted working hours accordingly. The second issue is the removal or reduction of the PM/SM oversight to the project. We have seen when this is done the velocity also suffers proportionally. I do agree they have a tendency to get in the way, esp if they have less experience. Overall good information, would like to hear more.