Quality assurance vs. quality control

5 minutes 5 Questions

Quality assurance (QA) and quality control (QC) are two distinct but complementary components of project quality management that ensure deliverables meet stakeholder expectations and requirements. Quality Assurance is a proactive, process-oriented approach that focuses on preventing defects before they occur. QA involves establishing standards, procedures, and methodologies that guide how project work should be performed. It encompasses activities such as process audits, documentation reviews, and implementing best practices throughout the project lifecycle. QA answers the question: Are we using the right processes? The goal is to build quality into the project from the start by ensuring team members follow established procedures and standards consistently. Examples include conducting process improvement initiatives, performing compliance audits, and reviewing project documentation for adherence to organizational standards. Quality Control is a reactive, product-oriented approach that focuses on identifying defects in completed deliverables. QC involves inspecting, testing, and measuring project outputs to verify they meet specified requirements and acceptance criteria. It answers the question: Does the deliverable meet our standards? QC activities include peer reviews, testing procedures, inspections, and statistical sampling. When defects are discovered, corrective actions are implemented to address the issues. The key differences between QA and QC include their timing and focus. QA occurs throughout the project during process execution, while QC typically happens after deliverables are produced. QA is preventive in nature, aiming to stop problems before they happen, whereas QC is detective, finding problems that already exist. Both QA and QC are essential for successful project delivery. QA ensures the team follows proper processes, reducing the likelihood of defects, while QC validates that final outputs conform to requirements. Together, they form a comprehensive quality management strategy that helps projects deliver value and satisfy stakeholder expectations while minimizing rework and waste.

Quality Assurance vs. Quality Control: A Complete Guide for CompTIA Project+

Why This Topic Is Important

Understanding the distinction between Quality Assurance (QA) and Quality Control (QC) is fundamental for project managers. This concept appears frequently on the CompTIA Project+ exam because it tests your ability to implement proper quality management processes. Confusing these two terms can lead to incorrect project planning and execution in real-world scenarios, and wrong answers on your certification exam.

What Is Quality Assurance (QA)?

Quality Assurance is a proactive, process-oriented approach to quality management. It focuses on preventing defects before they occur by establishing proper processes, standards, and procedures.

Key characteristics of QA:
• Focuses on the process used to create deliverables
• Preventive in nature
• Occurs throughout the entire project lifecycle
• Involves audits, process documentation, and continuous improvement
• Asks the question: Are we using the right processes?

What Is Quality Control (QC)?

Quality Control is a reactive, product-oriented approach to quality management. It focuses on identifying defects in the finished product or deliverable through inspection and testing.

Key characteristics of QC:
• Focuses on the product or deliverable itself
• Detective in nature
• Occurs after work is completed
• Involves inspections, testing, reviews, and measurements
• Asks the question: Does this deliverable meet requirements?

How They Work Together

QA and QC are complementary processes within the overall quality management framework:

1. QA establishes the foundation - Creating checklists, templates, procedures, and standards
2. Work is performed - Following the established QA processes
3. QC validates the output - Testing and inspecting deliverables against requirements
4. Feedback loop - QC findings may lead to QA process improvements

Quick Comparison Table

Quality Assurance:
• Process-focused
• Preventive
• Ongoing throughout project
• Examples: Audits, process documentation, training, templates

Quality Control:
• Product-focused
• Detective
• After deliverable completion
• Examples: Testing, inspections, peer reviews, measurements

Exam Tips: Answering Questions on QA vs. QC

1. Look for keywords in the question:
• QA keywords: process, prevent, audit, procedure, standard, continuous improvement
• QC keywords: inspect, test, measure, review, verify, defect identification

2. Remember the timing:
• If the question mentions activities happening before or during work creation to establish proper methods, think QA
• If the question mentions activities happening after work is completed to check results, think QC

3. Focus on the intent:
• Preventing problems = QA
• Finding problems = QC

4. Use this memory trick:
• QA = Quality Assurance = Assuring good processes are in place
• QC = Quality Control = Controlling what gets released by checking it

5. Common exam scenarios:
• A project manager reviewing and improving development procedures = QA
• A team conducting code reviews on completed modules = QC
• Creating a testing checklist for future use = QA
• Using that checklist to test a deliverable = QC

6. Watch for trick questions:
• Both QA and QC are part of quality management
• Neither is more important than the other; they serve different purposes
• An organization needs both for effective quality management

Practice Application

When you see an exam question about quality, ask yourself:
1. Is this about a process or a product?
2. Is the goal to prevent issues or detect them?
3. Is this happening before/during work or after completion?

These three questions will guide you to the correct answer in most QA vs. QC scenarios on the CompTIA Project+ exam.
Test mode:
More Quality assurance vs. quality control questions
30 questions (total)

Other Project Management Concepts concepts

Action item documentationActivity sequencingAgile methodologyAgile vs. Waterfall selection criteriaChange control board (CCB)Change control processesChange request managementCommunication methods assessmentCommunication methods by methodologyCommunication plan developmentCommunication platformsConfiguration managementConflict resolutionContinuous improvementContract negotiationContract typesCritical path methodDaily standup meetingsDependencies and constraintsDuration estimationHybrid project management approachesImpact analysis for changesInformation distributionIssue documentation and outcomesIssue escalation proceduresIssue identification and trackingIssue log managementIssue resolution processesKanban methodologyKey performance indicators (KPIs)Lean project managementMeeting agenda settingMeeting minutesMeeting roles and responsibilitiesMilestone identificationProcurement documentationProcurement methodsProject auditsProject characteristicsProject management frameworksProject methodologies overviewQualitative risk analysisQuality management planningQuantitative risk analysisRACI matrixRequest for proposal (RFP)Request for quotation (RFQ)Resource allocationResource estimationResource gap analysisResource levelingRisk analysis techniquesRisk identificationRisk mitigation planningRisk monitoring and controlRisk register managementRisk response strategiesRisk roles and responsibilitiesRole definitionsSchedule compression techniquesSchedule developmentSchedule maintenance and updatesScrum frameworkService-level agreements (SLAs)Sprint retrospectivesSprint reviewsStakeholder communication strategiesStatus reportingTeam buildingTeam composition in different methodologiesTeam performance managementTesting cyclesTimeboxing techniquesVendor evaluation criteriaVendor selection processVirtual team managementWaterfall methodologyWork breakdown structure (WBS)