Spreading the Agile Practice


Extending new processes beyond a single project team presents unique challenges


Email    print   
October 15, 2007 —  (Page 1 of 6)
Many organizations have begun to reap the benefits of agile development on their internal projects—shorter time-to-market, better quality software, more team productivity. Now, they want to know how to get those same advantages when doing agile development throughout a distributed team.

The answer? Get a Subversion code management system, a Webcam for whiteboard meetings and a speakerphone.

Of course, achieving agile success with a distributed team is quite a bit more complicated than that. But three principles—the ability to share plans, access the code from a single repository, and communicate effectively—form the cornerstones of spreading agile processes over disparate locations. Then, experts agree, the members of the team must be highly competent and working in an environment that fosters trust, provides a feedback structure, and gives visibility across business and development efforts.

One of the messages of agile is that it improves quality. Andrew Glover, president of the consulting firm Stelligent, said that’s the wrong message. “People don’t want to pay for quality. You say quality, people think QA, and QA has no money. Switch out ‘quality’ with ‘delivery speed,’ and people start buying it,” he said.

The core principles remain the same regardless of the specific agile process in use; although at the recent Agile 2007 conference, a number of consultants and developers mentioned that distributed agile development is most effective when Scrum is used in tandem with Extreme Programming, or XP. Scrum provides the overarching management structure, while XP is in place at the developer level where the coding is actually done.

Before any code can be written, though, it’s important to get everyone on the same page. Several experts suggested bringing the teams, or at least representatives of each team, together before the project begins in a sort of common architecture design meeting. “It’s important for teams to get familiar with each other before they are dispersed,” said Paul Hodgetts, CEO of agile consultant practice AgileLogic. “It’s costly, but the benefit offsets the cost and helps the project not drift off.”




Pages 1 2 3 4 5 6 


Share this link: http://sdt.bz/31263
 
Most Read Latest News Blog Resources

Add comment


Name*
Email*  
Country     


  • Comment
Loading




close
NEXT ARTICLE
Finding the right tool for the agile job
Experts emphasize that tools should bolster the agile process above all else Read More...
 
 
 
 
News on Monday
more>>
SharePoint Tech Report
more>>


   

 
 

Download Current Issue
FEBRUARY 2012 PDF ISSUE

Need Back Issues?
DOWNLOAD HERE

Want to subscribe?


 
blogs tab
Are you at risk for burnout?
Burnout is a severe problem and it can strike at any time. Here's how to tell if you are nearing the edge.
02/09/2012 02:16 PM EST

Agility, mom, and apple pie
If we're to evaluate the state-of-the-art in software development, we should start with the values espoused in the Agile Manifesto.
02/07/2012 11:57 AM EST

RIM woos developers with free tablet
How do you get more apps ported to the BlackBerry PlayBook? By giving every developer a free tablet, of course!
02/04/2012 01:57 PM EST

GitHire: Use Headhunters to Find Your Perfect Programmer
Are you a hiring manager tired of scouring the job boards? Check out this new service that will find 5 people interested in your jobs.
02/03/2012 12:17 PM EST

Facebook claims hacker cred
Facebook's SEC S-1 filing form includes a short essay on the Hacker Way by Mark Zuckerberg himself.
02/02/2012 08:26 AM EST

Ryan Dahl steps down
Ryan Dahl, creator of Node.js, steps back from his position as gatekeeper for the project.
02/01/2012 04:58 PM EST

 
Events calendar tab
2/13/2012 to 2/16/2012
Santa Clara
TechWeb

2/26/2012 to 2/29/2012
San Francisco
BZ Media

2/27/2012 to 3/2/2012
San Francisco
RSA

3/4/2012 to 3/7/2012
Las Vegas
IBM Tivoli

3/5/2012 to 3/9/2012
San Francisco
TechWeb