After acting as scrum master for several months on a distributed team with people in six different locations, three different time zones and two different countries, Jon Archer offers ten tips to help get past those inevitable awkward silences in Scrum teleconferences.
“After working for some years in the domains of large, multisite, and offshore development, we have distilled our experience and advice down to the following: Don’t’ do it.” “Scaling Lean & Agile Development – Thinking and Organizational Tools for Large-Scale Scrum”, Craig Larman & Bas Vodde, Addison -Wesley
Written by Jeff Sutherland, Anton Victorov, and Jack Blount, “Distributed Scrum: Agile Project Management with Outsourced Development Teams” analyzes and recommends new best practices for globally distributed agile teams. Toyota routinely achieves four times the productivity and twelve times the quality of competitors. Can Scrum do the same for globally distributed teams? Two agile companies, SirsiDynix using Scrum, and StarSoft Development Labs using Scrum with some XP engineering practices, achieved comparable performance developing a Java application with over 1,000,000 lines of code. SirsiDynix best practices are similar to those observed on distributed Scrum teams at IDX Systems, radically different than those promoted by PMBOK, and counterintuitive to some practices advocated by the Scrum Alliance.