4/4/2024 0 Comments Sailboat retrospective image![]() ![]() For example: “STOP spending too much time on individual weekly reports that are not being reviewed. In short: activities that bring unnecessary wastes into the process and stall the group’s progress. Identify activities that do not bring value to the team or to the customer. Team members are invited to consider what they believe they need to: The Starfish retro format relies on a deep analysis of behaviours that are prevalent among the members of the team and continually impact the work process either positively or negatively.īy raising open-ended queries about the past as well as the future state of the team, this method of questioning encourages teams to take an honest look at their behaviors during the previous timebox of work and link them to process problems or successes. However, that hasn't prevented it from proving itself as an effective addition to any Agile team’s arsenal. Kua’s template is relatively new, compared to other more familiar retro formats like the Fishbone retro. The Starfish technique was developed in 2006 by Patrick Kua, technology leader, author, and keynote speaker. Here’s why you should seriously consider including it into your Agile ceremonies as a way to ensure that you are always running productive retrospectives that your team can look forward to. It’s a simple and powerful tool to boost visualization, anchor analytical skills, and improve decision-making during retrospective meetings.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |