Agile software development methods are being adopted widely, but they could cause confusion and result in higher costs, suggests recent research by US analyst firm Voke.
The Agile development movement proposes iterative and incremental methodologies that can get working systems to users quickly, but the rreport entitled “Market Snapshot: Agile Realities” warns of a downside. Comparing the experiences of over 200 companies, with the majority finding the transition to Agile “confusing, hard, or slow”. The cost of rework for Agile projects is also considerably higher that non-Agile counterparts.
Voke outlines something it calls the “Agile Dilemma” – a realisation that the practice brings both benefits and drawbacks, and might not be appropriate for all organizations or projects.
Out of over 200 participants, 64 percent said that switching to Agile Development was harder than it initially seemed. Forty percent of respondents did not identify an obvious benefit to the practice. Out of those who did, 14 percent thought it resulted in faster releases, and 13 percent – that it created more feedback. Seven percent of participants noted that Agile developers were happier due to reduced future planning and documentation.
According to Voke, since the global financial crisis of 2008, the average cost of software projects has seen a sharp rise, even though developer teams have become smaller and the deadlines tighter. Meanwhile, the risk of software failures associated with Agile Development has remained high.
The number of high-profile software glitches in the news is as high as ever, doing serious damage to the reputation of companies like RIM and RBS Group. The quality of the code is an important issue, which is often overlooked during rushed development. Research calls the associated price of reworking the code the “hidden cost” of Agile practices.
“While many people assume that Agile is faster, better, and cheaper, actual results vary greatly. Many organizations are diving into the Agile movement without a clear understanding of what it is, and what the consequences of adoption may be. They may not realize that today’s solutions are tomorrow’s problems,” said Theresa Lanowitz, lead analyst at Voke.
The report provides details on the types of software projects that are more likely to succeed with Agile. These include smaller projects, custom-development projects and Web applications, along with projects that used Agile “only when appropriate and by experienced teams”.
Voke also suggests that Agile might be a passing fad, a developer rebellion against unwanted paperwork, or just an opportunity to sell additional services including certification and training.
Is Microsoft Office your friend? Take our quiz!
'Unexpected behaviour' of Waymo's self-driving vehicles triggers investigation by American safety regulators
Group of TikTok creators in the United States attempt to block recent law that will…
Hundreds of climate activists clashed with police outside Tesla gigafactory near Berlin, in protest over…
AI very much the focus at Google's annual developer conference, including Google Gemini and a…
Co-founder and chief scientist Ilya Sutskever to leave OpenAI, after role in Sam Altman's firing…
Electric vehicles made in China are now subject to a 100 percent tariff, to protect…
View Comments
In my view, the report mis-represents Agile. Many, although I agree not all, organisations take a disciplined approach including continuous integration and testing, business value assessment and governance. Many organisations are getting significant benefits from Agile (Standish CHAOS report). See also our blog post Alternative Realities.
Of course Agile fails - people that think "less is more" and "faster is better" are always surprised at the mess they leave behind. Agile is a contractors dream - fast and furious development, no ability to maintain the product required. If it fails - well, there is no paper tail leading to your door and that are plenty of 'other' unnamed people to blame for it all.
According to Voke
Twenty-eight percent (28%) report success with Agile.
"The Agile movement is designed to sell services"
"The quality of the code is an important issue, which is often overlooked during rushed development."
That just says that they don't understand agile development practises. Agile != rushed, you can have rushed code that is rubbish using any development methodology. The fact that there was rushed development going on implies immovable deadlines arbitarily imposed on developers (Doesn't sound very agile to me).
It doesn't matter what development methodology you use, if you have an immovable deadline that doesn't give you enough time to do the work you have you get rushed and bad code.