Visualization Exampleīefore we start the first activity, I always show this flip chart. As soon as you have said something, it will be easier to say something again. The activities described below are for getting people to speak out. In this step, we establish the focus for the retrospective, share the plan for the meeting, establish or re-purpose work agreements, and get every person in the room in the meeting. As I said, retrospectives (any meeting) should be colorful.Īre you interested in Management 3.0? The Modern Approach to Management in Agile Organizations? Download my free Management 3.0 book, or attend a Management 3.0 Workshop. However, I just do it… and people seem to like it OK. I always said I can’t draw, I am bad at drawing pictures, really. Note that most activities come from Retromat, some from the book mentioned earlier Fun Retrospectives, some I found using Google and some of them I created myself. To make it fun, it should be visual and colorful. I will just share the activities to make your retrospective fun and how to make things visual. I am not going to describe how to act as a facilitator here. OMG… Retrospective Hell created by a facilitator who doesn’t know how to create Retrospective Heaven… A retrospective should be fun, energetic, surprising, and people should love it! When you talk to those teams, they often complain that the retrospectives are not interesting anymore, they are boring, not productive, and are considered as just another mandatory tiresome meeting. Worst case, people already come in with their findings written on a sticky note to put it on the board as soon as they enter the room. Now I hear you think… you know that activity! Good point! Many Scrum Masters, or facilitators, always use the same activities during the retrospective. For example, for the Gather-The-Data step, you could use “What Went Well and What Went Wrong.” Closing: don’t just walk away but close the retro with an activityįor every step you can use an activity.Decide What To Do: what are experiments that could help us to improve 1% a day.Generate Insights: analyze the data to find root causes.Gather The Data: what happened, make sure everyone has the same picture.Set the Stage: make sure everyone feels safe and is in in the retro.In this book, the authors explain a retrospective as having the following steps: It is a must read if you want to learn more about retrospectives. I really recommend, and I mean really recommend, that you read the book Agile Retrospectives: Making Good Teams Great by Diana Larsen and Esther Derby. I am not going to explain in depth how you should organize a retrospective. We can have a lot of discussion about Agile and what it stands for, but for me, when you have no regular retrospectives, things are definitely not Agile. Retrospectives are the backbone of every team, project, and organization. People who have worked with me, know how important I believe retrospectives are. In this blog post, I want to share some ideas for hosting agile retrospectives, including some ideas on how to make a retrospective visual more attractive. As this blog post is very popular, I decided to create a Retrospective Book for free! A booklet with all the activities described in this blog post plus more!Ĭlick here for downloading the free booklet!
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |