Here are some suggestions on what you can do to assure that you will have actions from agile retrospectives that are doable and that those actions get done.
These rules help to understand the agile approach and to work together in a smooth, efficient and positive way. They are based upon principles from the Agile Manifesto, EVO, Open Space Technology, Solution Focused, Root Cause Analysis, and Retrospectives.
Getting actions out of a retrospective that are doable, and getting them done helps teams to learn and improve. An overview of things that you can use to get value out of your retrospectives.
Retrospectives can have different purposes. A suggestion how you can classify retrospectives and pick appropriate exercises to make them more valuable for their teams.
You can continuously becoming better in the things that you are doing great by focusing on personal and team strengths with a strengths-based retrospective.
A retrospectives of retrospectives helps to improve collaboration between teams, increase their contributions in the project and to share learnings across projects.
Retrospectives exercises for teams which have more than one customer, maybe even multiple product owners.
Having some sort of visual indicator of the action items, along with the people responsible for them, always helps the team stay focused.
This exercise helps you to distinct between the team-level impediments and those that needed escalation to the next level.
This retrospective exercise can be used within agile frameworks like Scrum, SAFe, XP or Kanban to have teams agree upon the vital few improvement actions that they will do.
The Perfection Game can be used as a retrospective exercise to quickly discover strengths and define effective improvement actions.
A futurespective exercise can help teams teams to find ways to reach their goals, agree upon their way of working and define a Definition of Done.