Globally Distributed Software Engineering - The Good, the Bad and the Ugly
summary
Summarizes nine concrete goods, bads and uglies with case studies and numbers: distributed work gives access to talent and customer proximity but communication and coordination break down past a 15 meters threshold of informal interaction, and full product knowledge often takes a 1–2 year learning curve. Recommends Scrum/short iterations, daily video calls (Skype/Google Hangouts), co‑located onboarding, joint talent management and stable teams (retention can cut hidden costs by ~15%) as proven fixes.
AI-written summary · about
chapters (11)
- 0:00Globally distributed engineering
- 2:54Good side of distributed dev
- 7:54Communication challenges
- 12:3615-meter rule for teams
- 16:53Learning curves and retention
- 23:28Cultural differences impact
- 31:22Delft University insights
- 33:50Agile methods for distributed teams
- 38:28Personal experience lessons
- 45:57Talent management in outsourcing
- 47:27Face-to-face meetings importance
related talks
41mKeeping distributed agile teams ‘face to face’
33mDistributed Teams
57mLessons from {distributed,remote,virtual} communities and companies
41mHow to be a highperforming distributed agile team
41mAgility in a Distributed Team
38mDistributed Sys Teams
37mBuilding & Scaling Distributed Teams
49mDo's & Donts for Distributed Scrum