Hey dear team leads of agile crews! As a psychologist and Scrum Master, today I'm sharing some essential tips for facilitating agile retrospectives if you're not in the Scrum Master role yourself, but rather that of a team lead or "boss" in some way. As a manager and servant leader, how can you get the most out of this important moment in the agile process? Let's look for answers together!
Facilitate retro as an agile Team Lead or boss | Example
The most important first
First things first: It goes without saying that it is not ideal if you facilitate the agile retrospective as the team lead, i.e. (depending on your specific form of organization) potentially even the official decision-maker of an employee. Why is that?
Of course, this is because it can greatly inhibit the absolutely necessary, open atmosphere in the team. The less open you are to sharing honest feedback, the less fruitful your retrospective will be. It may even end in a so-called zombie scrum.
In this respect, if possible, try to have as neutral a facilitator as possible for your retrospective. However, if this is not possible for whatever reason, here are at least a few tips to get the best out of your situation.
Facilitate retro as an agile Team Lead or boss | Example
Tips for your retrospective as a team lead
Preparation is crucial:
- Prepare the retrospective well by setting the agenda in advance. Make sure that enough time is planned for each phase.
- Collect feedback or topics from team members in advance to make the discussion more targeted. Tools such as Echometer, for example, can help you to do this via a survey.
Create a positive atmosphere:
- Emphasize the constructive nature of the retrospective. The aim is to identify improvements, not to apportion blame. In short, don't forget to include the question "What went well?".
- Use icebreakers or short games to create a relaxed atmosphere and bring the team closer together.
Keep an eye on the time:
- Make sure that the retrospective stays within the specified time frame. Respect the team members' time and stick to the planned agenda.
Use various retrospective techniques:
- Use different methods to create variety and highlight different aspects of collaboration. Here are 50 agile retrospective ideas for every team.
Focus on concrete measures:
- Make sure that concrete actions and measures are identified during the retrospective to address the identified areas for improvement – Only then will the team feel that you as a manager are taking them seriously.
Promote active participation:
- Encourage all team members to actively participate. Make sure that everyone has the opportunity to share their perspective.
Be neutral and objective – your opinion comes last:
- As a moderator, try to remain neutral and objective. Avoid intervening too strongly in the discussion or dominating the discussion with your own opinion. As a leader, you can influence others very strongly with your opinion and contribute massively to "Group Think". Simple basic rule: your opinion should be the last to be mentioned.
Obtain feedback on the process:
- Ask for feedback after the retrospective in order to improve your moderation. This shows that you are open to suggestions and support continuous improvement. For example, in Echometer the "ROTI score" has proven its worth: A simple question about how well time was invested in the retro, "Return On Time Invested".
Record the results:
- Document the results of the retrospective, including the actions identified. This helps with tracking and shows progress over time.
Promote self-organization:
- Encourage the team to find self-organized solutions. Give them the freedom to improve their own processes and support them in taking responsibility.
Enable anonymous feedback:
- If necessary, offer the opportunity for anonymous feedback. Sometimes team members feel freer to express their opinions when they are sure that their identity is protected. Especially if you facilitate the retro as team lead. Tools like Echometer can also help you a lot here.
Facilitate retro as an agile Team Lead or boss | Example
The best tool for your retro as a team lead
Many of the above points can be relieved by a good retro and team development tool such as Echometer. It has been specially developed for when there is no dedicated full-time Scrum Master in teams.
Echometer is a digital tool that helps agile team leads with agile retrospectives and team Health Checks. Whether remote, hybrid or on-site: it makes team coaching measurable and professionalizes your work while saving you a lot of work. Just take a look at our website to find out more: www.echometerapp.com.
"Also worth an experiment: As team lead, you let the team perform a retro without you and ask whether the team prefers this."
Facilitate retro as an agile Team Lead or boss | Example
Conclusion - Retro facilitation as team lead or boss
Finally, another quick hint: If you would like to know how it feels to develop your team with our tool: You can start an agile retrospective below without logging in, in this case the "Keep, Stop, Start" workshop.
Alternatively, simply forward our website to the responsible colleagues: www.echometerapp.com.
