From the Editors: Developers, tools on same agile page



Email    print   
January 15, 2010 —  (Page 1 of 2)
The growth of agile development practices has turned the software development life cycle on its ear.

As the special report in this issue spells out, the way requirements are gathered has changed. In agile shops, no longer do business analysts spend months working with the customer to develop a huge requirements document that can only be changed at great cost. Agile processes demand that practitioners accept, even embrace, changing requirements throughout the project’s life.

The way testing is done has changed. No longer do QA teams wait for a completed project to run their tests, when finding defects is most costly. Programmers working in agile environments are using tests to drive development, performing unit tests and functional tests as they go.

The way code is built has changed. No longer are overnight batches run so that development teams must spend half their morning deciphering build reports. Continuous integration has become the coin of the agile realm.

Even the way code is written has changed. Developers are working more collaboratively than ever—even those separated by great geographic distances—to produce working code under shorter iterations.

So, too, the tools development managers and their teams use to create software have changed. Many ALM tool suites now include critical project management elements for tracking work and assets. The development environments programmers use are now including more social elements such as wikis, worker profiles, message boards and the like. Testing and build tools are evolving to meet the changing needs of developers producing pieces of projects that must work with other elements, and be changed as needed without “breaking” the software.

For years, we’ve been chronicling the disconnect between developers and tool makers. Developers say they just need help porting an application to a different platform, for example, while tool makers try to foist a methodology upon them that just so happens to be the foundation for their products. This time, it seems, the tool makers are getting it right. They seem to be listening to users rather than leading them down a path they might not want to travel.



Related Search Term(s): agile, XML

Pages 1 2 


Share this link: http://sdt.bz/34050
 
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