Scrum.org Community Podcast

Scrum.org

Welcome to the Scrum.org Community podcast, a podcast from the Home of Scrum. In this podcast we feature Professional Scrum Trainers and other Scrum Practitioners sharing their stories and experiences to help learn from the experience of others. 

  1. 4d ago

    Ask a Professional Scrum Trainer - Estimation and Planning with Ludwig Harsch

    Why are forecasts so often late, or short of what was planned? In this live Ask a Professional Scrum Trainer session, Professional Scrum Trainer Ludwig Harsch answers audience questions on estimation and planning for Scrum Teams. He draws on his training and consulting work to explain why estimation should be tested and adapted to each team's context, not treated as a universal rule. Ludwig explains how teams can move from unreliable hour estimates to relative sizing. He discusses when Planning Poker is worth the effort and when a lighter approach fits better. He also covers how to forecast when support work, context switching, and external dependencies eat into capacity. He makes the case for giving stakeholders projected dates with probabilities rather than fixed promises, and explains how Monte Carlo simulations can support that conversation. In this episode: Moving from hours to relative sizing, and what "size" should meanUsing Planning Poker and facilitation to build shared understandingKnowing when to stop estimatingUsing AI in estimation without losing team discussionChoosing a planning horizon, including for regulated productsHandling support work, dependencies, and shifting prioritiesComparing velocity, throughput, and capacity-adjusted metricsWhy Scrum Teams commit to the Sprint Goal, not a fixed number of backlog itemsAdvice for newly formed teams still collecting dataTune in for some great insights on Estimation and Planning in Scrum.

    Ask a Professional Scrum Trainer - Estimation and Planning with Ludwig Harsch
  2. Jul 23

    Rethinking HR from Scratch: How One Company Built a Truly Agile People System

    A conversation with Stephan Scholten and Cesario Ramos on transparent salaries, self-organized teams, peer-driven assessment, and what it really takes to design an HR function around people rather than processes. Most organizations claim to put people first. Their HR systems tell a different story. In this episode of the Scrum.org Community Podcast, host Dave West speaks with Stephan Scholten, Director of People and Organization at Visma Roxit and Cesario Ramos, creator of Creating Agile Organizations, about what happens when you actually redesign HR from the ground up with agile principles at its core. Stephan and Cesario discuss the radical steps Visma Roxit has taken: eliminating team leaders in favor of self-organization, opening up salary structures for collective input, and running peer-driven assessment processes that give employees genuine ownership over how their roles and compensation are defined. They explore the Theory X versus Theory Y tension that surfaces in nearly every organization attempting this kind of change, the slow and deliberate trust-building required before transparency can work, and how the arrival of AI fits into a system already designed around human interdependence and collective performance. Whether you are an HR professional, an agile coach, or a leader looking for a real-world example of empowerment done seriously, this conversation offers both inspiration and practical starting points. You can learn more about this story in the whitepaper titled Designing HR for Agile Organizations.

    Rethinking HR from Scratch: How One Company Built a Truly Agile People System
  3. Jun 11

    From Output to Outcome: How AI Forces a Rethink of Teams, Leadership, and Value

    Dave West sits down with Mik Kersten, author of Project to Product and the upcoming Output to Outcome, to explore why AI amplification is exposing the real bottlenecks in how organizations work. Mik shares data from over 3,600 value streams showing that development teams account for just 8% of end-to-end delivery time which means making those teams faster with AI doesn't move the needle if the constraints are upstream and downstream. The conversation digs into why most organizations are measuring the wrong things (hint: token consumption is not a productivity metric), why overlay agile structures have largely failed, and why the answer isn't fewer teams it's more empowered ones. Mik introduces the core models from his new book: the outcome loop, the outcome tree, and seven organizational shifts that together make up a new operating model designed for the age of AI. Key Takeaways: The bottleneck has moved from software delivery to planning, governance, and innovation and most organizations haven't caught upMaking development teams faster with AI delivers little value if the surrounding system isn't designed around outcomesAgile as an overlay structure doesn't work it has to become the primary operating model and the actual org chartEmpowered, autonomous teams are not optional in an AI-driven world the speed of feedback loops makes half-measures unsustainableLeadership roles need to be redefined and incentive structures realigned to match the way teams are actually workingThe theory of constraints still applies in the age of AI the constraint just keeps moving, and finding it is now the critical management skillLinks http://outputtooutcome.org/

    From Output to Outcome: How AI Forces a Rethink of Teams, Leadership, and Value

Ratings & Reviews

4.8
out of 5
13 Ratings

About

Welcome to the Scrum.org Community podcast, a podcast from the Home of Scrum. In this podcast we feature Professional Scrum Trainers and other Scrum Practitioners sharing their stories and experiences to help learn from the experience of others. 

You Might Also Like