QA in Agile Teams
The role of Quality Assurance in agile teams has evolved significantly from traditional QA: from a separate testing phase at the end of a waterfall cycle to an integrated quality function embedded throughout the sprint. Agile QA is about building quality in, not inspecting quality in — and that requires a fundamentally different approach to how QA practitioners work and where they sit in the team.
Embedded QA vs Separate QA Team
In mature agile organisations, QA practitioners are embedded in delivery teams — participating in sprint planning, refinement, and retrospectives. They contribute to acceptance criteria definition, review designs for testability, and work alongside developers during development rather than after. A separate QA team (testers who pick up work after developers finish) recreates the handoff delays of waterfall within an agile framework.
The QA Role in Sprints
- Sprint planning/refinement: Define acceptance criteria, identify test scenarios, flag testability concerns
- During sprint: Write automated tests alongside feature development, exploratory testing of completed work, bug investigation
- Sprint review: Demonstrate testing approach and coverage, highlight quality observations
- Retrospective: Identify quality process improvements, track defect root causes
Quality as a Team Responsibility
In the most effective agile teams, quality is not solely the QA practitioner's responsibility — every team member owns quality. Developers write tests, review others' tests, and consider quality in their implementation decisions. The QA role becomes one of quality leadership and coordination rather than a sole quality function.