We have 3186 guests and 8 members online
Home > Articles > Columns > Articles > Globally Distributed Development

Globally Distributed Development

E-mail
Written by Liz Barnett   
Tuesday, 08 July 2008 16:00

glob_dev1Welcome to the second issue of the Agile Journal. This month, we explore the many challenges Agile teams face in running globally distributed development projects.

Globally distributed development can include all/any of the following:

  • Teams with developers, testers, users and/or other team members working at more than one location.
  • Teams engaging with third-party partners -consultants, vendors, even customers - to deliver business applications.
  • Teams that must incorporate a number of different styles (cultural, technical, management, etc.) across their distributed locations.

 

Each of these types of distributed projects poses a new set of issues to the already challenging Agile team. Many teams include all three! In this issue, our contributors provide a range interesting perspectives and valuable practices for delivering globally distributed development projects.

I'll start the issue with some common scenarios that I see driving offshore Agile development projects (and no, that is not an oxymoron). Kevin Parker discusses the intensity of collaborating and communicating with a development team that spans all 24 hour time zones. Dean Leffingwell completes his "7+7 Agile Practices For Enterprise Agility" article with seven best practices that help achieve agility at the enterprise level. Ross Pettit presents an agile approach to managing distributed development that provides operational flexibility in even the most complex delivery programs. Brent Carlson shares his company's experiences for product development with an offshore partner. And Adam Finder offers both principles and best practices necessary to support an offshore Agile environment.

As always, keep your feedback coming! How do you run your distributed projects? What are your greatest challenges? We're always looking for input for future issue topics and themes, and for general areas of interest. Send your "Letters to the Editor" in the forum at AgileJournal.com.

Liz Barnett
Editor in Chief
editor@agilejournal.com

 

Comments (0)Add Comment


Write comment

You must be logged in to post a comment. Please register if you do not have an account yet.

busy
Last Updated on Tuesday, 21 April 2009 14:11
 

Agile Marketplace - Announcements and Special Offers

White Paper: Code Review IS an Agile Process!
Peer code review is one of the most effective ways to improve Software Quality – but is it Agile? Done correctly, it absolutely is. This white paper tells you how.
Download Today!

Virtual Conference: Collabnet Agile ALM
Stay current by attending CollabNet’s virtual conference, Agile ALM for Distributed Development, Thursday, April 15, from 7:30 am to 3:30 pm PDT. Free registration.
Register Today!

Webcast:  Moving Build and Code Quality Upstream
This interactive panel discussion moderated by Bob Aiello, Editor-in-Chief fo the CM Journal brings industry experts Anders Wallgren, CTO of Electric Cloud and Gwyn Fisher, CTO of Klocwork together for a candid discussion of the cost savings, productivity and quality benefits that can be achieved by stabilizing builds and code quality as early in the development cycle as possible.
Register Now!

Collabnet -TeamForge 5.3
CollabNet TeamForge 5.3 includes Dynamic Planning—providing flexibility to model release scope and timeline in a single view. Now, you can easily manipulate/adjust release data.
Download Your Free Trial

Requirements-based testing (RBT) can help to ensure comprehensive test coverage, reducing the risk of failure and improving software quality. This white paper details how application lifecycle management can be used to more effectively implement RBT processes, offering greater collaboration, traceability and control.can help you increase efficiency, reduce project risk, and improve overall software quality. Learn how MKS Integrity for application lifecycle management enables RBT, delivering full lifecycle traceability to help ensure that project requirements have complete test planning and execution coverage.
Download the Requirements-Based Testing whitepaper

PureCM –SCM for Agile Teams
PureCM helps you to manage development in short iterations: keeping track of changes, supporting automated builds and preserving frequent snapshots of your projects.
Get the free trial now