This video explains that distributed software development is a strategic capability for a company, presenting a framework and Agile practices for building such an environment.
It seems like everyone wants to scale their agile teams. The Agile approach to software development needs to scale up to larger team sizes as projects grow in scope. Agile also needs to scale out to handle geographically distributed teams. Both are challenging propositions for many teams. Ade Miller talks about his experiences at Microsoft; scaling agile up on the Visual Studio Tools for Office team and scaling out on the radically distributed teams within the patterns & practices group.
Video Producer: San Francisco Agile User Group
Related article: Distributed Teams and Agile
Tamara Sulaiman presents experiences in implementing Agile in teams across different time zones in large companies. She shares the pleasure and the pain, ideas that worked as well as ideas that didn’t. She also shares the critical success factors in making program level implementations successful and sustaining.
We are running a medium size project distributed across three countries (Norway, Czech Rep. and Sweden) using Distributed SCRUM, with a total of 20+ people in three teams. We learned some lessons on practical issues to look for on the setup, ramp-up, overhead and daily followups which could be quite interesting for other people to learn of. Presentation by Cristiano Sadun (TietoEnator) at Smidig 2007.
Last year, I exposed some of the initial lessons learned during the initial operation of two agile projects based on a mixed onshore-offshore model. One year after, the projects are concluded overall successfully, and some major additional lessons are learned: personalities and culture matter, hands-on management is as important as ever and agility concepts can be applied to an organization besides projects. Presentation by Cristiano Sadun (TietoEnator) at Smidig 2008.
Hubert Smits gives a hands-on overview of the activities that are involved in larger agile projects. Larger projects stretch out over more then a few months and have more then a single team involved. Things get more complex when the teams are not collocated. Hubert has based the talk on his paper “Multi Level Planning for Agile Projects” and presents a practical implementation of the planning levels. The experience he uses in the presentation is taken from his work as an agile coach for Rally Software Development, which brings him to projects with teams scattered across the globe: the US, Europe, Middle East and Far East.
In this presentation filmed during Agile 2008, Wes Williams and Mike Stout share their recent experience with a large distributed team, the planning hurdles they encountered and how they passed them, and their recommendation: avoid large distributed teams. Wes Williams has been a developer since 1993, works at Sabre Holding since 2001 and has been an Agile Coach and mentor on several projects since 2003. Mike Stout is an Agile Coach, Mentor and Trainer that works at Sabre. He has 18 years of experience in the IT industry spanning many aspects of software development.