9.2Scaling QA Across Teams

Anti-Pattern: Each team builds and maintains its own test infrastructure independently. There is no shared framework, no common standards, and no cross-team visibility into quality.

Pattern: QA guilds, shared standards, and an internal testing framework — with a critical distinction between standardizing principles and allowing flexibility on implementation.

QA Guilds

A QA guild is a cross-team community of practice for quality engineers. It meets regularly to:

• Share solutions to common problems
• Align on standards (naming conventions, tagging strategies, reporting formats)
• Review and evolve the shared testing framework
• Mentor less-experienced QA engineers across teams

Standards Governance

The key principle: standardize the interfaces, not the implementation.

• Standardize: how tests report results, how CI pipelines are structured, how flaky tests are tracked, what metrics are collected
• Allow flexibility: which test framework a team uses internally, how they organize test files, what assertion libraries they prefer

This approach gives teams ownership while maintaining cross-team visibility and consistency where it matters.