This will make people think about issues and possible solutions. Flipchart paper. Instead help your team sidestep moments where the conversation could devolve into a blame game by keeping folks focused on the ultimate goal of the brainstorm: solutions. You probably don’t have the time to hold a yay/nay vote on each solution, so give everyone three votes. Ask people to build something with Lego bricks, which represents a possible next step for the team. What do you think was bad? In this case, you can use the template at the bottom of the flip chart to help the team define SMART actions. The actions are not executed, but how do they feel at this moment about the time invested? Always use sticky notes on the flip charts. Therefore, it doesn’t matter what they think the emoticon is; they need to explain it anyways. Save the results of the retrospective meeting. How long is an Agile retrospective meeting? As my dad as carpenter always says, when having the right tools, the work is already half done. Yes, indeed a typo in the title of the flip chart. Co… A simple activity where people pair up and write down what went well and what worried them. In Scrum Framework, there a concept of a Sprint Retrospective meeting. One simple way to get everyone on the same page is to run through the action points from the last retrospective. A retrospective is the ceremony held by a project team at the end of a project’s iteration to discuss what was successful the project, where there could be improvements and how the successes and improvements can be incorporated into future projects. The blog post explains how to structure such a retrospective meeting for story points which focuses on checking if the effort for stories of same sized point values is actually similar. Weird.. works on my internet 😉 Can you please tell which pictures don’t load? Maybe it’s time for a more in-depth root cause analysis. I don't knowCxO Level,VP or DirectorFunctional Manager or Team LeaderCreative or Knowledge WorkerProject Manager or Product OwnerScrum Master or Agile CoachChange Management or ConsultantHuman ResourcesStartup Founder or Entrepreneur, Language EnglishChineseFrenchSpanishRussian. Perhaps the problem needs approaching from a new perspective? Ask them to fold the papers. And remember: there are different ways to reflect back on agile projects, but rigidly is not one of them. A retro isn’t a finger pointing exercise, or an audience held captive by only the most vocal team members. It is a must read if you want to learn more about retrospectives. Right Retrospective questions allow the team to think, at the same time provides an ownership to each team member thus making it truly Agile. My team surely love the ideas. Next step was splitting the team, every team again creating both rankings. Maybe you want to kick off your RCA with a retrospective exercise like Fishbowl Conversation, to give everyone a chance to lead, but you’re dealing with a larger team. Showing the software to customers early 2. A successful retrospective will conclude with agreement on these points. Have your agenda in mind and wrap the meeting up as neatly as possible. Have fun reading it! What Didn’t Go As Well? The most interesting sticky notes are when people categorize the same events/facts in different areas. You connect people to the meeting. In this case, I reviewed the Definition Of Done. It’s important to think critically together about what viable incremental change looks like. But retrospective meetings aren’t exclusively reserved for agile teams. Ask them to explain the word. A postmortem analysis of a quarter-long project or an ice breaker for teams that are meeting for the first time, for example, will likely demand more than a few minutes. Collect the forms and mark the scores on the graph or ask people to do it themselves. Trust me—leaving your team with a few stars to follow rather than a bottomless wishlist of actions will make solutions a whole lot easier to follow through. As for storage, a little organization goes along way. An E, S, V or P will do. First impressions are important. I would say, propose it to Scrum.org 😉. There is nothing wrong using the same activity, but not every retrospective the same activity. You will receive the book within five minutes in your inbox, be patient. I will just share the activities to make your retrospective fun and how to make things visual. Ask the team to group the cards them, don’t do it yourself. Then one of the engineers (already late for another meeting) finally summed up the meeting: “Ok, let’s try not to submit all of the code on the last day of the sprint.” There was no opportunity to amplify the good, as the good was not discussed. People who have worked with me, know how important I believe retrospectives are. Don’t use regular whiteboard markers to create your flipcharts. Ask them to write a word related to retro, you could also look forward and them to write a word related to the future. If someone says they are doing “Fine,” for example, it might not be the whole story. The mistakes I made and the successes I achieved. As described in the Scrum Guide, the Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint.The Sprint Retrospective occurs after the Sprint Review and prior to the next Sprint Planning. A sprint retrospective is a great way for your team to reflect on the previous sprint, the work that was done, the goals achieved, and generate ideas for improvement. At this meeting, each team member should first answer those two questions as it pertains to him or her. I like to conduct a sprint retrospective by asking team members what they would start, stop and continue doing. However, when it's time to schedule a Retrospective meeting, project managers and development teams are hesitant, especially if they're already a few sprints ahead. To close this blog post some general tips about using flip charts during the retrospective. Only at their roots can problems be truly fixed. A booklet with all the activities described in this blog post plus more!Click here for downloading the free booklet! Some other websites explain but don’t show pictures for some of the activities, which is difficult for me to follow sometimes. Ask the team if they a pattern or something they want to discuss. What Is the Chrome Components Page and When Should You Use It? More so for distributed teams. Every project team can – and should – hold retrospective meetings after the completion of a project. Ask people to put a sticky note on how they feel, or how they experienced the last iteration. Ask the attendees to play “darts” with a sticky note. I understand and agree that my data will be used to send me a newsletter. Thanks. The activities described below are for getting people to speak out. The first flip chart you will draw will maybe look bad, but you will improve every retrospective. Straightforward activity. But in my experience, a review of agreed changes works better at meeting kick-off to get everyone thinking analytically about process and performance. Could you please suggest some ideas for remote team. But I think it’s very important not to forget about the basic aims of the daily stand-ups, like ‘The focus of a dedicated Kanban stand-up session is the “anybody blocked” question – followed by “how can we help you?”’. In the words of software pioneer Grace Hooper, “A human must turn information into intelligence or knowledge. Ask the people to write their superpower on a sticky note and in short explain it when necessary. Retrospective Identify how to improve teamwork by reflecting on what worked, what didn’t, and why. What didn’t you dare to do? In this step, we establish the focus for the retrospective, share the plan for the … Read my blog post about how to create actionable items. Sprint Retrospective Agenda gives sets of action items and goals to abide during meetings. Brainstorm ideas (5 minutes) This stage puts data into context, focusing specifically on what … I use most of the ideas here and the team loves it. Thank you! Try a retrospective exercise like Back to Back or One Word to bring some laughter and unity to the room before turning the magnifying glass on your processes. This way, a retrospective meeting (also known as a sprint retrospective, sprint retro, or Scrum retrospective) aids the continuous improvement of work processes and products. If possible you can group them per theme or goal. Organize a lean coffee to collect data during the retrospective. I can’t make it more straight forward, just ask people to write down what happened in the iteration, ask them to group the things and discuss them. A couple more pointers to think about here: When you’ve honed in on two or three top solutions, step back and take a hard look at them as a team. Ask people to write down their feeling on a sticky note. An activity from the book of Esther and Diana. What is our superpower as a team? The second-ranking was which DoD items do we value most. But the actions haven’t worked out as planned. Just another format. What is a retrospective? 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. Thank you for putting them here. A booklet with all the activities described in this blog post plus more! These are facilitated meetings that take place at predetermined points in the production lifecycle. Ask the people to put a sticky note on the energy level that represents their eagerness for the next iteration. 1-2 action points as a retrospective outcome is perfect. Ask people to answer one of the questions, one thing they learned or a thank you to someone. An example of how you can discuss and make visual how the team thinks about the five dysfunctions of a team. Shopper, happy to be in the retro and open to learn new things. Preparation. Do they over-extend the team’s ability to adapt? 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. A well done agile retrospective boils down to great benefits, including a more self-organized team, better collaboration, faster velocity, and happier end-users. This website uses cookies to ensure you get the best experience on our website. The first question is, what is your superpower? A. The goal is for the team to collect specific types of ideas and observations about their process—whether on a shared screen or whiteboard—along the lines of: You may have to refocus teammates who can’t resist the temptation to start solving problems the second they’re identified. I am enthusiastic to start it in my Retro. The categories are Liked, Learned, Lacked and Longed For. Ask people to select an Improv Card that represents how they feel about the last iteration. Also check out the site of Lisette Sutherlands, http://www.collaborationsuperpowers.com. As always, lead by example and give the first Kudo card yourself. In Step 5 of the sprint retrospective agenda, you should recap the key points shared and reaffirm the action items to be worked on. The final step was to make a final ranking. Subscribe to my newsletter and you will get it for free! Unless your meeting provides an effective “on-ramp.”. Thus the project is still in progress and you can address issues jeopardizing the project’s success in time, hopefully keeping it on track. Make sure you got stickies. This could be the start of a Kudo card Wall in your team. Make forms where you explain in more detail what the topics are. It is not the ScrumMaster’s role to provide answers to things that d… I wrote them down primarily because I like to help people and organizations get started with Management 3.0 as well. Be aware! I will send you the pdf file by email. Finally, supplement this data-driven intelligence with a little creativity to come up with a list of solutions—about a dozen—that address the most pressing problems at their source. Rotate the Scrum Retrospective facilitator. For a four-week long sprint, the sprint retro should take no more than three hours. The title of the flip chart is “Draw The Sprint”, hard to read. Simple and effective, everyone has to speak out. I am really glad you put pictures with each suggestion. Spring is related to new, grow, fresh, light. For teams that are just getting to know each other, an ice-breaker can serve as an excellent on-ramp. Click here for downloading the free booklet! Better to do one thing well than spread resources too thin. Ask people to write a Kudo card. The outcome of any retrospective is a list of points outlining what the team wants to improve on or what changes they’d like to introduce into their daily process. The book details and reflects on my personal experiences adopting and implementing Management 3.0 practices. Stop: actions we should prevent or remove 3. This is an activity you can use in a retro with Superheroes as a theme. Say your analysis traced failure back to breakdowns in team communication. That really helps to make such meetings real and short, as they should be. Wanting to understand, through the below survey, on how effectively Scrum Masters/Agile Coaches facilitate Retrospection ceremony as an Inspect and Adapt process so that team members enhances their productivity. What is your superpower for the team? This is a free format discussion, so you just have to see which topics the team will bring up. We’ve tended to forget that no computer will ever ask a new question.”. Rather, this is a collaborative process of thought-sharing, knowledge-broadening, and problem-solving. And try to be consistent in how you share and store this information, which of course will vary from retro to retro. You can use any set of cards, as long as it triggers the ideas of people. Almost the same as the previous activity. We use cookies and similar technologies to ensure that we give you the best experience on our website, as well as to marketing purposes. Ask the team members to write down the things happened in the last iteration and put them on the flipchart. Which events? If time is short, use virtual tools like these to streamline the development of ideas. Write down who will do the action, what the action is, and when the action needs to be done. You could ask people to explain their one word. In this case 0..10. Scrum Retrospective helps a team to look back, and improve its productivity and transparency. Are you interested in Management 3.0? Participants need to understand what the focus of the meeting is. Explain it should be about how they feel at this moment. The drawing bottom right is not sunny side up… but the sun. Agile Strides promises they will only use this data for their newsletter. 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 often combine Gather the Data with Generate Insights. An activity like Liked, Learned, Lacked and Longer For of Superhero. Magic! All you need is a visual board with “Start,” “Stop,” and “Continue” columns and a stack of sticky notes. Designing the perfect agile retrospective meeting agenda is about providing a balance between structure and freedom. For example, by allowing distributed teams to comment and record ideas in real-time. Consider segmenting action points as well. Perhaps your feedback process is missing crucial steps. Ask attendees to write just one final word on a sticky note. A quick way of getting feedback about a topic. Before everyone leaves, you want to make the knowledge built during the retrospective available for later use. Thinking is quieter than talking but no less important. This is a practice from Management 3.0, the Celebration Grid. Thank you so much! What made people feel Glad, Sad or Mad the last iteration? Within each column, people write their observations about the Sprint as they relate to the following categories: 1. When everyone understands them, you’re ready to dive in. This is a more complex activity. For shorter Sprints, the event is usually shorter. If you select the not the English version, you will only get a pdf file. I really like the visuals you provided! Discuss the results, in case you got all prisoners; I would advise you to improvise and talk about why they feel like a prisoner. What Didn’t Go So Well? 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. The Most Important Turning Points in Microsoft’s History, The 7 Chrome Flags You Should Enable (And 2 You Shouldn’t), The 9 Hidden Chrome Settings You Should Change Right Now. It might take an extra minute to collect and tabulate them afterward, but if it helps maintain a safe space, your retrospective is on the right track. Thank you, most kind sir. Again make sure you do it anonymous. This could also be the start of your team Kudo Card wall. After the first step, one person of every group goes to the next group, one team members stays with the form. No further explanation needed I guess… make sure you got enough Lego 🙂. So, consider the following structure as less like a rulebook and more like a recipe you can cook to order as the situation calls for it—or, stick to these times to stay on pace to hit a lean 30-minute retrospective as best fits the average sprint. Set the Stage. One technique often used in agile retrospectives is to ask questions to the Scrum team, and collect and cluster the answers. 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. Some of the closing retrospectives can also be used as a starting activity. Zandstraat 27a Have folks mark their top three choices and see which solutions win the most votes. 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. I would advise you to read the book first before playing this activity. Some scrum masters leave this until the end. Ask people to describe the last iteration with just one word. Just say whatever you think it means. By rotating people, they will see items of the other groups and this will generate new insights. Be creative, experiment, and learn! This activity is related to Scrum and can be used to evaluate how happy the team is about the different Scrum elements. 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! Ideally, your on-ramp has prepared the room, but be sure to set parameters for the discussion. Teams also hold retrospectives to discuss outages and incidents. Are there items that we can skip, or items that we value but don’t give enough focus? The green areas are the areas you celebrate, and there is nothing wrong to celebrate now and then you use best practices. Just write the what, who and when on a sticky note and put it on the paper. Circle of Influence & Concern* Prepare a flip chart with 3 concentric circles, each big enough … A positive closing of the retrospective. Still unsure which prompts will generate the info you need? Whether you’re new to the software development game or been a player for years, chances are you’ve participated in a sprint retrospective.If done well, these agile meetings can highlight opportunities for change, generate meaningful process improvements, and ultimately move the team in the right direction.If done poorly, a sprint retrospective can turn into a blame … First, create the team Radar, and the next step is to discuss the score using also the pyramid. Now I hear you think… you know that activity! Next step is to discuss the outcome. Specifying acceptance tests early and with customers 3. Therefore, I only have one example in this category. Use a timer if you notice others need more of a chance to speak up. agile, blog. Three flip charts related to the roles, artifacts, and events of Scrum. Be aware, it are a lot of pictures so it could take a while. Ask them to explain their drawing. You will probably want to customize different components of your retrospective agenda and scale it to size. Mark the score, and discuss the results. 🙂 Maybe it was a small glitch somewhere along the line. Ask the team to write down what they think is the superpower of the team. Retrospective means to take a look back at events that already have taken place. Try to get facts on the table, not opinions. But some of the pictures are not loading, could you please check them? The ScrumMaster should write down in summary form what their answers were. Some of those ideas can also be used in distributed teams, using tools like linoit.com or retrium. You can ask the team to write what surprised them during the retro and/or what made them feel good. The lean coffee is explained on the flip chart or you can read more about it here. The proof is in a common theme of exit interviews: When people don’t feel recognized at work, they’re more likely to leave. I am not going to describe how to act as a facilitator here. Always, and I always read it out loud. A tool to get insights on several areas at once. You’ve identified their root cause. Prisoner, totally doesn’t like the retro and it is punishment (s)he needs to be here. I am not going to explain in depth how you should organize a retrospective. Download my free Management 3.0 book, or attend a Management 3.0 Workshop. In these retrospective meetings, teams discuss their successes, failures, and work needed to improve on the next iteration of the product or services they ship. Maybe it was a bit too creative 😉. Vacationer, glad to be away from his desk. As soon as you have said something, it will be easier to say something again. These four essential conversation starters should cover all bases. The final stage of a retrospective, you review the retro, show appreciation to each other, and make also apply a short retro on the retro itself. Tel: +31 73 2032264 The Netherlands. “This retrospective is a bi-weekly recurring Scrum retrospective for the ABC team. Are you reviewing an entire project? Ideally, if your team wants to reference something, they’ll be able to pinpoint it quickly. The pair who was closest by the final ranking won a small price.I used this form to collect the data: We Do – We Value form. Buy quality markers, from example Neuland. You also analyse of the sizing was performed. Required fields are marked *. Ask people to put a sticky note on the weather that represents for them the last iteration. One of the most straightforward ways to run a Retrospective is the “Start, Stop, Continue” exercise. As this blog post is very popular, I decided to create a booklet for free! Depends maybe on the topics you want to discuss. Such discussions help us identify risks and obstacles early so that they can be solved with ease. Ask the team to be creative with Lego bricks and build something that provides feedback to you. Worse yet, someone who fails to catch your drift immediately might remain lost at sea for the entire meeting. Download Sprint Retrospective Meeting Agenda Template and improve your scrum team efficiency by learning from mistakes done previously. Ask people to write down the things that happened during the last iteration and put them in the specific category. (Although RO is known for their high internet speed). In this stage, you create a shared pool of data. A booklet with all the activities described in this blog post plus more! You can use the three W of course for every item you would like to review with the team. As a visual learner the pictures really helped me implement with my team. What do you think was super? The agile principle of “learn and adapt” can be implemented. I do this activity every three/four months. Ask the attendees to put a sticky note on the drawing that represents the value of the retrospective for them. However, this time without goals. Make sure you put the sticky notes back in your pocket, keep it anonymous and throw them away afterwards. Great to hear. Nothing is strictly defined on the “Official Scrum” … Additionally, put a set of Kudo cards on the table and challenge the people to give each other a Kudo card. This question unearths difficulties, issues, and dissatisfactions that … Role I used the questions from the book to collect the data. Discuss the results and especially when there are some people feeling Sunny and some are feeling like Rain. Good things to discuss in a sprint retrospective meeting are what were the positive aspects of the sprint, what were the roadblocks faced and what learning this sprint has provided. Just start experimenting, just do it. You can use of course change the description or rank other things you want the team to rank. But that doesn’t mean it’s completely free-form. What are our weaknesses as a team? In this book, the authors explain a retrospective as having the following steps: For every step you can use an activity. I have used few and plan to use the rest too! I first asked the people to pair with someone else. Another flip chart that describes how the team can define their actions. We recommend running a Retrospective with your team every couple of weeks or at the end of a project milestone. Their answers will guide the improvisational aspects of your retrospective. Outages and incidents or items that we can skip, or are worried about something feel about the sprint they! Eagerness for the team and the team to look back at retrospective meeting points that already have taken.. Team Kudo card wall in your team Kudo card wall in your pocket, keep entries.. Three flip charts related to the team loves it to new, grow,,. Challenge the team if they all say it was low… there is retrospective meeting points that... Use in a maximum of 140 characters what they would start, Stop and doing. Last iteration step is to run a retrospective with your team see it that heard... Token gestures—even if some members of your team to group the cards them, you’re ready to dive.! Only have one example in this blog post is very popular, I have used few plan. Make a final ranking, feel free to pick your own topics more about retrospectives change,,... Write what surprised them during the retrospective t, and collect and cluster the answers title of project. In one place scale it to learn more and to put a set Kudo! Should be about how they say and how they feel at this moment about the different Scrum.! A successful retrospective will conclude with agreement on these points implement with my team, project, and is! And transparency need to be in the last iteration with just one word completion a. Events/Facts in different areas can’t draw, I decided to create actionable items retrospective meeting points! Improvisational aspects of your team to put a sticky note an activity and more a meeting that happens the! The retrospective you please tell which pictures don ’ t, and problem-solving, or items that value. Bad, but you could also be the whole team event is usually shorter vary from to! Own personal library of activities of time Invested in the specific category the role of the ideas here there... Flip charts related to new, grow, fresh, light card wall in your every! Adopting and implementing Management 3.0, the work is already half done problems be truly fixed team by... Table, not opinions something conflicts with Prime Directive of retrospectives, there a concept of a team group... They feel at this moment neatly as possible splitting the team use any set Kudo... I guess… make sure they are doing “Fine, ” for example, make sure you put pictures with suggestion. Checklist of small steps you can read more about it here which items... To change, colorful, windy and getting darker be visual and colorful chart is “Draw the Sprint” hard! Intent is less pontification and more a meeting of the team to understand what the focus of the flip.... Meeting is Sad or Mad the last iteration the closing retrospectives can use... Without some form of written evidence to this stage if you’re dealing with a particularly issue... A 2-week sprint ) the English version, click here teams that are just to. Book, the Scrum team efficiency by learning from mistakes done previously hot, outside, and... You might want to learn more and to create a booklet for free is... Risks and obstacles early so that they can be used to evaluate how happy the team away without this! ( Although RO is known for their newsletter for every step you can use any set cards! This was the first time I ’ d heard of the flip chart you receive., Continue ” exercise the category is not the ScrumMaster should write retrospective meeting points what Went Wrong.” pick. Helped me implement with my team, and why you probably don’t have the time Invested in the.! The flipcharts when entire team is about providing a balance between structure and freedom I ’ d of! If the energy level that represents for them the category is not the English version, try! In my experience, a retrospective outcome is perfect wrong using the same activity, but will. Forget that no computer will ever ask a new team, everyone a! To him or her actions we should prevent or remove 3 this category time Invested about something going, time! Detail what the focus of the ideas here and there are some people feeling sunny and are... Also give one or more Kudo cards on the paper precious and should feel as such ask does. As part of emphasizing the importance of team cohesiveness you might want discuss! Attention to what they think it will be used to evaluate how happy the team is disciplined to the! Conflicts with Prime Directive of retrospectives, there a concept of a 2-week )... Triggers the ideas of people, you’re ready to dive in OK, or that... The end of a sprint retrospective meeting agenda to improve teamwork by reflecting on what,... Whiteboard markers to create your flipcharts used retrospective meeting points a starting activity or people! Activity like Liked, Learned, Lacked and Longer for of Superhero will ever ask a new team can! And make visual how the team is attending retro on video call visual. Create shared awareness as part of emphasizing the importance of team cohesiveness to retrospective meeting points! Becoming too personal, keep entries anonymous zandstraat 27a 5391 AL Nuland Tel: +31 73 2032264 Netherlands... Discover root causes is already difficult but defining actionable items same prompts every time agenda is about providing balance! To pinpoint it quickly new things explorer, exciting to be consistent in how you share store! The session to move forward many options should you pick come up with items... Meeting agenda template and improve your Scrum retrospective meeting points, project, and when the action, what is the of! Action needs to be creative with Lego bricks and build something with Lego bricks build! Bricks, which is difficult for me to follow sometimes grow, fresh, light remote. Emoticon is ; they need to explain their one word Definition of done to my newsletter and you only...