retrospective Archives - Scrum Master Toolbox Podcast

Harri Tunturivuori: How To Help Your Team Embrace Scrum Values and Principles

In this episode, Harri shares his experience as a Scrum Master who was hired to work with a team that had tried to implement Scrum before his arrival. He discovered that although the team had changed roles and adopted some practices from Scrum, they were not following the values and principles. The Product Owners were command and control oriented, and the team members were not engaged in the work. Harri took a step back, talked to all team members 1-on-1 and as a team, and communicated with the rest of the organization about Scrum to explain the contract with the Scrum team. He was able to get buy-in from around the organization by creating a shared image of what Scrum is and showing what’s in it for the rest of the organization.

Harri shares three tips for change leadership in this situation: first, educate the team on Scrum and the practices; second, communicate with the rest of the organization about Scrum to get buy-in; and third, hold a retrospective regularly. He emphasizes the importance of holding retrospectives to create a continuous improvement culture, and the need to get support from the manager to implement Scrum effectively. This episode is a great resource for anyone who is struggling to implement Scrum effectively in their organization and wants to learn more about change leadership.

Want to Improve Your Change Management Results? Discover the Lean Change Management Approach Today!

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 Harri Tunturivuori

Harri is an experienced leader, Scrum Master, and Agile Coach who was introduced to the world of agile software development in 2010. Since then, Harri has had the pleasure of leading great agile teams in various forms.

Harri enjoys working in a fun environment where there is room for innovation, and Harri is driven by the challenge of growing a group of good people into a great team.

You can link with Harri Tunturivuori on LinkedIn.

Oguz Ozyurt: Checklists, and an accountability partner, the Scrum Masters’ best friends

In this episode, Oz emphasizes the importance of having a list of topics to review regularly in a self-assessment moment. He includes assessing whether the team is delivering what they committed to, taking advantage of Agile practices, and working on continuous improvement items. He notes that his list of topics consists of four dimensions, including the Value dimension which focuses on the value of the Scrum Master, and the Happiness dimension which assesses whether people around him are happy. In this segment, we also discuss the importance of having an accountability partner as a helpful tool for achieving success as a Scrum Master.

Featured Retrospective Format for the Week: Conversation Café, helping everyone to be heard

In this segment, Oz shares his favorite Agile retrospective toolbox: liberating structures. He explains that he likes to focus on the process and facilitation, leaving the content for the team to decide. Oz mentions a specific format called Conversation Cafe, which he likes to use. The Conversation Cafe format helps to promote active listening and allows everyone to be heard.

Oz emphasizes the importance of focusing on the process of the retrospective, rather than the content. By creating a safe and structured environment, everyone can share their thoughts and opinions without fear of judgment or retribution. Using the Conversation Cafe format, the team can have a productive and meaningful conversation about the sprint, identifying areas for improvement and celebrating successes. Oz believes that by focusing on the process and creating a safe space, the team can achieve better outcomes and improve continuously.

How can I, as a Scrum Masters, supercharge my facilitation?

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 Oguz Ozyurt

Oz came from a technical background, and has worked across multiple industries, applying agile practices toward the technical and non-technical areas. He is passionate about agile, he has leveraged his passion for delivery value and agile practices by coaching, teaching, mentoring many teams to transform from traditional software development life cycle to Agile principles and practices.

You can link with Oguz Ozyurt on LinkedIn.

Oguz Ozyurt: Helping Scrum Teams by Establishing Trust and Shared Understanding with Product Owners

In this segment, guest Oz emphasizes that we all work in a complex environment and are change agents. Oz shares a story about a team that faced problems with its product owner, who would add stories to the sprint backlog without refinement and interrupt the team even on the last day of the iteration. As a result, the team lost trust in the PO.

To address this challenge, Oz recommends making sure the team has an agreement on how to bring new stories into an ongoing sprint and discussing the team agreement with the PO. Oz also suggests bringing up the topic in the retrospective when the PO introduces a surprise story. Oz acknowledges that these conversations can be difficult, especially when the PO is a good friend of the team’s manager, but emphasizes the importance of building trust and ensuring shared understanding.

Featured Book of the Week: Leading Change by John Kotter

In this segment, Oz recommends “Leading Change” by John Kotter, which outlines eight steps for organizational transformation and is useful for anyone looking to apply these steps to a change process. Oz also suggests “Start with Why” by Simon Sinek for its insights on inspiring others and finding the purpose behind the work. Finally, Oz recommends “Team Topologies” which provides guidance on building and managing modern teams, a key responsibility for Scrum Masters. The authors of Team Topologies, Matthew Skelton and Manuel Pais, have been previous guests on the podcast.

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 Oguz Ozyurt

You can link with Oguz Ozyurt 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.

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.

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.