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.