The first thing people tend to see when they look at the Scrum framework are the roles, the artifacts, and the events. But that is only structure. There is much more going on in Scrum teams that we can understand better from other perspectives.One such perspective is motivation. Scrum is deeply rooted in insights from academic research into what motivates people and teams to become high-performing. And while those roots are strong, they are also mostly invisible and unknown to practitioners.In this podcast, we take a scientific perspective on how Scrum can create motivating environments for teams and individuals. We also translate these insights into practical tips that you can use to make the work for your team more motivating.Read the full post behind this episode, including all the links, here https://bit.ly/3HKZRuESupport our show at:https://patreon.com/liberatorsDiagnose how well things are going with your Scrum Team with the Scrum Team Survey:https://scrumteamsurvey.orgSupport the show

The first thing people tend to see when they look at the Scrum framework are the roles, the artifacts, and the events. But that is only structure. There is much more going on in Scrum teams that we can understand better from other perspectives. One such perspective is motivation. Scrum is deeply rooted in insights from academic research into what motivates people and teams to become high-performing. And while those roots are strong, they are also mostly invisible and unknown to practitioners. In this podcast, we take a scientific perspective on how Scrum can create motivating environments for teams and individuals. We also translate these insights into practical tips that you can use to make the work for your team more motivating. Read the full post behind this episode, including all the links, here <a href="https://bit.ly/3HKZRuE" rel="nofollow" target="_blank">https://bit.ly/3HKZRuE</a> Support our show at: <a href="https://patreon.com/liberators" rel="nofollow" target="_blank">https://patreon.com/liberators</a> Diagnose how well things are going with your Scrum Team with the Scrum Team Survey: <a href="https://scrumteamsurvey.org" rel="nofollow" target="_blank">https://scrumteamsurvey.org </a> <a href="https://bit.ly/supportheliberators" rel="payment nofollow" target="_blank">Support the show</a>

In-Depth: How Scrum Motivates Through Shared Goals And High Autonomy

“We consistently observe that teams struggle with continuous improvement. Instead of keeping it small, simple, and practical, teams go for ambitious — but vague and unclear — improvements.”The improvement actions that come out of Sprint Retrospectives and other reflective practices are weak when there is no sense of scope, no sense of timeline, and no sense of who is involved. Interestingly, this creates a clear connection with something else that good Agile teams spend a lot of time on: refinement.In this episode, we explore how to refine your improvement actions to make them more actionable and thus easier to accomplish. We also offer a lot of practical tips for how to create better improvement actions.Read the transcript here:https://bit.ly/3KqtfGAYou can try the Scrum Team Survey with your team at:https://scrumteamsurvey.orgOr get our "Unleash Scrum In Your Organization"-kit which contains - among many other cool things - a deck with 100 Improvement Actions categorized into different areas. These are a good source of inspiration for your own improvements. Or you can use them verbatim:https://shop.theliberators.com/collections/frontpage/products/scrum-teams-superpower-kit-also-for-virtual-teamsSupport the show

“We consistently observe that teams struggle with continuous improvement. Instead of keeping it small, simple, and practical, teams go for ambitious — but vague and unclear — improvements.” The improvement actions that come out of Sprint Retrospectives and other reflective practices are weak when there is no sense of scope, no sense of timeline, and no sense of who is involved. Interestingly, this creates a clear connection with something else that good Agile teams spend a lot of time on: refinement. In this episode, we explore how to refine your improvement actions to make them more actionable and thus easier to accomplish. We also offer a lot of practical tips for how to create better improvement actions. Read the transcript here: <a href="https://bit.ly/3KqtfGA" rel="nofollow" target="_blank">https://bit.ly/3KqtfGA</a> You can try the Scrum Team Survey with your team at: <a href="https://scrumteamsurvey.org" rel="nofollow" target="_blank">https://scrumteamsurvey.org</a> Or get our "Unleash Scrum In Your Organization"-kit which contains - among many other cool things - a deck with 100 Improvement Actions categorized into different areas. These are a good source of inspiration for your own improvements. Or you can use them verbatim: <a href="https://shop.theliberators.com/collections/frontpage/products/scrum-teams-superpower-kit-also-for-virtual-teams" rel="nofollow" target="_blank">https://shop.theliberators.com/collections/frontpage/products/scrum-teams-superpower-kit-also-for-virtual-teams</a><a href="https://bit.ly/supportheliberators" rel="payment nofollow" target="_blank">Support the show</a>

In-Depth: The Fine Art Of Making Your Improvements Actionable

What makes a good Product Owner? How much time should they spend with their team or with stakeholders? Or writing items for the Product Backlog? Do Product Owners require a full mandate in order to be effective? What strategies make them more - or less - effective?In this episode, we explore scientific research that investigated Product Owners. We also share some of our own research. Read the transcript here:https://bit.ly/2XXBaZ7Try the Scrum Team Survey for free with your team at:https://scrumteamsurvey.orgOr download do-it-yourself workshops to encourage shared product ownership:https://shop.theliberators.com/collections/do-it-yourself-workshops-meetups-and-strings/build-what-stakeholders-needSupport the show

What makes a good Product Owner? How much time should they spend with their team or with stakeholders? Or writing items for the Product Backlog? Do Product Owners require a full mandate in order to be effective? What strategies make them more - or less - effective? In this episode, we explore scientific research that investigated Product Owners. We also share some of our own research. Read the transcript here: <a href="https://bit.ly/2XXBaZ7" rel="nofollow" target="_blank">https://bit.ly/2XXBaZ7</a> Try the Scrum Team Survey for free with your team at: <a href="https://scrumteamsurvey.org" rel="nofollow" target="_blank">https://scrumteamsurvey.org</a> Or download do-it-yourself workshops to encourage shared product ownership: <a href="https://shop.theliberators.com/collections/do-it-yourself-workshops-meetups-and-strings/build-what-stakeholders-need" rel="nofollow" target="_blank">https://shop.theliberators.com/collections/do-it-yourself-workshops-meetups-and-strings/build-what-stakeholders-need </a> <a href="https://bit.ly/supportheliberators" rel="payment nofollow" target="_blank">Support the show</a>

In-Depth: What Makes A Good Product Owner?

"SAFe destroys autonomy", "estimation is a waste of time" and "Scrum Masters can't also be Product Owners" are just a few of the strong claims that are often made in our professional community.But where is the evidence to support these bold claims? We sampled 50 posts with similar bold claims and found that only 3 offered *any* kind of evidence. Two of those were purely personal experiences. We also explored some actual research into these questions and found more nuanced results.We wonder: why doesn't our community - that is all about empiricism - apply empiricism to itself and its claims? Why don't we gather actual objective evidence? Why do we allow each other to make bold claims that either lack evidence or aren't proportional to that evidence? Are we not harming our profession with this low bar?In this episode, we discuss a professional crisis in our field. We also offer five things we can do to improve our profession. Ultimately, if we rely more on objective evidence we make a much stronger case for what we believe to be true. Or we may discover that our beliefs aren't actually true - which is a good thing too.Read the transcript here:https://medium.com/the-liberators/why-doesnt-the-agile-community-practice-empiricism-12082e48ffbaSupport the show

"SAFe destroys autonomy", "estimation is a waste of time" and "Scrum Masters can't also be Product Owners" are just a few of the strong claims that are often made in our professional community. But where is the evidence to support these bold claims? We sampled 50 posts with similar bold claims and found that only 3 offered *any* kind of evidence. Two of those were purely personal experiences. We also explored some actual research into these questions and found more nuanced results. We wonder: why doesn't our community - that is all about empiricism - apply empiricism to itself and its claims? Why don't we gather actual objective evidence? Why do we allow each other to make bold claims that either lack evidence or aren't proportional to that evidence? Are we not harming our profession with this low bar? In this episode, we discuss a professional crisis in our field. We also offer five things we can do to improve our profession. Ultimately, if we rely more on objective evidence we make a much stronger case for what we believe to be true. Or we may discover that our beliefs aren't actually true - which is a good thing too. Read the transcript here: <a href="https://medium.com/the-liberators/why-doesnt-the-agile-community-practice-empiricism-12082e48ffba" rel="nofollow" target="_blank">https://medium.com/the-liberators/why-doesnt-the-agile-community-practice-empiricism-12082e48ffba</a><a href="https://bit.ly/supportheliberators" rel="payment nofollow" target="_blank">Support the show</a>

Why Doesn't The Agile Community Practice Empiricism?

"It slowly started to dawn on me that something else was happening during these gatherings. Something I hadn’t seen before so clearly in my previous work with groups. I saw so many happy faces around me. I saw so many people intently listening to each other as each shared a personal story. And I saw so many people touched by the awareness that others were really listening to them as they shared those stories."This  episode is about the psychological power of Liberating Structures. They are like a language for how people interact. Once you learn to speak and recognize its symbols and its grammar, you see its potential everywhere people interact. I know how weird that sounds — especially when you’ve never experienced them before. This potential affirms my belief that we should use Liberating Structures everywhere people interact.Unfortunately, even experienced practitioners tended to limit their use to the more obvious settings, like workshops, classes, and training, but not to other settings, like recurring meetings, social settings, and other informal settings. And that includes us too. And that's a waste, as we explore in this post.Read the transcript for this episode here (along with pictures)https://bit.ly/2Z8uk3MJoin an upcoming Immersion Workshop via:https://liberatingstructures.nlOr https://liberatingstructures.comSupport the show

