Print

Agile development: Built to scale



David Rubinstein
Email
June 15, 2009 —  (Page 1 of 5)
The notion of agile development by now is well known for most every responsible CEO and CIO. With the economy stuck in low gear, organizations need to find ways to shorten development cycles and improve quality, all with the resources they already have on hand.

The Agile Manifesto, which spells out the ideas and practices for its implementation, was written in 2001, and in the eight ensuing years, many organizations have taken the first steps toward agile development. By now, many have had successful projects done by designated agile teams and have realized the cost savings and time-to-market benefits that agile espouses.

Now, these organizations want to reap bigger benefits by bringing agile out of its silos and into a wide deployment, across geographical locations, time zones and language barriers. Yet among the Manifesto’s 12 core principles are that “the most efficient and effective method of conveying information to and within a development team is face-to-face conversation,” and “business people and developers must work together daily throughout the project.” And there’s the one about “individuals and interactions over processes and tools.”

Those principles would almost seem to inhibit the adoption of agile processes in a large, distributed development organization. So how do organizations scale their agile practices to get a bigger payback?

Not to scale?
Robert Holler, CEO of agile project management software maker VersionOne, took a step back to answer that question. “There are challenges with scale. The problem’s not unique to agile or to software development,” he said. “Scaling is just tough. Sometimes agile gets a black eye for not scaling, but it’s more like, ‘Development doesn’t scale.’”

And Paul Hodgetts, lead consultant at Agile Logic, said that planning before embarking down the agile path is critical.

“There’s no way to get a big organization behind something like this without first thinking it through," he said. "‘Why are we doing this? How will we get everyone on board?’ You must show them a way to get from point A to point B that won’t make their lives miserable for the next 12–18 months.”



Related Search Term(s): agile

Pages 1 2 3 4 5 


Share this link: http://sdt.bz/33552
 
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
MAY 2012 PDF ISSUE

Need Back Issues?
DOWNLOAD HERE

Want to subscribe?


 
blogs tab
Slick...but who needs it?
compilr.com is a well-designed site and the folks behind it seem to have their heart in the right place. But...who needs it?
05/16/2012 12:45 PM EST

How to be a better software developer
Want to be a better developer? You won't get there by mastering an interesting language or learning a new set of APIs.
05/14/2012 12:18 PM EST

Wooing Galatea
Do yourself a favor and check out Galatea 2.2, a wonderful book by novelist Richard Powers.
05/12/2012 07:05 PM EST

The world as story
An artificial-intelligence system at Carnegie Mellon seeks to understand the world by making statements about it.
05/10/2012 06:39 AM EST

The Rise of the Brogrammer, or the Rise of the Sexist Programmer?
Women in Silicon Valley get vocal about sexist ads and campaigns that contribute to a tense work environment.
05/09/2012 03:14 PM EST

Retriever Communications Releases RADE3
Organizations concerned about the growing popularity of bring your own device to work policies may be comforted by the release of RADE3.
05/09/2012 11:46 AM EST

 

Events calendar tab
5/13/2012 to 5/18/2012
Boston
Lean-Kanban University

5/14/2012 to 5/18/2012
Denver
IDUG

5/23/2012 to 5/24/2012
Chicago
IEG

6/3/2012 to 6/7/2012
Orlando
IBM Rational

6/10/2012 to 6/15/2012
Las Vegas
SQE