Quality Assurance

Quality Assurance is the set of proactive, process-oriented activities aimed at building confidence that a team's way of working will reliably produce acceptable outcomes, focusing on the systems, standards, and practices that shape how work is created rather than on inspecting any single finished item after the fact. Within Agile Quality Management, it complements built-in quality and testing by operating at the level of process design and continuous process improvement, addressing the conditions under which quality is produced rather than only the presence or absence of defects in a particular output.

Distinguishing Quality Assurance From Quality Control

Process Focus Versus Product Focus

Quality assurance concerns itself primarily with whether the processes, standards, and practices a team follows are capable of reliably producing acceptable work, whereas quality control concerns itself with examining specific outputs to determine whether they individually meet requirements.

Proactive Versus Reactive Orientation

Quality assurance activities are largely proactive, aiming to prevent quality problems by improving the process before defects occur, while quality control activities are reactive by nature, responding to and identifying issues in work that has already been produced.

Complementary Rather Than Redundant

The two are not substitutes for one another; a strong process established through quality assurance reduces the frequency and severity of defects, while quality control remains necessary to catch the defects that still occur despite a well-designed process, and Agile teams rely on both operating together.

Core Activities Within Quality Assurance

Establishing and Refining Process Standards

Quality assurance includes defining the standards and practices a team follows — coding conventions, review requirements, testing approaches — and periodically refining them based on observed effectiveness, ensuring the process itself continues to support reliable outcomes.

Auditing Adherence to Agreed Practices

Periodically examining whether the team is actually following its agreed standards and practices, rather than assuming compliance, is a core quality assurance activity, since a well-designed process only produces its intended benefit if it is genuinely followed.

Root Cause Analysis of Recurring Defects

When defects recur in a similar form across multiple pieces of work, quality assurance investigates the underlying process weakness that allows this pattern to persist, addressing the systemic cause rather than treating each instance as an isolated, unrelated occurrence.

Continuous Process Improvement

Using data gathered from retrospectives, defect patterns, and flow metrics, quality assurance drives ongoing refinement of the team's practices, treating the process itself as something to be iteratively improved in the same way the product is.

Quality Assurance's Relationship to Agile Practices

Integration With Retrospectives

Retrospectives serve as a natural forum in which quality assurance observations — patterns in defects, gaps in process adherence, or opportunities for improvement — are surfaced and translated into concrete changes to the team's working agreements.

Support for Built In Quality

Quality assurance activities identify where built-in quality practices are insufficiently embedded or inconsistently applied, providing the systemic feedback needed to strengthen those practices over time rather than leaving their adoption to chance.

Influence Over Definition of Done Evolution

Findings from quality assurance activity often directly inform revisions to a team's definition of done, since gaps revealed through process review frequently point to standards or checks that should be added, clarified, or removed from that shared baseline.

Who Performs Quality Assurance in Agile Teams

Distributed Across the Team

Consistent with shared quality ownership, quality assurance activity in Agile contexts is not confined to a single dedicated role; team members across disciplines contribute observations and participate in refining process standards collectively.

Supported by Dedicated Expertise

Where a team includes members with specific quality assurance expertise, their role typically centers on facilitating process analysis, coaching the team in stronger practices, and maintaining a broader view of quality trends across the team's work, rather than performing all process oversight alone.

Consequences of Neglecting Quality Assurance

Recurring, Unaddressed Defect Patterns

Without quality assurance attention to root causes, similar defects tend to reappear repeatedly across different work items, since only the immediate symptom is addressed each time rather than the underlying process weakness producing it.

Process Drift

In the absence of periodic review, a team's actual practices can gradually diverge from its stated standards without anyone deliberately deciding to change them, weakening the reliability that those standards were meant to provide.

Missed Opportunities for Systemic Improvement

Quality control alone identifies individual defects but does not by itself generate insight into how the process could be changed to prevent similar defects in the future; without quality assurance, this systemic learning opportunity is largely lost.

Visual Representation

Findings from checking the output feed back into refining the process itself, closing the loop between the two disciplines. This relationship can be expressed as:

Quality Assurance is the discipline directed specifically at improving the term on the right-hand side of this relationship, rather than only measuring or reacting to the defect rate it produces.