A retrospective turns into a complaints session when nobody reviews last time's actions or leaves with a decision. This deck gives a scrum master a structured hour: a check-in with sprint numbers, a review of previous actions, start-stop-continue cards, a vote on themes and a short list of actions with owners and dates.

The sample follows the platform team at Sandpiper Cloud, a fictional software company, after Sprint 24. It shows velocity of 38 points, a 3-day cycle time, three of four previous actions done and two new actions for Sprint 25. Replace the sprint data with your own, keep one retro format and reduce the actions to one or two.