A 30-minute remote retrospective agenda for small teams

Try this agenda with a small team of roughly three to six people reflecting on a short, familiar period of work. It is a practical starting point for a weekly check-in or a focused follow-up to a recent change. The aim is one worthwhile conversation, not a quick tour of everything that happened.

Choose a longer session if you need to unpack a difficult incident, establish shared context or hear from a large group. A short agenda should not become a reason to cut someone off while they are explaining a serious concern. This is a suggested team format, not a required Scrum meeting length.

Send the meeting link, the board link and one sentence naming the scope: “Let’s review how this week’s release handover worked.” Add three prompts: what helped, what got in the way and what we could try. Give people time during their normal working day to recall an example.

Check that participants can open the board and understand who will see their notes. In Retro, anyone with the participant link can read and join the shared board. Private reflection can hold new notes until a facilitator reveals them, but authors’ names remain on shared notes.

Put the agenda somewhere visible and ask one person to facilitate. The checkpoints below add up to 30 minutes. Use a shared timer as a reminder, then make a deliberate choice if the conversation needs a different pace.

Imagine three notes describe last-minute release questions. Instead of discussing each note separately, name the theme “Missing release context” and ask for one concrete example. Then explore what information was missing and when someone needed it.

If the conversation moves into redesigning the entire delivery process, bring it back to the next release. An experiment could be a short handover note covering the change, the support contact and the rollback decision. Record other topics in the parking list with a plan for returning to them.

Votes help allocate time; they do not settle whether a concern matters. Before moving on, ask whether a low-vote topic needs a separate conversation or a quicker response.

Write down the action while everyone is still present. Ask the owner to confirm the next step and agree when the team will review the result. A useful close is: “Maya will draft the handover note on Thursday; we’ll try it on Friday and review it next week.”

If time runs out before you understand the problem, record the question that remains and arrange the next discussion. An honest unfinished conversation is easier to follow up than an action nobody believes in. At the next retro, review what actually happened before starting a new list.