Artificial intelligent assistant

How can I organize a more engaging Sprint Retrospective? I'm going to be organizing the retro (Scrum) and I would like to get more experience on it. I have assisted to some and have organized some as well, but the format always seems to be | What went wrong | What worked --- --- | What should continue doing | What should we stop doing I will like to do something else or another format, but I'm not knowledgeable enough on the subject to know how to proceed. **TL;DR:** I will like to get feedback from my team during a the retrospective in a way that it's fun, engaging and productive.

There are a lot of different options for retrospectives depending on what you want to get out of them. The book Agile Retrospectives by Diana Larsen and Esther Darby is a great place to look.

I also highly recommend looking at Retromat for ideas.

As a final piece of advice, I would consider using the 5-stage retrospective talked about in both of those two resources. While it may feel a little over-structured and take a little longer, it ensures that the format of the retro is solidly geared towards valuable outcomes.

xcX3v84RxoQ-4GxG32940ukFUIEgYdPy 5f1fcd1e27bc75be037ab637be9bc1d9