Guest View: The half-agile path leads nowhere



Email    print   
March 15, 2010 —  (Page 1 of 3)
Almost a decade has passed since much of the influential early material on agile software development was published. In that time, the agile movement has gone from being perceived as undisciplined, impractical and scary, to being front and center on the agenda of a growing number of mainstream IT executives.

Today, there's hardly an IT organization on the planet that isn't using, adopting or thinking about trying an agile approach. There are many things to celebrate about this progression, not least of which is that, as an industry, we are learning a lot about new and better ways to build software.

But where mainstream agile adoption is concerned, we are massively under-delivering on the potential of the Agile movement and, by association, on our potential as software professionals. We are failing to advance good agile engineering practices at anywhere near the pace that we are advancing agile planning practices.

Currently, the typical approach to agile adoption within a large mainstream IT organization starts with introducing some flavor of iterative planning and daily stand-up meetings. Though it's never straightforward, most business and IT stakeholders will eventually grok the value of these practices, and work at them until they achieve some degree of successful implementation.

In contrast, it's often much harder for organizations that are new to agile software development to understand the value of engineering practices like pair programming, test-driven development, refactoring and continuous integration. So simply trying (let alone implementing) these practices is often de-prioritized to a later date, which often never arrives.

There are many people in the industry who will argue that it doesn't matter. They will say that for most organizations, iterative planning is a huge step forward and they should be happy with such an achievement. I do have some sympathy for this view, considering I have seen how hard it is for most organizations to get that far. However, this does not change the simple fact that when we do software development, we end up with software. And the better designed and simpler that software is, the easier it will be to change. If you believe in “responding to change over following a plan,” you will agree that’s pretty important.



Related Search Term(s): agile

Pages 1 2 3 


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