Skip to content

Final retrospective for a team

Usually a retrospective is to look at the past and then think of a way to improve your team’s process going forward. But what if this is your team’s last sprint together? Do you have a retrospective?

We were posed with this problem at a client. We had trained them a year before and they had successfully used Scrum for that year. Now the company was restructuring and this team was going to no longer exist – each of the people would be joining other teams. Their manager wanted a retrospective as she was hoping the team had learned some valuable lessons, and wanted them to take them with to their new teams.

We planned and ran the retrospective and we were very surprised by just how well it ran. It was a great way for the team to conclude their time together. Below is the plan we had for 90 minutes.

The team was 6 people plus the manager so 7 in total. We felt it was important for the manager to be part of this retrospective, however she was briefed to let team answer any questions before she did so that there would be less anchoring during the retrospective.

[5 min] Manager to set the stage. Why are we running their last retrospective and what is the purpose of it (as they are disbanding).

[5min] Check in: If this team was a household item – what would it be, and why?

[3min to think, 5 min for feedback] For each person in the room we stuck up an A4 piece of paper. Then we asked everyone to move around the room filling in the papers with: What does this person bring to this team? Think of strengths, skills, characteristics.

[10 min] Create a timeline. We made this for the year the team was together.

[15 min] Populate the timeline with events like training, conferences, major events – use only yellow stickies, one event per sticky.

[10 min] Populate the timeline with things you learned – use only blue stickies, one thing per sticky.

[5 min] We asked them to think about the future, and what the one most important thing is that they would like to take forward with them – using the timeline to remind them of everything that happened.

[5 min] Next we reminded the team of the agile manifesto and more specifically the format. We then asked them to craft a statement “I value … over …” based on the thing they want to take forward, and write it on an A4 piece of paper.

[10 min] Ask each person to read out their personal value statement and explain why

[10 min] As a team we asked them to create a “manifesto” poster with all of their value statements on it.

[5 min] To close the retrospective we had a ball toss, with the question “One word on how you are feeling about your new team”.

If you do use this plan for a team that is disbanding, please leave a comment to let us know how it goes.






3 thoughts on “Final retrospective for a team”

    1. I want to conduct a final retrospective with similar input thoughts. The things I miss in this post are some more detailed description of activities, especially their form, how the outcomes looked like (for better imagination), what were the reactions of the team members, what were the challenges you had to face…

      I am thinking about following version:
      1. (2 min) Introduction – similarly as in the post above
      2. (5 min) Team existence summarisation and look back – graphs with sprint fulfillness (yes/no), velocity, velocity ratio, number of done stories and list of completed projects… + some statistic data around mentioned graphs (min, max, average, median, modus)
      3. (2 min) Write down at least 1 strength of our team on a yellow post-it.
      4. (2 min) Write down at least 1 team success on a green post-it.
      5. (2 min) Write down your personal learning/success you gained in the team on pink post-it.
      6. (10 min) Ideas/comments sharing.
      7. (5 min) Describe in one word your feeling about your new team.
      8. (2 min) Thank you for your work and good luck in your new team.

      1. Hi Martina

        Your plan sounds great, good luck, and let us know how it goes. We didn’t want to share images of what the team actually created in this retro because it was very personal for them, but they all enjoyed it and it was surprising to see how often people didn’t know what characteristics their team mates actually valued in them. I think everyone left the retro feeling valued and uplifted.


Comments are closed.