If you are using Scrum and you have come to the end of a sprint, its retrospective time! But after a few sprints the same formula or Start/Stop/Continue starts to wear a bit thin. The team start to think this event has less and less value but your Scrum coach and the guide tell you its mandatory!! What should you do?
We've all been there. It's Retro Fatigue :(
The event is designed to let your team share their views on how to improve either the process or the product you are working on. To make the next sprint easier or more efficient. After a while using the same formula, it starts to lose its impetus and then its overall value. The team get bored.
I've worked through this with my teams and we have managed (through hard work and careful choices) to keep our retros fresh, productive and above all, the team keep improving.
I'll share :
- 5 key tips and tricks with you over 30 minutes
- Then give you 10 ideas for really useful retros that have worked for us
- I'll also give you links to 3 awesome websites that have inspired me (even if its just to show that there is more to a retro than just start/stop/continue
Please log in again. The login page will open in a new tab. After logging in you can close it and return to this page.