Hello,
Originally, it was explained to us as a best practice to set up a QA system that would closely mimick production. One productive client in production would mean one productive client in QA.
Furthermore, the original intent of QA was to be used to perform an end-to-end test of a "fully" delivered solution (say as close to done as reasonable) when used for projects. It was not architected to handle a high degree of change that would come from a solution that may be 30-50% delivered for example (risks of frequent re-start etc).
We are receiving challenges to the original approach to QA, and I would like to understand how you are handling your QA system, it's client strategy, and it's purpose. Your insight would be very much appreciated.
Thank you,
John
Edited by: John Klaassen on Mar 18, 2008 8:22 PM