Quality Assurance Should be “Everybody’s Job”

3 thoughts on “Quality Assurance Should be “Everybody’s Job””

1. While I agree, that quality should be the responsibility of everyone from the managers, devs, technical writers, analysts, and testers, I disagree with the entire Assurance meme. We can’t assure anything, people who say that are trying to apply industrial memes and methods to a product that is always unpredictable, never exactly the same as last time (because each customer is unique), and let’s be honest, that most teams that separate development and testing into silos on products like this, where they are brought in N sprints late, are not only behind the quality curve, they are more behind than teams that have testers and other analysts involved for the duration of the product. Assurance of quality of software, is not a reasonable thing to expect from such an abstract industry. However, that doesn’t mean we shouldn’t be concerned about improving quality throughout the process, rather than waiting to ‘test it in at the end.’

   Reply

   1. Evidently, it is impossible to assure quality. We can do our best, but we can never be sure that it’s not going to fail. But that doesn’t mean that we don’t have to work for it and that we don’t have to try to achieve the highest quality in the software product we are building together. And that is what I tried to explain in this post: everyone involved in the development of an application should be involved in quality, so that be can have the best product fom the beginning. Although this doesn’t mean that the product is perfect.

      Reply

2. Just wanted to say the super work you are doing by providing clear info in your blogs. I just came to know about this website yesterday, one day before my exam.I spent about 2 – 3 hours reading all your articles, which made concepts crystal clear. Keep up the excellent work..!!

   Reply