What is retrospective?
Quick definition
A scheduled team meeting held after completing a work cycle to reflect on what went well, what didn't, and identify improvements for future cycles.
A retrospective is a structured reflection ceremony typically conducted at the end of a sprint, iteration, or project phase. Team members gather to discuss their recent work, examine their processes, and collaboratively identify actionable improvements. The primary goal is continuous process improvement by creating psychological safety where developers can openly share feedback without fear of blame.
In Kanban environments, retrospectives may be scheduled at regular intervals (weekly, bi-weekly) or triggered by specific events (major releases, process changes). Unlike sprint-based Scrum retrospectives with fixed boundaries, Kanban teams often run continuous or rolling retrospectives. These sessions typically follow a structured format: what went well, what didn't go well, and what we'll improve—sometimes called the "Start, Stop, Continue" or "Plus, Delta" frameworks.
For AI-agent teams and autonomous workflows, retrospectives become particularly valuable for examining agent decision-making patterns, workflow automation effectiveness, and identifying where human oversight or model tuning is needed. Developers use retrospective insights to refine agent prompts, adjust MCP server configurations, and optimize multi-agent orchestration patterns.
Example
How it shows up in practice
Sprint 17 retrospective: Team identified that unclear task descriptions in the Kanban backlog caused context-switching. Action item: Implement definition-of-done checklist requiring acceptance criteria before tasks enter in-progress columns.
Frequently asked questions
How often should we hold retrospectives?
Scrum teams typically hold retrospectives after each sprint (1-4 weeks). Kanban teams often schedule them weekly or bi-weekly. Frequency depends on your cycle time and team preference for reflection cadence.
Who should attend a retrospective?
Core team members who worked on the completed work should attend. Include developers, QA, product owners, and scrum masters. Stakeholders may attend occasionally, but ensure a safe environment for honest feedback.
What should we do with retrospective action items?
Create specific, measurable action items with owners and target completion dates. Add them to your backlog and track them like regular work. Review progress at the next retrospective to ensure accountability.
How do retrospectives differ between Scrum and Kanban?
Scrum retrospectives occur after fixed sprints with clear boundaries. Kanban retrospectives are often continuous or rolling, tied to releases or time intervals rather than sprint completion. Both aim for improvement but operate within different workflow structures.