39 / 57 · 21 Communication & Stakeholder Management · Sprint Review Presentations← prev⊞ allnext →☰ Read as one page
5.6Retrospective Facilitation from a QA Perspective
QA engineers bring unique insights to retrospectives because they see quality from every angle -- requirements, implementation, testing, and production.
Quality-Focused Retro Topics
- Escaped defects analysis: What bugs reached production? What would have caught them? Was it a missing test, a test environment gap, or a requirements gap?
- Shift-left wins: Did any bugs get caught earlier than they would have in previous sprints? What practice made that possible?
- Automation ROI: How much time did automation save this sprint? Are there manual tests that should be automated?
- Collaboration quality: Did developers and QA communicate well about changes? Were there any surprises?
- Environment reliability: Did test environments cause delays? What can be improved?
Turning QA Retro Insights into Action
| Insight | Action | Owner |
|---|---|---|
| "We caught the payment bug in three amigos instead of testing" | Continue three amigos for all payment stories | QA + Product |
| "Flaky test caused 2 hours of investigation this sprint" | Fix the 3 most flaky tests next sprint | QA |
| "Staging was down for 1.5 days" | Add staging health monitoring and alerts | DevOps |
| "New API endpoint had no test coverage" | Add API test template to PR checklist | QA + Dev |