Agile changes QA from end-of-cycle to continuous.
Within sprint:
- Sprint planning: QA participates; estimates testing effort.
- Story refinement: QA contributes acceptance criteria.
- Daily standups: testing progress / blockers.
- Mid-sprint testing: as code merges, tests run.
- Sprint review / demo: tested features shown.
- Sprint retro: process improvements.
Test approach:
- Tests in same sprint as feature — not deferred.
- Continuous testing — CI/CD-driven.
- Definition of Done includes tests passing, coverage met.
Sprint length implications:
- 2-week sprint: ambitious; tests + feature in 2 weeks.
- 3-4-week sprint: more time for thorough testing.
Roles:
- QAs embedded in dev teams — not separate.
- Pairing with devs on hard tests.
- Joint ownership of quality.
Anti-patterns:
- QA at end — defeats agile.
- QA in separate team — coordination friction.
- Tests in next sprint — debt accumulates.
Specific Salesforce considerations:
- Sprint 0 for initial setup.
- Discovery before sprints.
- UAT spans multiple sprints typically.
Senior QA insight: agile requires shift-left. QA earlier, more continuous, more collaborative.
The senior framing: agile QA is a lifestyle change. Embraces continuous testing; rejects batch testing.