Christian
Christian

Managers in Retrospectives? 5 Tips & Thoughts

The question of whether a manager should or may participate in agile retrospectives depends on various factors and there are different opinions in the agile community. But what if you have no choice? The team manager wants to attend the sprint retrospective. Let’s take a closer look at all this.

The basic rule is probably clear: Managers should tend to stay away from the retro because they are very likely to restrict openness in the team. At the same time, in a perfect world, managers are in a way part of the team, are servant leaders, and also have a trusting relationship with their employees. So what to do? 

There is also the question in some Scrum certifications: “The team manager would like to participate in the sprint retrospective. What should you do?”

The correct answer according to the test is: “Suggest another forum where the manager can meet with the team.” This should also be the first impulse in principle. In addition, the need should be questioned: Why does the manager want to participate in the retro at all? Perhaps the thirst for knowledge can be satisfied in other ways.

At the same time, if a manager wants to take part in Retros, see this as an opportunity. Surely he/she can help you with a few of your obstacles. 

Also, see it agilely: An experiment should be worth him/her coming to it once. Let’s see how it works - that’s exactly how you learn empirically.

Can Manager Sprint attend Retrospektive or Retro?

Tips: Managers in agile sprint retrospectives

So if the team manager wants to attend the sprint retrospective, you can maximize the probability of success with the following tips and mental models.

  • Set clear expectations:

    • Transparency is a key value in agile methods. When a manager participates in the retrospective, this can influence the openness of team members. Some members may be reluctant to express their opinions or concerns if they fear that the manager may interpret their contributions negatively. Discuss the expectations for the manager’s participation with the team and the manager in advance. Clarify what role the manager will play and how much influence they should have on the discussion.
  • Emphasize the role of observer:

    • If so desired, emphasize the manager’s role as an observer, serving to understand and support the team’s dynamics rather than actively intervening in the discussions. This can help to maintain the trust of the team. At the same time, emphasize the observer effect: It is clear that the manager’s presence alone is likely to influence the discussion. The effect may therefore be weakened somewhat.
  • Provide feedback after the retrospective:

    • Ask the manager to share his feedback and observations after the retrospective, rather than during the session - or maybe even never. This allows the team to at least get a sense of what exactly the manager was able to or wanted to take away from the retrospective at its core.

Should Manager be in Retro? | Sprint Retrospective Manager

Maximize the chances of your success

There are other tips you can take into account in this context and when considering whether managers should be in retros.

  • Emphasize self-organization:

    • Emphasizes the importance of the team’s self-organization. The manager should understand that the main purpose of the retrospective is for the team itself to identify and implement improvements.
    • At the same time, of course, it can also be seen as an opportunity to actively involve the manager. Some arguments support the participation of managers to provide leadership support and coaching. A manager can bring valuable feedback and perspectives from a higher level to help the team improve: What external factors beyond our control as a team are holding us back right now? What could the manager help us with?
    • Corresponding questions could also make your retrospective workshop more productive. But it should not end in a “justification monologue” by the manager. Instead, the manager must be clear that it is only about understanding and taking away tensions in the team in the first place, in order to discuss them at a higher level if necessary.
  • offer workshops and training courses:

    1. Provides the manager with the opportunity to participate in workshops or training aimed at deepening understanding of agile principles and practices. This can help to create a common basis for collaboration.
  • Influence through questions, not instructions

    • If the manager interferes: Instead of giving instructions, focus on questions that stimulate reflection. An example: Instead of saying “We need to do this faster”, ask: “How could we improve our processes to move forward faster?”. This strengthens the focus on self-organization and commitment.

Finally, there is a specific tool that could help you with a retrospective with managers, for example by keeping the data anonymous and helping with data-driven continuous improvement.

Can Manager Sprint attend Retrospektive or Retro?

Better retros for data-driven managers

Agile sprint retrospective tools can also help you to conduct a constructive retrospective with your manager. For example, managers are often data-driven. This is exactly where Echometer can help you by incorporating a Health Check survey into your retrospective. This makes team development more transparent and measurable. In addition, Echometer can guarantee the anonymity of opinions.

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.

If you can hire or fire, stay out of the team’s retrospective.

Aino Vonge Corry, Retrospectives Antipatterns

Can Manager Sprint attend Retrospektive or Retro?

Conclusion - Should managers be in retros?

So, can or should a manager attend the sprint retrospective or retro? Difficult: The integration of managers in retrospectives requires a sensitivity for agile principles and the observer effect. By focusing on openness, questions and reinforcing Scrum values, you can mitigate the potentially negative effect of managers in retros. However, managers tend to be out of place in retros.

Finally, another note: If you would like to try out how it feels to develop your team further with our tool: You can start an agile retrospective without logging in below, in this case the “Keep, Stop, Start” workshop. 

Alternatively, simply forward our website to the responsible colleagues: www.echometerapp.com.

Continue: What should we keep?
Stop: What should we stop doing?
Start: What should we start doing?

Blog category

More articles on "scale agility"

View all articles in this category
5 Ideas for Sprint Retrospectives Your Team Will Love

5 Ideas for Sprint Retrospectives Your Team Will Love

As a psychologist and Scrum Master, I probably have an unusual view of Sprint Retrospective ideas. I have a slightly stronger focus on the "soft" side of continuous improvement. You could also talk...

My 7 All-Time Favorite Agile Retrospective Templates

My 7 All-Time Favorite Agile Retrospective Templates

In my team, we conduct an agile retrospective more often than average: every Friday, i.e. once a week. And you won't believe it - thanks to the many super agile retrospective templates, among other...

How can you improve communication in a remote software development team?

How can you improve communication in a remote software development team?

There are various measures and approaches to improve communication in virtual or remote engineering teams of software developers and software engineers. It is irrelevant whether they are front-end,...

DORA & SPACE Metrics: 2 Team Workshops to improve them

DORA & SPACE Metrics: 2 Team Workshops to improve them

If you're a tech leader, you probably want to know how well your team is delivering software and how you can improve it. You may have heard of the DORA metrics and the SPACE framework, two powerful...

Agility Health Radar: 13 most popular models measuring agile

Agility Health Radar: 13 most popular models measuring agile

U.S. journalist and author Prentice Mulford once said: „"He who recognizes an evil has almost cured it.".“ Prentice Mulford Therefore, it's no wonder that we take our temperature, visit the doctor,...

Working Agreements: 10 Examples, Samples & Templates

Working Agreements: 10 Examples, Samples & Templates

Effective collaboration in teams is crucial for success, especially in the context of agile methods such as Scrum. Working Agreements play a crucial role in creating a clear framework for collabora...

Checklist for Team Leads: 10 key Tasks (incl. PDF)

Checklist for Team Leads: 10 key Tasks (incl. PDF)

As a team lead, you take on a lot of responsibility for your employees and your team. This checklist for team leads will make it easier for you to keep an overview and ensure that nothing goes wron...

The Scrum Master as Servant Leader: 8 Tips & Thoughts

The Scrum Master as Servant Leader: 8 Tips & Thoughts

As an experienced psychologist and Scrum Master, I understand the challenges that team leads face in agile environments. Finding the balance between agility and leadership is no easy task. In this...

Not Every Scrum Team Is Agile: Fake Agile

Not Every Scrum Team Is Agile: Fake Agile

Fake Agile: Is every Scrum team agile? No, unfortunately not every Scrum team is actually agile. Let me explain: A Scrum team is defined by working according to the Scrum framework: So it has sprin...

Echometer Newsletter

Don't miss updates on Echometer & get inspiration for agile working