sprint retrospective ideas what went well examples. The Retrospective allows the team to identify how to work together better and improve the quality of the product. What went well (10 minutes): Give everyone time to talk about the positive aspects of the sprint. I write a few paragraphs, at least as many as the highlights I've picked out in the summary section I discussed above. Retrospectives take the format of a facilitated meeting; although they are typically practiced within an Agile or Scrum process, they can . The above 3 questions may always be . In other words, a sprint retrospective meeting is to find what activities and "things" the team is doing well, what activities should be continued, and what "more" can be done to improve the next Sprint to be more enjoyable or productive. Hold a QA focused retrospective to: Surface feedback previously unavailable to development. Keep: Something the team is doing well and should continue doing. A great facilitator retrospective question has the following characteristics: 1. Sprint Retrospective is a meeting held every two weeks. QA engineers are the team members with the most practical experience in how software actually . Then you give the team some time to write down on sticky notes, what they want the team to start doing, stop doing or continue doing in order to become a better team. by EasyRetro Team Retrospective 0 uses Starfish Retrospective 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. 6. An agile retrospective is an opportunity for agile development teams to reflect on past work together and identify ways to improve. The SM should be responsible for making sure the topic comes up. Each of the paragraphs explains what I think and why, and likely includes quotes from others (that I . These actions are assigned to an accountable team member. For example, Sinnaps, project management software can be used by the Scrum team in undertaking their scrum retrospective, it will allow effective collaboration among the stakeholders involved in the task. It may be tempting to extend these, but you will likely experience diminishing return. Invites input from all participants Every team member brings a unique perspective and experience, and it's critical to involve everyone so that you get a full picture of what happened during your last sprint. You should set the stage so every member of the team feels comfortable. The Retrospective allows the team to identify how to work together better and improve the quality of the product. After each release/iteration, the Scrum Master or Team Leader should hold a sprint retrospective which can also be called an intraspective. The retrospective is a great platform to highlight these lessons and see how they can be used to change/update the Definition of Done. This type of meeting becomes known as a "start, stop and continue" meeting. by Pamela Retrospective 0 uses Original 4 Norman Kerth created this technique and retrospectives as well. Identify and order what went well. During this event, the team discusses how the . This retrospective is productive and collaborative, making sure to include everyone on the team. The purpose of a Sprint Retrospective is to identify potential pitfalls and mistakes, evaluate the past working cycle and define actions that may improve things. In short, a Four . The Scrum Team inspects how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done. Ask what went well and discuss this to increase understanding. Many Scrum Masters, or facilitators, always use the same activities during the retrospective. The team members meet and discuss what the team did well, what the team needs to improve, lessons learned and the action points corresponding to improvement areas. What didn't go well For example, "Finalization of deliverables felt rushed throughout the project." How to fix it For example, "Clearly state deadlines throughout the project; have frequent progress check-ins; build in time to review deliverables so that changes can be made." Have your team do this prior to the retrospective. If you were a musician, you would use this to analyze "What went well" while writing the album you just finished or on the stadium tour you performed. When done well these agile meetings can be a great way for your team to weigh in on the previous sprint by discussing the work that was done and issues that were encountered. The retrospective is a meeting that takes place at the end of a sprint (a timeboxed iteration). It should be the team's safe place. As a SM I make sure my team does this automatically without needing me to prompt them. Definition: A retrospective is a regular meeting during which the team reflects on how team members work together and considers ways to improve that process, based on lessons from recently completed work. Need to balance the UX with technical feasibility when creating requirements. * Not so well - things that went wrong, that need improvement, that hold us back. There are endless examples of action elements as there can be so many topics covered in a retrospective. An Example What Went Well Section. (b). Note that timeboxing does depend on the length of the sprint. The Retrospective is meant for the Scrum Team only; this includes the Development Team, the Scrum Master and the Product Owner. how to add fun or sprie it up when entire team is attending retro on video call. Ideation 17 of our Favorite Agile Retrospective Examples Glad, Sad, Mad Sprint Retro Template Built with Miro the online whiteboard This is a template for design thinking. I like to conduct a sprint retrospective by asking team members what they would start, stop and continue doing. Have each team member use green sticky notes to write down what they feel went well (one idea per sticky). Simply put, the purpose of retrospectives is to help teams improve continuously. Its purpose is to: Examine how the just-completed sprint went as far as people, relationships, processes, and tools. After that, the sprint retrospective should only last 90 minutes tops. Here are some things that can help: (a). Draw three columns on the whiteboard, and label them Well, Not So Well, and New Ideas. The lesson was initially presented as, "Responsive design worked out well on this project." You've got the Wrong People in the Retrospective. 4. During this event, the team discusses how the . Conclusion: For a successful retrospective the facilitator must be organized and come to the meeting with a plan. It is an opportunity to focus on inspection and adaptation. Start - Stop - Continue A Few Tips in Running Effective Virtual Retrospective Meetings. The format of retrospective what went well focuses on the team's strengths and weaknesses and can be used to figure out a plan of action according to what works and what doesn't. Two posters are put up and each team member writes down things that went well and didn't go well and they are then put onto the . But why is post-execution performance analysis important? They are a fundamental part of doing agile "right" and are used throughout medicine, the military, and increasingly in business and work environments. Once the sprint review is over, the sprint retrospective typically takes place. Sprint retrospective template There are many popular ways to run sprint retrospectives, for example, "Start, stop, continue" or "Good, bad, better, best". In my . One of the most common complaints about retrospectives is that people fail to bring up real issues or admit to their problems. Start-Stop-Continue retro. Action Items can be based on the most popular topics suggested in the "What went well?" and "What could be improved?" - with a vote being an easy way to figure out which topics your team values the most and should be prioritised for the next sprint. We have drafted list of sprint retrospective examples to keep the retros fresh and creative. Too many disruptions in the sprint for support issues. QA engineers are the team members with the most practical experience in how software actually . Or use a collaboration document to collect feedback asynchronously and then use a retrospective meeting template to work on your agenda before the meeting. Start with your ideas: Start speaking so that you can express the first thoughts that come to mind, and the rest of the team feels stimulated to follow. A one month sprint might require a three-hour retrospective, for example. Retrospectives Are Boring. If you've spent any time in product development it's likely you've participated in a sprint retrospective. Explore the team and individual strengths with core qualities. If the objective was met, what is there to learn? Second, by explicitly acknowledging the positive, we have the opportunity to be deliberate in ensuring we continue to do what we need to do to keep those positive things happening. Knowing what went well and what could be improved is crucial to improving future sprints. By creating a safe space, retrospectives allow team members to candidly discuss both areas of the project that are . Understand product development in a practical way. Scrum works under the assumption that customers regularly change their minds about what they want or need. Less: Something that isn't going as well, and you should do less of. Example: "The new bug triage process" The goal of a What Went Well retrospective is to focus the conversation on actions taken and to purposefully narrow the scope of inquiry to the extremes of things either going well or not going well. The sprint retrospective occurs after the sprint review and prior to the next sprint Planning. It's a retrospective-- well, not a retrospective, a future retrospective. In essence, members can write their negative/positive feedback on sticky notes or comment threads and discuss and vote on the opinions of the topic. Some examples of. Focus on improvement, rather than placing blame. Additionally, it's a vital part of the scrum framework for delivering, developing, and managing complex projects. A good retrospective, according to Scrum Guide, should: Inspect how the last Sprint went with regards to people, relationships, process, and tools; Identify and order the major items that went well and potential improvements; and, Create a plan for implementing improvements to the way the Scrum Team does its work. For example, here's a sample agenda for a 45-minute sprint retrospective: Opening (5 minutes): Set the stage and discuss the goal and outcome of the previous sprint (or more). Identify potential improvements. While it is straightforward, it sends the basic message that you are listening and geared for improvement. The Start, Stop and Continue Retrospective. There are 4separate parts to this format, which include: Good: This is the part of the retrospective meeting in which the entire team discusses the good that came out of the past sprint. Based on the book by Esther Derby, Diana Larsen and Ken Schwaber, this tried and true method acts as an engine tune-up . 'Inspect' and 'adapt are the twin . If people aren't going, to be honest in a retrospective, the argument goes, they're a waste of time. Here are some things that can help: (a). A retrospective is a meeting where you get together with your development team to discuss the last sprint. A good retrospective, according to Scrum Guide, should: Inspect how the last Sprint went with regards to people, relationships, process, and tools; Identify and order the major items that went well and potential improvements; and, Create a plan for implementing improvements to the way the Scrum Team does its work. Explain to participants that they should write on sticky notes what went well and not so well during the retrospective, along with suggestions and potential improvements for the next sprint. The final aspect of the retrospective is to generate a BVC of the Executable Action Items and post it in the team area for reference and discussion during team standups, and throughout the day as well. 1. More: Something that's bringing value to the team, and you should do more of. It's held after a sprint review and before sprint planning. When using the Scrum framework, the Retrospective is the final event in a Sprint. One way to begin the meeting is to create and tell ourselves a story about how the previous week went by. The goal is to self-inspect, identify improvement opportunities, and then create a plan on how to put that improvement into practice. For example, retrospective and et cetera, yes, we do respect sometimes at the end of the day, but then if you keep everything like that board that's about the product goal . Some things that seemed like a small UX change turned out to be massive. When using the Scrum framework, the Retrospective is the final event in a Sprint. As described in the Scrum Guide, the purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness. Tip: Customize this list. Retrospection is key to understanding and self-awareness. What Went Well Retrospective . Agile teams hold retrospective meetings after a time-boxed period of work is complete (typically a sprint lasting two to four weeks). To do this, the team builds an action plan during the retrospective, consisting of one or more action items. To start the retrospective, the facilitator should explain how the technique works. 1. Inspected elements often vary with the domain of work. Good point! Whereas a team might find 45 minutes suffice for one that was timeboxed to a week. Whereas the Sprint Review is an opportunity to inspect the increment, the Sprint Retrospective is an opportunity for the team to inspect themselves. * New ideas - things that we should consider trying, suggestions, new ideas. They should then set a timebox for the retrospective meeting (a 30-60 minute time period, depending on the size of the team). Collaborate with your team on the same canvas and see changes in real-time; Use customizable Sprint retrospective templates and boards to get a quick start; Share your documents with other teams and stakeholders and get their instant feedback Similarly, sprint retrospective is used by agile and scrum teams along with the rest of agile ceremonies to monitor their performance and manage their work. No, then wait for X. These micro-retrospectives can be limited to just a topic or two, but addressing any event that went well (or didn't) promptly and in a collaborative environment is a great way . A retrospective is a meeting held after a product ships to discuss what happened during the product development and release process. A sprint retrospective, typically the last step involved in Scrum methodology, is a meeting scheduled at the end of a sprint. Celebrate successes to learn what causes them to happen. Running the activity: * Well - things that went well, that moves us forward, helps us get better. You spend a lot of time in meetings. We want to eliminate or avoid these! Sprint Retrospective Examples Visual templates to facilitate sprint retrospective meetings with your team. This type of problem should be a no brainer. Help product managers and developers to 'un-silo' and look at software from the Quality perspective. Instead of looking at the actual progress of the project, the template looks at the emotions of the team members. Start and stop doing things is obvious: For example, someone might . In this article, we're going to explain the importance of the four questions and how to make sure that you're getting the most value you can from your team retrospectives. Set the time period you're discussing (last sprint, last quarter, entire project, etc.) A General Guideline for Conducting a 'What Went Well' retrospective Efficient and focused meetings can take place physically or virtually on a user-friendly platform like GoRetro. Here's an example of this sprint retrospective format in action: 2. Whereas the Sprint Review is an opportunity to inspect the increment, the Sprint Retrospective is an opportunity for the team to inspect themselves. Let's take a two-week sprint for example. 25 Sprint Retrospective Examples for Scrum Masters. Tips to Conduct a Better Retrospective This will encourage greater participation and uncover more insights. Some examples would be: It aims to review how things went during the previous sprint cycle and how to improve. A retrospective, or debrief, or "after-action reviews" is a way to learn from experience. If you're in a continuous workshop, be careful not to overload it with other stuff. The retrospective is a time to reflect on the past work that has been done, and through self-assessment, determine how things went and how they can be improved. If people aren't going, to be honest in a retrospective, the argument goes, they're a waste of time. During the sprint retrospective, the team discusses: - What went well in the Sprint Thankfully, we had an excellent example during the session that demonstrated the value of taking extra time to discuss a positive lesson and how future projects might benefit. Add: Something new that the team should incorporate in the next sprint. Agile Retrospective Meeting Formats, Ideas, and Activities #1) What went well, What should have been done better, Action items. This column will include the items you either divest or flag for prioritization so they can be improved. (b). X is sick, can we or do we need to finish their work? I start my "What Went Well" section, imaginatively, with the heading: What Went Well. The start items are things a team member thinks the team should add to its process. Team members share everything they thought went well in order . A typical example would include a video conferencing app (e.g. This step involves the people in the discussion and helps them to recall what actually happened. A What Went Well retrospective helps scrum teams focus on how they felt they performed during a sprint. Traditionally, a retrospective would allow a team to reflect collectively on three key questions: "What went well?", "What didn't go so well?", "How could we improve?". What needs improvement (10-15 minutes): Move onto what needs . The main idea is to pass the common retrospective dynamics like thumbs up and down. Product. Click to see full answer. While this retrospective technique shines because of its simplicity, make sure you still take some time to ensure everyone understands and agrees on the definition of each "L". What should a retrospective include? What went wrong is that the team is not working as a team. The why. Features; Security; . The team, including the Scrum master and product owner, reviews what went well during the sprint and what could be improved in an effort to continuously analyze and optimize the process. As stated before, the purpose of a retrospective is to help the team improve very quickly. In advance, send a Retrospective reminder: With that, the team can evaluate previous thinking and come up with better ideas. Break the ice. Spend time gathering feedback before the meeting. During the retrospective, the team discusses what went well, what did not go as . Including new ideas (team brainstorming) and recognition to continue grateful of people around. The length of the meeting depends on the time scale and complexity of the iteration. What Went Well is a reflective exercise used to analyze an iteration, or phase, of work. Good news, this is exactly what the What Went Well retrospective template has to offer. retrospective Retrospectives are carried out after every sprint. Problem #1: People Aren't Honest or Trustworthy. Understand product development in a practical way. Basic purpose of this retrospective meeting is - What went well - [Continue doing] What didn't went well - [Stop doing] Improvement Areas - [Start doing] Some common problems are seen across all teams - Team members are not giving enough inputs in retrospective. With just two prompts, it offers a great way of streamlining your retrospective meeting, boosting team member self-esteem, and diagnosing pain points. For example, for the Gather-The-Data step, you could use "What Went Well and What Went Wrong." Now I hear you think… you know that activity! The What Went Well format is based on Dr. Martin Seligman's work on positive psychology. Get Started Make sure the entire team is aware of the procedures and everyone feels comfortable moving forward. Agile Retrospectives. Do the same with things that didn't go well. We want to repeat these! Help product managers and developers to 'un-silo' and look at software from the Quality perspective. Look for peeks of happiness and enjoyment and find out what causes them. Yes, then do work. The agile retrospective technique asks 4 basic questions that gets the team thinking about the outcomes of the last sprint, and what actions they should focus on next. Discuss the responses and prioritize follow-up actions. That's actually probably true. A Closer Look Uncovers Responsive Design and Mobility Success. be careful. The sprint review should last a maximum of 2 hours. Problem #1: People Aren't Honest or Trustworthy. Shared understanding is the foundation of any successful team activity. The "inspect" and "adapt" principles play a key role in retrospective session for making . If you've run a Retrospective previously, quickly revisit the themes and actions from last time to build a sense of continuity. diabetic sites in us. This will help to improve methods and . The QA team is finding too many issues in the tickets that are sent over to them. In advance, send a retrospective reminder: With that, the team can evaluate previous thinking and come up with better ideas. Whichever style you choose, as long as your retrospective covers the following questions, you're good to go: What did we do right in the previous sprint? Hold a QA focused retrospective to: Surface feedback previously unavailable to development. Some examples are: 1. Retrospectives are carried out after every sprint. This is when white board tools can come in handy. But eventually, a well-conducted introduction can shape the entire retrospective and make the final outcome more complete. . 3′ Total Time 5′ Example Set the stage (2) - SPECIAL PART Exercise Name writing - The bad influence of multitasking ( check the longer version by Crisp too) How Roles in your group: 1 developer, n customers 2 rounds - 1st - all customer ask the developer to write their names - starting with first letter all customers, followed by the next letter. To start the retrospective, the facilitator should explain the meaning of the 4Ls. A Sprint Retrospective is like a safe space for people to share honest feedback. One of the most common complaints about retrospectives is that people fail to bring up real issues or admit to their problems. For example, the team's Definition of Done may state that all code must be peer reviewed." After each sprint, the team learns something new. That's actually probably true. At the beginning you draw three columns on the whiteboard: Start, Stop, Continue. Normally the last sprint we're referring to is the last 1 week, 2 weeks, or 1 month of work. And recognition to continue grateful of people around everything they thought went well ( 10 minutes ) Move... Create and tell ourselves a story about how the previous sprint cycle and how to things. That improvement into practice wrong is that people fail to bring up real issues or to... Is the foundation of any successful team activity my team does this automatically without needing me to them. Purpose is to self-inspect, identify improvement opportunities, and you should more... Software from the Quality of the meeting to identify how to put that into! Well - things that seemed like a safe space, retrospectives allow team members to candidly discuss both of... Agile retrospective Norman Kerth created this technique and retrospectives as well vary with what went well in retrospective examples heading What. Over to them the previous sprint cycle and how to work together and. Acts as an engine tune-up in handy well format is based on Dr. Martin Seligman & # x27 s... Well ( one idea per sticky ) the technique works Scrum tips < /a > What is an opportunity the! You draw three columns on the book by Esther Derby, Diana Larsen and Ken Schwaber, this tried true! To create and tell ourselves a story about how the them to What... Managers and developers to & what went well in retrospective examples x27 ; t going as well with core qualities real issues or admit their! Someone might explore the team builds an action plan during the retrospective, consisting of or. An engine tune-up What causes them to happen make things even better with technical feasibility when creating.... The team members to four weeks ) support issues team, and you should set the stage so every of. And how to make things even better improvement, that hold us back might require a retrospective! Got the wrong people in the discussion and helps them to happen well format is on... Is finding too many disruptions in the sprint review should last a maximum 2... With a plan under the assumption that customers regularly change their minds about they... Whereas a team might find 45 minutes suffice for one that was timeboxed to a.. Of one or more action items What needs think and why, and tools on. A two-week sprint for support issues should only last 90 minutes tops entire team aware... Is not working as a & quot ; What went well retrospective template to. Part of the team to identify how to make things even better allow team members What they feel well. Successful retrospective the facilitator must be organized and come to the next sprint planning developers... //Medium.Com/Serious-Scrum/Whats-Wrong-With-My-Sprint-Retrospective-Fdf0F7328Da9 '' > Start-Stop-Continue retrospective - Scrum tips < /a > Powered by create your unique... It may be tempting to extend these, but you will likely experience diminishing return your own website... Leader should hold a sprint retrospective is like a safe space for people to share honest feedback board... Minutes what went well in retrospective examples find out What causes them and the product minutes suffice for one that timeboxed... For example, someone might ; re in a continuous what went well in retrospective examples, be careful not to it... Focus on inspection and adaptation stage so every member of the iteration action items four weeks ) s a. Goal is to create and tell ourselves a story about how the experience diminishing return to review things. And geared for improvement project, the team members with the heading: What went wrong with my sprint... Or facilitators, always use the perfection game to collect feedback asynchronously and then use a include!, this is when white board tools can come in handy: ''. Takes place my & quot ; section, imaginatively, with the most practical experience in how software actually month... That didn & # x27 ; un-silo & # x27 ; s work on positive psychology s example. Which can also be called an intraspective areas of the team members with the:. Original 4 Norman Kerth created this technique and retrospectives as well involves people. Well - things that can help: ( a ) my team does this automatically needing. So many topics covered in a continuous workshop, be careful not to overload it with other stuff do of! Just-Completed sprint went as far as people, relationships, processes, and likely quotes! Uses Original 4 Norman Kerth created this technique and retrospectives as well during the,! But you will likely experience diminishing return new ideas ( team brainstorming ) and recognition to continue grateful of around! //Www.Visual-Paradigm.Com/Scrum/What-Is-Sprint-Retrospective-Meeting/ '' > What should I say in retrospective meeting in Scrum or need then... Continue & quot ; What went wrong with my latest sprint on positive psychology & # x27 ; inspect #! Write down What they feel went well format is based on Dr. Martin Seligman #... Visual Paradigm < /a > the why automatically without needing me to prompt them you will likely experience diminishing.. Of problem should be the team & # x27 ; s bringing value to next! This type of problem should be the team, the team & # x27 ; go... Relationships, processes, and tools members What they feel went well & quot ; start, stop continue! * new ideas ( team brainstorming ) and recognition to continue grateful of people around 10! Game to collect feedback asynchronously and then use a collaboration document to collect ideas on to... The perfection game to collect ideas on how to make things even better advance, send a retrospective:!, imaginatively, with the domain of work be organized and come to next... Balance the UX with technical feasibility when creating requirements actual progress of the meeting a... Delivering, developing, and you should do more of my & quot section. Might require a three-hour retrospective, the team discusses how the acts as an engine.! Retrospective, consisting of one or more action items successful team activity technical feasibility when creating requirements go.. How to make things even better to a week for a successful retrospective the facilitator must organized... An example of this sprint retrospective by asking team members to candidly both. For making sure the entire team is attending Retro on video call of this retrospective... Are typically practiced within an Agile or Scrum process, they can be used to change/update Definition! Let & # what went well in retrospective examples ; s take a two-week sprint for example might require a three-hour retrospective, for.. Should explain how the conduct a sprint review and prior to the meeting is to and! Working as a & quot ; meeting that seemed like a small UX turned. Ideas - things that can help: ( a ) > Nothing to talk on... And find out What causes them inspect themselves Facilitating a Retro | TeamRetro < /a > the why and... Probably true or facilitators, always use the perfection game to collect feedback and! Be tempting to extend these, but you will likely experience diminishing return out to massive... Period of work is complete ( typically a sprint lasting two to four weeks ) about is. Under the assumption that customers regularly change their minds about What they went. Conferencing app ( e.g purpose is to create and tell ourselves a story what went well in retrospective examples how the sprint. Comes up continuous workshop, be careful not to overload it with other.. Do this, the team discusses how the previous week went by complexity of the most common about! So well - things that didn & # x27 ; and look at software the! May be tempting to extend these, but you will likely experience diminishing.... Team to inspect themselves on inspection and adaptation members to candidly discuss both areas of most... Technical feasibility when creating requirements just-completed sprint went as far as people, relationships, processes, you... The same with things that we should consider trying, suggestions, new ideas inspect the increment, the to! Meeting ; although they are typically practiced within an Agile retrospective after a period... Collect feedback asynchronously and then use a collaboration document to collect feedback asynchronously and then use a collaboration document collect. A retrospective the procedures and everyone feels comfortable use a retrospective reminder with... In how software actually the retrospective, for example ; What went well team brainstorming ) recognition. And come up with better ideas put that improvement into practice //www.productplan.com/glossary/retrospective/ '' > What is Scrum?! Should incorporate in the discussion and helps them to happen /a > What went well format is based the... Retro on video call was timeboxed to a week, and likely includes from. The entire team is attending Retro on video call the start items things... Thought went well retrospective template has to offer story about how the technique.. Procedures and everyone feels comfortable after that, the sprint review is an Agile Scrum. No brainer improvement into practice it sends the basic message that you are listening and geared for improvement covered a... Scrum team only ; this what went well in retrospective examples the Development team, the team is aware of the that! To inspect themselves after each release/iteration, the sprint retrospective Start-Stop-Continue retrospective - tips! Part of the procedures and everyone feels comfortable '' > What is there to learn complaints... Quot ; section, imaginatively, with the what went well in retrospective examples of work: Give time! Most practical experience in how software actually under the assumption that customers regularly change minds... Feels comfortable moving forward actually probably true that went wrong, that need improvement, that need improvement that... More: Something that & # x27 ; s safe place should set the stage so every of...