Keynote Speaker

Rik Marselis is Principal Quality Consultant at Sogeti in the Netherlands. He is a highly regarded presenter, trainer, author, consultant and coach who supported many organizations and people in improving their quality engineering & testing practice by providing useful tools & checklists, practical support and having in-depth discussions. His presentations are always appreciated for their liveliness, his ability to keep the talks serious but light, and his use of practical examples with humorous comparisons. 

Rik is an accredited trainer for TMAP, ISTQB and TPI certification training courses, but also he has created and delivered many bespoke workshops and training courses. For example, on quality engineering and on Intelligent Machines and DevOps testing. 

Rik is a fellow of Sogeti’s R&D network SogetiLabs. These R&D activities result in presentations, books, white-papers, articles, podcasts and blogs about IT in general and quality engineering in particular. In 2020 his latest book “Quality for DevOps teams” was presented. 

 

Title: The end of testing as we know it 

 

Why do we test? How do we test? Should we continue to test like we test today? 

 

In this presentation Rik Marselis challenges you on these questions. And he proposes that you start implementing quality engineering. 

 

Businesspeople today ask IT teams to deliver business value. And they want it fast. To continuously deliver IT systems at speed, with a focus on the business value, high-performance IT delivery teams (Agile / Scrum / DevOps) must integrate quality engineering in their way of working. 

 

Quality engineering is the new concept in achieving the right quality of IT systems. Testing only after an IT product was developed is an outdated approach. Built-in quality from the start is needed to guarantee business value in today’s IT delivery models. Quality engineering is about changes in skills, organization, automation and the relevant quality measures. 

 

By creating a quality engineering strategy IT people enable themselves and their stakeholders to create IT systems with the right quality at the right moment. And this way avoid to use testing at the end of the process to add some quality to the product when it’s already (too) late. 

 

Testing is still a very valuable activity, but only as an integrated part of your quality engineering strategy. This way testing changes from bringing bad news about quality to an enabler of creating the right quality.