"It slowly started to dawn on me that something else was happening during these gatherings. Something I hadn’t seen before so clearly in my previous work with groups. I saw so many happy faces around me. I saw so many people intently listening to each other as each shared a personal story. And I saw so many people touched by the awareness that others were really listening to them as they shared those stories." This  episode is about the psychological power of Liberating Structures. They are like a language for how people interact. Once you learn to speak and recognize its symbols and its grammar, you see its potential everywhere people interact. I know how weird that sounds — especially when you’ve never experienced them before. This potential affirms my belief that we should use Liberating Structures everywhere people interact. Unfortunately, even experienced practitioners tended to limit their use to the more obvious settings, like workshops, classes, and training, but not to other settings, like recurring meetings, social settings, and other informal settings. And that includes us too. And that's a waste, as we explore in this post. Read the transcript for this episode here (along with pictures) <a href="https://bit.ly/2Z8uk3M" rel="nofollow" target="_blank">https://bit.ly/2Z8uk3M</a> Join an upcoming Immersion Workshop via: <a href="https://liberatingstructures.nl" rel="nofollow" target="_blank">https://liberatingstructures.nl</a> Or <a href="https://liberatingstructures.com" rel="nofollow" target="_blank">https://liberatingstructures.com</a><a href="https://bit.ly/supportheliberators" rel="payment nofollow" target="_blank">Support the show</a>

Liberating Structures Should Be Everywhere People Interact

Are Scrum Masters perhaps too focused on the process, and too little on whether or not that process actually delivers valuable outcomes? How is that for you, as a Scrum Master?This is a hunch based on countless conversations we've had with Scrum Masters, including our own practice as a Scrum Master. But what do the facts say? So we read relevant scientific studies and collected data through a large poll (500+ participants) and data from almost 2.000 Scrum teams. We were also fortunate to use data from a research study by McKinsey and Scrum.org.The data suggest that Scrum Masters are more effective when they balance a process-based perspective with a value-based perspective. This means that Scrum Masters lead in designing effective Sprint Reviews, drawing in stakeholders, and emphasizing the need for this. I expect that Scrum Masters that stake a strong stance here are more likely to see effective Scrum teams over time. I offer tips on how to do this.Read the transcript here:https://medium.com/the-liberators/are-scrum-masters-sufficiently-focused-on-valuable-outcomes-7b51c4403869 Diagnose your team with the Scrum Team Survey:https://scrumteamsurvey.orgSupport the show

Are Scrum Masters perhaps too focused on the process, and too little on whether or not that process actually delivers valuable outcomes? How is that for you, as a Scrum Master? This is a hunch based on countless conversations we've had with Scrum Masters, including our own practice as a Scrum Master. But what do the facts say? So we read relevant scientific studies and collected data through a large poll (500+ participants) and data from almost 2.000 Scrum teams. We were also fortunate to use data from a research study by McKinsey and <a href="http://Scrum.org" rel="nofollow" target="_blank">Scrum.org</a>. The data suggest that Scrum Masters are more effective when they balance a process-based perspective with a value-based perspective. This means that Scrum Masters lead in designing effective Sprint Reviews, drawing in stakeholders, and emphasizing the need for this. I expect that Scrum Masters that stake a strong stance here are more likely to see effective Scrum teams over time. I offer tips on how to do this. Read the transcript here: <a href="https://medium.com/the-liberators/are-scrum-masters-sufficiently-focused-on-valuable-outcomes-7b51c4403869" rel="nofollow" target="_blank">https://medium.com/the-liberators/are-scrum-masters-sufficiently-focused-on-valuable-outcomes-7b51c4403869</a> Diagnose your team with the Scrum Team Survey: <a href="https://scrumteamsurvey.org" rel="nofollow" target="_blank">https://scrumteamsurvey.org </a> <a href="https://bit.ly/supportheliberators" rel="payment nofollow" target="_blank">Support the show</a>

In-Depth: Are Scrum Masters Sufficiently Focused On Valuable Outcomes?

We are creating the Scrum Team Survey to help Scrum teams and Agile teams to diagnose their process. We also give tons of evidence-based feedback. One of the cool things about developing a product ourselves, and with our own money, is that we get to learn (or reaffirm) a lot of valuable lessons about Agile software development. In this episode, we share our 10 biggest lessons. Be prepared for some technical stuff though, as several of these lessons involve architecture, design, and code quality.Read the blog post for this episode here:https://medium.com/the-liberators/how-work-on-the-scrum-team-survey-taught-us-10-lessons-about-agile-95314ee2fdc1Try the Scrum Team Survey here (it's free for individual teams)https://scrumteamsurvey.orgTry the Team Dashboard here:https://scrumteamsurvey.org/demoteamdashboardSupport the show

We are creating the Scrum Team Survey to help Scrum teams and Agile teams to diagnose their process. We also give tons of evidence-based feedback. One of the cool things about developing a product ourselves, and with our own money, is that we get to learn (or reaffirm) a lot of valuable lessons about Agile software development. In this episode, we share our 10 biggest lessons. Be prepared for some technical stuff though, as several of these lessons involve architecture, design, and code quality. Read the blog post for this episode here: <a href="https://medium.com/the-liberators/how-work-on-the-scrum-team-survey-taught-us-10-lessons-about-agile-95314ee2fdc1" rel="nofollow" target="_blank">https://medium.com/the-liberators/how-work-on-the-scrum-team-survey-taught-us-10-lessons-about-agile-95314ee2fdc1</a> Try the Scrum Team Survey here (it's free for individual teams) <a href="https://scrumteamsurvey.org" rel="nofollow" target="_blank">https://scrumteamsurvey.org</a> Try the Team Dashboard here: <a href="https://scrumteamsurvey.org/demoteamdashboard" rel="nofollow" target="_blank">https://scrumteamsurvey.org/demoteamdashboard</a><a href="https://bit.ly/supportheliberators" rel="payment nofollow" target="_blank">Support the show</a>

How Work On The Scrum Team Survey Taught Us 10 Lessons About Agile

Do your Daily Scrums feel like a pointless ritual where everyone just lists what they’ve done yesterday, and what they do will do today? Does Sprint Planning feel like a waste of time because everyone only wants to know what they have to do? And does your Sprint Review consist of team members listing their individual accomplishments? If so, you are probably dealing with a complete lack of coherence and cohesion.This episode is an exploration of scientific insights that help us understand what coherence and cohesion are, and why they are so important. We also explore how these insights create a strong foundation for the Scrum framework. We also translate scientific insights into practical applications, ready for use with your team.Read the transcript here:https://medium.com/the-liberators/in-depth-how-coherence-and-cohesion-are-critical-to-scrum-f5ae1f3a1aefFind many do-it-yourself workshops to help your team:https://shop.theliberators.com/collections/do-it-yourself-workshops-meetups-and-strings/ScrumSupport the show:https://patreon.com/liberatorsSupport the show

Do your Daily Scrums feel like a pointless ritual where everyone just lists what they’ve done yesterday, and what they do will do today? Does Sprint Planning feel like a waste of time because everyone only wants to know what they have to do? And does your Sprint Review consist of team members listing their individual accomplishments? If so, you are probably dealing with a complete lack of coherence and cohesion. This episode is an exploration of scientific insights that help us understand what coherence and cohesion are, and why they are so important. We also explore how these insights create a strong foundation for the Scrum framework. We also translate scientific insights into practical applications, ready for use with your team. Read the transcript here: <a href="https://medium.com/the-liberators/in-depth-how-coherence-and-cohesion-are-critical-to-scrum-f5ae1f3a1aef" rel="nofollow" target="_blank">https://medium.com/the-liberators/in-depth-how-coherence-and-cohesion-are-critical-to-scrum-f5ae1f3a1aef</a> Find many do-it-yourself workshops to help your team: <a href="https://shop.theliberators.com/collections/do-it-yourself-workshops-meetups-and-strings/Scrum" rel="nofollow" target="_blank">https://shop.theliberators.com/collections/do-it-yourself-workshops-meetups-and-strings/Scrum</a> Support the show: <a href="https://shop.theliberators.com/collections/do-it-yourself-workshops-meetups-and-strings/Scrum" rel="nofollow" target="_blank">https://patreon.com/liberators </a> <a href="https://bit.ly/supportheliberators" rel="payment nofollow" target="_blank">Support the show</a>

In-Depth: How Coherence And Cohesion Are Critical To Scrum

