![]() One of the most common complaints about retrospectives is that people fail to bring up real issues or admit to their problems. Problem #1: People Aren’t Honest or Trustworthy In this article, I’ll describe the four most common problems I’ve seen with retrospectives, and I’ll offer advice on overcoming each problem. Teams often struggle to get their retrospectives just right. Unfortunately, not all retrospectives are perfect. This search for continual improvements is the purpose of the iteration retrospective. No matter how good an agile team is today, its team members feel compelled to seek ways to become even better in the future. It does not store any personal data.An essential part of agile is continuous improvement. The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. The cookie is used to store the user consent for the cookies in the category "Performance". This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. The cookies is used to store the user consent for the cookies in the category "Necessary". The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". The cookie is used to store the user consent for the cookies in the category "Analytics". These cookies ensure basic functionalities and security features of the website, anonymously. Necessary cookies are absolutely essential for the website to function properly. Try to improve a little each sprint instead of trying to bring big changes at once. A small action that brings a small improvements is already very good. Remember: you will not always have big live changing action items in each retrospective. You want to have 1 – 2 action items at the end of the retrospective that you can implement in the next iteration(s). Don’t focus too much on external people or factors, but mainly on the things that are within the control of the team to identify improvement actions that the team is able to take. While having the discussion on a topic, always focus on what’s within the control of the team. It’s important that everything you are discussing in the “Helping us”, “Holding us back” and “Obstacles” categories are related to the overall goal that you are trying to achieve as a team. After this, you can do a quick dot voting session to determine the most important one(s) and start with a discussion on those.įirst discuss all the post-its in the “Destination” category and come to a conclusion of the goal of the team before discussing the other stages. “Obstacles”: what risks do we see in the future, that could prevent us from reaching the goal? Something that we see happening, but is not yet happening to us today.Īfter explaining the stages to your team, give everybody a few minutes to write down their thoughts on a post-it.“Holding us back”: what is currently holding us back, slowing us down, or preventing us to reach our goal?.“Helping us”: what is currently helping us on our road to achieving this goal? What should we keep doing?.What are we striving for? As mentioned above, this can be something related to the product that you are building, or it can be something related to the way of working within the team. “Our destination”: what’s our goal? This should be the main theme for the retrospective.The sailboat retrospective consists of two rounds:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |