Study highlights the devastating financial and business implications of software failures that build up in the backlog of CI test suites
While the adoption of continuous integration (CI) is on the rise, software engineering teams are unable to take a zero-tolerance approach to software failures, costing enterprise organizations billions annually, according to a quantitative study by Undo- Cambridge Judge Business School MBA project.
“Every company is a software company. The ability for engineering teams to deliver high quality software at velocity is the difference between companies that gain a competitive edge versus those that fall behind,” said Undo CEO Barry Morris. “The next phase of CI will be about making defect resolution bounded, efficient and less skills-dependent. Organizations that evolve with CI will be able to resolve bugs faster, accelerate software delivery and reduce engineering costs.”
The research concluded three key findings:
- Adoption of CI best practices is on the rise. 88% of enterprise software companies say they have adopted CI practices, compared to 70% in 2015.
- More than 50% of businesses surveyed report deploying new code changes & updates at least daily, with 35% reporting hourly deployments.
- Reproducing software failures is impeding delivery speed. 41% of respondents say getting the bug to reproduce is the biggest barrier to finding and fixing bugs faster; and 56% say they could release software 1-2 days faster if reproducing failures wasn’t an issue.
- Software engineers spend an average of 13 hours to fix a single software failure in their backlog.
- Failing tests cost the enterprise software market USD 61 billion annually. This equals 620 million developer hours a year wasted on debugging software failures.
Although CI adoption is becoming ubiquitous, test suites are still plagued by a growing backlog of failing tests. Failures in integration and automated tests cause bottlenecks in the development pipeline, and substantially increase engineering costs.
The study further suggests that reproducibility of failures is also a major blocker, finding that not being able to reproduce issues slows engineering teams down and prevents them from releasing software changes at pace.
To fully realize the benefits of CI, software failure replay offers a way out by enabling engineering teams to reproduce and fix software bugs faster. By eliminating the guesswork in defect diagnosis, development teams are able to accelerate Mean-Time-to-Resolution (MTTR) - resulting in considerable cost savings.