Pick sync / async / hybrid. Set the duration. Get a markdown agenda built around the conversation, not the demo.
Loading template...
SprintFlint surfaces ticket-by-ticket sprint progress, sprint goal status, and the next-sprint backlog in one view. Sprint review prep takes 0 minutes.
Start Free60 minutes for a 2-week sprint with a 6-person team is the sweet spot. 30-45 minutes for tight teams who keep the demo section short. 90 minutes only for 3-4 week sprints with multiple stakeholder groups.
Sprint review looks at the *product* — what shipped, what we learned, what's next. Retrospective looks at the *process* — how the team worked, what to improve. Don't combine them.
Yes for tight, senior, distributed teams with engaged stakeholders. The pattern: demos posted as Loom recordings on day 1, async stakeholder reactions, then a short 30-minute live "now what" conversation on day 2.
The whole engineering team, the PM, and any stakeholders who care about the product (sales, support, leadership, design). Not other engineering teams' reps unless there's a dependency.
The "now what" conversation about the next sprint backlog. Most teams demo, then end. The whole point of having stakeholders in the room is to use their reaction to inform what's next. Don't skip this.
If your team and stakeholders talk every day already, and the product is internal, yes. Replace with a 5-minute Slack update at end-of-sprint. Otherwise the meeting is doing real work even if it doesn't feel like it.
SprintFlint shows what shipped, what's at risk, and the next-sprint backlog in one view. Free for the first 300 tickets — no card.