Do you start a new Scrum team by explaining the roles, artifacts, and events? Do you rarely consider how to build coalitions and persuade people in power to support your work with Scrum? Are you thinking about the psychological needs of people and how to motivate them to work with Scrum? You may be engaging in a bit too much blueprint thinking.In this episode, we explore how blue-print thinking is too dominant in our profession. There are exceptions. But much of the professional discourse is focused on frameworks, processes, and structure — independent of the messy sociological, political, and psychological realities of organizations. We explore how this bias leads to blind spots. It also explains why so many framework implementations fail. This episode is based on the “Color Theory of Change”, and we think its quite eye-opening if you've never reflected on this before.Find the transcript here:https://medium.com/the-liberators/is-blue-print-thinking-limiting-the-potential-of-the-agile-community-a2ee716b6888Support our show at Patreon:https://patreon.com/liberatorsSupport the show

Do you start a new Scrum team by explaining the roles, artifacts, and events? Do you rarely consider how to build coalitions and persuade people in power to support your work with Scrum? Are you thinking about the psychological needs of people and how to motivate them to work with Scrum? You may be engaging in a bit too much blueprint thinking. In this episode, we explore how blue-print thinking is too dominant in our profession. There are exceptions. But much of the professional discourse is focused on frameworks, processes, and structure — independent of the messy sociological, political, and psychological realities of organizations. We explore how this bias leads to blind spots. It also explains why so many framework implementations fail. This episode is based on the “Color Theory of Change”, and we think its quite eye-opening if you've never reflected on this before. Find the transcript here: <a href="https://medium.com/the-liberators/is-blue-print-thinking-limiting-the-potential-of-the-agile-community-a2ee716b6888" rel="nofollow" target="_blank">https://medium.com/the-liberators/is-blue-print-thinking-limiting-the-potential-of-the-agile-community-a2ee716b6888</a> Support our show at Patreon: <a href="https://patreon.com/liberators" rel="nofollow" target="_blank">https://patreon.com/liberators</a> <a href="https://bit.ly/supportheliberators" rel="payment nofollow" target="_blank">Support the show</a>

Is Blue-print Thinking Limiting The Potential Of The Agile Community?

Recently, the concept of “fluid teams”, “dynamic reteaming” or “ad-hoc teaming” has gained traction in the Agile community. Although the concept has many different definitions, a characteristic they share is that members move in and out of a team during its lifetime.However, decades of academic research into teams and workgroups have underscored the importance of team stability as a requirement for high performance. Although these studies did not compare stable teams versus fluid teams specifically, the most reliable theories we currently have to understand team development also seem to favor stability over fluidity.In this episode, I explore the research in this area. Considering just how popular the notion of fluid teams has become, I think it is important to weigh the evidence that supports it or contradicts it.Read the transcript of the episode here (including all references): https://medium.com/the-liberators/in-depth-stable-or-fluid-teams-what-does-the-science-say-95833b0b91a2Read an in-depth post about team cognition:https://medium.com/the-liberators/why-great-scrum-teams-have-a-mind-of-their-own-2ba4d9d17918Read an in-depth post about social cohesion:https://medium.com/the-liberators/in-depth-how-coherence-and-cohesion-are-critical-to-scrum-f5ae1f3a1aefSupport the show at:https://patreon.com/liberatorsSupport the show

Recently, the concept of “fluid teams”, “dynamic reteaming” or “ad-hoc teaming” has gained traction in the Agile community. Although the concept has many different definitions, a characteristic they share is that members move in and out of a team during its lifetime.However, decades of academic research into teams and workgroups have underscored the importance of team stability as a requirement for high performance. Although these studies did not compare stable teams versus fluid teams specifically, the most reliable theories we currently have to understand team development also seem to favor stability over fluidity.In this episode, I explore the research in this area. Considering just how popular the notion of fluid teams has become, I think it is important to weigh the evidence that supports it or contradicts it. Read the transcript of the episode here (including all references): <a href="https://medium.com/the-liberators/in-depth-stable-or-fluid-teams-what-does-the-science-say-95833b0b91a2" rel="nofollow" target="_blank">https://medium.com/the-liberators/in-depth-stable-or-fluid-teams-what-does-the-science-say-95833b0b91a2</a> Read an in-depth post about team cognition: <a href="https://medium.com/the-liberators/why-great-scrum-teams-have-a-mind-of-their-own-2ba4d9d17918" rel="nofollow" target="_blank">https://medium.com/the-liberators/why-great-scrum-teams-have-a-mind-of-their-own-2ba4d9d17918</a> Read an in-depth post about social cohesion: <a href="https://medium.com/the-liberators/in-depth-how-coherence-and-cohesion-are-critical-to-scrum-f5ae1f3a1aef" rel="nofollow" target="_blank">https://medium.com/the-liberators/in-depth-how-coherence-and-cohesion-are-critical-to-scrum-f5ae1f3a1aef </a> Support the show at: <a href="https://patreon.com/liberators" rel="nofollow" target="_blank">https://patreon.com/liberators</a><a href="https://bit.ly/supportheliberators" rel="payment nofollow" target="_blank">Support the show</a>

In-Depth: Stable Or Fluid Teams? What Does The Science Say?

If you're excited about unleashing organizational superpowers, then this is the podcast for you. We talk about Scrum, Liberating Structures, and creating better workplaces. This podcast is created by Christiaan Verwijs and Barry Overeem. Both are Professional Scrum Trainers for Scrum.org and stewards of the Professional Scrum Master II class they created. Aside from their extensive background and experience with Scrum, they are very excited about Liberating Structures and are active members of this worldwide community. We publish a new episode every first Friday of the month.

If you're excited about unleashing organizational superpowers, then this is the podcast for you. We talk about Scrum, Liberating Structures, and creating better workplaces. This podcast is created by Christiaan Verwijs and Barry Overeem. Both are Professional Scrum Trainers for <a href="http://Scrum.org" rel="nofollow" target="_blank">Scrum.org</a> and stewards of the Professional Scrum Master II class they created. Aside from their extensive background and experience with Scrum, they are very excited about Liberating Structures and are active members of this worldwide community. We publish a new episode every first Friday of the month.

The Liberators Network

Does Refinement feel like a chore for your team? Is refinement taking place during required meetings during the Sprint? In this episode, we address the myth that refinement is a required meeting in Scrum. We also explore what the purpose of refinement is in the first place, and how to make it more effective.We love to share our materials. Please help us by supporting our work. You can do so by giving us a thumbs-up on the platform you're listening on. Or follow us on Twitter, Medium or LinkedIn (Barry &amp; Christiaan).This podcast is an audio recording of this post on Medium: http://bit.ly/2N59XfWFollow us on Medium:https://medium.com/the-liberatorsOr check out our upcoming events at:https://theliberators.com/eventsDonate to support our workhttps://bit.ly/supportheliberatorsSupport the show

Does Refinement feel like a chore for your team? Is refinement taking place during required meetings during the Sprint? In this episode, we address the myth that refinement is a required meeting in Scrum. We also explore what the purpose of refinement is in the first place, and how to make it more effective. We love to share our materials. Please help us by supporting our work. You can do so by giving us a thumbs-up on the platform you're listening on. Or follow us on <a href="http://bit.ly/2S6YZGE" rel="nofollow" target="_blank">Twitter</a>, <a href="http://bit.ly/2CdRdad" rel="nofollow" target="_blank">Medium</a> or LinkedIn (<a href="http://bit.ly/2PAAq6s" rel="nofollow" target="_blank">Barry</a> &amp; <a href="http://bit.ly/2Q7YECl" rel="nofollow" target="_blank">Christiaan</a>). This podcast is an audio recording of this post on Medium: <a href="http://bit.ly/2N59XfW" rel="nofollow" target="_blank">http://bit.ly/2N59XfW</a> Follow us on Medium: <a href="http://bit.ly/2CdRdad" rel="nofollow" target="_blank">https://medium.com/the-liberators</a> Or check out our upcoming events at: <a href="http://bit.ly/2Lw6M1w" rel="nofollow" target="_blank">https://theliberators.com/events</a> Donate to support our work <a href="https://bit.ly/supportheliberators" rel="nofollow" target="_blank">https://bit.ly/supportheliberators</a><a href="https://bit.ly/supportheliberators" rel="payment nofollow" target="_blank">Support the show</a>

Scrum Mythbusters: Refinement Is A Required Meeting For The Entire Scrum Team

Are you a Scrum Master and ready for the next step as Agile Coach? Do you need an Agile Coach to help facilitate organizational change while Scrum Masters focus on the Scrum Teams? Do you have experience as a Scrum Master and want to become Agile Coach with a 3-day course? Ever considered changing your job title to ‘Agile Coach’ because it nets you a higher salary?These statements exemplify the myth that we intend to bust today; the idea that the Scrum Master is a Junior Agile Coach. Or maybe even that you need Agile Coaches ...We love to share our materials. Please help us by supporting our work. You can do so by giving us a thumbs-up on the platform you're listening on. Or follow us on Twitter, Medium or LinkedIn (Barry &amp; Christiaan).This podcast is an audio recording of this post on Medium:http://bit.ly/2VJD8tvFollow us on Medium:https://medium.com/the-liberatorsOr check out our upcoming events at:https://theliberators.com/eventsDonate to support our workhttps://bit.ly/supportheliberatorsSupport the show

