Add it to the poster by the island the ship is leaving. This is very effective to be able to pin point what type of behaviors, not just actions, that will help to create a change. If you want to do a bigger change you can also ask the team (it doesn’t need to be a scrum team, it can be a management team as well, or any other where they work together as a team) to add what behaviors they should leave behind to be able to do the change. Afterwards you can easily have a scrum of scrum to pick up what needs to be fixed between the teams, or you can bring the managers there (perhaps they where already joining) to take on the issues that they can help solving from all teams. If you do this exercise with more than one team at a time a good wrap up is to let all teams put up their posters on the wall side by side. If there are too many issues to be able to solve them during one sprint ask them to agree on the most important ones, 3-5 and bring them to their Scrum or Kanban board. Usually the team should work on solving the issues during the sprint. Ask the team to present their problems as well as their goals, and what actions they are going to take.Also write this down on stickies and put it by the sun. Ask the team what actions they could take as a team to reach these goals.Write down the goals separately on new stickies, perhaps a new color, and put them on the left side by the island with the palms. If you have little time and a lot of goals, ask the team to pick 3 or 5. Focus on the anchors on the first (team) level and ask the team to turn each anchor on the into goals.This brings a lot of value to the team and could be what helps the team to move forward. When doing this they should describe the problem, ask needed questions (but not discuss) and agree on what level the problem is on. Ask the team to put out the anchors, one by one.This is usually quite easy for the team if there is a good level of trust. Ask every one in the team to do it quietly, one by one, and write them down on stickies. Ask the team to collect all the anchors.Introduction: Present the format, show them the poster, ask them to assign someone responsible for facilitation (if you do more than one team) and tell them the agenda (or even hand it out) and time box. The time box for the whole retro should be not less than one hour, and not more than 1,5 hour if you do a big group and have presentations as well. It´s the teams responsibility to handle issues within the team, the Agile Coach/Scrum Masters job is to give them the capabilities to do that (not to do it for them).ĭ ownload the speedboat retrospective poster in high resolution (PDF) here >ĭownload the speedboat retrospective Power Point here (instructions and online retro space)> Some Agile coaches or Scrum Masters only highlight the negative on retrospectives, I believe it is a great thing to focus on the positive and also help the team take action more easily on real issues. Visualization helps the team to more easily figure out what problems they should solve them selves, and what problems needs to be solved through collaboration between the teams, and what they need to ask management to help with. I find it to be a good way for the team to think individually, and then collaborate and define solutions for their problems through visualization. The speedboat format for retrospectives is something I like a lot and have used with teams or even whole organizations (divided into teams). The online version that you can run in Google Drive via Google Slide.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |