Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
In this episode, Daniel emphasizes the importance of collecting data from day one in product development. He discusses how data can help assess the capability of the system in place and create forecasts to assess delivery dates. He mentions the NoEstimates movement and suggests counting the product backlog items that can be finalized in one sprint as a useful metric. Daniel also provides tips for helping teams accept the data, and continuously updating forecasts. He emphasizes the need to work in hypotheses rather than requirements, as it allows for acceptance that they may be wrong. Finally, he notes that data gives us information on how to act and change over time.
[IMAGE HERE] 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 Daniel Westermayr
Daniel is a Kanban Trainer with a knack for all things Lean and Theory of Constraints. He wants to help teams achieve and measure their continuous improvements.
You can link with Daniel Westermayr on LinkedIn.
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
In this episode, Daniel discusses the overuse of the word "team" and the importance of true teams in product development. He highlights the need for preconditions for a team, and notes that sometimes teams don't even have a shared goal. Daniel also warns against the "it's done, just needs to be tested" anti-pattern and explains how it can lead to problems with team collaboration. We discuss the use of Causal Loop Diagram to find hypotheses, and mention a talk by Jeff Patton on the client-vendor anti-pattern. Finally, Daniel emphasizes the need to remove the notion that one party needs to own the game in the client-vendor relationship.
In this segment, Daniel Westermayr discusses the importance of data-driven decision making in product development. He references the book "Thinking, Fast and Slow" by Daniel Kahneman, which highlights the biases and faulty intuitions that can arise in decision making. Daniel emphasizes the need to use data to inform decisions and cites the book "Out of the Crisis" by W. Edwards Deming as an important resource. He also provides a link to a talk by Russell Ackoff about Deming's approach.
[IMAGE HERE] 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 Daniel Westermayr
Daniel is a Kanban Trainer with a knack for all things Lean and Theory of Constraints. He wants to help teams achieve and measure their continuous improvements.
You can link with Daniel Westermayr on LinkedIn.
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
In this episode, Daniel Westermayr discusses his belief in the importance of the Scrum Master role in helping companies achieve their product goals. He shares his experience of encountering a cluttered backlog with items that were years old and how he cleaned it up, only to face complaints from someone in support. Daniel emphasizes the need for Scrum Masters to clarify why a large backlog is a problem, and why the company wants to keep all items. He also advises that Scrum Masters should understand what they stand for and constantly question why certain practices are being implemented. Finally, he suggests that, in order to avoid fears of losing important information, the older requirements can be stored in a safe location. Daniel also mentions an article on how to declutter product backlogs.
[IMAGE HERE] 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 Daniel Westermayr
Daniel is a Kanban Trainer with a knack for all things Lean and Theory of Constraints. He wants to help teams achieve and measure their continuous improvements.
You can link with Daniel Westermayr on LinkedIn.
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
In this segment, we discuss the need to focus on, and develop a great partnership between a Product Owner (PO) and Scrum Master (SM). Oz shares the example of such a partnership, where the conversation between PO and SM focused on the value that the team can deliver. The PO was new to Agile but had an open mind and was an expert in the product domain. The PO was a natural leader and encouraged the team to pull stories from the backlog. He also asked the team to bring their perspective into the prioritization of the backlog. The PO acknowledged the team at every opportunity and brought an appreciation culture into the team. Oz highlights the importance of having a great partnership between the PO and SM, which is the main requirement for a successful Agile team.
In this segment, Oz discusses the challenges of working with a product owner who lacks a product mindset and is more focused on tasks than the product vision. This can lead to them "making up" work and not prioritizing tasks effectively.
Oz suggested a few tips for dealing with bad POs. First, he recommended asking about prioritization and trying to understand the PO's background. He also advised having a 1-on-1 coaching session with the PO to help them develop a better understanding of their role and how to prioritize tasks effectively.
Additionally, Oz emphasized the importance of focusing on empathy between the PO and the team. By fostering a positive relationship and working collaboratively, the PO and team can work together to ensure that the product is delivered effectively and meets the needs of stakeholders. Overall, Oz's advice for dealing with this type of POs is to approach the situation with understanding and empathy, while also providing coaching and support to help the PO develop a product mindset and prioritize tasks effectively.
[IMAGE HERE] 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 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.
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
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.
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.
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.
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
In this episode, Oz discusses the challenges of leading change and shares some tips for Scrum Masters to enable effective planning and team participation. Oz describes a scenario where the team was struggling to commit to the goals of the next PI and how it was discovered that the teams were not self-organizing and did not understand the "why" behind their work. The planning process was already defined before the teams came into the PI planning session, which was an anti-pattern of using agile terms but applying waterfall practices.
Oz suggests that effective facilitation is critical for Scrum Masters and advises creating a planning process that involves the team in defining the plan. Oz also recommends observing the meeting first to understand what the team is trying to accomplish and encourages enabling the team to speak up. Oz shares some links to resources that can be useful in planning and facilitating team participation, such as the wise crowds liberating structure. Additionally, Oz suggests using break out rooms to help the team talk about goals/user stories in private and to find problems in the plan using the 1-2-4-all Liberating Structure.
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.
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
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.
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.
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.
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
In this episode, Oz (Oguz Ozyurt) shares a story of a difficult collaboration with a Product Owner. He was working with a team and Product Owner who had different levels of experience, and while the team had completed the functionality for the iteration, they were not ready to release it. The Product Owner was surprised and pressed the team to release the functionality, which led to a failure. From this experience, Oz learned the importance of defining the definition of done with the team, as well as partnering with the Product Owner to define the goal together. He also emphasizes the importance of accepting that sometimes we fail, and working together with the team and Product Owner to define a plan for how to handle failures.
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.
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
About Jeff Campbell and Vasco Duarte
Jeff is an Agile Coach who considers the discovery of Agile and Lean to be one of the most defining moments of his life, and considers helping others to improve their working life not to simply be a job, but a social responsibility. As an Agile Coach, he has worked with driving Agile transformations in organizations both small and large and has published a book on the subject: bit.ly/aatbook.
You can link with Jeff Campbell on LinkedIn.
Vasco is a leading voice in the agile community, known for his contributions to the development of agile methodologies and practices. He is the co-founder of Agile Finland and the host of Scrum Master Toolbox Podcast, the most popular Agile podcast in the world, which has more than 8 000 000 unique downloads. He is also the author of "NoEstimates: A novel look at how Agile can transform software development, making it both more sustainable, as well as incredibly profitable." Vasco is a keynote speaker at many conferences and events, sharing his knowledge and experience with the agile community. With his passion and expertise in agile, Vasco has made a significant impact on the way software development is done today, helping organizations to become more efficient, flexible, and responsive to changing requirements. You can link with Vasco Duarte on LinkedIn and connect with Vasco Duarte on Twitter.
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
In this segment, Meena describes a great product owner who was very effective at product discovery. This PO paired hypothesis with metrics to ensure that what was being built was what the customer wanted. He focused on feedback loops, using customer interviews to learn about the flow and using that feedback to inform delivery decisions. The PO also involved the team in interpreting the numbers, which helped the team understand how to build the right thing.
Meena shared a story about a product owner who transitioned from being a senior developer and was unable to let go of technical leadership. This resulted in the PO intimidating the team by providing specific solutions and telling them exactly what to do, creating an unhealthy dependency. Meena gave one-on-one feedback to the PO, and appealed to the PO's human relations ability. She emphasizes the importance of coaching and giving feedback to the PO, and not just focusing on the rules.
[IMAGE HERE] 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 Meena Venkataraman
Meena is an Agile & Lean coach who helps organizations and teams transition to Agile ways of working. She is passionate about the neuroscience behind team dynamics and is interested in organizational design and the application of Agile principles across different business domains. Meena enjoys speaking at conferences and is an avid learner.
You can link with Meena Venkataraman on LinkedIn.
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
In this segment, Meena shares how, as a scrum master, she strives to step back once the team is self-sufficient.
Meena mentions that it is important to make sure that there is no unhealthy dependency between the team and the scrum master. To do this, the scrum master needs to ensure that they are not the only one who can resolve conflicts and that the team is communicating effectively with stakeholders.
The success of a scrum master is also measured by whether the team is delivering a quality product. Meena provides several tips for scrum masters, including making sure that it's not about them, and observing the behaviors of the team to determine if they can self-manage.
In this segment, Meena shares that when it comes to retrospectives, she prefers to focus on simplicity and creating conversations with the team. She emphasizes the importance of creating insights and actions with the team, rather than just generating data. Meena shares a tip to ask questions that crystallize insights and anchor them in the agile principles.
She also shares a story about observing a retro led by someone else where there was a lot of data but no actionable insights. Meena emphasizes that retros are great places for scrum masters to coach and that it's not about the format, but rather about anchoring questions in the agile principles.
In this segment, we refer to a shared whiteboard tool named MURAL.
[IMAGE HERE] 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 Meena Venkataraman
Meena is an Agile & Lean coach who helps organizations and teams transition to Agile ways of working. She is passionate about the neuroscience behind team dynamics and is interested in organizational design and the application of Agile principles across different business domains. Meena enjoys speaking at conferences and is an avid learner.
You can link with Meena Venkataraman on LinkedIn.
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
In this episode, Meena shared her experience coaching a team where the Product Owner (PO) was hostile towards her. The PO had previously been a project manager with control over many aspects of the project, and had trouble adjusting to the new role in Agile. Meena observed that the team was using a mix of Scrum and Waterfall practices, and the PO was still using language like "resources" and moving team members around like Lego pieces.
Meena worked with the team to establish common vocabulary and practices through training and discussions, but found it challenging to help the PO understand the Agile approach. Meena emphasized the importance of working with early adopters in the team and coaching stakeholders outside of the team. Overall, the experience highlights the challenges of change management in Agile and the need for patience, education, and communication to help teams and stakeholders understand and adopt new practices.
[IMAGE HERE] 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 Meena Venkataraman
Meena is an Agile & Lean coach who helps organizations and teams transition to Agile ways of working. She is passionate about the neuroscience behind team dynamics and is interested in organizational design and the application of Agile principles across different business domains. Meena enjoys speaking at conferences and is an avid learner.
You can link with Meena Venkataraman on LinkedIn.
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
In this segment, Meena shares her experience coaching a team that struggled to take off and was stuck in a cycle. Despite being nice to each other during scrum events, team members were not sharing feedback with each other, and psychological safety was not present in the team. Meena stresses the importance of having hard conversations and discussing the interpersonal topics in the team, and she suggests that teams should have the necessary tools to talk about difficult topics.
By highlighting the value that a team coach can bring to a team, Meena emphasizes the importance of psychological safety and how it plays a crucial role in team dynamics. She suggests that teams should be aware of the small things that can become big things and make sure that they are having hard conversations to address interpersonal issues. Ultimately, Meena's experience coaching this team shows that building a successful team is not just about being nice to each other but also about creating a culture of openness, trust, and psychological safety.
We also discuss how using approaches such as non-violent communication can help the Scrum Master create an open environment that is also psychologically safe.
In this segment, Meena Venkataraman recommends the book "Sooner Safer Happier: Antipatterns and Patterns for Business Agility" by Jonathan Smart as a valuable resource for scrum masters. She notes that as a scrum master, it's important to have a holistic view of agile and to be "T-Shaped" - understanding the various facets of product development. Meena highlights that the book brings the 12 principles of agile to life and is a resource she refers to often.
[IMAGE HERE] 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 Meena Venkataraman
Meena is an Agile & Lean coach who helps organizations and teams transition to Agile ways of working. She is passionate about the neuroscience behind team dynamics and is interested in organizational design and the application of Agile principles across different business domains. Meena enjoys speaking at conferences and is an avid learner.
You can link with Meena Venkataraman on LinkedIn.
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
Meena discusses her lessons learned from her first experience in navigating agile adoption. She emphasizes how important it is for us to have a sponsor in our role as Scrum Masters, and notes that we should look out for anti-patterns such as agile being just a buzzword. Meena also highlights the importance of dealing with dysfunctions in the wider system and staying neutral while accepting when things don't work. She suggests coaching managers and asking questions before accepting a job to understand how the organization works. Meena also suggests investigating conversations to find out more about people and aligning expectations with a sponsor as a coach or Scrum Master.
Overall, Meena's lessons learned highlight the importance of navigating change with patience.
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 Meena Venkataraman
Meena is an Agile & Lean coach who helps organizations and teams transition to Agile ways of working. She is passionate about the neuroscience behind team dynamics and is interested in organizational design and the application of Agile principles across different business domains. Meena enjoys speaking at conferences and is an avid learner.
You can link with Meena Venkataraman on LinkedIn.
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
This segment describes an example of a great Product Owner who was also a developer before (like the anti-pattern example). However, this PO had a deep understanding of the product and the business, thought ahead and talked about opportunities with stakeholders. She made tradeoff decisions using her experience, talked to the team on their terms, and went to bat for the team. There was a great chemistry between the Scrum Master and the PO.
In this segment, Mike discusses Product Owner anti-patterns, including POs who think they are the boss, those who are clueless, and those with a development background who second-guess the team. The segment advises that POs should focus on overall aspects such as working with stakeholders, and recommends setting expectations on the role with each PO. The segment also emphasizes the importance of being deliberate about how we integrate our background in our future positions.
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 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.
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
In this segment, we discuss how to measure the success of a scrum master. Mike mentions several questions that can help determine the effectiveness of a scrum master, including whether the team will continue to meet for sprint planning in their absence, or whether team members are actively participating and solving problems together. The goal is to assess whether the team is thriving and hitting their own ambitions even when the scrum master is not present.
In this segment, Mike shares his favorite retrospective format, which is the "Sailboat" format. He explains that this format involves visualizing a sailboat and discussing its different aspects, such as the wind, anchor, and rocks. This visualization helps the team reflect on their work and start conversations that they may not have had otherwise. The sailboat format also helps introverted team members share more and encourages those who tend to dominate discussions to listen more. Mike offers tips for facilitating this retrospective format, including knowing your team and finding ways to encourage everyone to participate.
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 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.
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
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.
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
In this segment, Mike recounted a situation where he was brought in to help a team where there was conflict between two team members who fought about roles and responsibilities. Despite being excellent people individually, when they were together in the same room, they would undermine each other and interrupt each other. Mike took the initiative to understand what was going on and went through every single issue with them.
Upon reflection, Mike realized that remote work was the reason for the misunderstandings and conflict. When the team members first came into the same physical room, they started to mellow out, and this face-to-face presence helped them to accept each other as humans. Mike noted that the team members had projected their problems onto each other, and when they met in person, those problems dissipated. Mike shared two tips based on this experience: first, to meet in person if possible, and second, to have cameras on for retrospectives.
Mike recommended two books related to agile software development and leadership in the podcast. The first book is "Extreme Ownership" by Jocko Willink, which Mike described as agile in a nutshell. The book emphasizes values that can be thought of as the core values for Scrum Masters and explains the key characteristics of a team player. It also helps readers understand what it means to be a servant leader. Mike highlighted the importance of transparency, ownership, and teamwork, which are critical components of agile methodologies. Overall, "Extreme Ownership" provides practical insights into how to become an effective leader and team player.
The second book that Mike recommended is "Trillion Dollar Coach" by Bill Campbell. The book follows the life and work of Bill Campbell, a legendary coach who worked with Google leaders and other leaders in Silicon Valley. Mike noted that the book explains many ideas that are equally applicable to being a Scrum Master and emphasizes the importance of transparency, ownership, and teamwork. Mike explained that the Scrum Master's role is to help team members shine and facilitate effective collaboration. Overall, "Trillion Dollar Coach" provides valuable insights into leadership, team building, and helps understand why agile methodologies actually work.
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 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.
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
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.
BONUS: Mastering the Product Backlog, lessons for Product Owners with Jeff Bubolz and Chad Beier
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
About Jeff Bubolz and Chad Beier
Jeff is a Professional Scrum Trainer (PST) with Scrum.org, organizational agility advisor and speaker. He has been a Product Owner, Scrum Master and Development Team member and has worked with companies ranging from enterprise to small start-ups.
Jeff is the co-host of The Agile Wire podcast where he speaks with industry leaders around the world. He speaks at conferences across the United States and is active in the Wisconsin agile community.
You can link with Jeff Bubolz on LinkedIn and connect with Jeff Bubolz on Twitter.
Chad is an organizational agility advisor, external change agent, and Professional Scrum Trainer (PST) with Scrum.org. He works with all levels of the organization to optimize your business to respond to change.
Chad is the co-host of The Agile Wire podcast where he speaks with industry leaders around the world. He speaks at conferences across the United States and is active in the Wisconsin agile community.
lYou can link with Chad Beier on LinkedIn and connect with Chad Beier on Twitter.
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
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.
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.
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
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.
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.
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.
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
In this episode, Caterina discusses a large-scale Agile transformation she was involved in at a manufacturing company. The transformation was initiated after a successful pilot with a few software development teams. The company adopted a top-down approach, hiring many Agile coaches and implementing a model that combined the Spotify Model and a big-bang change. Despite its success, the transformation was risky due to its size, and Caterina suggests starting the Agile adoption with a single Value Stream and measuring the impact on the business. In this case, the company's culture was also key in integrating the many different backgrounds and expectations from the different regional offices.
The success factors Caterina identified were: team coaching, focus on effective communication, and constant respect for each other.
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.
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
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.
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.
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.
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
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.
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.