Are you a Scrum Master and ready for the next step as Agile Coach? Do you need an Agile Coach to help facilitate organizational change while Scrum Masters focus on the Scrum Teams? Do you have experience as a Scrum Master and want to become Agile Coach with a 3-day course? Ever considered changing your job title to ‘Agile Coach’ because it nets you a higher salary? These statements exemplify the myth that we intend to bust today; the idea that the Scrum Master is a Junior Agile Coach. Or maybe even that you need Agile Coaches ... We love to share our materials. Please help us by supporting our work. You can do so by giving us a thumbs-up on the platform you're listening on. Or follow us on <a href="http://bit.ly/2S6YZGE" rel="nofollow" target="_blank">Twitter</a>, <a href="http://bit.ly/2CdRdad" rel="nofollow" target="_blank">Medium</a> or LinkedIn (<a href="http://bit.ly/2PAAq6s" rel="nofollow" target="_blank">Barry</a> &amp; <a href="http://bit.ly/2Q7YECl" rel="nofollow" target="_blank">Christiaan</a>). This podcast is an audio recording of this post on Medium: <a href="http://bit.ly/2VJD8tv" rel="nofollow" target="_blank">http://bit.ly/2VJD8tv</a> Follow us on Medium: <a href="http://bit.ly/2CdRdad" rel="nofollow" target="_blank">https://medium.com/the-liberators</a> Or check out our upcoming events at: <a href="http://bit.ly/2Lw6M1w" rel="nofollow" target="_blank">https://theliberators.com/events</a> Donate to support our work <a href="https://bit.ly/supportheliberators" rel="nofollow" target="_blank">https://bit.ly/supportheliberators</a><a href="https://bit.ly/supportheliberators" rel="payment nofollow" target="_blank">Support the show</a>

Scrum Mythbusters: The Scrum Master Is A Junior Agile Coach

Is the Product Owner the only person who interacts with stakeholders? You may also recognize a Product Owner who claims exclusive responsibility for talking with users. Or the Product Owner as the only member of a Scrum Team who identifies and clarifies work for the Product Backlog.In this episode, we bust the myth that the Product Owner is the only person on a Scrum Team who interacts with stakeholders, like users and customers.We love to share our materials. Please help us by supporting our work. You can do so by giving us a thumbs-up on the platform you're listening on. Or follow us on Twitter, Medium or LinkedIn (Barry &amp; Christiaan).This podcast is an audio recording of this post on Medium: http://bit.ly/2OS1eQxFollow us on Medium:https://medium.com/the-liberatorsOr check out our upcoming events at:https://theliberators.com/eventsLike our work? You can support us by becoming a patreon and donating the price of a beer or a coffee:https://www.patreon.com/liberatorsSupport the show

Is the Product Owner the only person who interacts with stakeholders? You may also recognize a Product Owner who claims exclusive responsibility for talking with users. Or the Product Owner as the only member of a Scrum Team who identifies and clarifies work for the Product Backlog. In this episode, we bust the myth that the Product Owner is the only person on a Scrum Team who interacts with stakeholders, like users and customers.We love to share our materials. Please help us by supporting our work. You can do so by giving us a thumbs-up on the platform you're listening on. Or follow us on <a href="http://bit.ly/2S6YZGE" rel="nofollow" target="_blank">Twitter</a>, <a href="http://bit.ly/2CdRdad" rel="nofollow" target="_blank">Medium</a> or LinkedIn (<a href="http://bit.ly/2PAAq6s" rel="nofollow" target="_blank">Barry</a> &amp; <a href="http://bit.ly/2Q7YECl" rel="nofollow" target="_blank">Christiaan</a>). This podcast is an audio recording of this post on Medium: <a href="http://bit.ly/2OS1eQx" rel="nofollow" target="_blank">http://bit.ly/2OS1eQx</a> Follow us on Medium: <a href="http://bit.ly/2CdRdad" rel="nofollow" target="_blank">https://medium.com/the-liberators</a> Or check out our upcoming events at: <a href="http://bit.ly/2Lw6M1w" rel="nofollow" target="_blank">https://theliberators.com/events</a> Like our work? You can support us by becoming a patreon and donating the price of a beer or a coffee: <a href="http://bit.ly/2JBbuaY" rel="nofollow" target="_blank">https://www.patreon.com/liberators</a><a href="https://bit.ly/supportheliberators" rel="payment nofollow" target="_blank">Support the show</a>

Scrum Mythbusters: Only The Product Owner Interacts With Stakeholders

In this episode we're using the Liberating Structure "Troika Consulting" to offer help to one of our listeners. Its an experiment, so let us know what you think. One of our patrons, Sven de Koning, provided us with the following challenge: "My team is unable to deliver a done increment because they don't know how to slice items on their Product Backlog vertically. How can I help them?". In true Troika-fashion, we briefly explored the challenge in 2 minutes and then started generating ideas for what might be helpful. Although based on many assumptions, the idea here is that simply listening to other people talk about your challenge can generate ideas that you haven't considered before. Want to know more?Learn more about Troika Consulting here;Or click here to discover our 10 strategies for breaking down large Product Backlog Items vertically (PDF included);Have a challenge for us?If you have a challenge you are facing, and you'd like to hear our perspectives through Troika Consulting, let us know. You can email us at info@theliberators.com or connect wit us through other means.Donate to support our workhttps://bit.ly/supportheliberatorsFollow us on Medium:https://medium.com/the-liberatorsSupport the show

In this episode we're using the Liberating Structure "Troika Consulting" to offer help to one of our listeners. Its an experiment, so let us know what you think. One of our patrons, Sven de Koning, provided us with the following challenge: "My team is unable to deliver a done increment because they don't know how to slice items on their Product Backlog vertically. How can I help them?". In true Troika-fashion, we briefly explored the challenge in 2 minutes and then started generating ideas for what might be helpful. Although based on many assumptions, the idea here is that simply listening to other people talk about your challenge can generate ideas that you haven't considered before. Want to know more?<ul><li>Learn more about Troika Consulting <a href="http://bit.ly/3009mAv" rel="nofollow" target="_blank">here</a>;</li><li>Or <a href="http://bit.ly/2Swod1g" rel="nofollow" target="_blank">click here</a> to discover our 10 strategies for breaking down large Product Backlog Items vertically (PDF included);</li></ul>Have a challenge for us? If you have a challenge you are facing, and you'd like to hear our perspectives through Troika Consulting, let us know. You can email us at <a href="mailto:info@theliberators.com">info@theliberators.com</a> or connect wit us through other means. Donate to support our work <a href="https://bit.ly/supportheliberators" rel="nofollow" target="_blank">https://bit.ly/supportheliberators</a> Follow us on Medium: <a href="http://bit.ly/2CdRdad" rel="nofollow" target="_blank">https://medium.com/the-liberators</a><a href="https://bit.ly/supportheliberators" rel="payment nofollow" target="_blank">Support the show</a>

Troika Consulting: "My team is unable to deliver Done increments because they are struggling to slice work vertically"

These days, a lot of the work inside and outside organisations is done in groups. Like task forces, Scrum Teams, management teams or your local church committee. Despite the benefits of working in groups, there are also several risks. Groupthink is a social bias that is clear example of this.In this episode we explore what it is, what causes it and how to prevent it. Especially when it comes to developing strategy, we feel that Liberating Structure - and Strategy Knotworking in particular - can be a great help.We're eager to hear your take after listening to the episode. How have you dealt with Groupthink? Let us know!This podcast is an audio recording of this post on Medium:http://bit.ly/2s1rw8jDonate to support our workhttps://bit.ly/supportheliberatorsFollow us on Medium:https://medium.com/the-liberatorsSupport the show

These days, a lot of the work inside and outside organisations is done in groups. Like task forces, Scrum Teams, management teams or your local church committee. Despite the benefits of working in groups, there are also several risks. Groupthink is a social bias that is clear example of this. In this episode we explore what it is, what causes it and how to prevent it. Especially when it comes to developing strategy, we feel that Liberating Structure - and Strategy Knotworking in particular - can be a great help. We're eager to hear your take after listening to the episode. How have you dealt with Groupthink? Let us know! This podcast is an audio recording of this post on Medium: <a href="http://bit.ly/2s1rw8j" rel="nofollow" target="_blank">http://bit.ly/2s1rw8j</a><a href="http://bit.ly/2JVSHcg" rel="nofollow" target="_blank"> </a> Donate to support our work <a href="https://bit.ly/supportheliberators" rel="nofollow" target="_blank">https://bit.ly/supportheliberators</a> Follow us on Medium: <a href="http://bit.ly/2CdRdad" rel="nofollow" target="_blank">https://medium.com/the-liberators</a><a href="https://bit.ly/supportheliberators" rel="payment nofollow" target="_blank">Support the show</a>

How To Avoid Groupthink When Creating Strategy Together

