> Markdown version of [/videos/467-quality-strategy-with-a-side-of-swiss-cheese](https://www.wearedevelopers.com/videos/467-quality-strategy-with-a-side-of-swiss-cheese). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Quality Strategy with a side of Swiss Cheese

Aerospace systems prevent disaster using the multi-layered Swiss Cheese model. Discover how applying this risk strategy to software engineering eliminates brittle tests and builds resilient ecosystems.

- **Speakers:** Sarah Hutchins
- **Event:** World Congress 2022
- **Published:** June 15, 2022
- **Duration:** 29:04
- **URL:** https://www.wearedevelopers.com/videos/467-quality-strategy-with-a-side-of-swiss-cheese

## Summary

Defining software quality as the "informed confidence that we're building the right thing at the right time," this talk introduces the Swiss Cheese model to comprehensively structure software quality strategies. Adapted from high-stakes industries like aerospace, this multi-layered risk mitigation approach assumes no single defensive layer is flawless. Instead, combining targeted strategies effectively prevents systemic failures, minimizing the inevitable "bucket" of defects, unplanned maintenance, and database bottlenecks.

To operationalize this model, teams can leverage a three-stage quality strategy workshop. First, engineers map out direct, indirect, and malicious user personas to understand varying interaction goals. Next, architectural dependencies and APIs are analyzed to identify friction points and testing complexities. Finally, teams brainstorm specific system concerns and assign them to existing or missing functional layers. This assessment ensures tests are fulfilling their purpose cost-effectively. For example, rather than maintaining a slow, brittle inventory of 200 end-to-end tests, teams can pivot toward highly reliable data layer tests and proactive database performance monitoring.

Ultimately, the Swiss Cheese method integrates seamlessly with the traditional Agile test pyramid—while the pyramid dictates *how* to implement tests optimally, the layered model defines *what* actually needs testing. Fostering a quality-centric engineering culture shifts QA professionals from end-of-the-line gatekeepers into proactive process coaches. By maintaining an ideal "golden ratio" of roughly one QA specialist to every four-to-six developers, organizations can successfully shift quality left, collaborate across cross-functional product boundaries, and build a highly resilient software ecosystem.

**Keywords:** swiss cheese model, software quality strategy, agile test pyramid, defect management, API integration testing, pact framework, end-to-end testing, data layer testing, contract testing, database performance monitoring, incident root cause analysis, QA metrics, user persona mapping, multi-tier architecture mapping, cross-functional product teams, QA to developer ratio

## Chapters

1. **Defining software engineering quality using a cheese production analogy** (00:05) — Quality represents the informed confidence that teams are building the right thing at the right time.
1. **Using the Swiss Cheese model for multi-layered risk avoidance** (03:36) — Applying multiple imperfect defensive layers together significantly reduces systemic failures.
1. **Managing unplanned work and system failures using the bucket analogy** (06:23) — Identifying unaddressed technical debt and system defects prevents overwhelming operational incidents.
1. **Identifying system stakeholders and user expectations through personas** (08:40) — Mapping direct users, indirect dependencies, and malicious actors clarifies system requirements and vulnerabilities.
1. **Mapping architectural dependencies to characterize product integrations** (10:39) — Visualizing upstream and downstream connections highlights contract stability and testing constraints.
1. **Aligning technical concerns with protective quality testing layers** (12:21) — Brainstorming system risks enables teams to evaluate existing defenses and introduce missing quality gates.
1. **Evaluating the maintenance and execution costs of testing layers** (15:58) — Removing overly expensive or slow defenses like unstable end-to-end tests ensures sustainable testing models.
1. **Sizing operational buckets to realistically handle maintenance workloads** (17:31) — Appropriately staffing support and accurately tracking technical debt prevents hidden operational failures.
1. **Integrating the test pyramid with the Swiss Cheese risk model** (19:33) — While the test pyramid dictates test implementation efficiency, risk models highlight which behaviors require coverage.
1. **Discovering risk models and implementing contract testing tools** (21:24) — Using API consumer-driven contract tools manages integration stability across varied service architectures.
1. **Tracking technical debt metrics and cross-functional team engagement** (23:45) — Measuring bug-to-feature time reveals maintenance loads, while cross-functional involvement ensures comprehensive system analysis.
1. **Determining the optimal ratio of developers to quality professionals** (27:11) — Embedding quality engineers directly with small development teams fosters an early testing mindset over isolated gatekeeping.

## Related Moments

- [Transforming software quality from assurance to enablement](https://www.wearedevelopers.com/videos/100184-self-service-quality-qa-without-qa) (from "Self-service Quality: QA Without QA")
- [Introduction to software quality assurance in enterprise applications](https://www.wearedevelopers.com/videos/100012-let-s-talk-quality) (from "Let’s Talk Quality!")
- [Approaching software quality as a subjective social science](https://www.wearedevelopers.com/videos/87-excellent-software-testing) (from "Excellent Software Testing")
- [Establishing a company-wide approach to software quality assurance](https://www.wearedevelopers.com/videos/428-automated-code-quality-checks-with-custom-sonarqube-rules) (from "Automated Code Quality Checks with Custom SonarQube Rules")
- [Shifting software testing from adversarial gatekeeping to enablement](https://www.wearedevelopers.com/videos/1134-the-affordances-of-quality) (from "The Affordances of Quality")
- [Understanding the role of software architecture and quality](https://www.wearedevelopers.com/videos/1684-modern-software-architectures) (from "Modern software architectures")

## Related Articles

- [Now is the time for industrialized software development](https://www.wearedevelopers.com/magazine/601-now-is-the-time-for-industrialized-software-development)
- [How to create a test plan for software testing](https://www.wearedevelopers.com/magazine/56-how-to-create-a-test-plan-for-software-testing)
- [What is a Test Plan: Guide to Test Planning](https://www.wearedevelopers.com/magazine/191-what-is-a-test-plan-guide-to-test-planning)
- [Building Security Champions](https://www.wearedevelopers.com/magazine/87-building-security-champions)

## Related Jobs

- [QA Automation Engineer](https://www.wearedevelopers.com/jobs/ext/1414297-qa-automation-engineer) at **Bitpanda**
- [Lead Systems Architect](https://www.wearedevelopers.com/jobs/ext/1283192-lead-systems-architect) at **ZEISS Group**
- [Security Architect - AI](https://www.wearedevelopers.com/jobs/ext/1581899-security-architect-ai) at **ZEISS Group**
- [Mid/Senior Full-Stack Engineer (Web-first)](https://www.wearedevelopers.com/jobs/ext/1210833-mid-senior-full-stack-engineer-web-first) at **SMG Swiss Marketplace Group**
- [Senior Process Architect - Electronic Testing & System Integration](https://www.wearedevelopers.com/jobs/ext/1667721-senior-process-architect-electronic-testing-system-integration) at **ZEISS Group**
- [Scientific Software Developer - Tolerance Analysis & Algorithm development](https://www.wearedevelopers.com/jobs/ext/1417919-scientific-software-developer-tolerance-analysis-algorithm-development) at **ZEISS Group**