BONUS: The top 3 challenges to better retrospectives with David Horowitz

In this episode, we interview David Horowitz who’s the CEO of Retrium, a company that builds tools to help you facilitate remote retrospectives. The links to Retrium’s Retrospectives Academy below are affiliate links, if you prefer to follow a link that takes you to Retrium’s site, but does not give anything back to the podcast, you can. Just follow this link: Retrium.com. On the other hand, if you want to help us grow this podcast, you can follow the links below or this link to Retrium’s Retrospective’s Academy.

As David started his Scrum Master journey, he was faced with a big challenge. He struggled with remote retrospectives. No wonder, he ended up creating and being the CEO for a remote retrospectives company. He experienced the pain first-hand! 

As he got started experimenting, he found the Lean Coffee format to be effective (see our Lean Coffee episodes). However, he found that even when the format worked well, there was something else missing. 

The collaboration that can be had when the team is in the same room simply isn’t the same when we are all remote, and sometimes even without video! 

Solving remote retrospectives, one tool at a time

Continue reading BONUS: The top 3 challenges to better retrospectives with David Horowitz

Darren Smith: 3 Anti-patterns PO’s should avoid

In this episode, we explore in detail some of the most common anti-patterns Darren sees in the Product Owner role, and we discuss why a PO training is not necessary for a great PO. 

The Great Product Owner: Business knowledge and outcome focus

To be a great Product Owner, it isn’t necessary to have attended a certification course. However, it is necessary to have a good connection to the business and a sharp focus on outcomes (impact) over output (more work). In this segment, we discuss what happens when you have those characteristics in your PO.

The Bad Product Owner: 3 Anti-patterns PO’s should avoid

There are many sides to a failed Product Owner role. In this episode, Darren shares with us some of the most common anti-patterns that he’s witnessed in his career as a Scrum Master.

In this segment, we refer to the remote facilitation online masterclass by Judy Rees.

For more anti-patterns, read Darren’s “How to Fail as Product Owner” infographic.

 

Are you having trouble helping the team working well with their Product Owner? We’ve put together a course to help you work on the collaboration team-product owner. You can find it at: bit.ly/coachyourpo. 18 modules, 8+ hours of modules with tools and techniques that you can use to help teams and PO’s collaborate.

About Darren Smith

Darren, aka the Naked Scrum Master, has been helping teams and organizations be better than they were by exposing dysfunction and helping people to remove obstacles from their path so they can be happier and more fulfilled in their working lives.

You can link with Darren Smith on LinkedIn and connect with Darren Smith on Twitter.

Rik Pennartz: Making remote, distributed team members feel part of the team

In this episode, we explore the story of a team that was scattered and working outside the office. We then explore the anti-patterns that made those team members feel like outsiders in their own team. Finally, we talk about the antidote, what to do to make the team feel like a team, no matter where they are.

In this episode, we also talk about Transformational Leadership.

Featured Book for the Week: The culture code, Daniel Coyle

In The Culture Code by Daniel Coyle, Rik found a definition of the characteristics of successful groups. What makes them tick and got some inspiring stories that help him be a better coach for his teams.

About Rik Pennartz

Rik is an agile coach, who’s worked during the last years at the Volksbank, the Dutch Railways and ABN AMRO bank. Rik also teaches various agile courses such as Professional Scrum Master, DevOps fundamentals and Leading SAFe.

You can find Rik Pennartz at the Cap Gemini Academy.

You can link with Rik Pennartz on LinkedIn and connect with Rik Pennartz on Twitter

BONUS: Aino Corry on how to prepare for and facilitate for Distributed Retrospectives

Scrum Masters all over the world make a significant effort to get better at facilitating retrospectives… Until they have to host a Distributed Retrospective. At that point, we learn that all you learned about facilitating retrospectives is still useful, but not nearly enough!

Preparing, hosting, and facilitating a Distributed Retrospective is a completely different challenge.

The 4 things that you need to make Distributed Retrospectives work

Continue reading BONUS: Aino Corry on how to prepare for and facilitate for Distributed Retrospectives

BONUS: Johanna Rothman and Mark Kilby share tips on how to help Distributed teams succeed

When Johanna visited Agile 2017, one of the largest Agile conferences that year, she was disappointed that the main advice people were giving on stage was: “don’t do distributed”. She then met Mark and started sharing her experience on how she had been able to make distributed agile work in her consulting work.

From that disappointment and both Johanna’s and Mark’s experience, a book was born: From Chaos to Successful Distributed Agile Teams: Collaborate to Deliver.

The most important lessons about making Distributed Agile work for your team

Continue reading BONUS: Johanna Rothman and Mark Kilby share tips on how to help Distributed teams succeed

Kristopher Stice-Hall: how to keep meeting-inflation in check for remote Scrum teams

