QA should participate before development starts
QA involvement in Scrum begins during refinement, not after a story enters development. Early QA questions improve clarity and reduce avoidable churn inside the sprint.
Backlog refinement
- Clarify acceptance criteria
- Identify dependencies
- Challenge ambiguity
- Surface test data needs
- Identify integration risks
- Flag non-functional needs
- Check story size
- Assess testability
Sprint planning
QA helps estimate testing effort, identify sequencing constraints, confirm environment/data readiness, and ensure quality activities fit inside the sprint rather than becoming spillover work.
During development
QA and developers should collaborate on examples, negative cases, API behaviour, data conditions, testability, and automation hooks while implementation is still changing.
Daily collaboration
The Daily Scrum is not a status meeting for QA. Useful quality discussion includes blockers, failed builds, environment issues, unexpected regression impact, unresolved defects, and dependencies affecting sprint goals.
Acceptance and regression
Story acceptance should not be confused with release readiness. A story can meet its acceptance criteria while broader integration, regression, performance, security, or operational validation is still required.
Retrospectives
Use retrospectives to improve quality flow:
- Why did defects escape?
- Where did testing wait?
- Which environments failed?
- What manual work should be automated?
- Which requirements repeatedly caused confusion?
- What should change in DoR or DoD?