Ard is a software tester from the Netherlands and is working for OrangeCrest. He calls himself a Qualisopher which stands for someone “who loves truth and wisdom and at the same time is decisive to improve man and his environment”. This means he is interested in the world around us, to see what he can learn and subsequently apply in software testing. That is one of the reasons why Ard tells stories in books and at (test) conferences such as EuroStar, Expo:QA, TestWarez, TestingCup, Romanian Testing Conference. Besides working in IT he is also active as a sport (volleyball) coach and chair of the music school in his town.
From experience, we know that Scrum teams are very focused on delivering something new and exciting. All of that is to create new value that all our customers are eagerly waiting for (or so we hope). As testers, we also know that there is a threat, such as the loss of the current value, as a result of all these new developments. Something that we already explored during the workshop RiskStorming that was part of the Sanae conference last year. But we want to take one step further: we as testers need to be able to monitor the (current) quality of our product. You might think, „Isn’t that done through regression testing?“ That’s not what we mean! There is so much more that should have our attention (and the attention of the entire organization). After all, everyone is responsible for quality.
In Ard’s workshop, we want to focus on three important aspects of monitoring the quality of the product for your organization: First, we will address the question: What are the expectations regarding the quality of the systems and the product in your organization? How do you ensure that the process you initiate is accepted and successfully implemented within your organization, with your stakeholders, your Product Owner, and your team? How do you ensure that you also monitor and evaluate those expectations? Here, you will look more into the Ops side of DevOps. We offer you a workshop where you will learn to look beyond the user stories of your sprint and beyond your role as a tester, so that you can take on a coaching role in maintaining the quality of the systems. Together, we will discuss how to get the people around you on board with this approach by speaking a language that everyone understands.