Info

Scrum Master Toolbox Podcast

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!
RSS Feed
Scrum Master Toolbox Podcast
2020
February
January


2019
December
November
October
September
August
July
June
May
April
March
February
January


2018
December
November
October
September
August
July
June
May
April
March
February
January


2017
December
November
October
September
August
July
June
May
April
March
February
January


2016
December
November
October
September
August
July
June
May
April
March
February
January


2015
December
November
October
September
August
July
June
May
April
March
February
January


Categories

All Episodes
Archives
Categories
Now displaying: Category: general
Sep 9, 2019

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 Scrum Masters, our role is to help the team grow and continuously deliver valuable software. Sometimes we work with stakeholders to do that, but other times we must be able to set limits to how the stakeholders interfere with the team. In this story, Angeliki talks about a story where the CTO started interfering with the team, and how she learned that as a Scrum Master she needed to help the team set limits to that interference. 

In this episode, we talk about the concept of “Powerful Conversations” which can help communicate with stakeholders when the stakes are high, and there’s a high likelihood of conflict.

 

About Angeliki Hertzfeldt

Angeliki finds that Scrum has transformed her into a better person: in the working environment, with friends and strangers, in social activities, and with her family, as a new mum.

You can link with Angeliki Hertzfeldt on LinkedIn and connect with Angeliki Hertzfeldt on Twitter

Sep 6, 2019

From facilitation to stepping away from line-management approaches, how do we help Product Owners do a good job, and collaborate with the team and Scrum Master? 

The Great Product Owner: The Facilitator of Product Conversations

We often refer to the Scrum Master as a “facilitator”. Sure, but how about the Product Owner? Do we expect the Product Owner to be a “dictator”, and tell others what to do without ever listening to their input? 

In this segment, we talk about the Product Owner as a facilitation role. Facilitating conversations with team and stakeholders about the product. 

The Bad Product Owner: The line-manager turned Product Owner

Some Product Owners expect that they “own” the team. They might even assign tasks to people in the team, and manage people’s time. This is expected if the PO has been - or is - the team’s line manager. But, in those cases, how do we establish a positive relationship and clarify agreements with the Scrum Master? In this segment, we discuss how to work with the PO to set expectations for the work of both the Scrum Master and the Product Owner.


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 Joost Mulders

Joost has been an agile practitioner since 2008 and is continuously uncovering new ways to help teams and organizations on their agile journey. He’s taken several roles in that journey, such as Scrum Master, agile coach or management coach. He strives to create work-life fusion with agile, ultrarunning and filmmaking as the main ingredients.

You can link with Joost Mulders on LinkedIn and connect with Joost Mulders on Twitter.

Sep 5, 2019

According to Joost, seeing our own value is a hard task. How to reflect, what to look at, and how to be sure? 

In this episode, we discuss how Scrum Masters can reflect on their contribution to the team, and what kind of behavior to look for that helps Scrum Masters be sure that they are having a positive impact on the team.

Retrospective Format for the Week: The Lego retrospective that uses self-reflection

When teams enter a retrospective, they usually expect to work on the process. Find improvements, plan some changes, and move on to action. In this segment, we discuss a different type of retrospective, one that focuses on the team’s own self-image, and how it helps the team learn about its team members in-depth.

About Joost Mulders

Joost has been an agile practitioner since 2008 and is continuously uncovering new ways to help teams and organizations on their agile journey. He’s taken several roles in that journey, such as Scrum Master, agile coach or management coach. He strives to create work-life fusion with agile, ultrarunning and filmmaking as the main ingredients.

You can link with Joost Mulders on LinkedIn and connect with Joost Mulders on Twitter.

Sep 4, 2019

Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website

This episode is about the story of changing an airport company to use Agile. This provides a great background to talk about the essence of Agile, and the management practices that go with it. We discuss how to avoid the “buzzword” resistance to change, and how to engage a team that has never heard of Scrum before.

About Joost Mulders

Joost has been an agile practitioner since 2008 and is continuously uncovering new ways to help teams and organizations on their agile journey. He’s taken several roles in that journey, such as Scrum Master, agile coach or management coach. He strives to create work-life fusion with agile, ultrarunning and filmmaking as the main ingredients.

You can link with Joost Mulders on LinkedIn and connect with Joost Mulders on Twitter.

