Scrum Master Toolbox Podcast

Caterina Palmiotto: Address conflicts in your Agile Team, or else…

In this segment, Caterina Palmiotto discusses the story of a software development team that was self-destructing due to conflicts and a blame culture. When Caterina joined the team, she heard blame, resentment, and conflicts among the developers. The team struggled to resolve bugs, and one developer was causing the majority of the conflicts. Caterina tried to address the conflicts and had some success, but it took a difficult decision to remove the person causing the conflicts for the team to work better. Caterina emphasizes the importance of addressing conflicts and the impact of culture on the success of a team.

Featured Book of the Week: Legacy, by James Kerr

In this segment, Caterina Palmiotto discusses the book Legacy by James Kerr, which is a collection of leadership stories about the All Blacks rugby team from New Zealand. As a scrum master, Caterina noticed similarities in leadership between sports and software development. The book connected all the dots in her mind and emphasized the importance of a strong team culture. According to Caterina, if you focus on the team, the results will follow. The book highlights the idea that strong leadership is essential to building a strong team culture.

Do you wish you had decades of experience? Learn from the Best Scrum Masters In The World, Today! The Tips from the Trenches – Scrum Master edition audiobook includes hours of audio interviews with SM’s that have decades of experience: from Mike Cohn to Linda Rising, Christopher Avery, and many more. Super-experienced Scrum Masters share their hard-earned lessons with you. Learn those today, make your teams awesome!

About Caterina Palmiotto

Caterina started as a software developer but soon realized that she was passionate about team dynamics and communication, and embraced agility from the moment she saw it.

Caterina believes a team can be more than the sum of its parts and that growing the right culture is essential. When people are surrounded by good examples they will be motivated to do their best. So the first step is doing your best to be a good example of the culture you want to nurture.

You can link with Caterina Palmiotto on LinkedIn.

Caterina Palmiotto: A Scrum Master anti-pattern, introducing Agile in a “bubble”

In this episode, Caterina shares her experience as a Scrum Master in the IT department of a big company. Caterina and her colleague were responsible for two teams developing an in-house software, but no one in the company knew about Scrum. Despite initial difficulties and blaming, after 18 months, Caterina and her colleague were able to create an “agile bubble” where the teams and product owners were able to work together. They protected the teams from negative aspects happening elsewhere in the company.

However, after Caterina left the company, the agile environment fell apart since the decision-makers in the company were not aware of the agile methodology. Caterina realized that she failed to spread agile practices elsewhere in the company and suggested inviting more people into sprint reviews and demos, organizing open sessions, and creating curiosity in other departments. In this episode, Caterina emphasizes the importance of finding allies to continue agile practices even after leaving the company.

Recovering from failure, or difficult moments is a critical skill for Scrum Masters. Not only because of us, but also because the teams, and stakeholders we work with will also face these moments! We need inspiring stories to help them, and ourselves! The Bungsu Story, is an inspiring story by Marcus Hammarberg which shows how a Coach can help organizations recover even from the most disastrous situations! Learn how Marcus helped The Bungsu, a hospital in Indonesia, recover from near-bankruptcy, twice! Using Lean and Agile methods to rebuild an organization and a team! An inspiring story you need to know about! Buy the book on Amazon: The Bungsu Story – How Lean and Kanban Saved a Small Hospital in Indonesia. Twice. and Can Help You Reshape Work in Your Company.

About Caterina Palmiotto

Caterina started as a software developer but soon realized that she was passionate about team dynamics and communication, and embraced agility from the moment she saw it.

You can link with Caterina Palmiotto on LinkedIn.

Kirill Golubev: The Pitfalls of a Project Management Mindset in the Product Owner role

The Great Product Owner: Building a strong relationship between Scrum Master and PO, a critical contribution to the success of the team

Kirill talks about how important it is for Scrum Masters to build a close understanding and trusting relationship with the product owner (PO), and how that relationship is critical for the success of the team. He emphasizes that if there is no chemistry between the Scrum Master and PO, it’s better not to join that team. When there is good chemistry, the team will benefit much more from both Scrum Master’s and PO’s presence.

