![]() Make sure everyone knows that there should be no blame, judgmental comments, or blatant negativity. Discuss how the retrospective will run and what the goals are. Setting expectations and creating a safe space for sharing - Before you begin any retrospective, get everyone in your group on the same page by laying some ground rules. Using a model can help keep things fun, organized, and enhance team participation. Model - There are a lot of different models and templates that you can use for sprint retrospectives. For example, a two-month sprint might require a half-day retrospective, whereas a week-long sprint might only need 30 minutes. The length of the meeting will vary depending on the length of the sprint. Timing - Sprint retrospectives should happen immediately after the conclusion of a sprint. There are four key things to keep in mind in order to run a productive sprint retrospective: Make a plan for improvements on the next sprint.Discuss the data and insights and make action items around them.Gather data and insights from their team (what went well, what went poorly, etc.).A Scrum Master will gather together all the critical stakeholders of the sprint and: If you’re not familiar with the basics of running a sprint retrospective, here’s a quick rundown:Ī sprint retrospective is an in-depth review meeting that takes place immediately at the end of a sprint. Luckily, in this blog, we’ve done most of that work for you! A quick recap of sprint retrospectives This can (and should) be 50% of the work in running an effective review. To get the best possible information and action items out of a retrospective, you have to start by finding the right sprint retrospective questions to ask. But concentrating solely on results misses half of the equation - we’d argue the most important half! (For more inspiration on Retrospectives, have a look here).When it comes to holding a sprint retrospective, the Scrum Master’s primary concern is often what the outcomes of the exercise will be. Give the retro form a try and let me know what you think! If used for part 2, each team member will throw the dice a couple of times, but we dig deep into some of the answers to discover which actions we can take to improve.īoth ways work and the game element keeps the retro light and fun (my dice is covered in foam, making it bounce around a bit). The answer sometimes lead to insights what is going on in people’s heads (at least for me) and sometimes to some discussion. When I use it as part 1, I typically run it a two or three of rounds (optionally: an extra round where people can pick one question themselves they want to answer). I use this game either as part 1 or part 2. My Retrospectives typically consist of three parts:Ģ) Create and select possible actions to improve I like this set of questions (the result of some experimentation), as it combines looking back, looking forward as well as more ‘emotionally charged’ questions. If you throw 6: Give someone a compliment If you throw 5: Name something that really frustrates you If you throw 3: I look really forward to… If you throw 2: What I did not like about last sprint was: If you throw 1: What I liked about last sprint was: In my Retrospective, I ask my team members to roll the dice and answer a question: It looked like fun and I decided to give it a try, but I decided against using glue and one of my kids’ fidget spinners (I would never get away with that), so I bought a big dice made of foam instead. That’s why I was immediately inspired when I read Patrick Hellers blog on what he called the Wheel of Retro. If it gets the participants to laugh, it gets bonus points! I am always on the lookout for new ideas or new Retrospective formats I can try. As a consequence, I think putting (a lot of) effort into the preparation of your Retrospective is always worth it. Without it, the team would not be able to inspect and adapt it’s proces and work environment. I consider Retrospectives a key part of Scrum. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |