Even though it has now been 17 years since the agile manifesto was written, many teams are still challenged with the transformation. Often the focus is so much on getting the method right; the right ceremonies, the right roles and the right artefacts that the team forget the most important thing – WHY they are taking the agile journey.

The focus is not on building quality in and delivering working software continuously during the iteration – one of the core principles of agile, testing is not an integrated part of the way of working. These agile transformation failures prevent teams from getting the maximum value out of the agile way of working.

Failing to create a mindset and environment where quality is built-in continuously and testing is an integrated part of the development lifecycle are risks not only to quality in classical terms but also to the core agile principle of delivering working software of value to the customer. Gitte will look at some challenges of an agile transition seen through a testers’ eyes and give inspiration to practical initiatives: proactively using the testers toolbox to gain a better understanding of the user’s needs, getting tests integrated in the daily work rather than late in the sprint, and introducing test automation.


  1. Use your testing toolbox to support a better understanding of the users need
  2. Ownership of quality - the team, not the tester
  3. idea on how to get started with automation when having a large existing manuel regression test suite