Kirill also stresses that the PO needs to have guts and be clear about prioritizing the backlog. He warns against the anti-pattern of conflict between the Scrum Master and PO.

The Bad Product Owner: The Pitfalls of a Project Management Mindset in the PO role

In this segment, Kirill shares why he thinks that the PO role is a cornerstone role in Scrum and without a PO, a Scrum team cannot even get started properly. We explore how POs that come from the project management field, often have a project management mindset, which hinders their ability to grasp the PO role.

Kirill shares an example of 3 POs for one team who were new to the role and to Agile. The POs did not trust the team to self-manage, and wanted to control everything by telling the team what they had to work on, and when. We discuss how we can help the PO understand that it helps the team to trust and help them self-manage. We also refer to the concepts of Theory X and Theory Y and how, knowing about that can help the PO’s understand their role as a leader.

Are you having trouble helping the team work 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 Kirill Golubev

Kirill considers himself an Agile and common-sense apologist. He wants to see simple processes in place, when people self-organize and manage themselves without constant push from management.

You can link with Kirill Golubev on LinkedIn.

Kirill Golubev: How the Scrum Master’s Role Contributes to Team Success

In this episode, Kirill discusses the difficulty of measuring the value of a Scrum Master and how success is ultimately tied to the success of the team. He emphasizes the importance of paying attention to retrospective preparation and capturing concerns expressed by the team. Kirill measures his own success and that of the team by the value delivered to a satisfied customer.

Featured Retrospective Format for the Week: Making Agile Accessible and Using User-Friendly Retro Formats

In this segment, Kirill discusses the importance of using different retrospective formats depending on what the team wants to achieve and the inputs involved. He mentions examples such as the hot air balloon and sailboat retrospectives, which can visually illustrate the key principles of Agile and help the team reflect on how they implement those. Kirill emphasizes the importance of avoiding the use of hard vocabulary in retrospectives, and making sure that everyone, including those unfamiliar with Agile, can actively participate and benefit from the session.

Retrospectives, planning sessions, vision workshops, we are continuously helping teams learn about how to collaborate in practice! In this Actionable Agile Tools book, Jeff Campbell shares some of the tools he’s learned over a decade of coaching Agile Teams. The pragmatic coaching book you need, right now! Buy Actionable Agile Tools on Amazon, or directly from the author, and supercharge your facilitation toolbox!

About Kirill Golubev

Kirill considers himself an Agile and common-sense apologist. He wants to see simple processes in place, when people self-organize and manage themselves without constant push from management.

You can link with Kirill Golubev on LinkedIn.

Kirill Golubev: A Scrum Master’s Insights on Being a Change Agent in the Pharmaceutical Industry

In this episode, Kirill shares the story of when he was a Scrum Master in the pharmaceutical industry, and learned some important lessons about being a change agent in an organization. He highlights the importance of having the team’s support and readiness when implementing any change. Kirill also emphasizes the value of training management to showcase the benefits of Agile to them.

Kirill believes that Scrum Masters have a revolutionary role in bringing change to the workplace and that it’s essential to define a Scrum Master vision and have a mentor to understand critical things that are necessary for success in the role.

As Scrum Master we work with change continuously! Do you have your own change framework that provides the guidance, and queues you need when working with change? The Lean Change Management framework is a fully defined, lean-startup inspired change framework that can be used as the backbone of any change process! You can buy Lean Change Management the book at Amazon. Also available in French, Spanish, German and Portuguese.

About Kirill Golubev

Kirill considers himself an Agile and common-sense apologist. He wants to see simple processes in place, when people self-organize and manage themselves without constant push from management.

You can link with Kirill Golubev on LinkedIn.

Featured Book of the Week: Legacy, by James Kerr

You might also be interested in...

The Great Product Owner: Building a strong relationship between Scrum Master and PO, a critical contribution to the success of the team

The Bad Product Owner: The Pitfalls of a Project Management Mindset in the PO role

Featured Retrospective Format for the Week: Making Agile Accessible and Using User-Friendly Retro Formats