Free, no sign-up — opens the agenda as a live countdown.
Most retrospectives fail in the last ten minutes, when the team has plenty of feelings and no decisions. This 60-minute shape follows the classic five stages and reserves real time at the end for choosing actions with owners, so the next sprint inherits something concrete.
| Topic | Minutes | Running total |
|---|---|---|
| Set the stage Restate the sprint goal and the prime directive. A one-word check-in round works well here. | 5 | 5 |
| Gather data What actually happened: the timeline, the numbers, the incidents. Facts before interpretation. | 15 | 20 |
| Generate insights Why did it happen? Cluster the data and look for the pattern, not the culprit. | 15 | 35 |
| Decide what to do Two or three actions, each with a name and a date. Fewer, owned, is better than ten orphans. | 15 | 50 |
| Close Read the actions back, check the team agrees, and say how the retro itself went. | 10 | 60 |
Open this agenda in BriefMe:
Opens a working agenda you can start straight away. Nothing to sign up for — anonymous agendas are kept for 7 days.
Already connected to BriefMe? Paste this. Connect BriefMe to Claude
Using BriefMe, create a 60-minute sprint retrospective for eight people: a 5-minute stage-setting opening, 15 minutes each for gathering data, generating insights and deciding actions, and a 10-minute close.
An hour for a two-week sprint is the common default, and forty-five minutes is enough for a small team that retrospects often. Ninety minutes suits a month-long sprint or a team working through something painful.
Because a retrospective that ends with sentiment and no owner changes nothing. The decide stage is the only part that alters the next sprint, so it gets protected time rather than whatever is left over.
It depends on whether people will say the true thing. If the team is new to each other or the sprint went badly, a retro without the reporting line often surfaces more; share the actions afterwards either way.