How to run a project retrospective

It's super easy to move on to a new project as soon as one is finished. However it's valuable for the entire team to get together and reflect on how the project went. In this video I share how to run a successful project retrospective and what you'll need.
If you're new here, hi! I'm Femke and I'm a product designer at a large tech company, making videos about design and research. On the side I co-host a podcast, travel and enjoy cooking.
----------------------------------------------
// LINKS (affiliate)
Timetimer: www.amazon.com...
Sharpies: www.amazon.com...
Post-its: www.amazon.com...
Voting dots: www.amazon.com...
// MORE
Portfolio: www.femke.co.nz/
Blog: www.femke.co.n...
Podcast: www.designlife...
// SOCIAL
Twitter: / femkesvs
Instagram: / femkesvs

[@RareQuestGiver]

Hey Fem! The retros I've been involved in have mostly the same intention for exercises but with the exercises slightly different. We tend to do the "Sailboat Exercise" where we list out things (on post-its) that were our "Wind" (went well), our "Anchors" (didn't go so well, held us back) or our Rocks (risks to the project) and then vote on them. If we don't do the Sailboat, we'll simply write down what we should Start Doing, Keep Doing or Stop Doing. Both of these I find very helpful!

[@KonradKustosik]

Great video ! very helpful and congruent. Helped a ton

[@femkedesign]

Glad it helped!

[@ayushshakya5552]

By Voting did you mean giving votes to the "What could have gone well" section?

[@Diicasti]

Do you use Agile? We do, so we have a Retro every 3 weeks! They vary, is not always what went well and what went wrong, but they are cool. I feel like Agile is too many meeting though :P

[@Diicasti]

femke at the beginning of the project yes, because changes were offered for the following sprint. As we are arriving to launching stage, there’s fewer space :( I don’t know if agile is good or bad for design

[@nabeshane1726]

Most Agile methodology suggests having a retrospective for every sprint which is probably what you are dealing with. The length of the sprints may vary, but are never supposed to be more than 4 weeks. This means that, by default, you would have a retrospective once every three weeks. With that in mind, one of the main principles of Agile is that it was designed to be flexible. This kind of constructive criticism is exactly why we have this retrospective. That said, the default Agile framework does not work best for every company. Maybe suggest doing a retrospective every other sprint because you feel that it would allow you to devote more of your time to meeting your customer's and/or Product Owner's (and by proxy, Stakeholder's) needs. You might even add in that the extra time between these retrospectives would further allow you to analyze issues and come up with effective solutions as you observing how the team works together for a longer period of time.