We can sometimes overwhelm the teams we work with by introducing too many methods. Anton explains how he likes to introduce methods to the team, by running experiments with the team to see if the method fits the team, and solves the problem they want to tackle. He also gives a critical advice on one of the most common anti-patterns for Scrum Masters: wanting to help too much.
Retrospectives are the tool for Scrum Masters to achieve success in their role. In this Episode we discuss many different types of retrospectives and Anton introduces the “themed” retrospectives as well as some tools on how to facilitate those. You can also read about one example of a themed retrospectives that Anton wrote especially for this episode. The Human Aspect Retrospective by Anton Zotin.
Recruiting is a critical process for any organization, not the least of which because hiring and wrong person and firing them later can destroy the team. Anton tells the story of a “perfect” hire that turned out to be very destructive for the team. He also asks us to involve the whole team in the process by asking the whole team to interview the person, and if possible, invite the candidate to work one day with the team.
Conflicts are part of the journey of any team. In this episode Anton explains the case of a team where conflicts were not addressed, and they became a source of problems for the team.
We discuss in this episode several Retrospective exercises that can help you address the conflicts by creating a more empathic atmosphere: the Journey Lines Exercise and The Constellation Exercise. The Nonviolent Communication book by Rosenberg is also mentioned in this podcast.
As Scrum Masters we are often very passionate about what is the “right way”, we see a lot of problems immediately, and we know how to fix them. Anton shares the story of such a moment in his career and how he started to accept that “everyone has their own journey”. His recipe is:
Gradually lead the time in the right direction. Don’t try to change everything at the same time.
Whatever you think is going wrong, reflect that back to the team and help them find their own solution. Be an Agile Mirror!