Ahhh... spoken like a true developer. Blame the QA department.

The problem with having a QA department is by definition, if they are a "department", they are not part of the development team. The only way testing is ever taken seriously is if the top architect spends his coding time writing test cases, instead implementing features, after all the architecture documents are put under ECO control. And let's hope the same architect believes in closed-loop validation (that is, instrument and measure your test coverage) instead of open-loop validation (write tests without actually measuring what code gets tested by it.)

You're assuming that places have QA departments. Those, in my experience, are the first thing to vanish.

This reminds me of the content editors vanishing for the newspapers and the drop in the quality of articles.

QA? Why bother? We're agile, so just push another release. ;)