Has anyone ever heard of the idea of the qa resource creating requirements for a product. I'm used to working in environments where requirements are provided to QA and QA provides "test response" asking clarifying questions... etc.
Is this happening in your place of work? If so do you have a dedicated BA team? If the answer is Yes - what is their responsibility if they're not writing requirements?
Life should NOT be a trip to the grave with the intention of arriving safely in an cool and well preserved body, but rather to skid in, chocolate in one hand, beer in the other, body wrecked, totally worn out and screaming WOO HOO what a ride!
Our US colleagues include a Business Analyst reporting to QA next to the "standard" Project Business Analyst in the requirement definition meetings. It has to be an SME as otherwise it doesn't really make sense I think.
We in Europe rely on requirement documentation to base first reviews upon frequenly during the define phase. We get the BA's to document what's been discussed and we read through it following ambiguity review guidelines + own functional knowledge. Works as well.
Of course this conclusion is also based on the facts that we're smaller and have a lot less budget. (i.e. 1 dedicated EU QA resource vs. 30 QA FTE's and 50 QA contractors in the US... *harrumph*
It might be a wise idea to include a QA resource in the requirement definition phase as long as you can afford it and as long as the person is an SME (and thus adds value to the discussions instead of lenghtening them with rather "stupid" questions...