Blog Stats
  • Posts - 84
  • Articles - 0
  • Comments - 36
  • Trackbacks - 2

 

<< Why You Should be Verifying Your Javascript (JSLint) | Home | Frankenserver - Part 1 >>

The Trouble With Agile

When a customer sponsors a software development project they want to know two things: how much will the project cost and when will the project be finished. The trouble with agile is that it cannot answer either of these questions with any degree of confidence...

Read the full article

 

Print posted @ Wednesday, May 13, 2009 9:10 PM

Feedback

# re: The Trouble With Agile

Gravatar It's actually not a problem with agile, it's a problem with software development. I've never had much success using traditional software development methodologies. Even if I spend days, weeks or months gathering and analyzing requirements, once the customer changes something, some or all of that time, might be irrelevant. Jeffrey Palermo calls it "The Lie We Can Both Live With". Give them a range where if I go over, I can live with eating it and the high end of the range is something the customer can live with.
Just a thought.
~Lee 5/13/2009 11:12 PM | Lee Brandt

# re: The Trouble With Agile

Gravatar These are also problems with "traditional" methodologies. How many of those projects go over budget and miss deadlines? I've heard the number is as high as 80% (can't remember where I heard that though). Certainly most that I've seen or worked on have had this happen. With that in mind how is Agile any different? The only thing is that you'd be upfront with the client on both accounts instead of backing them into it. 5/16/2009 8:05 AM | Donald Belcham

# re: The Trouble With Agile

Gravatar From the customers perspective waterfall seems safer, because they have a guaranteed timeframe, budget and scope. They pay heavily for this illusionary guarantee (in time for BDUF as well as the vendor's margin to cover risk). 5/16/2009 5:44 PM | Liam McLennan
Post a comment





 

 

 

Copyright © Liam McLennan