Print

A Disciplined Approach To Healthy Software


Experts offer up advice for making life-cycle management work


Email
June 1, 2007 —  (Page 1 of 6)
Watch out for trouble around handoffs. Apply agile ideas. Run your shop like a business. Don’t expect to change everything overnight.

That’s a high-level summary of the advice offered by analysts, consultants and tool makers when asked how best to manage large application development efforts, where dozens of team members work across disparate locations.

“Application life-cycle management has never been easy, or automatic,” said Upside Research analyst David Kelly. “It takes discipline and effort to put a strong ALM process in place, and the drive toward distributed development simply increases the challenge.”

To help development managers achieve that discipline, SD Times asked more than 15 experts to weigh in with best practices for seven stages of the application life cycle: requirements, architecture, code, build, test, deploy and maintain.

Some key themes emerged from their responses. First, while each stage of the life cycle focuses on a single activity, it is critical to define each stage in terms of its relationship to the other stages, the experts said. This idea is fundamental to the definition of ALM itself, said Forrester analyst Carey Schwaber. “ALM is any best practice that connects those stages.” The management of the application life cycle is about making sure the stages are in correspondence, she said.

“Don’t think of them as separate stages, but focus on the coordination [among them],” added CollabNet CEO Bill Portelli. Each stakeholder is involved in every stage, but the nature of their concerns differs, he said.

ALM IS AGILE
ALM isn’t about building software in one long sequential cycle, where one stage is completed before the next begins, the experts said. Ideas from agile programming, such as writing software in short stints, are central to ALM best practices, even for development teams that have not adopted officially agile methods such as Extreme Programming or Scrum.

“The serial way of working has been shown to be ineffective,” noted IBM practice leader for agile development Scott Ambler. A better approach is to do a little of each thing every single day: some analysis, some design, some coding, some testing and so forth, he said.




Pages 1 2 3 4 5 6 


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

Add comment


Name*
Email*  
Country     


  • Comment
Loading




close
NEXT ARTICLE
New York City to open Academy for Software Engineering
High school would give foundational education in technology 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
Why we leave
Ten reasons good workers leave their jobs, plus a few suggestions for retaining them.
05/22/2012 06:14 PM EST

Creation
To write better software, cultivate your ability to be creative.
05/19/2012 07:40 PM EST

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

 

Events calendar tab
6/3/2012 to 6/7/2012
Orlando
IBM Rational

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

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

6/11/2012 to 6/14/2012
Bellevue, Wash.
AMD

6/11/2012 to 6/14/2012
Orlando
Microsoft