Study finds 268% higher failure rates for Agile software projects

sir_pronoun@lemmy.world to Technology@lemmy.world – 472 points –
268% higher failure rates for Agile software projects
theregister.com

We all knew it

113

You are viewing a single comment

That's because they forgot the meaning of the word agility and want to apply the rules what ever the cost

And also because it's a comfortable cover up for any kind of money saving stupidity. We don't need proper requirements engineering, we're agile. We don't need an operations team we're doing an agile DevOps approach. We don't need frontend Devs, we're an agile team you all need to be full stack. I have often seen agility as an excuse to push more works towards the devs who aren't trained to do any of those tasks.

Also common problem is that still tons of people believe agile means unplanned. This definitely also contributes to projects failing that are just agile by name.

A lot of places seem to view it as "we just work from the backlog" with no requirements on when features are delivered, or their impacts on other parts of the project.

You still need a plan, goals and a timeline. Not just a bucket of stuff to get done.

Or, even worse, they want to apply some of the rules, cherry-picking bits and pieces of a framework without truly understanding it.