Measure it or it didn't happen

What I learned about quality KPIs over the last 5 years in testing

In order to improve quality, we have to find the right KPIs to measure progress

In order to improve quality, we have to find a way to measure progress. Also managers love KPIs. My experience started counting the tests executed vs the test failed. Since these numbers are far away both from the user value and from the health state of the product itself, I deemed them as irrelevant.

Next I started counting the bugs opened and closed per sprint. It had couple of downsides: its too simplistic and its’ easy to manipulate. 

I wanted less subjectivity and a more granular approach. From the tech side, I tried the mean between bug creation on release on live, downtimes, count of post mortems. From the user side, the number of ’non-issues’ was quite interesting. 

Let me take you on a KPI journey throught the metrics I tried, that worked and didn’t work for us and how I assessed them. I hope  some of them will help you as well.

Related Sessions

  • Tutorial
  • Keynote
  • Talk
  • Workshop
  • Combo
  • Bonus
  • Active
  • Social

Full-Day Tutorial (6-hour Workshop)


Test Management in Agile

Equipment required


14:45-14:55 Room F3 - Track 3: Talks

T-Shaped Testing or How to Crucify Your Co-Workers


14:25-14:35 Room F3 - Track 3: Talks

The power of demo

30-min New Voice Talk

16:10-16:40 Room F1 - Track 1: Talks

Using 8D approach to develop product team

Equipment required

If you like the Agile Testing Days Conference you might also like: