Review the discussion, create and refine the action list in collaboration with your team members.Start the discussion around those ideas, but make sure you follow the order of the template’s structure.If you come across similar ideas, you should group them.Brainstorm new ideas and add them to the relevant category.Invite other team members to join your project.Log into your Moqups account and select the Starfish Retrospective Template.Using the starfish retrospective template in Moqups Start Doing - Put in practice new ideas that show potential and could lead teams to success.Acanthaster planci Outbreak: Decline in Coral Health, Coral Size Structure Modification and Consequences for Obligate Decapod. Going through all sections you proceed to the closure of the retrospective. Stop Doing - Let go of the things that don’t bring any value or that stand in the way of achieving new milestones. Acanthaster planci infestations of reefs and coral assemblages in Japan: a retrospective analysis of control efforts, (1986) by M Yamaguchi Venue: Coral Reefs, Add To MetaCart. This is a good way for a team to start with positive brainstorming.More Of - List the activities that have a promising potential of adding value to the team, but which are not taken advantage of enough.Less Of - What are the activities that are unproductive for the team? From unhelpful routines to negative behaviors, team members should work towards reducing them as much as possible.Keep Doing - This step fills the team with positive energy because this is when the team lead recognizes the things that are done well and the value they bring to a project. This is an agile retrospective technique with five sections: Keep Doing, Do Less Of, Do More Of, Stop Doing, Start Doing.It is essential to follow the order they are placed in, as this will allow teams to start the retrospective on a positive note, encourage the discussion of central issues, and end the session with a positive affirmation. The Starfish exercise provides the structure to help have those conversations, so the team can debug any issues and make work more meaningful and enjoyable.The structure of the starfish retrospective template When you want to check-in emotionally: Sometimes there isn’t always a forum for team members to say what they need more of or less of in their work.This can make it easier to come up with practical action items at the end of your retrospective meeting. First teams think about what they want to Start, Stop, and Keep doing, but the additional two prompts force team members to think about what practical things they need more of or less of. When you want to focus on solutions: The addition of “More of” and “Less of” categories encourages agile teams to take a solutions-focused approach from the get-go.If you have complex processes, a lot of change in the team, or your traditional scrum retrospectives aren’t quite working, the Starfish retrospective can bring in-depth nuance to your conversations that help to uncover root issues.

When you need more nuance: Start, Stop, Continue is all well and good, but it might not give you that nuance you need to really deliver constant improvement.