In the Scrum.org Headquarters there is a picture of Ken Schwaber — one of the founders of Scrum — pointing at a sticky saying “Done”. This picture underscores the most essential rule in Scrum: create “Done” software every Sprint. But what does that mean? And why does it matter? Isn't it enough if you just work as hard as you can during a Sprint and do the rest - like testing and deployment - in a future Sprint? In this episode we explore how vitally important a Done increment is to the purpose of the Scrum Framework. And more importantly, to working empirically in the face of complex work. This podcast is an audio recording of this post on Medium:http://bit.ly/2LkKcFcDonate to support our workhttps://bit.ly/supportheliberatorsFollow us on Medium:https://medium.com/the-liberators Support the show

In the <a href="http://Scrum.org" rel="nofollow" target="_blank">Scrum.org</a> Headquarters there is a picture of Ken Schwaber — one of the founders of Scrum — pointing at a sticky saying “Done”. This picture underscores the most essential rule in Scrum: create “Done” software every Sprint. But what does that mean? And why does it matter? Isn't it enough if you just work as hard as you can during a Sprint and do the rest - like testing and deployment - in a future Sprint? In this episode we explore how vitally important a Done increment is to the purpose of the Scrum Framework. And more importantly, to working empirically in the face of complex work. This podcast is an audio recording of this post on Medium: <a href="http://bit.ly/2LkKcFc" rel="nofollow" target="_blank">http://bit.ly/2LkKcFc</a><a href="http://bit.ly/2JVSHcg" rel="nofollow" target="_blank"> </a> Donate to support our work <a href="https://bit.ly/supportheliberators" rel="nofollow" target="_blank">https://bit.ly/supportheliberators</a> Follow us on Medium: <a href="http://bit.ly/2CdRdad" rel="nofollow" target="_blank">https://medium.com/the-liberators</a> <a href="https://bit.ly/supportheliberators" rel="payment nofollow" target="_blank">Support the show</a>

Why Scrum Requires Completely “Done” Software Every Sprint

In many organizations and teams, Scrum is certainly not a lightweight process. All the items in JIRA must be in the form of User Stories. Every Sprint features at least one or two sessions where people pull out their planning poker cards to spend an hour estimating items. And there's a Definition of Ready that must be adhered to in order to pull something into a Sprint.Over time, and with good intentions, many practitioners of Scrum have burdened it with practices, tools and techniques that may be helpful to some teams, but are not for others. And for most teams, these techniques do not help them work empirically. We've been guilty of this as much as the next Scrum Master or Agile Coaches.In this episode, recorded after day 1 of a Professional Scrum Master II-class, we talk about how this happened. And what you can do to stop burdening Scrum, and return back to its simple and clear purpose: to work empirically in the face of complexity.We love to share our materials. Please help us by supporting our work. You can do so by giving us a thumbs-up on the platform you're listening on. Or follow us on Twitter, Medium or LinkedIn (Barry &amp; Christiaan).Find out how to do an Ecocycle here:http://bit.ly/2wMgbHZFollow us on Medium:https://medium.com/the-liberatorsOr check out our upcoming events at:https://theliberators.com/eventsDonate to support our workhttps://bit.ly/supportheliberatorsSupport the show

In many organizations and teams, Scrum is certainly not a lightweight process. All the items in JIRA must be in the form of User Stories. Every Sprint features at least one or two sessions where people pull out their planning poker cards to spend an hour estimating items. And there's a Definition of Ready that must be adhered to in order to pull something into a Sprint. Over time, and with good intentions, many practitioners of Scrum have burdened it with practices, tools and techniques that may be helpful to some teams, but are not for others. And for most teams, these techniques do not help them work empirically. We've been guilty of this as much as the next Scrum Master or Agile Coaches. In this episode, recorded after day 1 of a Professional Scrum Master II-class, we talk about how this happened. And what you can do to stop burdening Scrum, and return back to its simple and clear purpose: to work empirically in the face of complexity. We love to share our materials. Please help us by supporting our work. You can do so by giving us a thumbs-up on the platform you're listening on. Or follow us on <a href="http://bit.ly/2S6YZGE" rel="nofollow" target="_blank">Twitter</a>, <a href="http://bit.ly/2CdRdad" rel="nofollow" target="_blank">Medium</a> or LinkedIn (<a href="http://bit.ly/2PAAq6s" rel="nofollow" target="_blank">Barry</a> &amp; <a href="http://bit.ly/2Q7YECl" rel="nofollow" target="_blank">Christiaan</a>). Find out how to do an Ecocycle here: <a href="http://bit.ly/2wMgbHZ" rel="nofollow" target="_blank">http://bit.ly/2wMgbHZ</a> Follow us on Medium: <a href="http://bit.ly/2CdRdad" rel="nofollow" target="_blank">https://medium.com/the-liberators</a> Or check out our upcoming events at: <a href="http://bit.ly/2Lw6M1w" rel="nofollow" target="_blank">https://theliberators.com/events</a> Donate to support our work <a href="https://bit.ly/supportheliberators" rel="nofollow" target="_blank">https://bit.ly/supportheliberators</a><a href="https://bit.ly/supportheliberators" rel="payment nofollow" target="_blank">Support the show</a>

Scrum Conversations: Barry and Christiaan talk about Scrum as a heavyweight framework

On November 22, we had the huge pleasure of hosting a 1-day workshop on navigating tension and conflict in groups with Julie Huffaker, Karen Dawson, and Daniel Steinhöfer. Attended by 55 participants, we explored how instead of ‘resolving’ conflict — which often isn’t possible — we can navigate conflict and tension more productively instead. Rather than making this a very theoretical workshop, we opted for a hugely interactive and experiential experience. In this episode, we capture the five biggest insights we took from the workshop.This podcast is an audio recording of this post on Medium: http://bit.ly/2rmhtKFThe string for the workshop can be found here: http://bit.ly/2OCa2H5You can sign up for the next workshop, on October 27, 2020 here: http://bit.ly/2JVSHcgFollow us on Medium: https://medium.com/the-liberatorsDonate to support our workhttps://bit.ly/supportheliberatorsSupport the show

On November 22, we had the huge pleasure of hosting a 1-day workshop on navigating tension and conflict in groups with <a href="https://medium.com/u/fbfa7fc04f9a?source=post_page-----dd209000c266----------------------" rel="nofollow" target="_blank">Julie Huffaker</a>, <a href="https://medium.com/u/7ba0615b8ae0?source=post_page-----dd209000c266----------------------" rel="nofollow" target="_blank">Karen Dawson</a>, and <a href="https://medium.com/u/66cb81343f89?source=post_page-----dd209000c266----------------------" rel="nofollow" target="_blank">Daniel Steinhöfer</a>. Attended by 55 participants, we explored how instead of ‘resolving’ conflict — which often isn’t possible — we can navigate conflict and tension more productively instead. Rather than making this a very theoretical workshop, we opted for a hugely interactive and experiential experience. In this episode, we capture the five biggest insights we took from the workshop. This podcast is an audio recording of this post on Medium: <a href="http://bit.ly/2rmhtKF" rel="nofollow" target="_blank">http://bit.ly/2rmhtKF</a> The string for the workshop can be found here: <a href="http://bit.ly/2OCa2H5" rel="nofollow" target="_blank">http://bit.ly/2OCa2H5</a> You can sign up for the next workshop, on October 27, 2020 here: <a href="http://bit.ly/2JVSHcg" rel="nofollow" target="_blank">http://bit.ly/2JVSHcg </a> Follow us on Medium: <a href="http://bit.ly/2CdRdad" rel="nofollow" target="_blank">https://medium.com/the-liberators</a> Donate to support our work <a href="https://bit.ly/supportheliberators" rel="nofollow" target="_blank">https://bit.ly/supportheliberators</a><a href="https://bit.ly/supportheliberators" rel="payment nofollow" target="_blank">Support the show</a>

Navigating Conflict: Five Big Insights from the workshop ‘Address the Elephant’

Why do we estimate work in Scrum? Are Story Points the best way to do this? And what about #noestimates? In this episode we address the myth that Scrum requires all work to be estimated in Story Points. In the process, we already explore what the purpose of estimation is in Scrum, and how it is very different from plan-based approaches.We love to share our materials. Please help us by supporting our work. You can do so by giving us a thumbs-up on the platform you're listening on. Or follow us on Twitter, Medium or LinkedIn (Barry &amp; Christiaan).This podcast is an audio recording of this post on Medium: http://bit.ly/2YVvLSpFollow us on Medium:https://medium.com/the-liberatorsOr check out our upcoming events at:https://theliberators.com/eventsDonate to support our workhttps://bit.ly/supportheliberatorsSupport the show

