Do Away With QA

  ProjectsAtWork  

More than ever, organizations are releasing software as soon as possible, skimping on Quality Assurance, squeezing testers, and pointing fingers when it all goes wrong. So let’s look at the top five reasons they should just do away with software QA completely.

Quality Assurance professionals are often the only defense we have in software development between utter disaster at worst and complete embarrassment at best. However, too many organizations don’t ever seem to learn the lesson that "quality is built in, not tested in.” So, with tongue-in-cheek, we have created a series that explores the top five reasons why we should just eliminate the software QA position.

If you work in software Quality Assurance, you may wonder from time-to-time why you chose a career characterized by disrespect, resentment, disappointment, over-work, and under-compensation. And that’s the happy part. If you're lucky, the gloom will only be broken by the sturm und drang of the occasional software release that ends in complete disaster.

Here are the top five reasons why we think that eliminating software quality assurance professionals entirely is perhaps the only solution, as argued in this and upcoming posts:

1. The demand for new code will always exceed the demand for quality code
2. To test the code of the smartest programmers, you must be even smarter
3. Managers need a …

Please log in or sign up below to read the rest of the article.