3 ms·

QA is essential. How else do you know that you have built what you set out to built? Traditional manual QA is highly effective, so much so, that you can get hug

QA is essential. How else do you know that you have built what you set out to built? Traditional manual QA is highly effective, so much so, that you can get huge gains by automating it. QA occurs at many levels and it makes sense to have a dedicated QA team for each level. Generally, the QA team for a level should be the exact people who requested and/or approved the specific feature subject to QA, as they are in the best position to confirm or deny that the feature meets the specification, as they created and/or approved it.

pc86 11y ago
But you're talking about QA as a general process, not QA as is meant in the article: > Software engineers at Yahoo are no longer permitted to hand off their completed code to another team for cross checking. Dev Team A was giving a batch of code to Dev Team B to review. I agree that the business user/product owner/whatever should be reviewing everything in test prior to approval and in production after but I'm not sure that's the article means by QA.