Delivering Quality Despite Ever-Shorter Release Cycles
Across industries, software updates need to be rolled out increasingly fast, to close potential security gaps, implement new legal requirements or simply offer new functionality. Software development must, therefore, meet ever-shorter release cycles.
This trend has a significant impact on quality assurance, as we can no longer secure releases in dedicated testing and stabilization phases. Instead, we must ensure that our software systems meet the quality standards for a release at virtually any time. To achieve this, we conduct quality assurance measures (code analysis, testing, reviews) throughout the development process and in a highly change-driven manner: Continuous Quality Control.
In the workshop, you will see how Continuous Quality Control works and what pitfalls there are, especially in mature systems with few automated tests. Through customer examples and a live demo, you will learn how to:
- use change-driven static code analysis to avoid quality deficits and improve legacy systems,
- build and enhance automated test suites in a risk-driven manner using test gap analysis, and
- create transparency through reviews and retrospectives, establishing a shared quality awareness within your team.
Speakers
- Dr. Tobias Röhm heads the “Quality Control Services” team at CQSE, which helps our clients design and implement quality processes tailored to their individual use cases and integrate them into their daily development routines. Over the years, he has gained extensive experience in determining when certain quality assurance measures make sense—and when they don't.
- Tobias Wiese is a software developer and consultant for software quality at CQSE. As part of the "Quality Control Services" team, he works closely with our customers on their continuous quality assurance measures. This includes assisting with the configuration of static analyses and leading quality retrospectives.