Member-only story
Challenge a Recent Study Claiming “268% higher failure rates for Agile Software Projects”
The reason is that most of those were practising fake Agile. Real Agile software projects, with robust automated end-to-end UI regression testing, achieve nearly 100% success rates and save both time and money.
I have come across posts on Reddit and LinkedIn referencing a study that claims “268% higher failure rates for Agile software projects,” but I have chosen to disregard them.
Today, I saw an article on the reputable site The Register and felt compelled to provide some clarification based on my ~20 years of experience in agile development (clients and my own).
Table of Contents:
· About the Study
· Why do Fake Agile Software Projects (without solid E2E Test Automation) fail?
∘ 1. “The benefits of specification”
∘ 2. “Agile causing delivery not to be on time”
∘ 3. Questioning The Agile Manifesto
· FAQ
∘ 1. Any additional information to support your view that Real Agile with E2E Test Automation guarantees success and is highly productive?
∘ 2. Any additional information to support your view that Fake Agile fails because of not doing E2E (UI) Test Automation?
∘ 3. We are doing serious unit testing; it shall be enough for Agile, right?
∘ 4. What is a quick way to identify Fake Agile?
∘ 5. I want to learn and do real Agile. What is the first step?
About the Study
The original source I could trace to is this article on Engprax. The study “consisting of 600 UK and US software engineers finds projects adopting…
