5.2QA's Role in Sprint Demos

Most sprint demos follow a predictable pattern: a developer shows a feature, the product owner nods, stakeholders ask questions. QA is either absent or mentioned in passing ("and it's been tested"). This undersells the QA contribution.

What QA Should Present

Content	Duration	Example
Quality summary	1-2 minutes	"This sprint we tested 23 stories, found 7 bugs (2 critical, 3 major, 2 minor), all resolved before release."
Testing highlights	2-3 minutes	Show a test automation run, a coverage report, or a before/after performance comparison
Risk areas	1-2 minutes	"The partner integration is tested for happy paths. We plan to add fault injection testing next sprint."
Quality trends	1-2 minutes	Sprint-over-sprint bug trends, automation coverage growth, escaped defect rate

Presenting Testing, Not Just Results

Showing a green checkmark is not a presentation. Showing the work behind the green checkmark is.

Instead of: "All tests pass."

Show:

• A 30-second screen recording of the browser test suite running against the new feature
• A coverage diff showing which lines of the new code are exercised by tests
• A test plan that maps acceptance criteria to specific test cases with results
• An exploratory testing session recording where you caught a critical edge case