Tuesday, April 5, 2011

What is it with QA these days?

Here is a sad fact for you; the last time I worked for a company with a strong, independent and respected QA dept was over six years ago. That company was LowerMyBills, and they had a killer QA department which contributed greatly to the overall success of the product and company.

So what is it with QA these days and why are good QA people so hard to find and retain?

Some thoughts are that once a company has found a QA tester worth his/her salt, they hide them away and keep them captive with "golden handcuffs" so they will not be tempted to seek out greener pastures.

Another thought is that QA is often used as the incubator from which development is fed so you have a perpetual cycle of brain drain. Still another theory is that QA testers are not born, they are developed and that takes both time and effort, both of which are in often times in short supply in a fast moving company.

Regardless of what is truth and what is fiction, one thing is for certain, when you have a strong, independent and respected QA department within your organization, your company is able to accomplish amazing things. Without out one, your organization will be in perpetual firefighting mode as defects leak out into production and your clients unknowingly become your beta testers.

As a leader of an Operations team, I am repeatedly reminded of the pricelessness of a QA team who are not beholden to engineering or operations, and are free to be an unbiased proving ground for your product. The sad truth is that often organizations place QA under the direction of engineering, which frankly is just incestuous, or under the direction of operations, which is almost as bad.

What is worse, I have often times observed QA being hobbled either by misalignment within the organization, poor staffing or insufficient experience, pillaging from other departments and/or an unclear mandate regarding the importance of quality within the organization.

In my opinion (and the opinion of many others I have spoken with) QA must be free and independent and should report directly to a "C" level executive like a COO or CIO (not CTO) and should be held to stringent standards. Additionally, they should be given the ability to "pull the cord" and halt production in the event egregious quality issues are identified. Without these qualities, your QA department is at best little more than a rubber stamp and at worst, a scapegoat for all of your organization's ills.

I am interested to hear what others have experienced and what they have done to help solve this problem. I am also interested to hear your thoughts about how we, as IT professionals, can help guide young people into becoming QA tester and engineers instead of code jockeys.

In the end, QA may not be the sexiest job in IT, but I think you will agree that it is arguably the most important link in the chain and should be celebrated as such.


  1. I agree that QA is both very important and not easily done well. I need to do a better job myself as a developer with my own personal QA on what I build.

  2. Agreed, a good QA team is priceless. I would also agree that it's not a simple matter to build and keep a QA team. The major issue in my opinion is that QA is not valued as highly as the software developers. I personally feel that they are equals! As a development manager I need them to work to build a product and verify that is works as designed. It's a checks & balance thing.

    Sadly too many organizations delegate their QA to the end user. Which in the end is more costly, either in terms of hard cash or reputation.