Why do we estimate work in Scrum? Are Story Points the best way to do this? And what about #noestimates? In this episode we address the myth that Scrum requires all work to be estimated in Story Points. In the process, we already explore what the purpose of estimation is in Scrum, and how it is very different from plan-based approaches. We love to share our materials. Please help us by supporting our work. You can do so by giving us a thumbs-up on the platform you're listening on. Or follow us on <a href="http://bit.ly/2S6YZGE" rel="nofollow" target="_blank">Twitter</a>, <a href="http://bit.ly/2CdRdad" rel="nofollow" target="_blank">Medium</a> or LinkedIn (<a href="http://bit.ly/2PAAq6s" rel="nofollow" target="_blank">Barry</a> &amp; <a href="http://bit.ly/2Q7YECl" rel="nofollow" target="_blank">Christiaan</a>). This podcast is an audio recording of this post on Medium: <a href="http://bit.ly/2YVvLSp" rel="nofollow" target="_blank">http://bit.ly/2YVvLSp</a> Follow us on Medium: <a href="http://bit.ly/2CdRdad" rel="nofollow" target="_blank">https://medium.com/the-liberators</a> Or check out our upcoming events at: <a href="http://bit.ly/2Lw6M1w" rel="nofollow" target="_blank">https://theliberators.com/events</a> Donate to support our work <a href="https://bit.ly/supportheliberators" rel="nofollow" target="_blank">https://bit.ly/supportheliberators</a><a href="https://bit.ly/supportheliberators" rel="payment nofollow" target="_blank">Support the show</a>

Scrum Mythbusters: Story Points are required in Scrum

You can use Liberating Structures without any prior training or experience. At the same time, practice makes perfect. One example is to always start your explanation by saying "When I'm done explaining". Its a simple tweak, but it prevents people from moving and pairing while you are explaining the steps. In this episode, we share this and 13 other tips for facilitating Liberating Structures that we've found to be helpful. For many of these, we are indebted to our great mentors Henri Lipmanowicz, Keith McCandless, Fisher Qua, Anna Jackson and other experienced users of Liberating Structures. And hopefully you can also benefit from ours :)Donate to support our workhttps://bit.ly/supportheliberatorsFollow us on Medium:https://medium.com/the-liberators Support the show

You can use Liberating Structures without any prior training or experience. At the same time, practice makes perfect. One example is to always start your explanation by saying "When I'm done explaining". Its a simple tweak, but it prevents people from moving and pairing while you are explaining the steps. In this episode, we share this and 13 other tips for facilitating Liberating Structures that we've found to be helpful. For many of these, we are indebted to our great mentors Henri Lipmanowicz, Keith McCandless, Fisher Qua, Anna Jackson and other experienced users of Liberating Structures. And hopefully you can also benefit from ours :)<a href="http://bit.ly/2JVSHcg" rel="nofollow" target="_blank"> </a> Donate to support our work <a href="https://bit.ly/supportheliberators" rel="nofollow" target="_blank">https://bit.ly/supportheliberators</a> Follow us on Medium: <a href="http://bit.ly/2CdRdad" rel="nofollow" target="_blank">https://medium.com/the-liberators</a> <a href="https://bit.ly/supportheliberators" rel="payment nofollow" target="_blank">Support the show</a>

Our 14 Tips For Facilitating Liberating Structures

Scrum Masters can't remove someone from the team, right? That would harm trust, it would violate their self-organizing nature. But what if the dynamic in the team is so harmful that it is affecting a team's ability to work. What if Scrum crumbles because of a prolonged and unresolved conflict?In this episode we dive into one of the toughest myths of Scrum. And by doing so, we explore the essence of what it means for the Scrum Master to be both and servant and a leader.We love to share our materials. Please help us by supporting our work. You can do so by giving us a thumbs-up on the platform you're listening on. Or follow us on Twitter, Medium or LinkedIn (Barry &amp; Christiaan).This podcast is an audio recording of this post on Medium:http://bit.ly/2NMxZLmFollow us on Medium:https://medium.com/the-liberatorsOr check out our upcoming events at:https://theliberators.com/eventsDonate to support our workhttps://bit.ly/supportheliberatorsSupport the show

Scrum Masters can't remove someone from the team, right? That would harm trust, it would violate their self-organizing nature. But what if the dynamic in the team is so harmful that it is affecting a team's ability to work. What if Scrum crumbles because of a prolonged and unresolved conflict? In this episode we dive into one of the toughest myths of Scrum. And by doing so, we explore the essence of what it means for the Scrum Master to be both and servant and a leader. We love to share our materials. Please help us by supporting our work. You can do so by giving us a thumbs-up on the platform you're listening on. Or follow us on <a href="http://bit.ly/2S6YZGE" rel="nofollow" target="_blank">Twitter</a>, <a href="http://bit.ly/2CdRdad" rel="nofollow" target="_blank">Medium</a> or LinkedIn (<a href="http://bit.ly/2PAAq6s" rel="nofollow" target="_blank">Barry</a> &amp; <a href="http://bit.ly/2Q7YECl" rel="nofollow" target="_blank">Christiaan</a>). This podcast is an audio recording of this post on Medium: <a href="http://bit.ly/2NMxZLm" rel="nofollow" target="_blank">http://bit.ly/2NMxZLm</a> Follow us on Medium: <a href="http://bit.ly/2CdRdad" rel="nofollow" target="_blank">https://medium.com/the-liberators</a> Or check out our upcoming events at: <a href="http://bit.ly/2Lw6M1w" rel="nofollow" target="_blank">https://theliberators.com/events</a> Donate to support our work <a href="https://bit.ly/supportheliberators" rel="nofollow" target="_blank">https://bit.ly/supportheliberators</a><a href="https://bit.ly/supportheliberators" rel="payment nofollow" target="_blank">Support the show</a>

Scrum Mythbusters: The Scrum Master Can't Remove People From The Team

Carsten Grønbjerg Lützen

"I'm more of a Scrum Janitor" - Carsten Grønbjerg LützenIn this edition, Christiaan and Barry talk with Scrum Master Carsten Grønbjerg Lützen about his journey as a Scrum Master. Carsten works at the LEGO Group, and has been a passionate and driven Scrum Master for many years. Together, we dive deep into what makes Scrum work at the LEGO Group, and how it all starts with having a clear purpose to rally behind. Carsten also shares some of the things that helped him on his journey as a Scrum Master.Check out Carsten's videos here.We love to share our materials. Please help us by supporting our work. You can do so by giving us a thumbs-up on the platform you're listening to. Or follow us on Twitter, Medium or LinkedIn (Barry &amp; Christiaan).Follow us on Medium:https://medium.com/the-liberatorsOr check out our upcoming events at:https://theliberators.com/eventsDonate to support our workhttps://bit.ly/supportheliberatorsSupport the show

"I'm more of a Scrum Janitor" - <a href="https://www.linkedin.com/in/carstenlutzen/" rel="nofollow" target="_blank">Carsten Grønbjerg Lützen</a> In this edition, Christiaan and Barry talk with Scrum Master <a href="https://www.linkedin.com/in/carstenlutzen/" rel="nofollow" target="_blank">Carsten Grønbjerg Lützen</a> about his journey as a Scrum Master. Carsten works at the LEGO Group, and has been a passionate and driven Scrum Master for many years. Together, we dive deep into what makes Scrum work at the LEGO Group, and how it all starts with having a clear purpose to rally behind. Carsten also shares some of the things that helped him on his journey as a Scrum Master. Check out Carsten's videos <a href="https://www.youtube.com/channel/UCDvr4dS873jCpYDCEtBBW8g" rel="nofollow" target="_blank">here</a>. We love to share our materials. Please help us by supporting our work. You can do so by giving us a thumbs-up on the platform you're listening to. Or follow us on <a href="http://bit.ly/2S6YZGE" rel="nofollow" target="_blank">Twitter</a>, <a href="http://bit.ly/2CdRdad" rel="nofollow" target="_blank">Medium</a> or LinkedIn (<a href="http://bit.ly/2PAAq6s" rel="nofollow" target="_blank">Barry</a> &amp; <a href="http://bit.ly/2Q7YECl" rel="nofollow" target="_blank">Christiaan</a>). Follow us on Medium: <a href="http://bit.ly/2CdRdad" rel="nofollow" target="_blank">https://medium.com/the-liberators</a> Or check out our upcoming events at: <a href="http://bit.ly/2Lw6M1w" rel="nofollow" target="_blank">https://theliberators.com/events</a> Donate to support our work <a href="https://bit.ly/supportheliberators" rel="nofollow" target="_blank">https://bit.ly/supportheliberators</a><a href="https://bit.ly/supportheliberators" rel="payment nofollow" target="_blank">Support the show</a>

Scrum Conversations: Christiaan and Barry talk with Carsten Grønbjerg Lützen about his work at the LEGO Group and the importance of shared purpose

What do pizzerias have in common with software development? Not much, right? But they do offer a useful perspective on what kind of metrics are really useful and which are likely to encourage the wrong things.In this episode, we explore how tracking user stories, number of hours, number of hours spent is like measuring the number of pizzerias. It doesn't tell you anything about how valuable that was. Instead, focusing on these kinds of metrics encourages the accumulation of more waste (heaps of pizza to throw away).Plus, we give you some examples out metrics that ARE useful to measure and actually encourage the removal of waste.P.s. apologies for the chatty birds in the background. I couldn't get them to shut up :)You can also read the accompanying blogpost here:http://bit.ly/37dT21DDonate to support our workhttps://bit.ly/supportheliberatorsFollow us on Medium:https://medium.com/the-liberators For more about Evidence-Based Management, check out Scrum.org's EBM Framework.Support the show

