Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Your question seems to be ambiguous; I’ll reply to the sense which the rest of the answers don’t address: Should individuals doing testing report to non-QA managers? That <em>does</em> have an answer, and the answer is: “The QA department should be independent and powerful, it must not report to the development team, in fact, the head of QA should have veto power over releasing any software that doesn't meet muster.” “Top Five (Wrong) Reasons You Don't Have Testers” by Joel Spolsky (<a href="http://www.joelonsoftware.com/articles/fog0000000067.html" rel="nofollow noreferrer">http://www.joelonsoftware.com/articles/fog0000000067.html</a>)</p> <p>Having testers report to engineering rather than a single head of QA seems to be something that companies want to try every other re-org. It’s generally a sign that upper management wants to ship something on time rather than when it meets the criteria they supposedly support. It’s always a good way to avoid accountability for quality problems, even if that wasn’t the supposed intent. </p> <p>A strong, accountable head of QA is crucial even for bugs he never hears about: If I’m deciding whether to file, or dispute, a bug which I consider important, if I know that I the head of QA will back me up if it’s genuinely important, then I’ll probably do what’s right, even if engineering doesn’t want to fix the issue. If I know that the ultimate decision will be made by an engineering manager whose bonus is determined by meeting a schedule, and unaffected by quality, then I’ll be tempted to duck a pointless battle.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload