Fill in these first
- Team and product: [e.g. mobile app team, food delivery app]
- Sprint number, dates and goal: [details]
- Completed items: [paste ticket titles with one line each]
- Items not finished: [titles and reason]
- Metrics affected, if any: [e.g. checkout time, crash rate]
- Stakeholders attending: [roles]
- Meeting length: [e.g. 30 minutes]
- Decisions or feedback needed: [e.g. which of two layouts to keep]
Task
Plan a review that shows working software in a story order and leaves with clear stakeholder input.
Session plan
- Sprint goal and verdict, 2 minutes: met, partly met or not met, in one sentence.
- Demo, about half the meeting: completed items ordered as one user's journey, not by ticket number.
- Not done, 3 minutes: what slipped, why, and where it goes now.
- Numbers, 3 minutes: any metric that moved.
- Feedback, the rest: specific questions, not "any thoughts?".
- Next sprint preview, 2 minutes.
Output format
- | Section | Minutes | Presenter | Slides or screen |
- Demo order: | Step | User action | Feature shown | Ticket |
- | Not done | Reason | Plan |
- Five feedback questions, each with the decision it informs.
- A follow-up note to send after the meeting, with decisions and owners as [Owner].
Rules
- Demo only items that are done to the team's definition of done; show nothing from a local branch as finished.
- No slides of ticket lists; show the product.
- Keep technical detail out unless a stakeholder asks.