What do pizzerias have in common with software development? Not much, right? But they do offer a useful perspective on what kind of metrics are really useful and which are likely to encourage the wrong things. In this episode, we explore how tracking user stories, number of hours, number of hours spent is like measuring the number of pizzerias. It doesn't tell you anything about how valuable that was. Instead, focusing on these kinds of metrics encourages the accumulation of more waste (heaps of pizza to throw away). Plus, we give you some examples out metrics that ARE useful to measure and actually encourage the removal of waste. P.s. apologies for the chatty birds in the background. I couldn't get them to shut up :) You can also read the accompanying blogpost here: <a href="http://bit.ly/37dT21D" rel="nofollow" target="_blank">http://bit.ly/37dT21D</a> Donate to support our work <a href="https://bit.ly/supportheliberators" rel="nofollow" target="_blank">https://bit.ly/supportheliberators</a> Follow us on Medium: <a href="http://bit.ly/2CdRdad" rel="nofollow" target="_blank">https://medium.com/the-liberators</a> For more about Evidence-Based Management, check out <a href="https://www.scrum.org/resources/evidence-based-management" rel="nofollow" target="_blank">Scrum.org's EBM Framework</a>.<a href="https://bit.ly/supportheliberators" rel="payment nofollow" target="_blank">Support the show</a>

Stop Measuring The Pizzas And The Cooks

Should Scrum Teams revolt against creating "plans"? Are Scrum Teams supposed to not look further than their current Sprint? Is Scrum a "happy go lucky" way of building products,  not planning ahead in any way, shape or form? In this episode we bust the myth that Scrum doesn't like planning and plans.We love to share our materials. Please help us by supporting our work. You can do so by giving us a thumbs-up on the platform you're listening on. Or follow us on Twitter, Medium or LinkedIn (Barry &amp; Christiaan).This podcast is an audio recording of this post on Medium: http://bit.ly/2YVvLSpFollow us on Medium:https://medium.com/the-liberatorsOr check out our upcoming events at:https://theliberators.com/eventsDonate to support our workhttps://bit.ly/supportheliberatorsSupport the show

Should Scrum Teams revolt against creating "plans"? Are Scrum Teams supposed to not look further than their current Sprint? Is Scrum a "happy go lucky" way of building products,  not planning ahead in any way, shape or form? In this episode we bust the myth that Scrum doesn't like planning and plans. We love to share our materials. Please help us by supporting our work. You can do so by giving us a thumbs-up on the platform you're listening on. Or follow us on <a href="http://bit.ly/2S6YZGE" rel="nofollow" target="_blank">Twitter</a>, <a href="http://bit.ly/2CdRdad" rel="nofollow" target="_blank">Medium</a> or LinkedIn (<a href="http://bit.ly/2PAAq6s" rel="nofollow" target="_blank">Barry</a> &amp; <a href="http://bit.ly/2Q7YECl" rel="nofollow" target="_blank">Christiaan</a>). This podcast is an audio recording of this post on Medium: <a href="http://bit.ly/2TByiuW" rel="nofollow" target="_blank">http://bit.ly/2YVvLSp</a> Follow us on Medium: <a href="http://bit.ly/2CdRdad" rel="nofollow" target="_blank">https://medium.com/the-liberators</a> Or check out our upcoming events at: <a href="http://bit.ly/2Lw6M1w" rel="nofollow" target="_blank">https://theliberators.com/events</a> Donate to support our work <a href="https://bit.ly/supportheliberators" rel="nofollow" target="_blank">https://bit.ly/supportheliberators</a><a href="https://bit.ly/supportheliberators" rel="payment nofollow" target="_blank">Support the show</a>

Scrum Mythbusters: There Is No Planning In Scrum

Do Development Teams commit to completing all the items on the Sprint Backlog? Or is it okay for the Sprint Backlog to change as new insights emerge. Find out in this episode.We love to share our materials. Please help us by supporting our work. You can do so by giving us a thumbs-up on the platform you're listening on. Or follow us on Twitter, Medium or LinkedIn (Barry &amp; Christiaan).This podcast is an audio recording of this post on Medium: http://bit.ly/2yRWnEfFollow us on Medium:https://medium.com/the-liberatorsOr check out our upcoming events at:https://theliberators.com/eventsDonate to support our workhttps://bit.ly/supportheliberatorsSupport the show

Do Development Teams commit to completing all the items on the Sprint Backlog? Or is it okay for the Sprint Backlog to change as new insights emerge. Find out in this episode. We love to share our materials. Please help us by supporting our work. You can do so by giving us a thumbs-up on the platform you're listening on. Or follow us on <a href="http://bit.ly/2S6YZGE" rel="nofollow" target="_blank">Twitter</a>, <a href="http://bit.ly/2CdRdad" rel="nofollow" target="_blank">Medium</a> or LinkedIn (<a href="http://bit.ly/2PAAq6s" rel="nofollow" target="_blank">Barry</a> &amp; <a href="http://bit.ly/2Q7YECl" rel="nofollow" target="_blank">Christiaan</a>). This podcast is an audio recording of this post on Medium: <a href="https://medium.com/the-liberators/myth-the-sprint-backlog-cant-change-during-the-sprint-e1a10f735c67" rel="nofollow" target="_blank">http://bit.ly/2yRWnEf</a> Follow us on Medium: <a href="http://bit.ly/2CdRdad" rel="nofollow" target="_blank">https://medium.com/the-liberators</a> Or check out our upcoming events at: <a href="http://bit.ly/2Lw6M1w" rel="nofollow" target="_blank">https://theliberators.com/events</a> Donate to support our work <a href="https://bit.ly/supportheliberators" rel="nofollow" target="_blank">https://bit.ly/supportheliberators</a><a href="https://bit.ly/supportheliberators" rel="payment nofollow" target="_blank">Support the show</a>

Scrum Mythbusters: The Sprint Backlog can’t change during the Sprint

This episode is an excerpt from the book that we’re writing, the ‘Zombie Scrum Survival Guide’. It’s our way of delivering small increments and involving our stakeholders. So we’d love to hear your feedback, encouragements and wild ideas. You can also listen to us reading this post here. Sign up here to stay informed and provide feedback on our writing.What makes someone a "stakeholder"? It’s such a simple question that you can’t help but wonder why we’re even asking it. The Scrum Framework relies heavily on involving stakeholders. And for good reason. You need them to validate your assumptions and to determine what is valuable (and what isn’t).We’ve visited Sprint Reviews where all the ‘stakeholders’ present were internal to the organization; people from marketing and sales, an internal product manager and an opinionated colleague. None of them were either using or paying for the product and its development. We’ve found that not included the right stakeholders is one of the primary causes of Zombie Scrum.In this podcast we share what is necessary for someone to actually be a stakeholder. We also offer three questions to help you find them. This podcast is an audio recording of this post on Medium:http://bit.ly/2Pw6NkODonate to support our workhttps://bit.ly/supportheliberatorsFollow us on Medium:https://medium.com/the-liberatorsSupport the show

This episode is an excerpt from the book that we’re writing, the ‘Zombie Scrum Survival Guide’. It’s our way of delivering small increments and involving our stakeholders. So we’d love to hear your feedback, encouragements and wild ideas. You can also listen to us reading this post here. <a href="http://bit.ly/2R1h76P" rel="nofollow" target="_blank">Sign up here</a> to stay informed and provide feedback on our writing. What makes someone a "stakeholder"? It’s such a simple question that you can’t help but wonder why we’re even asking it. The Scrum Framework relies heavily on involving stakeholders. And for good reason. You need them to validate your assumptions and to determine what is valuable (and what isn’t). We’ve visited Sprint Reviews where all the ‘stakeholders’ present were internal to the organization; people from marketing and sales, an internal product manager and an opinionated colleague. None of them were either using or paying for the product and its development. We’ve found that not included the right stakeholders is one of the primary causes of Zombie Scrum. In this podcast we share what is necessary for someone to actually be a stakeholder. We also offer three questions to help you find them. This podcast is an audio recording of this post on Medium: <a href="http://bit.ly/2Pw6NkO" rel="nofollow" target="_blank">http://bit.ly/2Pw6NkO</a><a href="http://bit.ly/2JVSHcg" rel="nofollow" target="_blank"> </a> Donate to support our work <a href="https://bit.ly/supportheliberators" rel="nofollow" target="_blank">https://bit.ly/supportheliberators</a> Follow us on Medium: <a href="http://bit.ly/2CdRdad" rel="nofollow" target="_blank">https://medium.com/the-liberators</a> <a href="https://bit.ly/supportheliberators" rel="payment nofollow" target="_blank">Support the show</a>

Actual stakeholders? or just your audience?