Sep 3, 2019

Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website

This team that Joost was working with was confronted with top-down decisions over which the team had no control. As an example, Architects would tell the team what to do, and how to do it, but would not listen to the team’s perspective. Slowly the team lost motivation, and the bad results quickly followed. In this segment, we reflect on the impact that the environment had on the team, and what Scrum Masters can do to work with teams in that situation.

Featured Book of the Week: Management 3.0 by Jurgen Appelo

In Management 3.0 by Jurgen Appelo, Joost found the inspiration he needed to focus on the overall organization, as opposed to focusing only on the team. We discuss the example of Delegation Poker from Management 3.0, which shows that delegation is not a binary game, but can have many levels and approaches.

About Joost Mulders

Joost has been an agile practitioner since 2008 and is continuously uncovering new ways to help teams and organizations on their agile journey. He’s taken several roles in that journey, such as Scrum Master, agile coach or management coach. He strives to create work-life fusion with agile, ultrarunning and filmmaking as the main ingredients.

You can link with Joost Mulders on LinkedIn and connect with Joost Mulders on Twitter.

Sep 2, 2019

Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website

Scrum Masters are seen as the “process owners”. Some people will even explicitly assign that responsibility to Scrum Masters. But what happens when we focus on the process and forget the business side? 

What would happen if redefined the Scrum Master responsibilities to explicitly include a business perspective? 

In this episode, we talk about the business side of the Scrum Master work, and discuss the important question: “Are we doing the right things?”

About Joost Mulders

Joost has been an agile practitioner since 2008 and is continuously uncovering new ways to help teams and organizations on their agile journey. He’s taken several roles in that journey, such as Scrum Master, agile coach or management coach. He strives to create work-life fusion with agile, ultrarunning and filmmaking as the main ingredients.

You can link with Joost Mulders on LinkedIn and connect with Joost Mulders on Twitter.

Aug 31, 2019

In this episode, we explore the role that checklists can have in helping teams improve their process, and their performance without adding more processes. 

It is a normal tendency to “add more processes” to fix a problem a team is experiencing. In this episode, we challenge that view. Checklists, we argue, are a simple, effective tool that helps you reach a similar goal, but does not require the process to grow, and become bloated. 

Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website

About Diana Getman

Diana Getman has more than 25 years of experience as a project manager leading cross-functional teams, in both startup and non-profit organizations. Diana has held the roles of Scrum Master, Product Owner, and Agile Coach and is the current President at Ascendle, a custom software development firm in Portsmouth, NH.

You can link with Diana Getman on LinkedIn, or visit Ascendle’s blog for more on checklists.

 

Aug 30, 2019

The level of detail and involvement with the implementation decisions is a good indicator of the quality of the Product Owner’s work.

The Great Product Owner: Focusing on the “why?”

Great Product Owners are open to the team’s questions, and even encourage them to ask questions. They focus on communicating the “WHY?” of the product instead of narrowly focusing on the detailed functionality.

The Bad Product Owner: Micro-managing the “how?”

In contrast, the Bad Product Owner focuses on the “HOW?” and may even try to micro-manage the team’s technology and implementation decisions. 

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 Remy Fletcher

Remy is a Scrum Master at a Fin-Tech corporation outside of Boston. Currently working with 3 scrum teams with a focus of migrating individual products onto a centralized, scalable platform.

You can link with Remy Fletcher on LinkedIn and connect with Remy Fletcher on Twitter

 

Aug 29, 2019

Can the team work well without you? This is only one of the questions that Remy asks when evaluating his own contribution to the team’s progress. But there are other questions. In this episode, we discuss questions we can ask ourselves that help us understand how autonomous the team really is. 

Featured Retrospective Format of the Week: Lean Coffee

The Lean Coffee format has been a regular on the podcast. In this episode, we discuss how this format can help teams execute a retrospective in a short time, but still be focused on creating concrete improvement ideas to take on.

In this segment, we also refer to the Kudos practice whereby the team members highlight positive behavior and attitude by other team members.

About Remy Fletcher

Remy is a Scrum Master at a Fin-Tech corporation outside of Boston. Currently working with 3 scrum teams with a focus of migrating individual products onto a centralized, scalable platform.

You can link with Remy Fletcher on LinkedIn and connect with Remy Fletcher on Twitter

