6.2For Sprint Reviews (Product Owner, Stakeholders)

Sprint reviews are about business outcomes, not technical details. Stakeholders want to know: Is the product ready? What works? What does not? What are the risks?

What to Include

• Execution summary: 342 tests run, 338 passed, 2 failed, 2 blocked
• New defects found: 5 (2 critical, 1 high, 2 medium)
• Defect resolution rate: 8 fixed this sprint, 3 carried over
• Features with full test coverage: Login, Cart, Checkout
• Features with gaps: Email notifications (2 test cases pending)
• Release readiness: Go / No-Go with clear justification

Example Sprint Review Slide

Sprint 23 Quality Summary
─────────────────────────
Tests Executed:    342 / 342 (100%)
Pass Rate:         98.8% (338 passed, 2 failed, 2 blocked)
New Defects:       5 found (2 critical - both fixed)
Carried Over:      3 medium-priority bugs from Sprint 22

Feature Readiness:
  ✅ Login redesign - fully tested, 0 open defects
  ✅ Cart optimization - fully tested, 1 low-priority cosmetic bug
  ⚠️ Coupon system - 1 critical bug (SHOP-812) fixed but needs re-verification
  ❌ Email notifications - test cases written but execution blocked (mail server down)

Recommendation: CONDITIONAL GO
  - Deploy login and cart changes
  - Hold coupon system pending verification of SHOP-812 fix
  - Defer email notifications to Sprint 24

What NOT to Include

• Flake rate details (too technical)
• Pipeline optimization metrics
• Individual test case results
• Code coverage percentages (unless the team has set coverage targets as a product metric)