What activities are maybe necessary but should be reduced?.What makes our agile collaboration less efficient?.What are elements of our work that we should use less?.Supporting questions to figure these aspects out are: These are aspects of your collaboration that should be used less. Some work processes are necessary for certain areas, but hinder the work flow in others. During this step you can collect aspects of your agile collaboration that didn’t go too well and therefore should be used less in your next sprint. This category is similar to “Stop” but covers topics that are less serious. And who knows – maybe you will discuss this next time at “Keep”? This is the opportunity to address these ideas and try them out in the next sprint. Maybe some of you heard or read of new ways of working together. What can be useful for easing our agile collaboration?Įven though the answers to these questions can be quite speculative it is always helpful to try out new things.What should we implement in our daily working routines?.In order to develop those ideas the following questions can be helpful: For this purpose you should consider strategies and steps that should be implemented in your next sprint. In this phase, you and your teammates should develop ideas together to make your future work more efficient and better. It’s the only way to solve these problems and to gain a deeper understanding for the roots of your difficulties.īy the way: If you like this retro format, you can open it directly in the team development tool Echometer: What hindered us in reaching our goals?Įven though it can be uncomfortable to talk about negative aspects it is really important to do this.Questions that can be asked in order to discuss this category are: This one is used to reflect the negative parts of your last sprint. What has eased our cooperation in the last sprint?Īs you can see, the questions are used to inspire your team members to think about what they do like about your collaboration and what they want to keep using in order to have a smooth and effective working behaviour.To figure this out you can ask the following questions: This category is used to explore what is already working well in your collaboration and therefore should be kept in your daily working routine. We’ll now give you an insight into what these categories contain. These are Keep, Stop, Start, Less and More. Using the Starfish Retro Format can help structuring this phase by providing categories for topics that should be discussed. This phase aims for reflecting the previous work and finding out what went well and what changes are needed in order to improve your cooperation. The Starfish Retro Format is an agile retrospective technique which can be implemented in the second phase of agile retrospectives: Gather data. As explained in our article on How to run a great retrospective team retrospectives are made of five different phases which are alle used to gain insight on what is working well and what can be improved for your future cooperation. To support you with that we’ll explain to you what the Starfish Retro Format is, how you use it and what advantages come with it.Īgile retrospective meetings are a major part of agile collaboration. But there’s every reason to broaden your horizons. I guess you’re not thinking about how to plan your next agile retrospective meeting with your colleagues. When thinking of starfishes you’re probably thinking of your next vacation, boat tours and nice ocean breezes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |