Testing : How do You Introduce a New Software QA Process?

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 appropriate. A lot
depends on team leads and managers, feedback to developers and good
communication is essential among customers, managers, developers, test
engineers and testers. Regardless the size of the company, the
greatest value for effort is in managing
requirement processes, where the goal is requirements that are clear,
complete and testable.