Our company has a database product used by over a dozen manufacturers, mainly in the consumer packaged good industry. The product has 3 'production' modules that impact order entry, invoicing, and financials. By next year or maybe 2002 that number could double. Our total install base is over 1,000. That could triple.

Because we have one product, there are a ton (and I'm not exaggerating) of database configuration options. The market is extremely competitive, so we often find ourselves needing to enhance the product.

I am trying to get our organization to beef up its internal Q/A efforts. Currently, after developers perform 'development' testing, the product goes to our customer support group, where it's pretty much 'Q/A by committee.' While our support group has done better than I ever would have dreamed, there's still not enough of a concentrated effort before our 'stuff' goes out the door.

Our upper management has resisted the idea of having a full-time QA person...claiming that for the type of creative mind to come up with testing scenarios, that type of person would get bored real quick. They've suggested a more 'aggressive' rotation schedule among our help desk support group, but I just don't see that improving enough.

Anyone who's been through this type of 'battle' is more than welcome to give me some insight.

Thanks,
Kevin