When working with multiple teams, in a multi-team Scrum project, we may face what Andreas faced: the finger pointing anti-pattern. This is especially common in environments where no one wants to “be wrong” or take risks.
Even if learning and growing requires taking risks and sometimes “being wrong”, the fact is that no one wants to be that team that delays the project, so the finger pointing starts.
But how can a Scrum Master overcome that problem? How can the Scrum Master help the teams collaborate? That’s the topic of this episode.
Featured Book of the Week: Succeeding with Agile by Mike Cohn
Teams need to take ownership of their own work, so that they can effectively focus on delivering running, working software every Sprint. However, sometimes there are strong personalities in the team. We may want to ignore that anti-pattern, but it won’t ignore us. In this episode we talk about one such story, where the Architect in the team wanted to overrule the team members, and even escalated the issue to the team’s manager. Listen in to learn about Mark’s role in that story, and how we, as Scrum Masters, can handle similar situations.
Featured Book of the Week: 10% happier by Dan Harris
The book 10% happier by Dan Harris is a true story of how Dan found a way to keep focused, but lose the stress and self-doubt. For Mark however, this was a book about learning to focus on the events in front of him. The “now” that must be our focus as Scrum Masters.
About Mark Cruth
Mark has been playing in the Agile space since 2009, helping multiple organizations move towards a more Agile perspective on work across several industries, including manufacturing, eCommerce, and FinTech. Today Mark works as an Agile Coach for Quicken Loans, as well as operates his own Consulting company called Teal Mavericks.
It’s hard enough to deliver a small increment of a product, yet we often find ourselves and our teams in positions where they need to deliver a whole product, project or release in 1 go. No change for mistake. And you know what happens: when failure is not an option, failure is the only option!
About Ruben Betancourt
Ruben Betancourt is a computer systems engineer with experience in project management. Currently in love with agile software development methodologies.
You can link with Ruben Betancourt on LinkedIn and connect with Ruben Betancourt on Twitter.