 Hi everyone, I'm Zana from Product School and in this video we're talking about product retrospectives, why they're important and how to create your own using the Product School template. Retrospectives are important for product teams to achieve continuous growth, be able to learn from their past failures and identify issues early on. In order to do that, PMs need to run focused and scoped retrospectives and leave team members with actionable items for the future. In this template, in the second slide, you will find resources that you can tap into to help you run your retrospective and you can always reach out to the Product School community here at the bottom if you have any questions. Now in this retrospective, in this retrospective template, you can find two types of templates. You'll have a sprint retrospective and then you have an incident retrospective. A sprint retro will only look at the last sprint and identify ways that it can become more efficient with actionable items for the future. However, an incident retrospective will look at a previous history of retrospectives that the retro lead will walk the team through and identify measurable items against that. In the first sprint retro, it will look something like this. In the first slide, you will identify what type of retro you are running and what the product or feature is. And then you'll give everyone 10 minutes per slide. So in the first slide, you will give team members around 7 to 8 minutes to write down their achievements and then 2 to 3 minutes for them to vote. Same thing here. You'll identify your challenges and then 2 to 3 minutes to vote. What ideas the team might have. You'll create this kind of safe space for everyone to write down their ideas and feel comfortable sharing how they want to take action. And then in the last slide, the PM will, based on the voting and all the data gathered during the meeting, you will be able to identify key takeaways, interaction items, jot down due dates and metrics you'd like to measure against. Same thing for an incident retrospective. The only difference is that in the first slide, the retro lead will walk the entire team through a history of retrospectives and be able to pinpoint accountability and identify next steps as well. Same thing here. You'll go through the same process with all these slides and identify next steps and takeaways. And that's pretty much it. In the last slide, you have an extra video that you can watch. If you have any questions, you can always reach out to the product school community, as I said before, and feel free to tap into the product school free resources page and YouTube channel for more information on this topic. Hope this was helpful and thank you for watching.