Rethinking the software development lifecycle (07 Jul 2005)
Meanwhile, developers wrestle with filling in the requirements gaps because the business has been unable to precisely and unambiguously specify what they want, and no effort has been spent on defining them accurately. The unrealistic timelines and budgets will ultimately mean that numerous critical functions will have to wait until future releases.
Beta testing then shows that end users donít get it, leading to endless back-peddling as the development team struggle to figure out why and how to fix it.
Time, money and technology have all been thrown at the problem, and things arenít changing. Techniques like Extreme Programming and Agile development methodologies wonít help either. Without the right blueprint, all these methods do is let you deliver poor technology, quicker than before.Add this article to Del.icio.us