Lacked: What seemed to be missing or could have been done better during that project? On reflection, this might be something that was unclear or needed to be implemented to ensure that things continue to run smoothly.These are any new discoveries, points of interest or highlights can be technical (new way for testing) or non-technical (a new effective way to keep stakeholders informed). Learned: What things did the team learn from experiments, testing, and conversation and from working with each other.Liked: What did the team like and enjoy about the project? This could be anything from a process, an achievement, a particular team action or even a technology that went better than expected.This one highlights the positive as well as the negative. 4 Ls (Liked, Learned, Lacked, Longed for).Problem Areas: This that did not go as well as we had hoped during the sprint that just ended.Accomplishments: Things we finished during the last sprint that we’re particularly proud of.Lessons Learned: Key takeaways from the sprint that just ended.Future Considerations: Things that we’ll need to think about/focus on the next project.It is a mix of retrospective and futurespective, which uncovers process risks. This one allows you to think forward, with an eye on the past. FLAP (Future сonsiderations, Lessons learnt, Accomplishments, Problem areas).We recommend choosing templates that will focus on what the team achieved or liked and also leave a space for future improvements.

3 - Focus on lessons learnt and future considerations for the Main StageĪs it’s final retro, one of the most important things is to summarise accomplishments and lessons. You can read more about health checks in the article Team health check: how Timbo can help in getting great insights or visit our Youtube page to watch the recording of the webinar Agile team health & morale checks. Have you managed to improve that or the end was tough and challenging and brought more room for improvement? Check what were the initial results, best results and worst one. If you’ve been tracking team health, team morale or team remote adaptation metrics during the project, it would be great to see the dynamics of it from sprint to sprint. 3 - Measure the final health check and compare it to your baseline That will help to set a context of inspection & adaptation. This way you will remember a lot of important achievements or lessons with no judgement yet. You can also try and draw just one timeline together where you as a Facilitator will ask the milestones from the team and place them on a timeline. Read them out loud or ask the team to comment. They can remember any milestones that were important to them. Ask them to draw a personal timeline of a project. This will activate their retrospective thinking and set the tone for the next exercises 2 - Build the timeline of the project to remember all important milestonesĪs long as you’re recalling not only the last sprint but the whole project the team might have already forgotten how it was. Ask them to describe a project in One Word. Try warming your team up with something quick and simple.

Explore overall team process and list improvementsġ - Break the ice with One Word technique.

Summarise achievements and success stories.

Let’s look at the objectives that you might need to include into your last retro. Just pick up those you feel your team needs or risk to take them all and still have your retro within a time box.

So that you can look at your inspect & adapt objectives not only from the point of the last sprint but the whole project. We’ve gathered the latest retro objectives, best practices and gaming techniques. There’re quite a few things you’d probably like to recall during your final retrospective. Everyone’s been working hard and your last retro should be a special one. Congrats to you and your team! That must have been a long and challenging journey. If you’re reading this article, you might be approaching the end of a project or phase.

Project retrospective