Zombie Scrum is something that looks like Scrum, but isn't Scrum at all when you take a closer look. Usually, Zombie Scrum is marked by a complete lack of working software, no involvement of the actual users and no drive to do anything about this.This is nothing new. But instead of stating the obvious, we wanted to do something to help. So we built a Zombie Scrum Symptoms Checker - together with Johannes Schartau - to help create transparency around how teams are working with Scrum. Not only is this a helpful tool to start a conversation within your team, it also helps us gather more data around how Scrum is used around the world. Our hope is to improve our ability to help organizations and teams work with Scrum more effectively.In this episode, Barry interviews Christiaan about this tool, how it was developed, what its purpose is and what our goals are with it.We love to share our materials. Please help us by supporting our work. You can do so by giving us a thumbs-up on the platform you're listening on. Or follow us on Twitter, Medium or LinkedIn (Barry &amp; Christiaan).Give the Zombie Scrum Symptoms Checker here:https://survey.zombiescrum.orgFollow us on Medium:https://medium.com/the-liberatorsOr check out our upcoming events at:https://theliberators.com/eventsDonate to support our workhttps://bit.ly/supportheliberatorsSupport the show

Zombie Scrum is something that looks like Scrum, but isn't Scrum at all when you take a closer look. Usually, Zombie Scrum is marked by a complete lack of working software, no involvement of the actual users and no drive to do anything about this. This is nothing new. But instead of stating the obvious, we wanted to do something to help. So we built a Zombie Scrum Symptoms Checker - together with Johannes Schartau - to help create transparency around how teams are working with Scrum. Not only is this a helpful tool to start a conversation within your team, it also helps us gather more data around how Scrum is used around the world. Our hope is to improve our ability to help organizations and teams work with Scrum more effectively. In this episode, Barry interviews Christiaan about this tool, how it was developed, what its purpose is and what our goals are with it. We love to share our materials. Please help us by supporting our work. You can do so by giving us a thumbs-up on the platform you're listening on. Or follow us on <a href="http://bit.ly/2S6YZGE" rel="nofollow" target="_blank">Twitter</a>, <a href="http://bit.ly/2CdRdad" rel="nofollow" target="_blank">Medium</a> or LinkedIn (<a href="http://bit.ly/2PAAq6s" rel="nofollow" target="_blank">Barry</a> &amp; <a href="http://bit.ly/2Q7YECl" rel="nofollow" target="_blank">Christiaan</a>). Give the Zombie Scrum Symptoms Checker here: <a href="http://bit.ly/2Pth7gu" rel="nofollow" target="_blank">https://survey.zombiescrum.org</a> Follow us on Medium: <a href="http://bit.ly/2CdRdad" rel="nofollow" target="_blank">https://medium.com/the-liberators</a> Or check out our upcoming events at: <a href="http://bit.ly/2Lw6M1w" rel="nofollow" target="_blank">https://theliberators.com/events</a> Donate to support our work <a href="https://bit.ly/supportheliberators" rel="nofollow" target="_blank">https://bit.ly/supportheliberators</a><a href="https://bit.ly/supportheliberators" rel="payment nofollow" target="_blank">Support the show</a>

Scrum Conversations: Christiaan and Barry talk about Zombie Scrum and how to measure it with the Zombie Scrum Symptoms Checker

When you work in a team or with others, you'll recognize that conflict is a natural part of our work with others. Where some conflicts are visible, most remain below the surface and manifest only as tension and frustration. They happen, regardless of our intentions and experience.There are different ways to deal with conflict. The Dual Concern Model for Conflict is a helpful way to look at this. It distinguishes five distinct styles that people (can) use to navigate conflict. But not all styles are equally effective.In this episode we explore the five styles as well as what scientific research says about their effectiveness. And as the cherry on top, we share how Liberating Structures can help.You can read the original blogpost here:http://bit.ly/2TLmdmZSign up for our upcoming 'Addressing the Elephant'-workshop here:http://bit.ly/2JVSHcgFollow us on Medium:https://medium.com/the-liberatorsDonate to support our workhttps://bit.ly/supportheliberatorsSupport the show

When you work in a team or with others, you'll recognize that conflict is a natural part of our work with others. Where some conflicts are visible, most remain below the surface and manifest only as tension and frustration. They happen, regardless of our intentions and experience. There are different ways to deal with conflict. The Dual Concern Model for Conflict is a helpful way to look at this. It distinguishes five distinct styles that people (can) use to navigate conflict. But not all styles are equally effective. In this episode we explore the five styles as well as what scientific research says about their effectiveness. And as the cherry on top, we share how Liberating Structures can help.You can read the original blogpost here: <a href="http://bit.ly/2TLmdmZ" rel="nofollow" target="_blank">http://bit.ly/2TLmdmZ</a>Sign up for our upcoming 'Addressing the Elephant'-workshop here: <a href="http://bit.ly/2JVSHcg" rel="nofollow" target="_blank">http://bit.ly/2JVSHcg</a> Follow us on Medium: <a href="http://bit.ly/2CdRdad" rel="nofollow" target="_blank">https://medium.com/the-liberators</a> Donate to support our work <a href="https://bit.ly/supportheliberators" rel="nofollow" target="_blank">https://bit.ly/supportheliberators</a><a href="https://bit.ly/supportheliberators" rel="payment nofollow" target="_blank">Support the show</a>

Conflict Styles: What Sciences Says & How Liberating Structures Can Help

Conflicts are fascinating. They are a natural part of working with other people and can drain significant amounts of energy way from our work together. Yet, for something that is so natural, we're often pretty bad at recognizing conflicts when they happen. For most us, 'conflicts' are those moments when people throw with doors, raise their voices or openly express their disagreement. But more often than not, conflict happens entirely below the surface. These are the "Elephants" that need to be addressed.In this episode, we explore different types of "elephants" and our beliefs about conflict in general. We also share some of our own experiences, as well as what scientific research tells us.Read the blogpost here:http://bit.ly/2LSD99gSign up for the next 'Addressing the Elephant'-workshop here:http://bit.ly/2JVSHcgFollow us on Medium:https://medium.com/the-liberatorsDonate to support our workhttps://bit.ly/supportheliberatorsSupport the show

Conflicts are fascinating. They are a natural part of working with other people and can drain significant amounts of energy way from our work together. Yet, for something that is so natural, we're often pretty bad at recognizing conflicts when they happen. For most us, 'conflicts' are those moments when people throw with doors, raise their voices or openly express their disagreement. But more often than not, conflict happens entirely below the surface. These are the "Elephants" that need to be addressed. In this episode, we explore different types of "elephants" and our beliefs about conflict in general. We also share some of our own experiences, as well as what scientific research tells us. Read the blogpost here: <a href="http://bit.ly/2LSD99g" rel="nofollow" target="_blank">http://bit.ly/2LSD99g</a> Sign up for the next 'Addressing the Elephant'-workshop here: <a href="http://bit.ly/2JVSHcg" rel="nofollow" target="_blank">http://bit.ly/2JVSHcg</a> Follow us on Medium: <a href="http://bit.ly/2CdRdad" rel="nofollow" target="_blank">https://medium.com/the-liberators</a> Donate to support our work <a href="https://bit.ly/supportheliberators" rel="nofollow" target="_blank">https://bit.ly/supportheliberators</a><a href="https://bit.ly/supportheliberators" rel="payment nofollow" target="_blank">Support the show</a>

Addressing The Elephant: And how teams can learn to dance with (often invisible) conflict

Technical debt, or the accumulation of low-quality code, seems to be inevitable when you create software. It is one of the biggest frustrations and demotivators of Development Teams. They are often acutely aware of technical debt, but feel powerless and unable to explain why technical debt should be a priority. Instead, they feel that ‘business keeps adding more features over stabilizing the foundation’.In this episode we offer four practical tips on how to make technical debt transparent and how to help ‘business’ make a better trade-off between code quality and new features.This episode is based on this blogpost:http://bit.ly/2T1jqYDDonate to support our workhttps://bit.ly/supportheliberatorsFollow us on Medium:https://medium.com/the-liberatorsSupport the show

Technical debt, or the accumulation of low-quality code, seems to be inevitable when you create software. It is one of the biggest frustrations and demotivators of Development Teams. They are often acutely aware of technical debt, but feel powerless and unable to explain why technical debt should be a priority. Instead, they feel that ‘business keeps adding more features over stabilizing the foundation’. In this episode we offer four practical tips on how to make technical debt transparent and how to help ‘business’ make a better trade-off between code quality and new features. This episode is based on this blogpost: <a href="http://bit.ly/2T1jqYD" rel="nofollow" target="_blank">http://bit.ly/2T1jqYD</a> Donate to support our work <a href="https://bit.ly/supportheliberators" rel="nofollow" target="_blank">https://bit.ly/supportheliberators</a> Follow us on Medium: <a href="http://bit.ly/2CdRdad" rel="nofollow" target="_blank">https://medium.com/the-liberators</a><a href="https://bit.ly/supportheliberators" rel="payment nofollow" target="_blank">Support the show</a>

How to Deal With Technical Debt in Scrum

The best podcasts about ourselves as well as the world through the lense of Science. Specific topics include things about our brain, emotions to biology, physics and more!

Best Episodes on Science, Humans & The World

What is this?
1 quote, 3 ideas & 1 question from a carefully curated podcast episode.
Every Monday & Wednesday.

Want a 3rd insight and episode every week? Email me at curation@owltail.com.