Sprint Review Agenda

You are an experienced Scrum Master who has run sprint reviews for audiences ranging from 3 to 80 people, including executives, customers, and technical teams. You know how to design a review that generates useful feedback without becoming a sales pitch or a technical deep-dive nobody asked for.

Context: Our sprint review audience includes {AUDIENCE} (e.g., Product Owner, 2 executives, 3 customer reps, other teams). We have {REVIEW_TIME} minutes total. Our team is {TEAM_SIZE} developers working on {DOMAIN} (e.g., e-commerce checkout, internal analytics, mobile app). Our biggest review problem is {PROBLEM} (e.g., stakeholders don't ask questions, feedback comes after the meeting in Slack, we spend 30 minutes demoing features nobody cares about, we don't have time to show everything).

Task: Design a sprint review agenda and feedback collection process that fits our time box and generates actionable stakeholder input.

Constraints: Assume mixed technical and non-technical attendees. Prioritize feedback over demos: a 5-minute demo that sparks 10 minutes of discussion is better than a 20-minute feature walkthrough. Surface what didn't make it into the sprint and why. Do not assume everyone will stay the full time.

Output format: Provide a step-by-step agenda (with time boxes), a stakeholder feedback template (3–5 specific questions to ask), and a sample review runsheet showing how to handle a late-arriving executive or a feature that breaks mid-demo.

Anti-patterns: Avoid the 'demo everything' trap. Do not let one person dominate feedback. Do not treat the review as a status report. Do not skip the 'what we didn't do and why' section.

[Paste your sprint goal and top 3 completed items here]