Retrospectives

Retrospectives are structured meetings held at the end of each sprint, during which teams reflect on their work process. Unlike status reviews, which focus on what was built, retrospectives examine how the team worked together and identify improvements for future sprints.

The meeting follows a clear format: gathering data about what happened, generating insights about why things happened, and deciding on specific actions to improve. Teams discuss what went well (to continue), what didn't go well (to change), and what they should try next sprint.

Retrospective actions should be specific, measurable, and achievable within the next sprint. For example, instead of saying “enhance collaboration,” the team could agree to “set up a shared digital workspace to improve file sharing and communication.” Tracking progress on these action items is essential for team accountability.

The scrum master facilitates retrospectives and ensures all team members participate actively. Creating a safe space for honest feedback is crucial in these meetings since retrospectives focus on process improvement, not blame assignment.