Retrospective

Basic

difficulty

Stage 2

Agile IQ® Level

Empiricism

practices

Scrum

Framework

Introduction

The Retrospective is one of five events in Scrum. It’s designed to help Scrum Teams plan ways to increase quality and effectiveness of the Scrum Team. The Scrum Team inspects how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done. Inspected elements often vary with the domain of work. Assumptions that led them astray are identified and their origins explored.

The Scrum Team discusses what went well during the Sprint, what problems it encountered, and how those problems were (or were not) solved.

Timebox: 3 hours. Less for Sprints of a shorter length.

Who should attend?

Scrum Master.
Product Owner.
Developers.

Improvements focussed on the work alone tend to alienate the Product Owner

Consider improvement actions that will create a positive impact on people, process and tools and the team's overall effectiveness with agile product management.

How do run an effective Retrospective

Don’t use the same pattern every Retrospective. It gets boring very quickly.
Choose a pattern that will best help the whole team deep-dive into the issues of the Sprint and address them.
Improvement actions should be visible in the Sprint Backlog. The whole team should plan how they will enact their improvements.
Just saying “we collaborated well” isn’t enough. Assess the root cause so you can make success repeatable and scalable.
Use Agile IQ® metrics to assess whether your improvements are having the desired impact.

Download

Download the Retrospective guide to print and use with your team.

All fields are required.