Christmas Retrospective This Christmas Retrospective can be used at the end of the year to reflect on the past year. Or, alternatively, it can also be used as a regular retrospective during the Christmas period. The Icebreaker The suggested icebreaker for this retrospective is having everybody share (a picture) about their favourite Christmas tradition. If […]
Went well, challenges and ideas This is a retrospective format that allows the team to reflect on the things that went well, the challenges and any new ideas that the team would like to try. It’s a basic retrospective format that can be used after a sprint-, release- or project retrospective. The Icebreaker The suggested
Mario Kart retrospective The Mario Kart is a fun retrospective format that allowed teams to focus on the things that are empowering them, slowing them down, but also things they wish would be possible or exist. It’s a combination of a retrospective and a futurespective. The Icebreaker This retrospective format does not have a specific
Functional refinement The goal of the user story is clear The value for the end user is clear The user story has acceptance criteria, it is clear when it is done It is clear how the user story will be tested and verified during the development Dependencies with other work items, teams and/or external parties
Preparation The product backlog is sufficiently refined and up to date so that the work can be selected for the next sprint The entire team is invited for the meeting The agenda is determined up front and available for all attendees Stakeholders and/or domain experts are invited if needed The Product Owner has a desired
The retrospective contains setting the stage The retrospective contains gathering data The retrospective contains generating insights The team knows the difference between actions and intentions The retrospective results in one or two action items Action items are SMART The retrospective contains a closure The action items of the previous retrospective are updated The focus is
The team gives a recap of the sprint goal to set the context for the review meeting Completed work items are shown to the Product Owner (and stakeholders). New insights are discussed Optional: work in progress is shown to get early feedback The team evaluates if the sprint goal was achieved. Important observations are discussed
Every team member shares what he did yesterday that brought us closer to achieving the sprint goal Every team member shares what he will be working on today to bring us closer to achieving the sprint goal Every team member shares what is blocking, impeding, or taking him longer possibly preventing us to reach the
The “Build your own Scrum Master” retrospective format was initially made by Carsten Lützen: Build Your Own Scrum Master with Carsten Lützen – YouTube. Jan-Willen Rutten made a modification by adding a 4th category to it. You can read the full explenation of the format on this post from Jan-Willem: (3) How to: Build Your
One thing retrospective The “one thing” retrospective format is a very simple but effective way to have the team reflect on the things that make them happy in the team, and also on what they would still like to improve. The focus is broader than just one sprint. The Icebreaker The suggested icebreaker for this
