OverOps surveyed over 600 engineering professionals to better understand the challenges they face in delivering high quality software at speed. This blog breaks down some of the key findings from the 2020 State of Software Quality Report.
TL;DR: Check out the findings from our 2020 State of Software Quality Survey.
In today’s software delivery pipeline, speed and stability are frequently at odds. The fast-paced business landscape has driven the need for increased development velocity – often at the expense of application quality. Engineering teams are thus challenged with the impossible task of keeping up with competitors without sacrificing the customer experience in the process.
Faced with this dilemma, some organizations opt for prioritizing speed over quality, while others double down on testing and observability in the hope of preventing critical issues in their live environment.
But which approach is the right one? Or is it possible to strike a balance between the two?
To answer these questions, we surveyed over 600 software development and delivery professionals and summarized the top takeaways in our 2020 State of Software Quality Report. Survey respondents represented a wide range of company sizes, industries and geographical locations.
Below we’ve highlighted a few of the biggest takeaways. Download and read the full report here, and don’t forget to join us for a webinar on June 18th where we’ll do a deeper dive into the key findings with software quality champion and CISQ Advisory Board Member Herb Krasner.
1. Speed vs. Quality Showdown: Engineering Teams Are Driven by Quality but Distracted by Speed
The overwhelming majority of engineering organizations (70%) say software quality trumps delivery speed, yet critical production issues persist. The survey found that despite most teams making quality a priority, a lack of processes, pressure to move fast and other factors hurt developer productivity and lead to over 50% of teams experiencing customer-impacting issues once or more per month.
2. The Modern Software Quality Ecosystem: Top Techniques, Tools & Metrics
From CI/CD and daily release schedules to feature flags and alerting, today’s engineering teams are using a broad ecosystem of cutting-edge technologies and practices. According to respondents, some of the top tools include manual testing (70%), automated testing (65%) and log management (62%). But failure to invest enough code analysis and observability could be causing software quality efforts to still fall short.
3. 2020 Roadmap: Automated Code Analysis Emerges as the Next Big Thing in Software Quality
Is this the decade automation will transform the way we see software quality? Survey results show that while engineering teams are continuing to invest in pipeline automation and containerized microservices, automated code analysis sees an uptick as an emerging technology. When asked about which tools participants plan to adopt in 2020, 37% said static code analysis and 28% said dynamic code analysis, putting these analysis tools at the top of the list.
The Biggest Takeaway? We Have a Long Way to Go.
The 2020 State of Software Quality Report shows just how much work there is to be done in striking a better balance between speed and quality. At the root of the problem is a misalignment between processes and resources with primary engineering and business goals. This is then compounded by failure to invest in the right tooling and culture that enables efficient error detection and resolution, regardless of where you are in the pipeline. To learn more about the findings and our recommendations for overcoming this hurdle, download the full report.