Quality assurance in agile projects

Many agile teams believe that testing begins after coding - a fatal mistake. Quality assurance must start with the initial requirements, otherwise there will be gaps between automated unit tests and technical acceptance testing that can hardly be closed later. What is crucial is a conscious test analysis with risk classification and the continuous delivery of small increments instead of last-minute chaos before the end of the sprint. Only when everyone involved looks at user stories with tester glasses can real software quality be achieved right from the start.

Podcast Episode: Quality assurance in agile projects

In this podcast episode, agile testing expert Christian Mercier focuses on quality assurance in agile projects. Key aspects of ensuring software quality are discussed, as well as team communication and how to find the right balance. Common pitfalls will be explained and how they can be avoided. The role of artificial intelligence (AI) in improving quality assurance in agile projects will also be highlighted.

“It doesn’t happen by talking. Software has to be created at some point.” - Christian Mercier

Christian has been working in the financial services sector since 1996 and has gained extensive experience in branch business, CRM, strategy and IT. He has worked for savings banks, Landesbanken and group banks. He acquired his expertise in the classic project business. However, he now concentrates almost exclusively on agile methods. As an expert in quality assurance, Christian Mercier supports his clients in implementing high-quality requirements. Long before the topic of agility was on everyone’s lips, he was already working on methods to create transparency and optimize project communication. He attaches great importance to usability and system maturity. He is particularly interested in setting up tests in an agile way and carrying them out in an agile environment.

Highlights der Episode

• Talking before coding: The most important phase is the early conversation about requirements and testability.
• Everyone wears tester glasses: Quality is not created in isolation, but through a common understanding within the team.
• Static analyses and reviews are quick wins and create robustness before code is executed.
• Do not check everything in at the end of the sprint: Early, frequent deliveries allow for quick feedback and correction.
• Choose the test scope consciously: Don’t test everything, prioritize based on risk and omit transparently.