Atlas › 21 Communication & Stakeholder Management › Sprint Review Presentations☰ Read as one page
Sprint Review Presentations
5.1Making Invisible QA Work VisibleQA work is inherently invisible when done well. Features ship smoothly, bugs do not reach production, regressions are caught before users…5.2QA's Role in Sprint DemosMost sprint demos follow a predictable pattern: a developer shows a feature, the product owner nods, stakeholders ask questions. QA is…5.3Presenting Test Coverage, Risk Areas, and Quality TrendsPresent coverage in terms stakeholders understand -- not lines of code, but features and user journeys.5.4Visualizing Quality: Storytelling with DataRaw data is not persuasive. Stories with data are. Every quality metric you present should answer a "so what?" question.5.5Handling Questions About Bugs Found in ProductionWhen a stakeholder asks "Why did this bug make it to production?", they are rarely asking a technical question. They are asking: "Can I…5.6Retrospective Facilitation from a QA PerspectiveQA engineers bring unique insights to retrospectives because they see quality from every angle -- requirements, implementation, testing…5.7Making Invisible QA Work VisibleHelp stakeholders see QA through a value lens:5.8Hands-On Exercise1. Prepare a 5-minute sprint review presentation for your current sprint using the structure above 2. Create a feature coverage…