Sprint Retrospective Summary
Turn retro board notes into themes, agreed actions and a summary to share with the team.
Prompt preview
Summarize our retrospective for Sprint 14. What went well: - Pairing on the search bug - Demo went smoothly What didn't: - Stories too big, two carried over - Late design changes - Standups ran 25 minutes Group the points into 3 to 5 themes, then propose up to 3 improvement actions that are specific and testable next sprint, each with an owner placeholder. Write it blameless: describe systems and processes, never individuals, so the team keeps being honest in future retros. I'm a project manager. Use these placeholders where needed: [Project name], [Team], [Sponsor], [My name]. My readers are busy stakeholders who skim. Lead with the status or the decision needed, then the detail. Flag risks and slips plainly, with an owner and a date, and never soften bad news into vague language. Use short sentences and bullet points, no corporate filler like 'synergy' or 'circle back', and never invent numbers, dates or names I didn't give you.