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. If you are using Miro, you can use the built in Timer and Dot Voting tools.
If you have a lot of topics (too much to discuss in this session), do a quick dot voting session and start with the topics that has the most vots. If your team members tend to write down a lot of topics, you might want to limit the amount to 3-4 per person.Īfter the timebox, quickly read through the post-its to make sure the content is clear for everybody. I usually put on a timebox of a few minutes and continu when everybody is ready. It’s good if everybody can at least write down one topic per stage since everybody thought of something while giving a score. “On to the 10!:” what is still needed to go to a straight 10?.“it’s no 0:” why didn’t you put a 0? What do you like, or think is going well that made you give your score instead of a 0?.After this, ask everybody to write down the following: First, quickly read every score out loud so that every team member is aware of the scores that the others gave. After the icebreaker, we can go in detail on the score that every team member gave.
0 kommentar(er)
