Quality advocate, working as product owner of SAP internal, program management tools. Current goal: Providing a seamless change management experience to all of our development teams.
I occasionally blog about the questions that occupy my mind regarding software quality, testing and development.
It is around 16:00 on a Friday afternoon and somebody from the other end of the office says out loud: “Who is working on fixing the API tests?” A silence, as thick as a morning fog, covers the entire floor. Nobody has done anything.
Slowly, all eyes are turn towards the tester. How could she allow this to happen? When the API tests fail, the deployment pipeline is broken. When the pipeline is broken, there can be no deployment to production. The hope of a work-free weekend is slipping away…
This could be the beginning of a fictional, admittedly a bit corny, story. Unfortunately, in my experience, this is not something unheard of in an Agile software development team, where quality is a whole-team effort and not just the tester’s obligation.
So, how do we create a clear action plan to avoid such drama scenes?
|Turning the Quality of Your Deployment Pipeline Into a Team Task||Agile Testing Days||November 2019|
|Turning the Quality of Your Deployment Pipeline Into a Team Task||TestBash Manchester||October 2019|
|Embracing Change: From Tester to Quality Coach||SwanseaCon||September 2019|
|Turning the Quality of Your Deployment Pipeline into a Team Task||Romanian Testing Conference||June 2019|
|Turning the Quality of Your Deployment Pipeline Into a Team Task||DevOpsDays Zürich||May 2019|