Distributed Agile and Off-sure Agile Resources

Off-shore agile, outsourcing agile teams, distributed agile, leveraging globalisation third world markets - or whatever it is you call it - creates additional process management work for teams. The question is whats the impact to business benefits, customer satisfaction, quality product, and healthy culture? Different clients i've coached have approached distributed agile product delivery in a variety of ways and yet they each encountered similar challenges that are worth keeping in mind: - Overcoming the distance to maintain good face-to-face communication flow - Establishing seamless infrastructure; environments, task management, knowledge management tools - Governing quality development and output - Customer satisfaction mindset Below are three interesting articles that explain well; their strategy, execution and learning by experience.

Martin Fowler of Thoughtworks shares his perspective on the Thoughtworks Bangalore off-shore agile services to their European and USA agile houses, and customers. http://www.martinfowler.com/articles/agileOffshore.html Martin Fowlers top learning list; - Use Continuous Integration to Avoid Integration Headaches - Have Each Site Send Ambassadors to the Other Sites - Use Contact Visits to build trust - Don't Underestimate the Culture Change - Use wikis to contain common information - Use Test Scripts to Help Understand the Requirements - Use Regular Builds to Get Feedback on Functionality - Use Regular Short Status Meetings - Use Short Iterations - Use an Iteration Planning Meeting that's Tailored for Remote Sites - When Moving a Code Base, Bug Fixing Makes a Good Start - Separate teams by functionality not activity Expect to need more documents - Get multiple communication modes working early - Costs and Benefits of Offshore Development

-------------------------- To better understand who has been doing it well and for a long time ive selected the below from Microsofts pool of off-shore agile articles. It's short, too the point and gives some practicle how tos. - agile practice trends - insight to the right tools i.e. integration - communication, communication, communication



And last but not least a nice checklist infographic to consider

attribution to QAT.com with this graphic