November 10 – 12, 2020

Online Edition!


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.

More Related Sessions

120-minute Workshop

10:25-12:25 Room D1+D2 - Track 6: Workshops

Product Owner's Dancing Guide to Writing Acceptance Tests

30-min New Voice Talk

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

3 questions that will help you create safe release planning

30-min New Voice Talk

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

Using 8D approach to develop product team

Equipment required

15-min Consensus Talk

15:25-15:40 Room F1 - Track 1: Talks

In sprint automation, build the culture.

If you like AgileTD you might also be interested in :

Your privacy matters

We use cookies to understand how you use our site and to give you the best experience on our website. If you continue to use this site we will assume that you are happy with it and accept our use of cookies, Privacy Policy and Terms of Use.