Skip to content
Intro page
The purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness.
The Scrum Team inspects how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done.
Scrum master role
the Scrum Master is responsible for keeping the meeting running smoothly moment-to-moment. That means ensuring the team doesn’t dwell too long on a particular topic, making sure that all questions are asked (and answered), and keeping everything running smoothly. It’s a role of a moderator on the retrospective meeting.
Team role
team use the opportunity to pause and reflect on how things have been going and then, based on those reflections, identify the improvements they want to make. Conducting Retrospectives frequently and regularly supports a team to continuously improve their performance
Format of an event
- Give people time to “arrive” and get into the right mood.
Small talk
Warm-up activities
- the chance to look back at your iteration to create a shared understanding of the events that shaped the present.
Help everyone remember the data, that can be reviewed;
Create a shared pool of information about the last iteration.
- analyse of gathered data stage.
Why did things happen the way they did?;
Identify patterns;
See the big picture
- based on generated insights create action for future iterations.
Pick a few issues to work on and create concrete action plans (action item) of how you’ll address them
Clarify follow-up;
Clear end;
How could the retrospectives improve?

Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
) instead.