trust Archives - Scrum Master Toolbox Podcast

Andrew Mitchell: From Command and Control to Shared Leadership, a Project Manager’s transition to the Scrum Master role

In this episode, Andrew shares his experience as a new Scrum Master and the mistake he made by trying to replicate a command and control leadership style. The team was demotivated and lacked trust, and Andrew initially felt the need to have all the answers despite his limited experience. However, he learned the importance of admitting mistakes and building trust with the team. He also discusses the transition from project manager to Scrum Master, emphasizing the need to let go of control and embrace shared leadership. Lastly, he advises embracing silence to foster deeper thinking and collaboration.

The inspiring story of how a failing hospital turned things around with Agile and Lean

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 Andrew Mitchell

Andrew prioritizes people when building products, aiming for happy and engaged employees who create great products and serve customers well. He emphasizes trust, psychological safety, servant leadership, and believes Scrum is the best framework to achieve these goals.

He was also a host of the Product Owner Summit 2023, where we collaborated.

You can link with Andrew Mitchell on LinkedIn.

Amruta Beri: Code Optimization and Scope Creep, Common Anti-Patterns Scrum Masters Must be Aware of

In this episode, Amruta shares her experience working with a team on a website migration project that involved adding client-specific features. Initially, the project started off well, but they soon realized that all the stories were heavily focused on technical aspects. After about four months, as the codebase grew, they faced challenges with introducing stories about code optimization without defined scope. The stories became too big, making it difficult to convince the engineers to prioritize and focus on one optimization at a time. The team started carrying stories from sprint to sprint, resulting in deviations from their original plan. Amruta provides tips such as presenting data to highlight time allocation, involving senior members to facilitate communication, and focusing on specific features instead of the entire scope.

Featured Book of the Week: The Five Dysfunctions of a Team: A Leadership Fable by Patrick Lencioni

In this segment, Amruta shares her favorite book, “Five Dysfunctions of a Team” by Lencioni. She highlights how relatable the story is for Scrum Masters, as many have experienced similar situations. The book emphasizes the significance of trust within a team, aligning closely with Agile principles. It explores the journey of a team’s transformation, shedding light on the challenges and dynamics that teams commonly face. Amruta’s summary showcases the book’s relevance to Scrum Masters and its valuable insights into building successful teams through trust and collaboration.

Transform Your Agile Teams with Hard-Earned Lessons from Super-Experienced Scrum Masters

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 Amruta Beri

Amruta is an Agile enthusiast, artist, and environmentalist. She loves quiz shows, travel and sports, and is an engineer at heart.

You can link with Amruta Beri on LinkedIn and connect with Amruta Beri on Twitter.

Johannes Lindman: Lessons in Communication and Trust for Scrum Masters, helping teams overcome adversity

In this episode, Johannes Lindman shares a story about a small team he worked with for a few months leading up to a major release. The team was focused on delivery and even had checklists to ensure that they were well-prepared. However, they encountered a problem that they had not anticipated and had to stop and acknowledge their failure. The team was surprised because they believed they had prepared well and were not sure how they missed the issue.

The team started to point fingers and look at one person who did not talk much. They realized that they were not talking about the problems they were afraid of and needed to be super honest with each other. Johannes notes that the team trusted each other as individuals, but they did not pick up on each other’s signs. In the end, the team learned the importance of communication, honesty, and trust. They realized that they needed to work on their communication skills and ensure that everyone felt comfortable speaking up when there was an issue.

Featured Book of the Week: Extreme Programming Explained by Kent Beck

In this segment, Johannes shares the impact that the book “Extreme Programming Explained” by Kent Beck had on his career. Johannes explains that the book helped him in many ways, and he found so many valuable ideas in it. He recalls the mantra “make it work, make it right, make it fast,” which he believes summarizes the essence of the book’s philosophy.

He credits the book with helping him to become a better developer and to embrace a growth mindset.

Transform Your Agile Teams with Hard-Earned Lessons from Super-Experienced Scrum Masters

About Johannes Lindman

Despite many years of experience Johannes still learns new things every day in order to stay relevant. This aligns with his curiosity on life and people.

You can link with Johannes Lindman on LinkedIn.

Caterina Palmiotto: The Phantom Product Owner, How Lack of Decision-Making Impacts the Team and Kills Innovation

The Great Product Owner: The Collaboration Between PO and Team as Key to PO Success

In this segment, Caterina shares a story of a great Product Owner who worked closely with their team. The PO took the time to share the high-level vision and timeline for a new module, collected doubts and comments from the team, and presented user stories with enough information to start a discussion. The PO listened to all suggestions and was available every day to collaborate. The refinement process was done in two parts, with the second part focused on investigating technical aspects. The PO even participated in retrospectives and worked with the team to improve the product based on either technical or functional ideas by the team. Caterina emphasizes the importance of building this kind of productive collaboration between POs and their teams, with the help of Scrum Masters.

The Bad Product Owner: The Phantom PO, How Lack of Decision-Making Impacts the Team and Kills Innovation

In this segment, Caterina talks about a Product Owner who only wrote user stories but was unable to make decisions. The Product Owner always needed to report to his boss, which caused a delay in decision-making. This led to delays in the team’s work, resulting in not completing the story in the sprint. Additionally, the team lost trust in the PO, and did not have enough information or support from the PO to bring their contribution to the product through technical innovation. Eventually, the team started to make decisions on their own and stopped suggesting ideas to the PO. Caterina emphasizes the importance of Product Owners being able to make decisions and not causing delays in the team’s work.

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

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.

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.