6.4For QA Team Retrospectives

The QA team needs operational metrics that help them improve their own processes and tooling.

What to Include

• Test cycle time: How long does a full regression run take? Is it getting faster or slower?
• Blocked tests: Which tests are blocked and why? Are the same blockers recurring?
• Test creation velocity: Are we keeping up with feature development? What is the ratio of new features to new tests?
• Automation candidates: Which manual tests should be automated next? Prioritize by frequency of execution and business criticality.
• Coverage gaps: Which areas of the product have the weakest test coverage?
• Tool effectiveness: Are our test management tools helping or hindering? What workflows are painful?

Example QA Retrospective Report

QA Team Health - Sprint 23
──────────────────────────
Execution Metrics:
  Full regression time: 22 min (target: 15 min)
  Manual test cycle:    4 hours (16 manual test cases)
  Test creation:        12 new test cases (vs 8 new stories)

Blockers This Sprint:
  - Payment sandbox down (3 days) → Blocked 8 test cases
  - Staging DB not refreshed → Delayed integration testing by 1 day
  - Playwright upgrade broke 3 page objects → Fixed in 2 hours

Automation Candidates (prioritized):
  1. TC-501: CSV export (run manually every sprint, straightforward to automate)
  2. TC-203: Weak password validation (high regression risk, stable UI)
  3. TC-304: Cart persistence (requires browser context, moderate complexity)

Coverage Gaps:
  - Email notifications: 0 automated tests (manual only)
  - Admin panel: 30% coverage (low priority, stable feature)
  - Mobile responsive: 15% coverage (high priority, growing user segment)

Action Items:
  - Automate TC-501 this sprint (estimated: 4 hours)
  - Request dedicated payment sandbox for QA (recurring blocker)
  - Investigate Playwright container caching to reduce regression time