I've just been asked to advise management on organisational
quality issues. There seems general agreement that the test
labour content across most development projects is around 50%
(when people do honest accounting). The central organisational
issue, then, is who does that 50% and how do we manage it?
Management are especially eager to learn good
answers to the following questions:
- What is the best tester to developer ratio?
- Who should QA report to?
- How skilled should "testers" be? And how do you hire them, keep them, and motivate them?
As detailed in the References section below, I've done a first
cut at googling for resources that might help me answer
these questions. If you know of other good resources, please
let us know.
Here's what we currently do:
- We have roughly one tester per ten developers.
- QA is part of and reports to Development. Most development project teams have a QA resource from day one in the project.
- Most of our "testers" have decent programming skills: they ensure requirements and designs are testable, design test strategies, write test plans, write test automation harnesses, and so on.
How do you do it?
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||