scrum master tools Archives - Scrum Master Toolbox Podcast

Mike Salogub: Overcoming Dysfunction and Harnessing Constructive Conflict in Agile Teams

In this episode, Mike discusses his experience working on a project to develop a new app in just one month. Despite overcommitting without a clear scope of work and still learning how to structure the work, there was a lot of waterfall mentality among the team members. As pressure mounted, the team started to experience dysfunction, but they eventually came together to deliver the project on time.

The team’s retrospectives were initially conflictuous, but this competitive conflict helped the team to build up and become better. Listen in to learn how to harness constructive conflict and help your team achieve more than they thought was possible.

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 Mike Salogub

Mike’s an accomplished, committed and creative Scrum Master with over 10+ years of expanding horizons in the healthcare technology industry. Focused on continuous improvement using data to inform business decisions, and driving innovation to meet the needs of patients.

You can link with Mike Salogub on LinkedIn and connect with Mike Salogub on Twitter.

Caterina Palmiotto: Autonomy and Accountability, Key Team Skills That Make You A Successful Scrum Master

In this segment, Caterina discusses how success for Scrum Masters depends on the team’s ability to be autonomous in defining and changing their working agreements. She suggests asking questions such as whether the team members are active when the Scrum Master isn’t there and if they are following the agreements they made together. She emphasizes the importance of the team being mature enough to trust themselves to make decisions and call out each other when they break the rules. Finally, she shares a tip on how keeping each other accountable to the work agreements is crucial to maintaining the desired team culture.

Featured Retrospective Format for the Week: Metaphor, or simple format? Which one to use and when?

In this segment, Caterina discusses an agile retrospective format based on team maturity. For new or less mature teams, she suggests using a metaphor, such as a favorite movie or sport, to change perspective. However, for more mature teams, a simple format like MAD/SAD/GLAD works well as they want to jump into and quickly solve problems they already know about. In the end, we must always adapt the retrospective format to the level of the team, as well as the current situation they are facing.

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 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.

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: 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.

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: The Challenges with Scaling and Product Ownership for a Growing Scrum Team

In the podcast episode, Kirill Golubev shares a story of a team he was working with, which had grown larger. As they grew larger, they added a second and a third product manager. However, this led to constant fighting for priorities among the product managers. What was worse, the product managers were organized around components, rather than features, which caused even more conflicts, and delays in delivery for the team.

In this episode, we talk about the importance of having only one Product Owner working on the backlog. In that situation, the team adopted the Nexus framework to scale their approach to Scrum and created three different teams for the three different components. This was not optimal, but helped to avoid the biggest PO anti-patterns.

Finally, Kirill emphasizes the importance of building agreements between teams and Product Owners to ensure a successful outcome. Overall, Kirill’s story highlights the challenges that can arise when a team grows too large and the importance of effective communication and collaboration between Product Owners, Scrum Master, and teams.

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.