1.5Sprint Retrospective

The retrospective is where the team reflects on what went well, what did not, and what to improve. Quality-focused questions ensure testing improves sprint over sprint.

Quality-Focused Retro Questions

• Escaped defects: Did any bugs escape to production this sprint? Why did our tests miss them?
• Flaky tests: Which tests were flaky this sprint? What is the plan to fix them?
• Bottlenecks: Did testing become the bottleneck at any point? How can we shift left?
• Infrastructure: Are our test environments reliable? What infrastructure improvements would help?
• Automation ratio: Is our test automation ratio improving or declining?
• Test creation velocity: Are we writing tests fast enough to keep up with feature development?

Turning Retro Items into Action

A retro insight without an action item is wasted. Every quality improvement should become a specific, assignable task:

Retro Insight	Action Item	Owner	Sprint
"3 bugs escaped to production"	Add edge case tests for coupon validation	QA Team	Sprint 24
"Pipeline took 35 min, devs stopped waiting"	Add 2 more test shards, cache Playwright browsers	QA + DevOps	Sprint 24
"Payment sandbox was down for 3 days"	Set up a local mock for payment API	Developer	Sprint 24
"6 flaky tests this sprint"	Dedicate 1 day to flaky test investigation	QA Team	Sprint 24