When working with remote teams we must be aware that the number of meetings can easily balloon up because the team does not meet in the corridor. As Scrum Master, we must help remote teams find workarounds for the calendar-driven, meeting-inflated anti-pattern for remote teams.

In this episode, we discuss how a Scrum Master can help a team find the right balance between meetings and ad-hoc interaction even when remote.

About Kristopher Stice-Hall

Is the co-owner of Digital Maelstrom, a consultancy specializing in custom software, DevOps, managed cloud services, and information security. He has been doing Scrum Master work for over 10 years. He has worked with fortune 500 companies to companies less than 15 people. He also has been doing software development for 17 years.

You can link with Kristopher Stice-Hall on LinkedIn and connect with Kristopher Stice-Hall on Twitter.

BONUS: Molood Noori discusses distributed Agile Software Development

Distributed teams are a fact of the multinational organizations we work with. Hiding from it is not going to remove that. And crying “distributed agile = bad agile” is only going to alienate people who genuinely need to learn to cope with the fact that distributed teams are the new normal.

There are good and bad ways to adapt to the reality of distributed software, and copying the methods and practices from co-located teams into the digital world is not enough. Molood shares some of the common anti-patterns that arise when we plainly try to copy the co-located team methods into the new distributed reality.

One such example is the communication channels: trying to copy daily meetings from the co-located team into a digital world will eventually bump against the frustratingly low quality sound of some conference room setups. Molood suggests a different route and shows how a team she helped took full advantage of Slack (or any other asynchronous communication channel) to make their daily meetings for effective, and efficient for everyone involved.

Read on for the detailed show notes….

Continue reading BONUS: Molood Noori discusses distributed Agile Software Development

Chad Beier: How Agile adoption can be defeated by the use of Email

Email is a very helpful tool. It has a lot of things going for it. Email gives us a quick way to jot down some thoughts and ask a colleague (or many) for help. It helps keep track of conversations. It even enables remote teams (with limited overlap in working hours) to communicate without loss of memory. However, it also has some bad sides when misused. In this story we explore how certain uses of email can be destructive for a team, and some tips on how to detect and avoid that anti-pattern.

Featured book of the week: Flawless Consulting, by Peter Block

Scrum Masters act as consultants. They help, but are not responsible for the outcome of the team. They answer, and most importantly, ask questions to help the team learn, reflect and advance. So, we must understand how to be a good consultant. Flawless Consulting, by Peter Block is a book about how to be a better “helper” (read consultant) for the teams and organizations we work with.

 

About Chad Beier

Chad’s first experience with Scrum was in 2005 on a global team responsible for consolidating financial software. After some dark days of death march projects, he left his traditional business analyst and project manager roles behind. He is now consulting organizations as an external change agent and organizational agility advisor.

You can link with Chad Beier on LinkedIn and connect with Chad Beier on Twitter.

Chad’s company is: Whiteboard Consulting.

Heidi Araya on what happens when only part of the company is on board with Agile

Systems, the collection of all the stakeholders and actors, that we work within are not always aligned. A common anti-pattern is when only part of the company is on board with Agile. What happens then? We need to be aware of our supporters, our detractors and the “on-the-fence” stakeholders we need to work with.

In this episode we discuss such a story, and how we – Scrum Masters – can understand and react to those challenges.

About Heidi Araya

Heidi is an Agile coach who has been working with remote teams since 1999. She aims to show teams and enterprises the value of a cohesive vision and mission, systems thinking, and self-organizing teams. An active member of the Agile community, she trains and speaks at events and conferences worldwide.

You can link with Heidi Araya on LinkedIn and connect with Heidi Araya on Twitter.

You can join Heidi and other coaches every month for a virtual meetup at https://www.coachingagilejourneys.com.

Heidi Araya on 4 characteristics of successful teams

Heidi shares with us 4 characteristics she has identified in successful teams, the ultimate measure of our Scrum Master success.

We also talk about how retrospectives can be used to assess our own impact as Scrum Masters.

In this episode we mention a tool you can use to keep a finger on the happiness pulse of your team: BlogYourMood.com Do you have experience with that tool? Please share that below!

Retrospective format of the week: The Futurspective

In Futurspectives (for example: success criteria futurspective) we look at the future. We understand what it would look like to “succeed” and we backtrack, asking what got us there. Heidi suggest you use this format if you want the team to “step out” of the complaining cycle. We also discuss how to turn those Futurspectives into actionable output.

About Heidi Araya

Heidi is an Agile coach who has been working with remote teams since 1999. She aims to show teams and enterprises the value of a cohesive vision and mission, systems thinking, and self-organizing teams. An active member of the Agile community, she trains and speaks at events and conferences worldwide.

You can link with Heidi Araya on LinkedIn and connect with Heidi Araya on Twitter.

You can join Heidi and other coaches every month for a virtual meetup at https://www.coachingagilejourneys.com.