Which retrospective format is best for your needs and team engagement?
We’re already aware of how retrospectives assist scrum and agile development teams to improve, collaborate, and progress productively from sprint to sprint.
But which retrospective format is best for your needs and team engagement?
Below is a list of retrospective formats available for your use as pre-built templates, so you can get started instantly and gain value as quickly as possible. Select any retro type to learn more about it or get started for free (no limit) and select the retro board of your choice.
This retro format works well for developing action plans, reviewing the previous sprint,and assessing product results. In short it asks:
● What went well? (start or continue)
● What didn’t go well? (stop)
With this retrospective, the focus is on how the team felt through the previous sprint learning on the techniques that assisted and should continue, as well as develop concrete directions to progress positively.
This retro type hopes to gain valuable insights from the team through open-ended questions and discussions covered by the team itself. With it, the team makes certain topics of interest to the team are given time and attention.
The Sailboat retrospective looks at the big picture by covering the variety of aspects of a project, allowing the team to provide insights on what helped, slowed them down, and develop an action plan moving forward.
A great retro to break down the previous sprint and projects worked on and look deeper at what was learned, what they lacked, and what they would like to see in the future.
A retrospective to help motivate your team by giving credit where it’s due to team members on various areas they shined in within the previous sprint.
A reflective format to look back on the previous iteration, where your team focuses on qualitative and quantitative reviews to help paint a bigger picture and assess goals and techniques.
A great retrospective solution for remote teams to run a retro together and improve as a team even while working remotely and not within the same space.
Do you know or use another retrospective format which you found has been very effective for your dev team and process? Please share with us, and GoRetro may end up creating a new template to help others.