Cost Effective Quality Assurance Management


I want to discuss with you the existing use of QA applications, identify the problems current by being experienced during the implementation of our QA Program, and introduce you some effective approaches.

In the context of quality assurance, quality is not a quantity of which one can have differing amounts. It is either present or absent. I find it easiest to define quality as meeting requirements. If mutually, by BJ and Client, established performance criteria are met, all parties are satisfied, and the task has been accomplished successfully. Failure to do so means failure to meet the requirements.

Hence quality assurance might better be termed requirement assurance.

Establishing the requirements for processes is a key step in ensuring that the outcome will meet expectations. Unless the requirements can be quantified, they cannot be measured and one cannot know whether they have been met. So, precise measurement of parameters relating to the output could provide an early warning of failure. (Later I will tell you more detailed about this)

Some have looked upon the application of QA principles as a ‘checking’ activity, and the consequences of this that the QA has become burden rather than a bonus.
Not being integrated into the operating activity QA becomes a heavy function which affects both productivity and profitability; and at the opposite, the system integrated with QA provides a hidden benefit. Quality assurance routines can and should be extended beyond the walls of my office. [pic]
The figure shows, that unless the right amount of reasonable degree of QA & QC is activated there may be overkill, wasted time and money, and often confusion. And worse, people will believe that QA can do no good at all. Lack of benefit from QA is an outcome of poor understanding, and improper applications. Another factor killing the benefit from QA is the attitude of management NOT to expend time and funds in what, at...