Scrum Events
Sprint Retrospective
Continuous improvement · Timebox: ≤ 3 hours (1-month Sprint)
Overview
The Sprint Retrospective is where the Scrum Team inspects how the last Sprint went with regards to individuals, interactions, processes, tools, and the Definition of Done. It’s the engine of continuous improvement — the most impactful improvements are addressed as soon as possible and may be added to the next Sprint Backlog.
Event Ownership
Owned / Facilitated By
Scrum Master (facilitator and guardian of improvement culture)
Design and facilitate the retrospective using appropriate techniques for the team’s current needs
Create psychological safety — people must feel safe to be honest
Ensure the retrospective produces concrete, actionable improvement items with owners
Track follow-through on previous retrospective commitments
Vary the format to prevent retro fatigue and surface different insights
Who Should Be Present
Entire Scrum Team
All members (Developers, PO, SM) participate equally. Everyone reflects, contributes ideas, and commits to improvement actions
Scrum Master
Facilitates the session, models vulnerability, and ensures action items are concrete and assigned
Product Owner
Participates as a full team member — their perspective on collaboration, priorities, and communication is essential
Preparation Checklist
01Scrum Master: Select a retrospective format appropriate for the team’s current situation
02Scrum Master: Gather Sprint data — velocity, burndown, escaped defects, impediment resolution time — to ground discussions in facts
03Scrum Master: Review previous retrospective action items and their completion status
04Team: Reflect individually on the Sprint before the meeting — what went well, what didn’t, and what they’d change
05Scrum Master: Prepare the facilitation space — boards, sticky notes, timers, or digital equivalents