» scrum software development
In my previous article, I argued that using a distributed team with the Scrum Framework was a bad idea and advised against it. There is sufficient information to show that distributed Scrum teams perform poorly compared to those that are co-located. However, everyone does it anyway! As Jeff Patton once said, “if you want to run a marathon with ankle weights, don't complain to me about your time!”
Recent studies show that 3 out of 4 Scrum Software Development Teams are distributed, meaning that at least some of the team members are not in the same location. Co-location is one of 12 factors that can contribute to or detract from high-performing teams. This article explores the 12 factors that contribute to high performance when using the Scrum Framework, and then explores how having a distributed team affects.
The new Scrum Guide, the definitive reference for the Scrum Framework, is out. As of November 7, Scrum co-creators Jeff Sutherland and Ken Schwaber have published an updated version of the Scrum Guide. The last three revisions were in 2011, 2013 and 2016 so this is a relatively fast update since July 2016.