Aug 28, 2019

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 Teams will, at some point, go through the process of improving how they run the QA process. Many start with the QA at the end of the Sprint, and then bump into the hard wall that is the timeboxed end of the Sprint. The consequences are many, from stories that spill over to the next sprint, to stressed out testers. In this episode, we walk through a change process that took a team from testing everything at the of the Sprint to testing much earlier and reducing the stress on the testers. 

About Remy Fletcher

Remy is a Scrum Master at a Fin-Tech corporation outside of Boston. Currently working with 3 scrum teams with a focus of migrating individual products onto a centralized, scalable platform.

You can link with Remy Fletcher on LinkedIn and connect with Remy Fletcher on Twitter

Aug 27, 2019

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 some teams, the role of the leader or manager can be a blocker to the team’s adoption of Agile and ownership of the product and process. However, those same managers usually develop their command and control approach due to past successes. As Scrum Masters, we must learn to work with those teams, starting by creating a close relationship with the team members. 

Featured Book of the Week: The Advantage: Why Organizational Health Trumps Everything Else In Business

In The Advantage by Patrick Lencioni, Remy learned about the concept of an executive team that he could apply to his own product when his team was struggling with direction. 

In this segment, we also refer to Start with Why, by Simon Sinek, a book that helped him understand the importance of communicating the rationale behind the decisions and involving the team in owning those decisions.

About Remy Fletcher

Remy is a Scrum Master at a Fin-Tech corporation outside of Boston. Currently working with 3 scrum teams with a focus of migrating individual products onto a centralized, scalable platform.

You can link with Remy Fletcher on LinkedIn and connect with Remy Fletcher on Twitter

 

Aug 26, 2019

Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website

Scrum Masters often need to deal and help resolve conflicts in the teams and with the stakeholders. In this episode, we look at a case of conflicting priorities. We discuss the different approaches, and how the 1-on-1 conversations may cause problems that can be solved unless Scrum Masters get all the parties into the same room.

In this episode, we also talk about the book Getting to YES! by Fischer, Ury and Patton

About Remy Fletcher

Remy is a Scrum Master at a Fin-Tech corporation outside of Boston. Currently working with 3 scrum teams with a focus of migrating individual products onto a centralized, scalable platform.

You can link with Remy Fletcher on LinkedIn and connect with Remy Fletcher on Twitter

 

Aug 23, 2019

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 topics Product Owners choose to focus on, impact greatly their, and their team’s effectiveness. In this episode, we contrast two types of focus, and how those different approaches affect the PO’s work.

The Great Product Owner: The holistic PO

Product Owners, as described in Scrum, are responsible for the success of the Product they own. In this segment, we talk about the whole ecosystem of the product. The PO role is not only about User Stories and Backlogs, and we dive into other critical aspects that are often forgotten.

The Bad Product Owner: The tech-centered, order taker

Product Owners can have a big impact on the effectiveness of the teams they work with. Some PO’s will take that seriously and invest in their growth in either technical or business knowledge. However, when that does not happen, we experience PO’s that take orders from business or want to dive into the technical details - because they are familiar with the technology. In this segment, we talk about the perfect storm of a PO: a PO that only takes orders and wants to dive into the technical details. Listen in to learn how you can help those Product Owners.


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

Aug 22, 2019

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 process of reflection Scrum Masters go through, helps us find our own personal and contextual definition of success. In this episode, Micah describes the types of questions he asks of himself when assessing his success as a Scrum Master.

Featured Retrospective Format for the Week: The 3 questions that focus teams on concrete changes

Micah likes simple formats, and he recommends a format where we focus on 3 questions that help the team members reflect on concrete things they’d like to change. Listen in to learn about what questions he asks his 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

Aug 21, 2019

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 explore the story of a team that was starting to adopt Agile. We discuss the successes, and also the need to accept Work-In-Process (WIP) limits before the team can succeed. 

We discuss a possible set of steps you can follow to introduce WIP limits to your team.

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

 

Aug 20, 2019

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

Aug 19, 2019

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.

Aug 16, 2019

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

Aug 15, 2019

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

Aug 14, 2019

 

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

 

Aug 13, 2019

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

Aug 12, 2019

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

Aug 9, 2019

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

 

Aug 8, 2019

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

Aug 7, 2019

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

 

1 « Previous 3 4 5 6 7 8 9 Next » 27