scrum Archives - Scrum Master Toolbox Podcast

Mike Salogub: How to help a team go from waterfall to Scrum in 3 sprints, the challenges to expect

In this episode, Mike talks about his experience with change leadership when his team transitioned from waterfall to Agile. The transition happened overnight, and Mike had to learn a new role quickly. After attending Scrum workshops, the team began working on their first sprint, but developers were eager to work on future projects and underestimated the amount of work to be done in the current sprint. This led to a pile-up of work and failure to meet sprint goals in the second sprint.

However, by the third sprint, team members started to understand the benefits of Agile, and by the fifth sprint, they were delivering more than expected. Mike shared three tips for successful change leadership: involve the boss in meetings, regularly remind team members of the mission, and have a leader who is committed to making the project a success. In this case, Mike’s boss acted as a Release Train Engineer (RTE), helping to steer the team towards success.

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

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

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