Joost van Wollingen & Erik Swets
Joost started his career at bol.com, which gave him the opportunity to learn and grow at one of the leading companies in Agile and DevOps in the Netherlands. Coming up through the ranks he has been a test engineer, multidisciplinary team member, scrum master, team lead & test architect. As a consultant with Xebia, he has helped clients with all sorts of testing and quality challenges. Currently, Joost is leading a team of software engineers in test at iptiQ, an insurtech startup. Throughout his career, Erik has helped companies to deliver software faster and at higher quality. Be it through applying practices like Behaviour Driven Development or Continuous Delivery, by architecting and implementing automated testing solutions or by building deployment automation solutions. With a background in economics, he is able to strike a good balance between business and IT.
Speech title: Progressing beyond Continuous Delivery

The world of software delivery is constantly evolving. Under the pressure of consumer expectations companies look to improve both their time to market as well as the quality of the software they deliver. Customers expect and demand a top-notch customer experience. It is no wonder that companies are looking for ways to roll out new software even faster, but also need to manage the risk of exposing their customers to software that is broken. Continuous delivery fixed the technical hurdles to ship your artifacts more quickly to production. So, where can we find further gains? When having the ability to ship very very fast, how do we avoid low-quality software for our users? In order to answer those questions, we have to look at a couple of aspects: how and when do we test our software, how do we roll this software out to our customers and how quickly can we identify potential issues once our customers use it. Front runners in this field, that already have continuous delivery in place, have turned to observability, traffic management, and user segmentation. An emerging term for these practices is Progressive Delivery. It was coined by James Governor and defines progressive delivery as: “Progressive delivery is continuous delivery with fine-grained control over the blast radius.” We will explore the four pillars of progressive delivery: automation, observability, traffic management, and user segmentation.  
Back to main page