Quality Assurance vs Quality Control

Quality Assurance vs Quality Control

The phrases "QA team" and "quality team" are often used interchangeably in job postings, but understanding the distinction sharpens your thinking about where in the development cycle you add the most value.

Quality Assurance: Upstream Work

QA is proactive. It is about designing processes, checklists, standards, and workflows that make defects less likely to occur in the first place.

Examples of QA activities:

• Participating in requirement reviews to catch ambiguous acceptance criteria before a line of code is written
• Creating test strategy documents that define what will be tested, how, and to what standard
• Setting up code review guidelines that include security and testability checks
• Running retrospectives after incidents to find root causes and process improvements

The key insight: QA happens before and during development, not just at the end.

Quality Control: Downstream Verification

QC is reactive. It involves examining a finished work product against a defined standard to determine whether it meets requirements.

Examples of QC activities:

• Executing a test suite against a build
• Reviewing a document against a style guide
• Running static analysis tools on committed code

The key insight: QC finds defects that already exist. It cannot improve the process that created them.

Why Both Matter in Agile

In a traditional waterfall model, QA was design/planning and QC was a distinct test phase. In agile, the line blurs — short sprints mean you need both happening continuously.

A modern QA engineer:

1. Reviews the user story during sprint planning (QA — prevent ambiguity)
2. Writes acceptance criteria with the team (QA — shared understanding)
3. Tests the implemented feature against those criteria (QC — detect defects)
4. Reports metrics and trends after the sprint (QA — process improvement)

The Tester's Mindset

Effective testers hold a productive tension: they are deeply curious and skeptical ("where does this break?") while being collaborative and constructive ("here is what I found and here is how to fix it"). They understand that a defect found in production is a shared failure, not an individual one.