It depends on the size of the organization and the risks involved. For large organizations with high-risk projects, a serious management buy-in is required and a formalized QA process is necessary. For medium size organizations with lower risk projects, management and organizational buy-in and a slower, step-by-step process is required. Generally speaking, QA processes should be balanced with productivity, in order to keep any bureaucracy from getting out of hand. For smaller groups or projects, an ad-hoc process is more advisable. Offcourse, the following goes without saying,
</Quote>"It all depends on team leads and managers. Becoz, they need to ensure feedback to developers and good communication is essential among customers, managers, developers, test engineers and testers".</UnQuote>
Regardless of the size of the company, the greatest value for effort should mainly be focussed on managing requirement processes, where the goal would be to ensure that the requirements are clear, complete and testable.
Please have a look at the following Links also.Hope it wud prove useful to you.
1. Invite experienced QAs
2. Discuss current state of your organisation. I am sure that you too must be among those who find a mess around them due to lack in organising the things. Reason : If you would have been in good shape then you must not have come for advice.
3. Evaluate feedbacks
4. Hire QAs providing best feedback and who have goals which can match with long term scenario of your organisation. Try to isolate feedbacks into short term and long term category.
5. make your selection
6. Get benefitted