84 episodes

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.

The Liberators Network The Liberators

    • Technologie
    • 5.0 • 4 Ratings

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.

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

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

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

    Support our show at Patreon:
    https://patreon.com/liberators


    Support the show

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

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

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

    Read an in-depth post about team cognition:
    https://medium.com/the-liberators/why-great-scrum-teams-have-a-mind-of-their-own-2ba4d9d17918

    Read an in-depth post about social cohesion:
    https://medium.com/the-liberators/in-depth-how-coherence-and-cohesion-are-critical-to-scrum-f5ae1f3a1aef

    Support the show at:
    https://patreon.com/liberators
    Support the show

    • 31 min
    In-Depth: How To Create Better Work Agreements For Your Team

    In-Depth: How To Create Better Work Agreements For Your Team

    Do high-performing teams communicate more than low-performing teams? 🤔

    If you think "Yes!", you may want to reconsider. Scientific studies often find the reverse. When researchers compare high-performing teams with low-performing teams, they consistently find that high-performing teams communicate less. This has been observed with flight crews, nuclear plant control crews, and work teams.

    These teams have not developed telepathy, but they've learned so well what is expected of each other that they don’t need to communicate explicitly for day-to-day coordination. This effectively keeps a lot of their bandwidth open for problem-solving, critical communication, and maintaining focus - and that makes them more effective.

    There is so much to unpack here. It tells us much about cross-functionality, team cognition, and what it takes to grow high-performing teams. In a very practical sense, I think it shows us how important it is to develop work agreements and mental team models about how to:

    - Coordinate work
    - Coordinate the use and application of skills
    - Coordinate the navigation of conflict
    - Coordinate psychologically safety (the proper kind)
    - Coordinate dealing with work pressure and stress

    Read the transcript of the episode here (including all references):
    https://medium.com/the-liberators/in-depth-how-to-create-better-work-agreements-for-your-team-7738e474ad13

    Support the show at:
    https://patreon.com/liberators
    Support the show

    • 27 min
    In-Depth: What Scientific Research Has To Say About Technical Debt And Code Smells

    In-Depth: What Scientific Research Has To Say About Technical Debt And Code Smells

    Why is code quality so often an issue? Why do software teams — despite their best initial intentions — often end up fighting a codebase that is hard to test, resistant to change, and prone to strange bugs?

    We have many intuitions about this. But we’ve learned the hard way that my intuitions are often wrong. So in this episode, we explore insights from scientific studies that have investigated technical and code smells. We also share evidence-based recommendations on how to write better code. This episode is interesting both for developers and non-developers.

    And yes, it turns out that several of our intuitions are indeed wrong :D
    Read the transcript of this episode (it includes the reference)Try the Scrum Team Survey with your teamSupport the show on Patreon.com/liberatorsSupport the show

    • 31 min
    Agility And Business Agility Are The Same

    Agility And Business Agility Are The Same

    There is a growing trend in our industry to distinguish between “Agility” and “Business Agility”. The idea here is that Agile is limited only to teams and to software and that more is needed. Many consultancy firms are now jumping into that gap with additional frameworks and models.

    This makes no sense to me. I think that this distinction reveals a glaring misunderstanding of the purpose of Agile. More importantly, I think that the distinction between Agility and Business Agility only muddies the waters and distracts leaders away from what it is they should be doing.

    We take a history tour to visit some of the precursors of Agile and learn what made them different from what came before, and why. With this historical understanding, we then revisit the distinction between business agility and agility to see if it makes sense. We also explore the notion that "Agile is only for teams" and "Agile is only for software".

    This episode is an opinion piece. You may agree or you may not. Either way, we hope you learn something from it.

    A transcript is available here (an account for Medium is necessary)
    Support the show

    • 15 min
    10 Powerful Strategies To Break Down Product Backlog Items

    10 Powerful Strategies To Break Down Product Backlog Items

    Great Scrum Teams know that refinement is one of the best ways to optimize the flow of work and deliver more value to stakeholders. Refinement is the act of breaking down and clarifying work for this and upcoming Sprints. We also know this from our research with 1.200 Scrum Teams; teams that actively refine also release more frequently. And they have more satisfied stakeholders and higher morale.

    Sounds good! But how? It is often surprisingly hard for teams to break down large chunks of work in such a way that the smaller pieces still deliver value on their own. Often, work is broken down across technical layers (horizontal) instead of functional layers (vertical).

    In this podcast, we share the 10 strategies that have worked well for us, and the Scrum Teams we've been part of. Each strategy breaks work across functional layers. We give examples for each strategy and explain how they support your team and the Product Owner.  We still actively use them for our work on the Scrum Team Survey too!

    We apologize for the length. You can easily listen to the episode in parts though.

    Download the cheatsheet (it is free):
    https://shop.theliberators.com/collections/free-downloads/products/experiment-10-powerful-strategies-to-break-down-product-backlog-items

    Get the Powerful Questions deck:
    https://shop.theliberators.com/collections/scrum-teams/products/powerful-questions

    Read the original post this podcast is based on:
    https://medium.com/the-liberators/10-powerful-strategies-for-breaking-down-user-stories-in-scrum-with-cheatsheet-2cd9aae7d0eb
    Support the show (https://bit.ly/supportheliberators)

    • 43 min

Customer Reviews

5.0 out of 5
4 Ratings

4 Ratings

Top Podcasts In Technologie

Lex Fridman
RTL Nederland
BNR Nieuwsradio
Tweakers
Jack Rhysider
BNR Nieuwsradio

You Might Also Like

Vasco Duarte, Agile Coach, Certified Scrum Master, Certified Product Owner
NRC
BNR Nieuwsradio
Tom Jessen & Maarten van Rossem / t-talks
Agile for Humans, LLC
Pete Mockaitis