QA in Agile is not a testing phase
Agile delivery compresses feedback loops. That means Quality Assurance should be integrated into backlog refinement, design, development, automation, acceptance, and release—not added as a separate phase after coding.
AskAQA principle: Agile quality is continuous collaboration around risk, testability, evidence, and readiness.
How QA contributes across a sprint
Backlog Refinement
↓
Risk & Testability Review
↓
Sprint Planning
↓
Development + Early Testing
↓
Integration / Regression
↓
Acceptance
↓
Release Readiness
↓
Production Feedback
What changes for QA in Agile
- Earlier involvement
- Smaller test scope per increment
- More collaboration
- Greater automation need
- Continuous regression
- Faster defect feedback
- More visible quality criteria
- Production learning
What should not disappear
Agile does not remove the need for test strategy, risk assessment, traceability, evidence, non-functional validation, release criteria, or quality accountability. It changes how those activities are expressed and maintained.
A practical Agile QA mindset
Ask continuously: What is the risk? How will we know this works? What evidence will we have? What could break outside the story? What must be true before release?