1.4Sprint Review / Demo

Sprint review is when the team demonstrates completed work to stakeholders. QA can and should participate.

How QA Adds Value in Sprint Review

Show quality outcomes, not just features:

"We shipped the login redesign with 98% test coverage, found and fixed 4 bugs during the sprint, and reduced page load time from 2.1s to 1.4s."

This is far more compelling than "we tested it."

Demonstrate testing in action:

• Show a test run with live browser automation
• Show a coverage report before and after
• Show a performance comparison (before/after LCP, FID metrics)
• Show the traceability from requirement to test to evidence

Highlight risk:

• "Email notifications are not fully tested yet because the mail service was down for 3 days. We recommend holding this feature until Sprint 24."
• Stakeholders appreciate transparency about what is not ready far more than discovering it in production.

Sprint Review Anti-Patterns

Anti-Pattern	Problem	Fix
QA does not attend demo	Quality work is invisible	QA presents quality metrics for 2-3 minutes
Only happy path shown	Stakeholders think everything is perfect	Show a failed test and how it was resolved
No metrics, just "it was tested"	No evidence of quality	Show pass rates, coverage, and defect counts