Helping Scrum teams have difficult conversations, safely | Samantha Menzynski and Brian Ziebart

Published: July 7, 2020, 10:05 a.m.

Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website.

 

When a team started to have “backchannel” conversations and excluding some team members from those conversations, it was clear that something was going on that was not allowed to be discussed in the wider team. Samantha and Brian then focused on helping the team share what was going on in a safe way. Listen in to learn about what was holding the team back from discussing the important topics. 

Featured Book of the Week: Ideal Team Player by Lencioni and Difficult Conversations by Stone et al.

In Ideal Team Player by Lencioni Samantha found a great reference for a team that had to go through a recruiting process. The book helped the team reflect and choose the right candidate, by working together to define what they were looking for in a candidate beyond the technical skills. 

In this segment, we also refer to Difficult Conversations by Stone et al, a book that discusses conversation techniques to help move from emotion to productive problem solving.

 

About Samantha Menzynski and Brian Ziebart

Samantha Menzynski has spent her entire career in software. Starting in support and account management, moving to customer support management, and with Penta's transformation to Scrum becoming Scrum Master for the Core product team.

You can link with Samantha Menzynski on LinkedIn

 

Brian Ziebart started his career in software as a developer, but found himself wanting to move towards coaching and developing people rather than product development.  When Penta's Scrum transformation started in August 2019, he jumped at the opportunity to work more with people while still staying involved with development.

You can link with Brian Ziebart on LinkedIn

You can read more about Samantha’s and Brian’s work and the Agile transformation they were part of in this Scrum.org blog post.