by Derk-Jan de Grood

Organizations have adopted Agile, Scrum, DevOps, CI/CD practices widely in order to increase their adaptivity. While doing so, they learn that it is impossible to speed up the IT deliverance without a trust in quality. Lean Agile and SAFe have the built-in quality as one of the core principles, but what does that mean for teams and organizations? In this presentation Derk -Jan will share the challenges he encounters in various organizations.

How do teams work and collaborate in order to release valuable increments, and what are approaches helping to increase the quality awareness? We will discuss the role of a tester on the team level, but also investigate how quality control is organized in scaled Agile settings where teams need to collaborate on a single increment.

How can you organize quality control on the release level? What types of releases can we distinguish and who is responsible? What do we see in practice and how should it work? In order to have the built-in quality, we need more than just good tests. We need a good strategy. Implementing this principle on various levels is challenging and has immense impact on the SDLC.

Take-aways: Understanding the built-in quality principle is a multi-level challenge that is gaining importance with the spread of Agile. Identification of the roles that are needed in order to organize testing in scaled Agile organizations is crucial. It is important to define the quality feedback loops and the impact for the development and business.

Speaker’s bio

Derk-Jan works for Squerist as Agile coach and Senior Test Manager. As a consultant he helps originations with their Agile Transformation embedding quality as a core principle in SDLC. He wrote several successful books on Software testing and Agile Transformations and he frequently writes for major publications. In 2014 he won the EuroSTAR testing excellence award. 

He is an experienced trainer, workshop host and a regular speaker at conferences. He spoke at Testing Uruguay, the Seoul Testing Conference, EXPO: QA, and the Agile Testing Days and STAR conferences in Europe and America. On his own blog he shares his knowledge and experience for everyone to benefit. You could also follow him on twitter.

We asked our keynote

What is the biggest obstacle or roadblock in SW testing that is slowing down improvement and innovation?

Good question. I think it is a mix between the fast developments of technologies in combination with legacy and workload. Many organizations are hold back and are struggling with their legacy. New technologies arise fast, and teams need to develop new skills and knowledge in order keep up. Often there is little time, since in most organizations there is a lot of pressure on delivering. That leaves the teams with little room for experimenting and innovation.

Will Manual Testing disappear in the next years?

Manual testing will not disappear completely, as there are still organization that have trouble with automating their tests and there will be a need for the experience with finding a solution in real live. But the days where a whole army of functional testers are doing a lot of manual tests is over. Automation will dominate, as will the monitoring in production. But canary releases aim to test the usage in production, and the users are the manual testers.

How software quality fits into DevOps?

Very well, I think. One of the principles of DevOps is that teams need to solve the production issues as well as develop new features. They get feedback on how their development work behaves in production. This helps to create the awareness about quality, the team learns on the go and takes efforts to improve the quality.

If you could choose a superpower, what would it be?

I would like to slow down the time, so I could do twice as much without having to rush through the day 😊

What’s your favorite hobby?

I like to play tennis, and I am quite serious into coffee. When I have the time, I roast my own beans.