Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

QA vs Development Ratio [closed]

I am working as a software developer and I had a quarrel today with our QA team about the following:

How much the QA team members should exceed the number of developers that are working on the same product?

I know that this is not a question about how to program something, but I think that this question is pretty much connected to the software development. So I hope that this question will not be closed. Instead I will get answers from professional programmers that have a good experience on working in SW developing companies so that I could make a good statistics.

like image 216
Narek Avatar asked Sep 16 '09 18:09

Narek


People also ask

What's the right ratio between QA testers and developers?

“There is a 9:1 ratio of developers to testers in the job market,” Moise says, noting that this has improved from an earlier ratio of 11:1. “To include front end people, it's more like 13:1.” That means it's harder to hire QA testers that it used to be.

What is a good developer to tester ratio?

A separate informal poll of participants from 29 organisations in a conference session found the most common ratio was one tester to three developers: Minimum ratio was 0 testers to 1 developer. Maximum ratio was 1 tester to 30 developers. Most common ratio was 1 tester to 3 developers.

What percentage of a project should QA be?

The 10% rule is based on the budget value that you assign to QA. It's called as such because for most mid-sized projects, approximately 10% of the development budget would be assigned to QA testing.

Are QA paid less than developers?

In my career, I've seen many QAs earning more than the Development counterparts. And vice versa is also true in many cases. Pay depends on: Skills and skill level.


1 Answers

The answer is very subjective, but here is my experience.

At Microsoft we have a strong test development organization. That's a little different than traditional QA because we hire programmers to test and involve them in the process as early as the design phase. Their job is to test and especially to automate the testing for the product. In my experience, it takes the tester approximately as long to test and automate a feature as it does the developer to code and fix bugs in the product. That implies a 1:1 mapping. This is very similar to the rule of thumb that writing unit tests takes about as long as writing the code.

This mix will vary depending on several criteria:

  1. How much unit testing the developers are doing. The more they do, the less test needs to do.
  2. How much the developers are writing from scratch versus leveraging existing libraries. If there is a lot of pre-existing code in use and the testers need to verify that functionality as well, that sunk development cost must be taken into account for the 1:1 mapping.
  3. How dynamic the development is. If you are writing a UI where relatively small developer tweaks cause a large change to the testable surface, you will need more testers invovled.
  4. How mission critical the feature is. To write something like GMail where it is used casually and bugs can be tolerated and fixed in the field, fewer testers are needed. At the other extreme, if you are working on medical imaging devices, you need a lot more testing because bugs are hard to fix in the field and very bad when they happen.
like image 143
Steve Rowe Avatar answered Sep 21 '22 23:09

Steve Rowe