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.
Asking questions is a technique that is easy to learn, but the effectiveness depends on the questions that you ask to the team. Here are some suggestions.
The 5 times why retrospective uses root cause analysis to identify the deeper causes of problems, and define actions to stop them.
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.
The most important thing is never to forget to appreciate and thank your team members for the ways they have helped each other.
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.
The dispersed team questions retrospective exercise is a variant of the questions-based retrospective for teams consisting of members working from different locations, for example team members working from home or working in different offices, countries or even continents.