I don't see ratio as a good measure. How much work are you pumping out? What level of testing are you after. Do you want your developers to own testing?
If you choose the wrong testing strategy your likely to need more testers than developers as your product grows.
What do you expect from your testers? I could spend full time on a project with zero developers (there were actually 2), because I was spending all my time learning the system to track down some very elusive bugs.
Yeah, I am starting to think the same thing, maybe the ratio is less interesting, its more about product complexity and the amount of new features/changes delivered that ultimately determine the appropriate number of testers.
Even so, still curious to see what ratios others do have. So far it seems to average out to about the same as we have on my team from the few answers I've gotten.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I don't see ratio as a good measure. How much work are you pumping out? What level of testing are you after. Do you want your developers to own testing?
If you choose the wrong testing strategy your likely to need more testers than developers as your product grows.
What do you expect from your testers? I could spend full time on a project with zero developers (there were actually 2), because I was spending all my time learning the system to track down some very elusive bugs.
Thanks for your input Jesse.
Yeah, I am starting to think the same thing, maybe the ratio is less interesting, its more about product complexity and the amount of new features/changes delivered that ultimately determine the appropriate number of testers.
Even so, still curious to see what ratios others do have. So far it seems to average out to about the same as we have on my team from the few answers I've gotten.