DiscoverScrum Master Toolbox Podcast
Scrum Master Toolbox Podcast
Claim Ownership

Scrum Master Toolbox Podcast

Author: Vasco Duarte, Agile Coach, Certified Scrum Master, Certified Product Owner

Subscribed: 2,339Played: 75,948
Share

Description

Every week day, Certified Scrum Master, Agile Coach and business consultant Vasco Duarte interviews Scrum Masters and Agile Coaches from all over the world to get you actionable advice, new tips and tricks, improve your craft as a Scrum Master with daily doses of inspiring conversations with Scrum Masters from the all over the world. Stay tuned for BONUS episodes when we interview Agile gurus and other thought leaders in the business space to bring you the Agile Business perspective you need to succeed as a Scrum Master.
Some of the topics we discuss include: Agile Business, Agile Strategy, Retrospectives, Team motivation, Sprint Planning, Daily Scrum, Sprint Review, Backlog Refinement, Scaling Scrum, Lean Startup, Test Driven Development (TDD), Behavior Driven Development (BDD), Paper Prototyping, QA in Scrum, the role of agile managers, servant leadership, agile coaching, and more!
956 Episodes
Reverse
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website.  The focus that some teams have on “execution” can be a great resource. It helps teams get into the details, and push forward even when finding the inevitable setbacks. However, when teams are completely focused on execution there are other aspects that lose focus, and that can derail the team. In this episode, we talk about how the execution focus that some teams have lead them astray from certain critical aspects of the software development process. Featured Book for the Week: The art of doing twice the work in half the time, Jeff Sutherland In The art of doing twice the work in half the time by Jeff Sutherland, Micah found a great reminder and introduction to the Lean principles he now applies in his own work. He also found a great reminder that software development has its own context, that needs to be taken into account in the work Scrum Masters do with software teams. About Micah Stamper Micah worked in technology for about 7 years. He has a background in lean principles and how to bring that to technology. Has done everything from Project Management to Software Engineering, Leadership, and Scrum Master. You can link with Micah Stamper on LinkedIn and connect with Micah Stamper 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.  Many Scrum Masters are incredibly passionate about their work, and helping teams. That’s a great energy and inspiration resource unless… In this episode, we talk about what happens when we expect or ask too much from the teams and people we work with.  In this episode, we refer to the Lean practice of Kaizen, small, constant improvements. About Micah Stamper Micah worked in technology for about 7 years. He has a background in lean principles and how to bring that to technology. Has done everything from Project Management to Software Engineering, Leadership, and Scrum Master. You can link with Micah Stamper on LinkedIn and connect with Micah Stamper 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.  In this episode, we talk about 2 extremes of team engagement by Product Owners: from micro-managing to asking questions and involving the team. The Great Product Owner: Asking Questions to involve the team Good Product Owners allow the team to participate and contribute their views when planning the Sprint. In this segment, we talk about Great Product Owners, those that not only allow, but encourage the team to bring their view into planning and defining the product. We also discuss how asking questions is a critical tool for Product Owners to get teams engaged in the development of the product. In this segment, we talk about transactional analysis, a tool that can help Scrum Masters recognize when the Product Owner needs help in involving the team. The Bad Product Owner: The micro-managing Product Owner When Product Owners “take over” the planning aspects they miss the team’s contribution, and likely motivation. However, there is an even more serious anti-pattern for Product Owners: being a micro-manager. In this segment, we discuss the dangers of over-controlling Product Owners, and how Scrum Masters should react in those cases. Are you having trouble helping the team working 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 Rahul Bhattacharya Rahul Bhattacharya is currently working as an Agile Coach at trivago. He is responsible for optimizing the ways of working within the organization, coaching others on best practices while simultaneously guiding teams working on different products. Rahul is passionate about constant learning through experimentation and feedback. He is also the host of a podcast about Agile, called the Agile Atelier. You can link with Rahul Bhattacharya on LinkedIn and connect with Rahul Bhattacharya 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.  In this episode, we review 5 different aspects that Rahul follows with each team he works with. From how the team delivers each Sprint, to the interaction with the Product Owner, we discuss different aspects that Scrum Masters should pay attention to. In this episode, we also refer to the Agile Maturity Model. There are several maturity models you can follow, I’d recommend starting with the Agile Fluency Model by Diana Larsen and James Shore, which has been introduced here on the podcast. Featured Retrospective Format of the Week: Radar chart for team self-evaluation There are many different exercises for teams to run a self-evaluation exercise. The Radar chart helps the team choose several (typically 5-7) items they want to follow-up on, and evaluate themselves in each topic. If you collect similar charts over time, you will have a graphical representation of how the team has evolved in those core skills or aspect. About Rahul Bhattacharya Rahul Bhattacharya is currently working as an Agile Coach at trivago. He is responsible for optimizing the ways of working within the organization, coaching others on best practices while simultaneously guiding teams working on different products. Rahul is passionate about constant learning through experimentation and feedback. He is also the host of a podcast about Agile, called the Agile Atelier. You can link with Rahul Bhattacharya on LinkedIn and connect with Rahul Bhattacharya 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.  Rahul and Markus, another Scrum Master were helping the QA team move from QA at the end to a more involved QA approach, where QA engineers were to be involved earlier in the process. As you’d expect, this was not an easy change. How did they pull it off? They started by thinking that change happens as a result of new actions as described by John Shook and helped the QA’s and the teams experiment with new approaches. In this episode, we also talk about the importance of accepting that not everybody can accept certain changes, and how that affects your change management efforts. In this episode, we also mention Test-Driven Development and the concept of Pi-Shaped Skills. About Rahul Bhattacharya Rahul Bhattacharya is currently working as an Agile Coach at trivago. He is responsible for optimizing the ways of working within the organization, coaching others on best practices while simultaneously guiding teams working on different products. Rahul is passionate about constant learning through experimentation and feedback. He is also the host of a podcast about Agile, called the Agile Atelier. You can link with Rahul Bhattacharya on LinkedIn and connect with Rahul Bhattacharya 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.  When Rahul started to work with a team that was new to Scrum and Agile, he noticed that the team members were very focused on their individual part of the product. Front-end developers only worked and worried about the front-end, and back-end developers focused on the back-end functionality. In the Sprint reviews, team members focused on their individual contribution, and the inevitable synchronization and coordination problems followed. In this episode, we talk about the risks of highly specialized teams and how to tackle those in your role as a Scrum Master. Featured Book for the Week: The 4-hour workweek by Tim Ferriss In The 4-hour workweek by Tim Ferriss, Rahul found an inspiring story about the choices we make in our daily lives. He learned about “time” as a spendable resource, and how to create more options for yourself as you seek a better life situation. In this segment, we also refer to the Tim Ferriss podcast. About Rahul Bhattacharya Rahul Bhattacharya is currently working as an Agile Coach at trivago. He is responsible for optimizing the ways of working within the organization, coaching others on best practices while simultaneously guiding teams working on different products. Rahul is passionate about constant learning through experimentation and feedback. He is also the host of a podcast about Agile, called the Agile Atelier. You can link with Rahul Bhattacharya on LinkedIn and connect with Rahul Bhattacharya 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.  In this episode, we learn about Rahul’s unusual route to being a Scrum Master, and how the initial focus on velocity led Rahul astray from what really affects a Scrum team’s performance.   We then explore how beginner Scrum Masters can learn to focus on the right aspects from the start and to be flexible enough so that the team does not reject the adoption of Scrum. About Rahul Bhattacharya Rahul Bhattacharya is currently working as an Agile Coach at trivago. He is responsible for optimizing the ways of working within the organization, coaching others on best practices while simultaneously guiding teams working on different products. Rahul is passionate about constant learning through experimentation and feedback He is also the host of a podcast about Agile, called the Agile Atelier. You can link with Rahul Bhattacharya on LinkedIn and connect with Rahul Bhattacharya 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.  In this episode, we talk about one of the most common anti-patterns for PO’s: being too busy, and we also discuss how PO’s can get up to speed in one sprint when they join a new team. The Great Product Owner: The Goal-Oriented PO In this segment, we talk about a new PO. The PO had just joined the company and had to learn quickly. Instead of spending a lot of time reading and asking people, this PO did something different. This PO engaged the team directly and with their help got off to a great start in just one sprint. The Bad Product Owner: The Proxy PO  When teams don’t have direct access to the “customer” PO, they usually resort to using a “proxy PO”. Someone close to the team, that acts as a communication link with the end customer and real PO. However, sometimes those Proxy PO’s have to fulfill other duties, and may even need to serve multiple teams. How can we help teams when that happens?  In this episode, we talk about how to help super busy-PO’s and teams that suffer from their absence. We’ve also produced a guide, that helps you, step-by-step get to an agreement of how to collaborate with overly busy or absent PO’s. You can get the guide on how to work with absent or overly busy Product Owners here. Are you having trouble helping the team working 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 Ines Stuppacher Ines Stuppacher is a passionate team coach and Scrum Master. Working with people challenges and inspires her every day. Her coaching mentality is an important pillar of her life and work. Ines does not impose things on people but rather sees herself as a waiter of options. She strives to show up as her full human self in all kinds of situations and with that fosters real connections with other people. You can link with Ines Stuppacher on LinkedIn or XING and connect with Ines Stuppacher 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.  One way to look at success for Scrum Masters is to ask the team about the contribution of the Scrum Master. Asking them directly, however, can lead to “polite” answers, and avoiding the problems that need solving. In this episode, we talk about other signs that tell us that the team appreciates the contribution of the Scrum Master, and we talk about concrete tools Scrum Masters can use to continue to grow and succeed with their teams. Featured Retrospective Format for the Week: The Wonder Question Agile Retrospective Exercise When a Scrum team is stuck and needs help to find improvements, we can ask them to imagine that something “magic” has happened. Then, we ask what does the team look like now that the “wonder” has happened. With this exercise, we help teams “think outside the box”, without ever having to bring them outside the box. This exercise appeals to the imagination and helps teams imagine a better team that they are all part of. About Ines Stuppacher Ines Stuppacher is a passionate team coach and Scrum Master. Working with people challenges and inspires her every day. Her coaching mentality is an important pillar of her life and work. Ines does not impose things on people but rather sees herself as a waiter of options. She strives to show up as her full human self in all kinds of situations and with that fosters real connections with other people. You can link with Ines Stuppacher on LinkedIn or XING and connect with Ines Stuppacher 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.  As more and more companies adopt OKR (Objectives - Key Results) as a management practice, it is critical that Scrum Masters understand how that tool is used in their organization. In this episode, we discuss how OKR’s can totally derail a company, and how Scrum Masters can join the process and help it improve. This is especially important because OKR’s - when effectively used - will have a large influence on the teams we work with. About Ines Stuppacher Ines Stuppacher is a passionate team coach and Scrum Master. Working with people challenges and inspires her every day. Her coaching mentality is an important pillar of her life and work. Ines does not impose things on people but rather sees herself as a waiter of options. She strives to show up as her full human self in all kinds of situations and with that fosters real connections with other people. You can link with Ines Stuppacher on LinkedIn or XING and connect with Ines Stuppacher on Twitter.   
loading
Comments (8)

Dan Matte

Hello Catrine, I'm impressed that you took up the initiative to defuse the conflict that had started to brew up in the team. Better late than never. The signs of being a leader is to always do something about anything going wrong, even though it may not be a matter of concern to us (this was however).

May 1st
Reply

Dominique lin

Very good poadcast !

Apr 30th
Reply

Patricia Ayuso

Hi Vasco, Ajeet. Thank you for your story. I have a question for you. Shouldn't the dev team include everyone involved in the success of the development of the project like designer, copywriter, UX expert...?

Mar 13th
Reply

Patricia Ayuso

Ajeet Singh Good point Ajeet thank you.

Apr 19th
Reply

Ajeet Singh

Patricia Ayuso Hi Patricia, ideally yes, but in real world every setup has its own dependencies and challenges to deal with so it differs and is contextual.

Apr 10th
Reply

Mya Z

Great podcast!

Aug 3rd
Reply

Sergei Davidov

Hi Vasco, I really enjoy the podcast 😉. Thank you. I was wondering if you could share the link to Scrum games that kristina mentioned in the episode around measuring?

Jan 14th
Reply

PH TrooperX

That's an insight.

Nov 7th
Reply
loading
Download from Google Play
Download from App Store