Blog

QA metrics for managers: defects and developers

When running these metrics pay special attention to the fact how long it took to fix the defect and which step was most intense.
25 October 2013
Quality assurance
The article by Dmitry Tishchenko
Head of global business development at a1qa

In previous articles we discussed, how to define the quality rate, evaluate testers` capacity and covered bug description method. All these things concerned tester`s work, but a tester is the one who detects a bug, while a developer fixes it. So this time I would like to cover some bits of a DEVELOPER`s niche on the QA consulting map. Taking bug statics as a basis, I want to tell about the indexes that reflect developer`s work efficiency.

First one is about defect lifecycle continuity. The index comprises “defect processing period”, “defect fixing period” and some other elements.

When running these metrics pay special attention to the fact how long it took to fix the defect and which step was most intense. Remember to track the index changes and put them in to the diagram, like this one, for example.

Defect lifecycle

The method of data collection resembles the one I described in the first article of QA metrics for managers, when told about defects having status “functions as designed”.

When you start calculating, you`ll see that index increases due to the defect lifecycle longevity. Considerable can be observed on stages like processing, assigning and queuing.

The other one index is the percentage of Rejected bugs. Defect is considered to be rejected, when a tester gives it status of a non-fixed one after checking. That means that a cycle has to be renewed: report to a developer, re-fix, re-check. The time is actually wasted for additional communication. On large scale projects such things cause additional expenditures, which is quite tangible.

Having exercised multiple projects, I noticed that 10% is an acceptable value for the index; try to keep to that limit. It is better to calculate the index after every release, especially on a large scale project, when more than two builds is released per week.

Remember to add the index in every report, to keep the tester and developer teams informed. Doing this you stimulate the team members to bring down the index percentage and define the positive work dynamics.

More Posts

a1qa-articles
31 January 2023,
by a1qa
5 min read
Best of 2022 by executives: 8 most visited a1qa blog posts
Let’s look back and revisit the most visited a1qa articles of 2022!
Quality assurance
Test automation
qa-trends
12 January 2023,
by a1qa
4 min read
The future of software testing: top 4 impactful trends that will dominate in 2023
Consider the major industry trends for the upcoming year to know how to improve current QA strategies and stay ahead of the curve.
QA trends
Quality assurance
Test automation
test-automation
7 December 2022,
by Dileep Marway
3 min read
Release at pace with test automation: What, why, and how to measure success?
An automation-first approach is key to enhancing testing capabilities and increasing overall operational efficiency. However, I would suggest justifying its implementation, so that it can deliver the promised value.
Quality assurance
Test automation
what-is-a-culture-of-happiness
2 December 2022,
by Dileep Marway
3 min read
What is a сulture of happiness for a QA company?
Great culture drives employee engagement and satisfaction, contributes to an impressive work output, and improves organisational performance. But how do we build a culture of happiness? In this blog, I will share more on the answer to this.
Quality assurance
agile-qa
30 November 2022,
by Dileep Marway
3 min read
Agile QA – what is needed for greater flexibility and speed?
What should your QA team focus on to become truly agile, enable quality at speed, and contribute to lasting performance improvement? In addition to introducing test automation, I suggest considering shared responsibility for software soundness.
Agile
Quality assurance
interview-with-dileep
28 November 2022,
by a1qa
9 min read
Interview with Dileep Marway on a series of articles “Agility and speed: Supercharging your business strategies with QA”
We cooperated with the VP of Engineering and Quality at SHL to present you with a series of his blog posts on: culture of happiness, test automation, and Agile-driven QA. Happy reading!
Agile
Quality assurance
Software lifecycle QA
Test automation
optimizing-budget-with-qa
31 October 2022,
by a1qa
4 min read
Optimizing telecom budgets with QA outsourcing: everything you need to know. Part 2 
Welcome to Part 2 of our blog on QA outsourcing and optimizing telecom budget with it. Let’s delve deeper into the topic!
QA trends
Quality assurance
optimizing-budget-with-qa
27 October 2022,
by a1qa
4 min read
Optimizing telecom budgets with QA outsourcing: everything you need to know. Part 1
Learn how to optimize telecom’s quality assurance expenses by relying on a trusted QA partner.
QA trends
Quality assurance
qa-trends-in-telecom
30 September 2022,
by a1qa
5 min read
4 telecom trends for 2023 and how to painlessly implement them with QA
It’s time to explore the telecom trends for the upcoming year. Let’s look at them together and also see the value that QA brings for their smooth deployment.
Cybersecurity testing
Migration testing
QA trends
Quality assurance
Test automation

Get in touch

Please fill in the required field.
Email address seems invalid.
Please fill in the required field.
We use cookies on our website to improve its functionality and to enhance your user experience. We also use cookies for analytics. If you continue to browse this website, we will assume you agree that we can place cookies on your device. For more details, please read our Privacy and Cookies Policy.