“If QA (Quality Assurance) is done then why do we need to perform QC
(Quality Control)?”, this thought may come to our mind some times and
looks a valid point too. This means if we have followed all the
pre-defined processes, policies and standards correctly and completely
then why do we need to perform a round of QC?
In my opinion QC is required after QA is done. While
in ‘QA’ we define the processes, policies, strategies, establish
standards, developing checklists etc. to be used and followed through
out the life cycle of a project. And while in QC we follow all those
defined processes, standards and policies to make sure that the project has been developed with high quality and at least meets customer’s expectations.
QA does not assure quality, rather it creates and ensures the
processes are being followed to assure quality. QC does not control
quality, rather it measures quality. QC measurement results can
be utilized to correct/modify QA processes which can be successfully
implemented in new projects as well.
Quality control activities are focused on the deliverable itself.
Quality assurance activities are focused on the processes used to create
the deliverable.
QA and QC are both powerful techniques which
can be used to ensure that the deliverables meet high quality
expectations of customers.
E.g.: we have to use an Issue tracking system to log
the bugs during testing a web application. QA would include defining
the standard for adding a bug and what all details should be there in a
bug, like summary of the issue, where it is observed, steps to reproduce
the bugs, screenshots etc. This is a process to create deliverable
‘bug–report’. When a bug is actually added in issue tracking system
based on these standards then that bug report is our deliverable.
Now, suppose some time at later stage of project we realize that
adding ‘probable root cause’ to the bug based on tester’s analysis would
provide some more insight to the Dev team, then we will update our
pre-defined process and finally it will be reflected in our bug reports
as well. This is how QC gives inputs to QA to further improve the QA.
I am very very like this post. It is so interesting and awesome
It’s never a guarantee that a product or service will have consistency and permanence when it comes to quality, even though quality assurance has been implemented. Thus, quality control is as important. QA and QC must co-exist for a business’ credibility and reputation to be thoroughly maintained.
The presence of quality assurance does not negate the necessity of quality control. They have different roles and they are both important for the business to grow. The combination of QC and QA molds deliverables to be good quality products. The business will surely benefit if both QA and QC have been utilize to provide quality products and/or services.
In purchasing products or hiring services, quality should be given importance. I agree with Clark, QA and QC should co-exist because both are beneficial in the establishment of the company’s credibility. With the presence of both, it is easier to meet the expectations of the paying customers.
-Barton Wilson