Podcasts about agile coaching

Most "people problems" are structural problems wearing a human face mask.Product Manager Brian and Enterprise Business Agility Leader Om dissect Molly Graham's Waterline Model! Listen or watch as we debate whether this framework is the most actionable restatement of systems thinking in decades or just Deming in a wetsuit. Stick around to the end and you'll know exactly where your org skips diagnosis and jumps straight to blame.Other issues discussed are:Why leaders default to firing individuals instead of fixing broken role definitionsThe four-level diagnostic (structure, dynamics, interpersonal, individual) most managers ignoreHow overlapping ownership and conflicting goals manufacture "personality clashes"Why changing what you reward is harder than writing new process documentationThe coaching judgment no framework can teach you: when to stop snorkeling and diveA practical test: ask three people their goals and see if any answers matchFor product managers, agile coaches, and tech leaders tired of watching teams churn through good people.#SystemsThinking #Leadership #TeamDysfunctionMolly Graham, Lenny's Newsletter, W Edwards Deming, National Outdoor Leadership School (NOLS), The Waterline ModelLINKSYouTube: https://www.youtube.com/@arguingagileSpotify: https://open.spotify.com/show/362QvYORmtZRKAeTAE57v3Apple: https://podcasts.apple.com/us/podcast/agile-podcast/id1568557596INTRO MUSICToronto Is My BeatBy Whitewolf (Source: https://ccmixter.org/files/whitewolf225/60181)CC BY 4.0 DEED (https://creativecommons.org/licenses/by/4.0/deed.en)

Your job description was written to get you hired, not help you know if a decision is your to make.That gap between what's on paper and who actually decides is where careers go to die. Experience & Process Improvement Leader Clint Murt once again joins Product Manager Brian Orlando and Enterprise Business Agility Leader Om Patel in a debate on why job descriptions and/or job role descriptions may buy false comfort, when executive "intrusion" is actually legitimate, and the problem with decision-making that nobody owns.Listen or watch if you're interested in :• Why job descriptions go stale the day they're posted• How that "startup magic" that becomes chaos at 100 people and burns out your best talent• When that exec has the right to overrides your roadmap• Why RACIs are fiction and what to use instead• Practical fixes for decision rightsIf you are a product managers, agile coach, or tech leader tired of role confusion and turf wars, this episode is for you!#ProductManagement #DecisionRights #OrganizationalDesignFlow by Mihaly Csikszentmihalyi, David Marquet, RACI matrix, OVIS framework (BCG), Spotify modelLINKSYouTube: https://www.youtube.com/@arguingagileSpotify: https://open.spotify.com/show/362QvYORmtZRKAeTAE57v3Apple: https://podcasts.apple.com/us/podcast/agile-podcast/id1568557596INTRO MUSICToronto Is My BeatBy Whitewolf (Source: https://ccmixter.org/files/whitewolf225/60181)CC BY 4.0 DEED (https://creativecommons.org/licenses/by/4.0/deed.en)

A startup lecture recommended by Sam Altman calls people "ammunition" and tells you to work 80-hour weeks.Brian and Om dissect Keith Rabois' (in)famous "How to Operate" talk, exposing the dehumanizing logic behind "barrels and ammunition," the cult of heroic effort, and why grading managers on output-per-head creates a fear-based culture.What Brian and Om get into:• Why the "people are irrational" premise is a condescending excuse for bad system design• The truth behind 80-100 hour work weeks and the duct-tape engine myth• What "build a company idiots can run" really means for your career• The "barrels and ammunition" metaphor and its Taylorist roots• Why "expand responsibilities until they break" destroys psychological safety• The output-per-head metric and how it incentivizes burning out your teamFor product managers, engineers, and anyone who's ever been called a "resource" by someone who read too much Ayn Rand.#ToxicLeadership #StartupCulture #ManagementAdviceKeith Rabois, Sam Altman, Y Combinator, Andy Grove, High Output Management, Warren Buffett, Square, PayPal, W. Edwards Deming, The Goal by Eliyahu GoldrattLINKSYouTube: https://www.youtube.com/@arguingagileSpotify: https://open.spotify.com/show/362QvYORmtZRKAeTAE57v3Apple: https://podcasts.apple.com/us/podcast/agile-podcast/id1568557596INTRO MUSICToronto Is My BeatBy Whitewolf (Source: https://ccmixter.org/files/whitewolf225/60181)CC BY 4.0 DEED (https://creativecommons.org/licenses/by/4.0/deed.en)

Velocity feels like proof.  Fifty story points done, a bigger number than last sprint, a box checked.  But velocity measures how busy a team is, not whether anything valuable reached the customer.  Kate Megaw and Ryan Smith take apart the metric everyone loves to report and rebuild the case for measuring what matters.  Velocity, they argue, was never a metric at all. It is an internal planning tool, Mike Cohn's “yesterday's weather”, useful for forecasting and useless for judging.  From there the conversation turns to the measures that actually signal agility: outcome over output, flow metrics like lead time, work in progress limits, emergent work per sprint, flow efficiency, and the strategic questions executives really care about, such as whether the business moved forward.  Along the way Ryan shares the MVP that 300 people found on their own, and Kate lands the question that cuts through it all: if your velocity doubled tomorrow, would your customers even notice? Velocity is vanity.  Outcomes are reality.  Agility lives in the flow.

“We have twelve scrum masters. Why is nothing working?” If you have ever asked some version of that question, this episode is for you.Kate Megaw, Anu Smalley and Ryan Smith dig into the challenge they hear in almost every class they teach, a real lack of role clarity. Companies send a strong project manager to a two day course, hand them a new title, and then wonder why nothing changes. The honest answer is that nobody ever defined what the role is actually accountable for. This episode unpacks the difference between roles and accountabilities, why a scrum master is not optional, and how to define seats around outcomes instead of titles. Along the way Kate and Anu have a friendly fight over RACI, whether it hardens into swim lanes or serves as a living guiding light, and what responsible really means at a startup versus a large enterprise.What we cover:“We have twelve scrum masters, why is nothing working?”Roles vs. accountabilities, and why the org chart liesThe RACI debate: swim lanes vs. guiding lightThe kitchen sink job description with 45 impossible dutiesStart with outcomes, not titles, and revisit at every kickoff

Everything is a fire. Everything is priority number one.  And by tomorrow, the number one priority has changed again. Sound familiar?In this episode, Kate Megaw, Anu Smalley, and Ryan Smith dig into the challenge they hear at almost every client and leadership class: a real lack of prioritization.  Not just inside the sprint, but across the whole organization, where teams get handed a brand new top priority every single day.When everything is important, nothing is important.  Constant reprioritizing whipsaws teams, burns people out, and leaves a trail of half-finished work and rising tech debt.  Jerry Weinberg's research found you can lose 20 to 40 percent of productivity every single time you switch context, so three projects can leave you down 60 to 80 percent.In this episode, we discuss:Why a lack of prioritization is really a sign that your stakeholders are not alignedThe real cost: burnout, rework, tech debt, lost innovation, and the context-switching taxWhy this is a leadership problem, not a team problem, and why the team always gets blamedUsing the sprint to hold the line and protect work the team has committed toEmergent requests as a better signal than velocity for how often the team gets interruptedMoSCoW for sorting the must-haves from the nice-to-havesThe 20/20 approach from Innovation Games for a truly ordered backlogThe impact-effort matrix for spotting quick wins and killing low-value workBuy-a-feature with stakeholders and a limited budgetThe wins on the board debate: put easy wins up first, or dig into why the big thing is bigEvery time someone says yes, it consumes time, money, and attention.  Prioritization is the discipline of protecting all three.Referenced in this episode: Jerry Weinberg's research on the cost of context switching, the 20/20 prioritization method from Innovation Games, the MoSCoW method, and the Eisenhower impact-effort matrix.

The damage from your Q1 goal doesn't show up until Q3, on someone else's dashboard, after the person who flagged it got fired.Part 2 of the Outcome Trap series. Brian and Om argue why you can't see the trap from inside it: second-order effects land too late to trace, the people who spot trouble get removed, and the truth fractures across team dashboards until nobody owns the whole picture. By the end you'll have questions to ask before any number you set quietly destroys the business.Listen or watch as we discuss and debate:Why Goodhart's Law turns every new leading indicator into another surface to gameHow Sears split into 40 competing units and imploded while every department hit its OKRsThe Wells Fargo whistleblower fired for 'tardiness' eight days after calling the ethics hotlineWhy Deming's 1986 warning to eliminate numerical goals got ignored for forty yearsTwo questions to ask before setting any targetIf you've ever been in a company where every conceivable metric was green while the business slowly bleed out, this podcast is for you!.#OKRs #Deming #GoodhartsLawW. Edwards Deming (Out of the Crisis, The New Economics), Goodhart's Law, Peter Senge The Fifth Discipline, The People's Republic of Walmart, Sears (Eddie Lampert), Wells Fargo (Bill Bado), Frances Haugen Facebook testimony, Careless People by Sarah Wynn-WilliamsLINKSYouTube: https://youtu.be/BuWgxH8VpRISpotify: https://open.spotify.com/show/362QvYORmtZRKAeTAE57v3Apple: https://podcasts.apple.com/us/podcast/agile-podcast/id1568557596INTRO MUSICToronto Is My BeatBy Whitewolf (Source: https://ccmixter.org/files/whitewolf225/60181)CC BY 4.0 DEED (https://creativecommons.org/licenses/by/4.0/deed.en)

Conference season is back, and so are the real conversations. In this episode, Peter Maddison and Dave Sharrock catch up after a busy stretch of travel and dig into something Dave has been road-testing at conferences: why most people given access to AI tools freeze up, and what actually helps them move past that.Dave ran a workshop at the Global Scrum Gathering in Vancouver for non-technical roles - product managers, Scrum Masters, agile coaches - people who've been told "use AI" but have no clear picture of where to start. What he found is that the problem isn't motivation or technical ability. It's the lack of scaffolding. Give people the right structure and the right room to experiment, and things shift pretty quickly.The conversation then moves into multi-agent systems - how Dave's team built a group of agents that continuously refresh the workshop itself based on current thinking. Peter adds his own take on testing these systems with personas and automated quality evaluation. It gets a bit technical, but in the best way.This is a good episode if you're thinking about how to help your organization actually use AI, not just adopt it on paper.Key Takeaways:Context beats generic. Prompts work when they're specific to your role and your actual problems. A product manager needs product management context, not a one-size-fits-all example.Think in teams, not steps. Multi-agent systems work best when you treat them like a team reviewing an artifact, each agent checking for something different, rather than a linear build process.Don't assume everyone gets it. The gap between people who use AI daily and people who tried it once and gave up is wider than most of us realize. Getting both groups in the same room is where the real learning happens, for everyone.Have a question or something to add? Reach out at feedback@definitelymaybeagile.com or find us at definitelymaybeagile.com. And if you're finding the show useful, subscribing and leaving a review goes a long way.

Project World | Business Analyst World - Day 3-4 ReviewDay 3 - Agile Fundamentals - One of the most common points of Agile adoption failure comes with the incremental on-boarding of Agile teams throughout an organization while not having everyone starting with the same foundational Agile knowledge. This workshop session is designed to help everyone on the team learn the fundamental principles behind what makes Agile work, and allows them to participate in several real world exercises. This structure allows everyone on the team to learn the ‘Why' behind the ‘How', and gives everyone a chance to leave with the tools needed to effectively do their job better. This session is designed for both new Agile / Kanban teams learning the ropes and experienced Agile teams who are trying to re-align or get started on the same Agile footing while establishing an internal Agile Center of Excellence. This workshop is often coupled with Agile Coaching in order to increase the effectiveness and impact. The Three Keys - Seeking & Embracing Success: Success can be defined by each of us in many different ways. The truth is there are three keys to a successful personal and professional career. Once we discover these keys and learn to use them, we are gifted the ability of a lifetime of success. This personal journey will teach you the importance of making dreams come true and give you the tools to make that happen.Day 4 - C-Suite Engagement - Too many transformation efforts stall not because the work is hard, but because the right people weren't invited to the table — or they were, and nobody spoke their language. This session gives leaders a pragmatic, no-fluff playbook for turning executives from passive approvers into active sponsors. We'll strip away the jargon and replace it with three things executives actually pay attention to: clear outcomes, short bets, and repeatable governance. Expect real templates (one-page decision memos, sponsor cadence scripts), live translation exercises to turn team metrics into executive value, and role-play scenarios you can use the moment you return to the office. If you want predictable, funded change — not theater — this workshop will help you get it. Attendees will leave with: • A one-page executive brief template that gets decisions — fast. • A sponsor-activation cadence that prevents “ghost sponsorship.” • Three scripts to convert technical/operational language into strategic outcomes.How to connect with AgileDad:- [website] ⁠https://www.agiledad.com/⁠- [instagram] ⁠https://www.instagram.com/agile_coach/⁠- [facebook] ⁠https://www.facebook.com/RealAgileDad/⁠- [Linkedin] ⁠https://www.linkedin.com/in/leehenson/

Is AI actually helping us escape the build trap, or just helping us build the wrong things faster?In this episode of Arguing Agile, hosts Brian Orlando and Om Patel discuss the new AI4Agile Practitioners Report 2026 from Scrum.org. The data reveals a startling trend: while 83% of practitioners have access to AI tools, the primary fear isn't job replacement, it's that AI is becoming a "supercharged way into the feature factory."Listen or watch as we examine the report's key findings, including the gap between AI access (83%) and actual competence (only 15% received formal training). We discuss why the reported productivity gains (73.7%) might be masking the erosion of agile values like reflection and collaboration. Citing Melissa Perri's "Escaping the Build Trap," we explore how organizations are using AI to accelerate output without redesigning workflows to improve outcomes.Key topics include:Why "speed of delivery" was never the real bottleneckWhat practitioners really fearThe lack of workflow redesign in the AI eraFive actionable questions to test if your team is escaping or acceleratingTune in to learn how to ensure your AI adoption drives value, not just volume.#Agile #ProductManagement #AIEscaping the Build Trap by Melissa Perri, The Goal by Eliyahu M. Goldratt, AI4Agile Practitioners Report 2026 by Scrum.org, Crossing the Chasm by Geoffrey MooreLINKSYouTube: https://www.youtube.com/@arguingagileSpotify: https://open.spotify.com/show/362QvYORmtZRKAeTAE57v3Apple: https://podcasts.apple.com/us/podcast/agile-podcast/id1568557596INTRO MUSICToronto Is My BeatBy Whitewolf (Source: https://ccmixter.org/files/whitewolf225/60181)CC BY 4.0 DEED (https://creativecommons.org/licenses/by/4.0/deed.en)

Agreeing on an idea doesn't mean you both understood the same thing. Dave Sharrock and Peter Maddison dig into why shared context breaks down in practice, and how AI makes that problem harder to ignore.This week's takeaways:Intent is always imperfect. Define how you'll validate it, not just what it is.Ambiguity in context isn't a bug. It's necessary. Validation is how you confirm you're aligned.Drive down the cost of validation, not just the cost of building.If this landed, share it with someone navigating the same tension. And reach out at feedback@definitelymaybeagile.com - we read everything.

Peter Merel: When Telling a Manager "You Don't Have a Role" Backfires — A Lesson in Agile Coaching Humility Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.   "A failure is not a failure. A failure is just the first step." - Peter Merel   Peter Merel became a Scrum Master by stealth — long before the title existed. Credited in Kent Beck's first XP book and present at the first agile conference, Peter was practicing lightweight processes at Hewlett Packard in the late 1990s. When he took a role at GMAC, the residential finance arm of General Motors, he brought XP practices with him and found early success. After six months of strong results, the project manager, Mike Alakom, sat Peter down and asked the most dangerous management question: "What do I do?" Peter gave what he now calls the stupidest answer possible — "You don't really have a role in this process." The next day, Mike called an all-hands meeting and calmly maneuvered Peter into crediting the entire way of working as Mike's idea. Peter stayed on for another six months, but at arm's length. In hindsight, Peter recognizes Mike did exactly what he should have done. The second failure came at Commonwealth Bank of Australia, where Peter was brought in to coach agile but was actually being set up to fail — a ripcord the organization could pull when it wasn't ready for change. The delivery manager, Des Webster, told Peter directly: "You were set up to fail." Peter walked away, thinking he'd never return. But six years later, every person he had coached had moved up in the organization, and Peter came back as principal coach for 50,000 people. The CIO declared Agile one of the bank's five pillars. Just because you hit the wall doesn't mean it's the end — it might be the beginning.   Self-reflection Question: When was the last time you failed at introducing change, and have you considered that the seeds you planted might still be growing in ways you can't yet see?   [The Scrum Master Toolbox Podcast Recommends]

Is the State of Agile Report a clear-eyed snapshot of the industry - or a sales brochure? In this episode of Arguing Agile, hosts Product Manager Brian Orlando and Enterprise Business Agility Consultant Om Patel are joined by returning guest Ed Martin to dissect the 18th State of Agile Report from Digital.ai. Applying the economic theory of the 'Market for Lemons,' where asymmetric information leads to market failure, we discuss the survey results and 'pontificate' on the state of the agile industry.Join us by watching or listening as we discuss:Why 41% of organizations increased agile investment while only 13% claim it is deeply embeddedIf the Rise of Hybrid and Homegrown Agile is an indicator of a return to 'cowboy coding'Analyzing the report's contradictory finding that 63% of companies struggle with quality while 68% claim high-quality deliveryThe critical issue of leaders demanding ROI from systems they do not understand or actively guideWe don't just discuss the report, but we also brainstorm and share actionable advice for agilists and tech workers on how to navigate a landscape of conflicting data and pressure to prove value.#Agile #ProductManagement #LeadershipThe Market for Lemons by George Akerlof, The 18th State of Agile Report by Digital.ai, Inspired by Marty Cagan, The Wright Brothers vs. Samuel Langley history, J.J. SutherlandLINKSWatch it on YouTube!YouTube: https://www.youtube.com/@arguingagileSpotify: https://open.spotify.com/show/362QvYORmtZRKAeTAE57v3Apple: https://podcasts.apple.com/us/podcast/agile-podcast/id1568557596INTRO MUSICToronto Is My BeatBy Whitewolf (Source: https://ccmixter.org/files/whitewolf225/60181)CC BY 4.0 DEED (https://creativecommons.org/licenses/by/4.0/deed.en)

In this insightful interview, Marina Alex shares her journey from a successful sales executive to an agile coach, discussing the challenges faced during the pandemic, the importance of adapting to market changes, and strategies for agile professionals to find new opportunities in a shifting landscape. She emphasizes the need for the agile community to broaden its reach beyond IT, focus on measurable results, and leverage local relationships to build a sustainable coaching and consulting business. Key Topics - Market shifts and the decline of traditional agile coaching - Strategies for finding clients outside of IT and enterprise - The importance of measurable results and ROI in agile consulting - Building relationships with local businesses and community engagement - The role of AI in transforming small and medium businesses Chapters 01:52 Introduction to Agile Coaching and Personal Journey 06:59 The Shift in the Agile Market 11:49 Reframing the Agile Value Proposition 19:44 Building Self-Organizing Teams in Non-IT Businesses 26:54 Implementing Agile Practices in Diverse Environments 28:49 Implementing Change in Traditional Environments 30:02 Setting Measurable Business Goals 31:51 The Role of a Coach in Business Transformation 34:19 Starting as a Local Coach 34:37 Optimizing Your LinkedIn Presence 37:26 The Importance of Practical AI Knowledge 40:33 Simplifying AI for Local Businesses 45:35 Finding Clients in Your Community LINKS Sway 2.0 AI Modern Consulting Blueprint Class begins April 6, 2026 Sign up here: https://www.swaysystem.com/sway-2026-Programs The promo code DAVE takes $250 off! Contacting Marina Marina Alex's Guide to Finding Your First Client in SMB - https://example.com/marina-alex-guide LinkedIn Profile of Marina Alex - https://linkedin.com/in/marinaalex Sway System by Marina Alex - https://example.com/sway-system Contacting Dave Linktree: https://linktr.ee/mrsungo Dave's upcoming classes: Certified Scrum Master https://tinyurl.com/mu74rwuc Certified Scrum Product Owner https://tinyurl.com/mpw6p622 PMI Project Management Professional (PMP)® Boot Camp and Exam Prep https://tinyurl.com/3znzpt7j PMI Agile Certified Practitioner (PMI-ACP)® Boot Camp https://tinyurl.com/bdebrrrb

Stop burning time and money on agile theater! In this podcast, Product Manager Brian Orlando and Enterprise Business Agility Consultant Om Patel strip business agility back to its absolute basics: no buzzwords, no frameworks - just the organizational muscles you need to survive. Listen or watch as we introduce and explain the five non-negotiable capabilities: Sensing and Responding (market feedback loops), Speed to Decision Making (decision velocity), Structural Flexibility (reorganizing without chaos), Distributed Authority (decentralizing command and control), and Learning Orientation (continuous evolution).Then stick around as we tear down the agile industrial complex, discuss why one study claims 47% of companies are operating purely under an "illusion" of agility, and discuss how the introduction of AI can amplify and exposes company's bureaucracy.Other topics we discuss are:• How to explain business agility to anyone from CEO to new hire• Why "scaling" agility is a big lie sold to enterprises• Typical bottlenecks to the five core capabilities• Why vanity metrics sabotage competitive advantages• Time to market, cost of delay, customer adoption, and much more...Whether you're in product management, leadership, agile coaching, or team development, this episode helps you truly understand business agility and can give you the confidence to push back or ask critical questions when teams and leadership claim they don't need help.#BusinessAgility #ProductManagement #AgileLeadership["Extreme Ownership by Jocko Willink and Leif Babin", "Team Topologies by Matthew Skelton and Manuel Pais", "Turn the Ship Around by L David Marquet", "The Fearless Organization by Amy Edmondson", "The Lean Startup by Eric Ries", "BCG Study: Why Companies Get Agile Right and Wrong (2024)", "Business Agility Institute 2025 Report", "Organizational Agility: Ill-defined and Somewhat Confusing by Anna Teresa Walter (2020)", "John Boyd's OODA Loop", "Jeff Bezos's One-Way Door vs Two-Way Door Decisions", "Block (Jack Dorsey)", "Arguing Agile Episode 83: Agile Doesn't Work Here"]LINKSYouTube: https://www.youtube.com/@arguingagileSpotify: https://open.spotify.com/show/362QvYORmtZRKAeTAE57v3Apple: https://podcasts.apple.com/us/podcast/agile-podcast/id1568557596INTRO MUSICToronto Is My BeatBy Whitewolf (Source: https://ccmixter.org/files/whitewolf225/60181)CC BY 4.0 DEED (https://creativecommons.org/licenses/by/4.0/deed.en)

Businesses killed QA with bad org design, but with AI, is there potential for a near-term QA boom?Join Product Manager Brian Orlando and Enterprise Business Agility Consultant Om Patel as we discuss the systematic elimination of QA roles over the past decade and discuss why that decision is now backfiring.That's right, with AI-generated code accelerating at breakneck speed and nobody to properly check or test it, Brian and Om argue that we might be heading toward a cliff of technical debt that will make skilled QA professionals more valuable than ever.We discuss this potential future in five acts:1. The Expensive Lie: Let's Dev Do the QA (until we lay them off as well)2. The Coming QA Boom3. When and Will Businesses Move Software Risk Upstream4. Why Dev Didn't and AI Won't Replace QA5. The Case for Human-In-The-LoopWhether you're a QA professional worried about your career, a product manager who inherited testing responsibilities, or a leader considering QA cuts - this episode provides data-backed arguments for why the QA field may be on the verge of its biggest resurgence yet.#QualityAssurance #AI #AgileLeadershipStack Overflow Developer Survey 2023, Practitest State of Testing Report 2024, World Quality Report 2025 by Capgemini and Micro Focus, GitLab DevSecOps Report 2024, Google Code Review Quality Study 2023, McKinsey Technology Report 2025 (State of AI in 2025), Theo (t3.gg) video on the future of developer roles, Software Quality and Beer podcast by Bob Cruz and Matt Kubal (Checkpoint Technologies), Cooper Bench (AI coding benchmark study), W. Edwards Deming (quality management principles), Toyota Production System (quality ownership model), Eliyahu Goldratt (Theory of Constraints / systems feedback loops), Brook's Law, Melissa Perri, Playwright (test automation framework), Claude Code (Anthropic)LINKSYouTube: https://www.youtube.com/@arguingagileSpotify: https://open.spotify.com/show/362QvYORmtZRKAeTAE57v3Apple: https://podcasts.apple.com/us/podcast/agile-podcast/id1568557596INTRO MUSICToronto Is My BeatBy Whitewolf (Source: https://ccmixter.org/files/whitewolf225/60181)CC BY 4.0 DEED (https://creativecommons.org/licenses/by/4.0/deed.en)

Meta and Amazon are cutting managers, but is it efficiency or chaos?Is de-layering, or flattening your org chart, good for a company, or is it a recipe for destruction?Join Product Manager Brian Orlando and Enterprise Business Agility Coach Om Patel as we wade into the murky pool that is the latest of corporate trends - "un-bossing" or the mass sacrifice of middle management and mid-level coordination roles on the unholy alter of efficiency. While the biggest of big companies are slashing layers to reduce costs and empower the IC (individual contributors), we take a more nuanced look, arguing that without proper system redesign, this approach leads to decision bottlenecks, leadership vacuums, and the collapse of career mobility.Listen or watch as we discuss:- Why firing coordinators doesn't eliminate the need for coordination- The dangers of "spreadsheet-driven development" (SDD™)- How informal hierarchies and politics emerge when formal authority is removed- The impact of removing middle management on mentorship, sponsorship, and career growth- How to actually flatten an org, when necessaryWe're pulling out all the stops (and the research) as we review Google's failed "no manager" experiment from 2002, revisit the book Team Topologies, and discuss the recent trend towards a Chief of Staff type role. If you are a leader considering a reorg or a developer wondering why your meetings are getting more chaotic, this episode is for you!#ProductManagement #Leadership #TeamTopologiesTeam Topologies by Matthew Skelton and Manuel Pais, Google Project Oxygen, Fortune article "Executives are drowning. Blame the vanishing middle management layer" by Lily May Lazarus, Zappos Holacracy, Arguing Agile Episode #67 (Team Topologies), Arguing Agile Episode #250 (AI ROI)LINKSYouTube: https://www.youtube.com/@arguingagileSpotify: https://open.spotify.com/show/362QvYORmtZRKAeTAE57v3Apple: https://podcasts.apple.com/us/podcast/agile-podcast/id1568557596INTRO MUSICToronto Is My BeatBy Whitewolf (Source: https://ccmixter.org/files/whitewolf225/60181)CC BY 4.0 DEED (https://creativecommons.org/licenses/by/4.0/deed.en)

Is Agile Coaching a Waste of Money?Around the world, software organizations are desperately trying to improve how their teams build and deliver software. Companies will hire herds of “wise sage” coaches to bring them out of the Dark Ages but are often disappointed when nothing extraordinary happens. Despite pouring loads of money into coaching efforts, their applications still fail to perform, their customers are still not having their needs met, and it still takes forever to get an idea to become reality. This project is 50% over budget, that one has missed three delivery dates now, and nothing seems to be going as planned. While all this is going on, agile coaches are hard at work “making the world a better place.”How to connect with AgileDad:- [website] ⁠https://www.agiledad.com/⁠- [instagram] ⁠https://www.instagram.com/agile_coach/⁠- [facebook] ⁠https://www.facebook.com/RealAgileDad/⁠- [Linkedin] ⁠https://www.linkedin.com/in/leehenson/

Your boss's biggest career win might be setting them up for their biggest failure.

AI agents failed spectacularly at teamwork, performing ~50% worse than one solo agent!This week, we're discussing Stanford's CooperBench study (a benchmark, testing whether AI agents can collaborate on real coding tasks across Python, TypeScript, Go, and Rust) and why AI-developer coordination collapses, even with a constant chat.Listen or watch as Product Manager Brian Orlando and Enterprise Business Agility Consultant Om Patel dig into the methods and findings of Stanford's 2026 CooperBench experiment and learn about the three capability gaps that caused these failures: • Expectation Failures (42%): Agents ignored shared plans or misunderstood scope• Commitment Failures (32%): Promised work was never completed• Communication Failures (26%): Silence, spam, or hallucinationsThe experiment's findings seem to confirm human-refined agile practices. The episode ends with a concrete call to action: stop treating AI as teammates. Use them as solo contributors. And if you must coordinate? Build working agreements, not handoffs.This episode is for anyone navigating the AI hype cycle and wondering if swarms of agents are going to coordinate everyone out of a job!#Agile #AI #ProductManagementSOURCECooperBench: Benchmarking AI Agents' Cooperation (Stanford University & SAP Labs US)https://cooperbench.com/https://cooperbench.com/static/pdfs/main.pdfLINKSYouTube: https://www.youtube.com/@arguingagileSpotify: https://open.spotify.com/show/362QvYORmtZRKAeTAE57v3Apple: https://podcasts.apple.com/us/podcast/agile-podcast/id1568557596INTRO MUSICToronto Is My BeatBy Whitewolf (Source: https://ccmixter.org/files/whitewolf225/60181)CC BY 4.0 DEED (https://creativecommons.org/licenses/by/4.0/deed.en)

Spotify never used the Spotify Model - and neither should you. In this $2 billion episode, Product Manager Brian Orlando and Enterprise Business Agility Consultant Om Patel take a cutting torch to one of big-A-Agile's most beloved organizational myths - the Spotify Model! We're doing invasive surgery to see what's inside beyond the over-hyped squads, tribes, chapters, and guilds that have been copied by companies the world over. ...but what if we found out that the inside was hollow? What if we found out that the Spotify Model was never even live and tested by Spotify?

Legacy systems work. So why do companies waste millions rewriting them? In this episode of Arguing Agile, Product Manager Nisha Patel joins Product Manager Brian Orlando and Enterprise Business Agility Consultant Om Patel for a debate on the dangerous obsession with rewriting legacy systems — from COBOL to green screens — that still power ATMs, government systems, and Fortune 500 billing engines. Watch or listen as we discuss the myth that "modern" equals "better" and reveal how most rewrites fail because they ignore customer value, edge cases, and real ROI as well as other topics, such as:How Chesterton's Fence applies to code (Brian still doesn't know)How Developers kill software with Resume-Driven Development (RDD)How Finance kills software with spreadsheet-driven development (SDD)Why chasing "parity" kills innovationRisk Mitigation, or, framing technical debt in business termsIf you've ever worked on or tried to replace legacy systems, this episode will either give you nightmares, or help how you approach legacy systems while helping you also stop burning budget on vanity projects.#LegacyCode #ProductManagement #AgileCoachingREFERENCESAA148 - An Introduction to Software Development FinancesLINKSYouTube: https://www.youtube.com/@arguingagileSpotify: https://open.spotify.com/show/362QvYORmtZRKAeTAE57v3Apple: https://podcasts.apple.com/us/podcast/agile-podcast/id1568557596INTRO MUSICToronto Is My BeatBy Whitewolf (Source: https://ccmixter.org/files/whitewolf225/60181)CC BY 4.0 DEED (https://creativecommons.org/licenses/by/4.0/deed.en)

Does getting promoted literally rewire your brain to lose empathy? The science says YES.

Is 'Move Fast & Break Things' just permission to be reckless?Join Product Manager Brian Orlando and Enterprise Business Agility Consultant Om Patel as they examine Mark Zuckerberg's (in)famous mantra and reveal how it may have metastasized from breaking code to breaking laws, teams, and even contributing to real human harm.Watch or listen as we explore the critical dimensions of this philosophy, including:BREAKING SOFTWARE: How the original meaning of 'break things' (emphasizing first-mover advantage) evolved from rapid iteration of code to justifying regulatory evasion and monopolistic behavior.BREAKING TEAMS: Using Harvard research that shows 'always-on' cultures decrease productivity by 20% and spike turnover to discuss how intensity without recovery is just exploitation (and what to do instead).BREAKING PEOPLE: Discussing the human costs of unchecked speed, from Facebook's alleged role in the Myanmar genocide to Uber's systemic harassment culture to Theranos's fraud.LEARNING OVER SPEED: We discuss Eric Ries's seminal work: The Lean Startup and how it went out of it's way to emphasize learning velocity over shipping velocity. WRONG (we guess)!PUSHING BACK (WITHOUT GETTING FIRED): We brainstorm for frameworks to use for challenging speed-obsessed leadership, including trade-off and discuss real-world experiences.Whether you're running a business, a product manager, or a team member just trying to keep up, this episode arms you with arguments and frameworks to advocate for ethical innovation.What's your take on 'move fast' culture? Have you seen it more of a positive or negative?#ProductManagement #TechEthics #AgileLeadershipREFERENCESMove Fast and Break Things by Jonathan Taplin (2017), Careless People: A Cautionary Tale of Power Greed and Lost Idealism by Sarah Wynn Williams, The Lean Startup by Eric Ries (2011), The Fearless Organization by Amy Edmondson (2018), Susan Fowler's blog 'Reflecting on One Very Very Strange Year at Uber' (February 2017), UN Human Rights Council 2018 report on Facebook and Myanmar, Harvard Business School research on always-on cultures (2009), Agile Podcast E22 - Interview with a Scrum Trainer: Fred Mastropasqua (August 2021), Extreme Ownership by Jocko Willink, The Social Network (film, 2010)LINKSYouTube https://www.youtube.com/@arguingagileSpotify: https://open.spotify.com/show/362QvYORmtZRKAeTAE57v3Apple: https://podcasts.apple.com/us/podcast/agile-podcast/id1568557596Website: https://arguingagile.com/

Stop wasting time building the wrong thing faster!In this episode of Arguing Agile, Product Manager: Brian Orlando and Business Agility Coach to THE STARS: Om Patel respond to yet another listener question, discussing Product Risk Analysis in agile environments! Listen or watch as they challenge the common misconception that analyzing risks upfront is "waterfall" and reveal why ignoring product risks until you've burned three sprints is how teams end up building features nobody wants.Stick around while the hosts break down Marty Cagan's four critical product risks (Valuable, Usable, Feasible, and Business-Viable) but stick around for the conversation on why most teams focus on execution risks while the real product killers are hiding in plain sight!The topics covered are:- Difference between product risks and execution risks- Why traditional risk registers are theater- "Speed-to-death" prioritization for testing assumptions- Handling team skill gaps as feasibility risks- Aligning stakeholders who fixate on the wrong risks- Why business viability (pricing, unit economics) is the most ignored yet most dangerous riskThis episode is great for product managers, agile coaches, and team members who want to stop building things people don't want.#ProductManagement #Agile #RiskAnalysisREFERENCES"Marty Cagan - Inspired", "Melissa Perri - Escaping the Build Trap", "Teresa Torres - Continuous Discovery Habits", "David Marquet - Turn the Ship Around", "Product School blog", "Eric Reis - The Lean Startup"LINKSYouTubeWebsiteSpotify: https://open.spotify.com/show/362QvYORmtZRKAeTAE57v3Apple: https://podcasts.apple.com/us/podcast/agile-podcast/id1568557596

Is your solution architect a gatekeeper or an enabler? Join Product Manager Brian Orlando and Enterprise Business Agility Consultant Om Patel as they draw from their experiences to debate the reasons these roles - which should be natural partners - often find themselves at odds. It's a no-holds-barred look into the eternal conflict between product managers and solution architects!Watch or listen as we explore:1. Why the role exists and if it's even necessary2. Who owns technical decisions3. How PMs may be part of the problem4. Three conversations that never happen5. Identifying architects: shepherds vs. hoarders6. When and how to escalate (without destroying your career)They provide actionable takeaways including the "documentation test," the "decision autonomy test," and the "vacation test" to evaluate whether your architect is enabling or blocking your teams.Whether you're a product manager frustrated by architectural gatekeeping, a solution architect trying to add value without becoming a bottleneck, or a leader trying to resolve these conflicts, this episode offers you solid, practical takeaways that you can start trying today!#ProductManagement #SolutionArchitect #LeadershipTeam Topologies by Manuel Pais and Matthew Skelton, Empowered by Marty Cagan (2020), Five Dysfunctions of a Team by Patrick Lencioni (2002), Radical Candor by Kim Scott, Release It! by Michael Nygard (2017), The Goal by Eliyahu Goldratt, Arguing Agile Episode 67: Team Topologies, Arguing Agile Episode 235: Changing Your Message - Adaptive vs Manipulative Communication, Arguing Agile Episode 236: Why Product Managers Should Own PricingLINKSYouTube https://www.youtube.com/@arguingagileSpotify: https://open.spotify.com/show/362QvYORmtZRKAeTAE57v3Apple: https://podcasts.apple.com/us/podcast/agile-podcast/id1568557596Website: https://arguingagile.com/

Lost a $2M deal and nobody discussed why? You're not alone!Your company is running on hope, not learning.Product Manager Brian Orlando and Enterprise Business Agility Consultant Om Patel are discussing the potentially career-limiting topic of asking "why does the organization systematically avoid learning from failures?" Thanks! We'll be sure to shut the door on our way out... but before we do, we'll explore why sales and product teams never debrief lost deals together, why customer churn meetings feel like career suicide, and why executives are never held accountable for their predictions.....as well as:• Why cross-functional lost deal retrospectives rarely happen (and how to run your first one)• The cost of ignoring customer churn and how to conduct no-blame churn reviews• Building prediction accountability systems to track strategic bets against reality• How organizational silos kill learning and prevent teams from improving• Why "move fast and break things" culture prevents meaningful learning• Creating learning backlogs and embedding continuous improvement in fast-moving organizationsToday is all about actionable tips, specific questions to ask in retrospectives, and strategies for navigating the political landmines of organizational learning. Today, we're giving you tools to transform how your organization learns from mistakes!Referenced Episodes:• AA235 - Changing the Message• AA199 - W. Edwards Deming: Profound Knowledge for Transforming Organizations• AA67 - Team Topologies: Organizing Business and Technology Teams for Fast Flow#ProductManagement #AgileCoaching #CustomerChurnTeam Topologies by Matthew Skelton and Manuel Pais, W. Edwards Deming's work on systems thinking and organizational learning, Amazon's six-pager concept, Arguing Agile Episode 235 (Changing the Message), Arguing Agile Episode 199 (W. Edwards Deming), Arguing Agile Episode 67 (Team Topologies), Silicon Valley move fast and break things culture, 996 work cultureLINKSYouTube https://www.youtube.com/@arguingagileSpotify: https://open.spotify.com/show/362QvYORmtZRKAeTAE57v3Apple: https://podcasts.apple.com/us/podcast/agile-podcast/id1568557596Website: https://arguingagile.com/

12 proven business models that separate successful products from failures!Product Manager Brian Orlando & Enterprise Business Agility Consultant Om Patel examine 12 real-world business models with real examples of the companies that employ them!Based on "The Art of Profitability" by Adrian Slywotzky (2002), this part-1-of-2 podcast covers:• Customer Solution Model (Palantir, SAP, Salesforce)• Product Pyramid (Apple, Tesla, GM)• Multi-Component Pricing (Uber, Coca-Cola)• Switchboard Platforms (Uber, Airbnb, eBay)• Time & Materials (Consulting firms)• Blockbuster Model (Pharma, Netflix)• Profit Multiplier (Microsoft, Disney)• Entrepreneurial Model• Specialist Model (Mayo Clinic, Agile Coaches)• Installed Base (Printers, Razors, K-Cups)• De Facto Standard (Windows, Adobe PDF)• Brand Model (Apple, Nike, BMW)Perfect for product managers, agile coaches, startup founders, and business leaders trying to understand which revenue model fits their product strategy.

Debating why pricing belongs in product management's hands, not sales or finance.Product Manager Brian and Enterprise Business Agility Coach Om are rankling egos as they discuss a heated debates: who should own pricing decisions? Listen or watch as they argue that pricing is product strategy, not a sales tactic. 

When does adapting your communication style cross the line into manipulation? Join Product Manager Brian Orlando and Enterprise Business Agility Coach Om Patel as we examine the differences between translation and transformation of messages.Together, we provide a framework for communicating effectively across audiences without becoming a "slimy shapeshifter."Discover the three-point integrity test, learn to spot narrative inconsistency, and understand why your reputation depends on what people say when you're NOT in the room!Watch this episode to hear/see us explore:• Difference between changing language vs. changing the message• Spot political operators who weaponize adaptive communication• 3 patterns of manipulative communicators• What bosses say when you're not in the room• How to maintain integrity across different audiences• The consistency of storytellingWe're exposing the difference between changing language vs. changing the message and discussing how to maintain integrity!REFERENCESAdam Grant (Think Again), Kim Scott (Radical Candor), Amy Cudd (Harvard Research)#ProductManagement #Leadership #Communication #Integrity #AgileCoaching #ProfessionalDevelopmentstakeholder communication, political operators, credit claiming, blame shifting, managerial integrity, trust building, adaptive communicationLINKSYouTube https://www.youtube.com/@arguingagileSpotify: https://open.spotify.com/show/362QvYORmtZRKAeTAE57v3Apple: https://podcasts.apple.com/us/podcast/agile-podcast/id1568557596Website: http://arguingagile.comINTRO MUSICToronto Is My BeatBy Whitewolf (Source: https://ccmixter.org/files/whitewolf225/60181)CC BY 4.0 DEED (https://creativecommons.org/licenses/by/4.0/deed.en)

What do you do when you're assigned to coach a team that clearly doesn't want your help? In this episode, we tackle the uncomfortable reality of coaching unwilling teams—from building trust with resistant groups to knowing when it's time to walk away.

BONUS: The Evolution of Agile - From Project Management to Adaptive Intelligence, With Mario Aiello In this BONUS episode, we explore the remarkable journey of Mario Aiello, a veteran agility thinker who has witnessed and shaped the evolution of Agile from its earliest days. Now freshly retired, Mario shares decades of hard-won insights about what works, what doesn't, and where Agile is headed next. This conversation challenges conventional thinking about methodologies, certifications, and what it truly means to be an Agile coach in complex environments. The Early Days: Agilizing Before Agile Had a Name "I came from project management and project management was, for me, was not working. I used to be a wishful liar, basically, because I used to manipulate reports in such a way that would please the listener. I knew it was bullshit." Mario's journey into Agile began around 2001 at Sun Microsystems, where he was already experimenting with iterative approaches while the rest of the world was still firmly planted in traditional project management. Working in Palo Alto, he encountered early adopters discussing Extreme Programming and had an "aha moment" - realizing that concepts like short iterations, feedback loops, and learning could rescue him from the unsustainable madness of traditional project management. He began incorporating these ideas into his work with PRINCE2, calling stages "iterations" and making them as short as possible. His simple agile approach focused on: work on the most important thing first, finish it, then move to the next one, cooperate with each other, and continuously improve. The Trajectory of Agile: From Values to Mechanisms "When the craze of methodologies came about, I started questioning the commercialization and monetization of methodologies. That's where things started to get a little bit complicated because the general focus drifted from values and principles to mechanisms and metrics." Mario describes witnessing three distinct phases in Agile's evolution. The early days were authentic - software developers speaking from the heart about genuine needs for new ways of working. The Agile Manifesto put important truths in front of everyone. However, as methodologies became commercialized, the focus shifted dangerously away from the core values and principles toward prescriptive mechanisms, metrics, and ceremonies. Mario emphasizes that when you focus on values and principles, you discover the purpose behind changing your ways of working. When you focus only on mechanics, you end up just doing things without real purpose - and that's when Agile became a noun, with people trying to "be agile" instead of achieving agility. He's clear that he's not against methodologies like Scrum, XP, SAFe, or LeSS - but rather against their mindless application without understanding the essence behind them. Making Sense Before Methodology: The Four-Fit Framework "Agile for me has to be fit for purpose, fit for context, fit for practice, and I even include a fourth dimension - fit for improvement." Rather than jumping straight to methodology selection, Mario advocates for a sense-making approach. First, understand your purpose - why do you want Agile? Then examine your context - where do you live, how does your company work? Only after making sense of the gap between your current state and where the values and principles suggest you should be, should you choose a methodology. This might mean Scrum for complex environments, or perhaps a flow-based approach for more predictable work, or creating your own hybrid. The key insight is that anyone who understands Agile's principles and values is free to create their own approach - it's fundamentally about plan, do, inspect, and adapt. Learning Through Failure: Context is Paramount "I failed more often than I won. That teaches you - being brave enough to say I failed, I learned, I move on because I'm going to use it better next time." Mario shares pivotal learning moments from his career, including an early attempt to "agilize PRINCE2" in a command-and-control startup environment. While not an ultimate success, this battle taught him that context is paramount and cannot be ignored. You must start by understanding how things are done today - identifying what's good (keep doing it), what's bad (try to improve it), and what's ugly (eradicate it to the extent possible). This lesson shaped his next engagement at a 300-person organization, where he spent nearly five months preparing the organizational context before even introducing Scrum. He started with "simple agile" practices, then took a systems approach to the entire delivery system. A Systems Approach: From Idea to Cash "From the moment sales and marketing people get brilliant ideas they want built, until the team delivers them into production and supports them - all that is a system. You cannot have different parts finger-pointing." Mario challenges the common narrow view of software development systems. Rather than focusing only on prioritization, development, and testing, he advocates for considering everything that influences delivery - from conception through to cash. His approach involved reorganizing an entire office floor, moving away from functional silos (sales here, marketing there, development over there) to value stream-based organization around products. Everyone involved in making work happen, including security, sales, product design, and client understanding, is part of the system. In one transformation, he shifted security from being gatekeepers at the end of the line to strategic partners from day one, embedding security throughout the entire value stream. This comprehensive systems thinking happened before formal Scrum training began. Beyond the Job Description: What Can an Agile Coach Really Do? "I said to some people, I'm not a coach. I'm just somebody that happens to have experience. How can I give something that can help and maybe influence the system?" Mario admits he doesn't qualify as a coach by traditional standards - he has no formal coaching qualifications. His coaching approach comes from decades of Rugby experience and focuses on establishing relationships with teams, understanding where they're going, and helping them make sense of their path forward. He emphasizes adaptive intelligence - the probe, sense, respond cycle. Rather than trying to change everything at once and capsizing the boat, he advocates for challenging one behavior at a time, starting with the most important, encouraging adaptation, and probing quickly to check for impact of specific changes. His role became inviting people to think outside the box, beyond the rigidity of their training and certifications, helping individuals and teams who could then influence the broader system even when organizational change seemed impossible. The Future: Adaptive Intelligence and Making Room for Agile "I'm using a lot of adaptive intelligence these days - probe, sense, respond, learn and adapt. That sequence will take people places." Looking ahead, Mario believes the valuable core of Agile - its values and principles - will remain, but the way we apply them must evolve. He advocates for adaptive intelligence approaches that emphasize sense-making and continuous learning rather than rigid adherence to frameworks. As he enters retirement, Mario is determined to make room for Agile in his new life, seeking ways to give back to the community through his blog, his new Substack "Adaptive Ways," and by inviting others to think differently. He's exploring a "pay as you wish" approach to sharing his experience, recognizing that while he may not be a traditional coach or social media expert, his decades of real-world experience - with its failures and successes - holds value for those still navigating the complexity of organizational change. About Mario Aiello Retired from full-time work, Mario is an agility thinker shaped by real-world complexity, not dogma. With decades in VUCA environments, he blends strategic clarity, emotional intelligence, and creative resilience. He designs context-driven agility, guiding teams and leaders beyond frameworks toward genuine value, adaptive systems, and meaningful transformation. You can link with Mario Aiello on LinkedIn, visit his website at Agile Ways.

Is product sense innate or learnable? We debate the million dollar question in product management.Brian and Om explore whether great product leaders are born or made, why organizations promote people with weak product intuition, and how to actually develop genuine product sense. We cover the promotion problem, delayed feedback loops, the role of mentorship, balancing data with intuition, and scaling product thinking across contexts.Key topics: nature vs. nurture in product thinking, why bad product leaders rise, learning challenges, mentorship environments, data vs. intuition, and transferring skills across domains.Whether you're developing your product intuition or building a product culture, this episode offers practical frameworks for intentional learning.#ProductManagement #ProductSense #Leadership #ProductStrategy #CareerDevelopmentLINKSYouTube https://www.youtube.com/@arguingagileSpotify: https://open.spotify.com/show/362QvYORmtZRKAeTAE57v3Apple: https://podcasts.apple.com/us/podcast/agile-podcast/id1568557596Website: http://arguingagile.comINTRO MUSICToronto Is My BeatBy Whitewolf (Source: https://ccmixter.org/files/whitewolf225/60181)CC BY 4.0 DEED (https://creativecommons.org/licenses/by/4.0/deed.en)

In this episode of Arguing Agile, Brian and Om explore the frustrating reality of constant repetition in leadership roles. They discuss why product managers, agile coaches, and team leads find themselves saying the same things over and over - and what to do about it. We explore:• Why repetition is actually part of a leader's core job• How to transform repetition into reinforcement• How the global attention crisis affects workplace communication • Creating single sources of truth and communication contracts • The hidden costs of poor organizational alignment • Practical strategies to reduce unnecessary repetition Whether you're dealing with stakeholders who don't listen, teams that forget decisions, or an organization drowning in information overload, this episode is packed with tips to improve your communication effectiveness. #LeadershipCommunication #ProductManagement #OrganizationalEffectivenessREFERENCESArguing Agile 225: The Team That Got You Here - Navigating Growth and Team EvolutionArguing Agile 211: Communication is Product's Only Job, Or Is It?Arguing Agile 201: Mastering Stakeholder Communication and ManagementArguing Agile 198: Better Communication - Mastering Crucial ConversationsLINKSYouTube https://www.youtube.com/@arguingagileSpotify: https://open.spotify.com/show/362QvYORmtZRKAeTAE57v3Apple: https://podcasts.apple.com/us/podcast/agile-podcast/id1568557596Website: http://arguingagile.comINTRO MUSICToronto Is My BeatBy Whitewolf (Source: https://ccmixter.org/files/whitewolf225/60181)CC BY 4.0 DEED (https://creativecommons.org/licenses/by/4.0/deed.en)

BONUS: Agile Tour Vienna 2025—Building Community-Driven Agile Excellence In this BONUS episode, we explore the upcoming Agile Tour Vienna 2025 (get your ticket now!) with three passionate organizers who are bringing together the Austrian agile community for a day of learning, networking, and innovation. Join us as we dive into what makes this community-driven event special, the challenges facing today's agile practitioners, and why local connections matter more than ever in our evolving professional landscape. The Heart of Community-Driven Events "For me, it's really about creating an event from the community for the community. So at the Agile Tour Vienna we really pay a lot of attention that the contributions are made by community members." - Sabina Lammert The foundation of Agile Tour Vienna lies in its commitment to authentic community engagement. Unlike corporate-led conferences focused on sales and marketing, this event prioritizes genuine knowledge sharing and peer-to-peer learning. The organizers emphasize creating space for meaningful conversations, where participants don't just consume content but actively contribute to discussions and support one another with real-world challenges. This approach fosters an intimate atmosphere where attendees leave with valuable professional connections and practical insights they can immediately apply. Balancing Local Expertise with Global Perspectives "This local aspect is very important, but then it needs to be enhanced by bringing in ideas from people from the outside world." - Robert Ruzitschka Agile Tour Vienna strikes a unique balance between showcasing local Austrian talent and bringing in internationally renowned speakers. The event features a carefully curated mix of practical experiences from Vienna-based practitioners working directly with teams and companies, combined with keynotes from global thought leaders. This blend creates opportunities for attendees to understand both the local context of agile implementation and broader industry trends, making the learning experience both immediately relevant and strategically valuable. A Thoughtfully Designed Experience "We make sure we have a good diversity within the speakers. We also take care that we have a good mix, because for me, agile started with the engineering practices." - Richard Brenner The 2025 program demonstrates attention to creating a comprehensive learning experience. The organizers ensure language accessibility by maintaining at least one English track throughout the day while also offering German sessions. The content spans from technical engineering practices to team coaching and business strategy, reflecting agile's evolution across organizational levels. The event takes place in a stunning castle location (Auersperg Palace) that enhances the intimate, family-like atmosphere the organizers work hard to cultivate. World-Class Content in an Intimate Setting "Agile Tour Vienna is never aiming to go big, but to stay small and familiar. By the end of the day, you know new people." - Sabina Lammert This year's highlights include keynotes from Dave Farley on engineering excellence and Mirella Muse on product operations, plus an innovative Comic Agile storytelling workshop. The organizers deliberately limit attendance to maintain the conference's intimate character, ensuring meaningful networking opportunities rather than overwhelming crowds. Additional touches like a professional barista bar and ample space for informal conversations between sessions create an environment where genuine professional relationships can develop. From Concept-Based to Context-Based Agility "The biggest challenge is that we go from concept-based agility to context-based agility. Companies realize the world is complex. There is no one framework to rule them all." - Richard Brenner The agile community faces a significant evolution as the methodology matures from underground movement to established practice. Organizations are moving away from rigid framework implementations toward contextual problem-solving approaches. This shift requires practitioners to focus on solving real business issues rather than introducing agile for its own sake. The challenge lies in maintaining agile's core values while adapting to diverse organizational contexts and avoiding the trap of seeking simple solutions for complex problems. Maintaining Values-Based Working "It's not about winning over something. It's about using common sense, getting into interaction and trying to find sometimes complex solutions for complex problems." - Sabina Lammert Rather than declaring agile "dead," the community must refocus on value-based working and continuous adaptation. The real challenge involves empowering people to constantly reevaluate situations and embrace the reality that today's solutions may not work in three weeks or three years. This requires normalizing the inspect-and-adapt mindset as standard practice rather than exception, moving beyond method-focused thinking toward principle-driven decision making. Sustaining Community Spirit Through Challenging Times "In times of crisis, people tend to fall back to old patterns of behavior. We need to keep the ideas that made us work in a specific way alive." - Robert Ruzitschka Economic and political uncertainties create pressure to abandon agile practices in favor of traditional command-and-control approaches. Community events like Agile Tour Vienna play a crucial role in maintaining momentum for collaborative, adaptive working methods. The discipline required for agile practices - continuous integration, experimental approaches, market-driven feedback collection - represents a more sophisticated and ultimately more sustainable way of working than traditional project management approaches. The Discipline of Adaptability The discussion revealed an important distinction about discipline in agile environments. Agile teams demonstrate remarkable discipline through practices like continuous integration, experimental product development, and systematic feedback collection. This represents a more humane form of discipline that acknowledges complexity and enables adaptation, contrasting sharply with the rigid discipline of following predetermined plans regardless of changing circumstances. About Robert Ruzitschka, Sabina Lammert, and Richard Brenner Robert Ruzitschka is a Senior Principal Engineer at Raiffeisen Bank International and leads a team of Engineering Coaches. You can connect with Robert Ruzitschka on LinkedIn. Sabina Lammert is Founder and Agile Coach of Leadventure and supports Teams and organizations to improve their way of collaboration. You can connect with Sabina Lammert on LinkedIn. Richard Brenner is a previous guest, he started as Software Engineer and is now working as Agile Coach helping clients to adopt agile ways of working. You can connect with Richard Brenner on LinkedIn.

It's a very human tendency to assume that if something is good, more is better. The real truth is that too much of anything - even a good thing - creates overwhelm, complexity and confusion. And we definitely don't need more of THAT in our practice....

Pascal Papathemelis: The Hidden Cost of Removing Scrum Masters from High-Performing Teams Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. Pascal shares a cautionary experience with mature Scrum teams that appeared to function flawlessly. These teams demonstrated excellent Scrum practices with minimal impediments, leading management to conclude that Scrum Masters were unnecessary. When management removed all Scrum Masters from the department, the previously high-performing teams began to struggle significantly.  Team members had to absorb the responsibilities previously handled by their Scrum Masters, causing them to lose focus on their core value-creating work. Different teams adopted various approaches to fill the Scrum Master void, but none proved effective. Pascal reflects that the Scrum Masters could have made their value more visible by supporting Product Owners more actively and becoming more involved in team tasks. This experience taught him the importance of demonstrating the ongoing value that Scrum Masters provide, even when teams appear to be self-sufficient. Featured Book of the Week: Learning Out Loud—Community Learning and Networking Pascal draws his greatest inspiration not from a single book, but from active participation in the Agile community. He finds tremendous value in discussions within local communities, networking events, and sparring sessions with colleagues. Pascal particularly benefits from Agile Coaching circles in Helsinki, which provide practical knowledge and insights. He also gains inspiration from Agile conferences, but credits Agile Coaching Camps as having the biggest impact - these 2.5-day open space format events are intense and packed with valuable insights. Pascal recommends that Scrum Masters actively engage with their local Agile communities and attend coaching camps to accelerate their professional development and gain diverse perspectives. Self-reflection Question: How visible is the value you provide as a Scrum Master, and what steps could you take to make your contributions more apparent to your organization? [The Scrum Master Toolbox Podcast Recommends]

Führung entscheidet über den Erfolg – oder das Scheitern – jeder agilen Transformation. Punkt.In dieser Folge spreche ich mit Dr. Thomas Karl, Stefan Kahl und Stephan Lang über das heißeste Thema im agilen Business: Leadership in Zeiten des Wandels.

Today we're examining Palantir's "Forward Deployed Software Engineers" - and separating fact from the hype!Everything old is new again! Move over companies that have been doing this for decades such as SAP, IBM, and countless consulting firms!https://blog.palantir.com/a-day-in-the-life-of-a-palantir-forward-deployed-software-engineer-45ef2de257b1Listen as we break down Palantir's 2020 blog post about their Forward Deployed Software Engineers (FDSEs) and discover what these engineers actually do versus what the marketing claims...Key topics covered:What FDSEs actually do, day-to-dayHow this compares to traditional consulting rolesThe difference between software configuration and software engineeringWhy embedded customer roles aren't newCareer advice for aspiring technical professionalsIf you're interested in understanding the reality behind tech industry buzzwords, this is your episode!#ProductManagement #SoftwareEngineering #TechCareers #Consulting #Leadership #AgileCoachingLINKS= = = = = = = = = = = =YouTube: https://youtu.be/SGvJK-aruJ8Spotify: https://open.spotify.com/show/362QvYORmtZRKAeTAE57v3Apple: https://podcasts.apple.com/us/podcast/agile-podcast/id1568557596Website: http://arguingagile.com= = = = = = = = = = = =Toronto Is My Beat (Music Sample)By Whitewolf (Source: https://ccmixter.org/files/whitewolf225/60181)CC BY 4.0 DEED (https://creativecommons.org/licenses/by/4.0/deed.en)

Today, we're delivering a not-your-typical-leadership-book review: "Extreme Ownership" by Jocko Willink and Leif Babin!Ed Martin joins hosts Product Manager Brian Orlando and Enterprise Business Agility Coach Om Patel for a chapter-by-chapter review of how military leadership principles directly translate to product management, agile coaching, and team development. The core message? True leadership isn't about barking orders - it's about taking complete ownership, empowering others, and leading with discipline and humility.Some quotes from our discussion include:• It's not what you preach, it's what you tolerate• If you can run retrospectives people actually want to attend, you've got leadership skills• Communication isn't just part of your job as a product manager - it IS your job• There's no 100% right solution, but leaders must act decisively amid uncertaintyListen to discover the striking parallels between leadership skill and "agile practices" such as decentralized command and the ability to prioritize and execute under pressure. Whether you're leading a development team or coaching organizational transformation, these principles apply.#ExtremeOwnership #Leadership #ProductManagementLINKS= = = = = = = = = = = =YouTube: https://www.youtube.com/@arguingagileSpotify: https://open.spotify.com/show/362QvYORmtZRKAeTAE57v3Apple: https://podcasts.apple.com/us/podcast/agile-podcast/id1568557596Website: http://arguingagile.com= = = = = = = = = = = =Toronto Is My Beat (Music Sample)By Whitewolf (Source: https://ccmixter.org/files/whitewolf225/60181)CC BY 4.0 DEED (https://creativecommons.org/licenses/by/4.0/deed.en)

When Business Owners assign business value during events such as PI Planning, they're considering a lot more than just a number. In this episode, Piotr Wojtera, Agile coach at Nordea describes a very important interaction that helps business owners determine the right number. Like what you hear? Connect with Piotr on LinkedIn. Explore SAFe courses here.

BONUS: Never Stop Experimenting—Building a Culture of Continuous Discovery with Stavros Stavru In this BONUS episode, we dive deep into the world of continuous experimentation with Stavros Stavru, Ph.D. in Organizational Transformations and founder of EdTech ventures AhaPlay and The Caringers. Stavros shares insights from his latest book "Never Stop Experimenting" and reveals how teams can maintain their discovery mindset while balancing the pressures of delivery. The Exploration-Exploitation Dilemma "What would we choose? What we know, and try to exploit? Or go for something new, and better than we currently have?" Stavros introduces us to one of the fundamental challenges facing modern teams: the tension between exploration and exploitation. He explains how teams often start with an exploration mindset, focused on solving real problems through discovery. However, over time, there's a natural shift from discovery to delivery, and teams forget the importance of continued exploration. The title "Never Stop Experimenting" serves as an anchor for teams to remember the value of maintaining their experimental approach even when delivery pressures mount. Born from a Decade of Practice "All the techniques that I describe in the book were born during 10 years of practice." The book isn't theoretical - it's grounded in real-world application. Stavros shares how every technique and framework in "Never Stop Experimenting" emerged from his extensive hands-on experience working with teams over a decade. This practical foundation ensures that readers get battle-tested approaches rather than untested concepts. Software Development as Incremental Experiments "Experimentation requires a creative process." Stavros addresses a common challenge: while teams understand the benefits of experimentation and want to experiment, they often face management resistance that ultimately demotivates the team. He emphasizes that viewing software development as a series of incremental experiments isn't just beneficial - it's absolutely necessary for teams to remain innovative and responsive to changing needs. The Fatware Matrix: Putting Products on a Diet "The challenge: how do you convince the business that you need to spend some time removing features?" One of the book's standout concepts is "The Fatware Matrix," which helps Product Managers recognize when their product is becoming bloated. Stavros introduces a practical tool combining the Kano framework with maintenance cost analysis to illustrate the true cost and impact of maintaining old features. This approach helped one team successfully remove features from their software, with stakeholders later commenting, "Now this is more transparent for us." The key is managing feature creep and software bloat before they become overwhelming. The NSE Ratio: Optimizing Experimentation Rhythm "It's when we try something new that we learn what works. We need to change something on a regular basis." The NSE (Never Stop Experimenting) Ratio measures how long teams wait before introducing new approaches or experimenting with their processes. Stavros explains how teams should define their NSE ratio as part of their team agreements, establishing a regular cadence for trying new things. This systematic approach ensures that learning and adaptation become embedded in the team's rhythm rather than happening sporadically. Building a Safe-to-Fail Culture "Speak of your own failures. When we show our failures as leaders, we show the team that they can run their own experiments." Creating a truly safe-to-fail environment requires leaders to model vulnerability and transparency about their own mistakes. Stavros emphasizes that leaders must give the example by sharing their failures openly, which gives permission for the rest of the organization to take risks and learn from their own experiments. This leadership modeling is crucial for establishing psychological safety around experimentation. About Stavros Stavru Stavros is a Ph.D. in Organizational Transformations and a leading voice in Agile coaching, leadership, and soft skills. Founder of EdTech ventures AhaPlay and The Caringers, he has delivered over 800 trainings and authored Never Stop Experimenting, a powerful toolkit for continuous improvement across teams and organizations. You can connect with Stavros Stavru on LinkedIn, and check his book site at Neverstopexperimenting.com.

The Scrum community is buzzing about a new 55-page expansion to the Scrum Guide. Is this the depth practitioners have been asking for, or is it turning the lightweight framework into bloatware? In this episode, Enterprise Business Agility Coach Om Patel and Product Manager Brian Orlando critically examine the "DLC" that claims the original guide was "deliberately oversimplified." We explore new concepts like outcome vs output definitions of done, the "supporters" role, and the inclusion of complex frameworks like Cynefin.Stick around as we debate whether these additions help teams navigate complexity or create more confusion, while highlighting crucial omissions around organizational structure and practical implementation guidance. #Scrum #Agile #ProductDevelopment= = = = = = = = = = = =LINKS= = = = = = = = = = = = http://arguingagile.comYouTubehttps://www.youtube.com/@arguingagileSpotify https://open.spotify.com/show/362QvYORmtZRKAeTAE57v3Applehttps://podcasts.apple.com/us/podcast/agile-podcast/id1568557596= = = = = = = = = = = =Toronto Is My Beat (Music Sample)By Whitewolf (Source: https://ccmixter.org/files/whitewolf225/60181)CC BY 4.0 DEED (https://creativecommons.org/licenses/by/4.0/deed.en)

Jensen Huang has 60 direct reports and does no 1:1s, so neither should you - right?!? Product Manager Brian Orlando and Enterprise Business Agility Coach Om Patel examine NVIDIA CEO Jensen Huang's claim that he champions "radical transparency" and his policy of no one-on-ones. Join us as we explore what this means for the rest and listen or watch as we agree that one-on-ones should be employee-driven, focused on growth over status updates, and designed to build the trust that actually gets work done, as well as other topics such as:Jensen Huang's leadership philosophy analyzedEmployee-driven vs manager-driven agendas Building trust through private conversationsRemote work and relationship buildingPractical frameworks for better 1:1sWhether you're a product manager, team lead, or individual contributor; whether you own a snappy leather jacket or not, owning your 1:1 agenda is crucial for career development.Now accepting all takes (hot or not) in the comments - do you vote for mass transparency or intimate coaching conversations?#Leadership #OneOnOnes #ArguingAgileLINKS = = = = = = = = = = = =YouTube: https://www.youtube.com/@arguingagileSpotify: https://open.spotify.com/show/362QvYORmtZRKAeTAE57v3Apple: https://podcasts.apple.com/us/podcast/agile-podcast/id1568557596http://arguingagile.com= = = = = = = = = = = =Toronto Is My Beat (Music Sample)By Whitewolf (Source: https://ccmixter.org/files/whitewolf225/60181)CC BY 4.0 DEED (https://creativecommons.org/licenses/by/4.0/deed.en)

"You can't do it alone. If you need to do everything for your client … then you're also blindfolded in only looking one way. You need to get many partners all together … so we have multiple visions, multiple cultures, and can be flexible. “ What started as a small network is now Connected Movement, an international consultancy that taps into the value and power of partnerships. In this episode, Adam talks to Jeroen Jan Elzinger, CEO, and Sukie Kang, SPCT, executive coach, and transformation architect about how the company is bringing people together to solve customers' problems. The trio discusses topics including why understanding cultural differences is important to extend their reach and expertise in more regions and markets, why building a diverse network and team is a strength, and they share examples of how communication styles and decision-making processes vary greatly across different countries. Like what you hear? Connect with Jeroen and Sukie on LinkedIn. Explore SAFe courses here.

If an organization's executives and managers don't understand the new way of working associated with an Agile transformation, how can they lead effectively? In this episode, Sukie Kang with Connected Movement shares his tips for coaches to help leaders become fully engaged. Like what you hear? Connect with Sukie on LinkedIn. Explore SAFe courses here.

BONUS: Beyond Frameworks, A Provocative Guide to Real Agility With Erwin Verweij In this BONUS episode, we dive into the provocative world of Erwin Verweij's latest book: 'How the f*ck to be Agile?' Erwin shares his journey from frustration to clarity as he witnesses organizations adopting Agile frameworks without understanding their purpose. With candid stories from his coaching experiences, Erwin reveals what happens when teams wake up to real agility beyond dogmatic practices and how organizations can find their own path to meaningful change. The Wake-Up Call for Agile Adoption "What the f*ck dude! Do you even know what it means? Do you really know what it means?" Erwin's journey to writing this book began with growing frustration at how companies approach agility. He frequently encountered teams proudly declaring "We're Agile!" or "Our department is Agile" without understanding what that truly meant.  This disconnect between label and understanding became the catalyst for his provocatively-titled wake-up call. Erwin describes his exasperation with organizations adopting frameworks halfheartedly, following mindsets that were completely off track, and ultimately "doing stuff without knowing what they're doing and why they're doing it." The F-word in his book title serves dual purposes - expressing his frustration while also functioning as a power word to wake people up from their complacency. Breaking Free from Framework Dogma "We're not gonna do Agile. Forget it. And we're not gonna do Scrum, even though you're doing Scrum. Let's look at what really works for you people." Rather than imposing rigid frameworks, Erwin advocates for teams to discover what actually works in their specific context. He shares a memorable story of tearing down Scrum posters that management had installed, shocking team members who couldn't believe he would challenge the prescribed approach.  In another example, Erwin creatively used a manager's "quarantine" language by posting contamination warnings at a department's entrance with the message: "If you enter this room, you might get contaminated with a new way of working." These disruptive approaches are designed to shake people from blindly following orders and encourage them to think critically about their processes. Finding Your Own Path to Agility "Any coach who goes into a company with a strict plan and a set approach - don't hire them. They don't have a clue what to do." After the wake-up call, Erwin focuses on helping teams discover their own effective ways of working. He believes that the key is to observe what's already working well, emphasize those elements, and discard what doesn't serve the team. This approach stands in stark contrast to consultants who arrive with predetermined solutions regardless of context.  Erwin emphasizes that real transformation happens when teams take ownership of their processes, adapt them to their unique needs, and make them their own. He cautions against hiring coaches who come with rigid, predetermined plans, as they often lack the flexibility to address a team's specific challenges. The Never-Ending Journey of Adaptation "We need to help teams to stay open for the change that is coming." Erwin stresses that agility is not a destination but a continuous journey of adaptation. The world never stops changing, so teams must remain flexible and open to evolving their approaches. He encourages a mindset of experimentation with phrases like "let's try" and "what could we try" to keep teams responsive to new challenges.  According to Erwin, one of the most powerful ways to foster this adaptive culture is to model the behaviors you want to see in the teams you support. By demonstrating openness to change yourself, you help others embrace the continuous nature of improvement. Scaling Without Bureaucracy "Work with the system, learn what is needed, iterate." When discussing scaling Agile across an organization, Erwin questions why companies feel the need to scale in the first place. He uses cities as a metaphor for how complex systems can organize beyond small groups without excessive bureaucracy.  In one organization where he currently coaches, teams have found a pragmatic approach by adopting elements from various frameworks that work for them. They use quarterly planning sessions from SAFe primarily as a networking opportunity that connects everybody and focuses their efforts, even though the planning itself might be "basically bullshit." This practical, results-oriented approach emphasizes what works rather than dogmatic adherence to frameworks. Software as a Creative Process "Software development is basically figuring out how stuff works. It's a creative process that mostly is being dealt with within the brain of people." Erwin views software development fundamentally as a creative process rather than a production line. He explains that it's not about "typing as fast as you can" but about thinking, problem-solving, and creating. This perspective helps explain why iterative approaches with small steps work better than trying to plan everything upfront.  Erwin notes that when complex problems become routine, teams might not need the full framework structure, but they should retain the values that help them coordinate effectively. The essence of frameworks like Scrum, he suggests, is simply "start working, figure it out, and see what happens" - an approach that many organizations have become afraid to embrace. Awakening Organizational Intelligence "We raise children, which is basically programming another human being - it's really complex. And we just take it for granted. And then we go to work, and we don't know how to make decisions anymore." One of Erwin's most powerful insights is how organizational structures can suppress the natural intelligence and decision-making abilities that people demonstrate in their personal lives. He points out the irony that we navigate incredibly complex systems like raising children or driving in traffic, yet when we arrive at work, we suddenly act as if we can't make decisions without higher approval. This disconnect creates frustration and wastes human potential. Erwin challenges organizations to wake up to this contradiction and create environments where people can bring their full capabilities to work, rather than checking their intelligence at the door. In this section, we refer to Jurgen Appelo's Book Management 3.0. About Erwin Verweij Erwin is a seasoned Agile Coach, Certified Enterprise Coach, and author of Viking Law and How the f*ck to be Agile?. With 15+ years' experience driving meaningful change, he helps organizations embrace real agility through coaching, transformation, and workshops—cutting through complexity to spark courage, clarity, and action. You can link with Erwin Verweij on LinkedIn and connect with Erwin Verweij on Twitter.

Richard Brenner: Contracting for Success,  Establishing Clear Agile Coaching Outcomes Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. Richard reflects on his evolution in defining success as a Scrum Master and Agile Coach. Initially, he believed that if his team was successful, he was successful—but soon realized this perspective was incomplete. Top management wanted tangible evidence of coaching impact, which became problematic without clearly defined metrics. Richard now advocates for establishing a coaching agreement at the beginning of any engagement, with both management and teams defining what success looks like for the coach. He emphasizes the importance of dual-sided accountability as a natural outcome of proper contracting, using metrics that matter to the organization such as flow metrics and outcome metrics to demonstrate coaching value. Self-reflection Question: How are you measuring your own success as a coach or Scrum Master, and have you created explicit agreements with both teams and management about what success looks like? Featured Retrospective Format for the Week: Solution Focused Retrospective Richard recommends the Solution Focused Retrospective from the book "Solution Focused Coaching for Agile Teams." While traditional retrospective formats from books like "Agile Retrospectives" typically open a topic and dig deeply into the problem space, the solution-focused approach suggests spending only a short time discussing problems before pivoting to designing the desired future state. This format focuses on identifying the next step and emphasizing what positive outcomes the team wants to achieve, rather than dwelling on what's wrong. Richard values this approach for its ability to maintain a positive, forward-thinking mindset within teams. [Scrum Master Toolbox Podcast Recommends]

BONUS: Beyond Individual Talent: 2 Leadership Myths We all Believed in with Arne Roock In this BONUS episode, we delve into the complexities of team effectiveness with Arne Roock, an experienced Agile consultant who has worked with organizations ranging from startups to large corporations. Arne shares his insights on what truly makes teams perform at their highest level, why simply assembling talented individuals isn't enough, and how organizations can move beyond the "feature factory" mindset to focus on outcomes and impact. The Myth of Individual Talent in Teams "A team of experts is not an expert team." Arne breaks down the common misconception that placing highly talented individuals together automatically creates a high-performing team. Drawing parallels from sports, he points to examples like the "Red Army" hockey team and the famous "Miracle on Ice," where team cohesion proved more valuable than individual star power. Through his consulting work, Arne observed that quick-fix workshops often produced short-term improvements but failed to create lasting change. Sometimes, teams even deteriorated after temporary interventions. This led him to Richard Hackman's work on team effectiveness, particularly the 60-30-10 rule: leaders should spend 60% of their time designing teams, 30% launching teams, and only 10% on coaching interventions. Coaching alone cannot change a team's trajectory without proper design and launch Leaders should engage with coaches at the beginning of team formation Teams need sufficient stability to achieve meaningful impact Existing teams can be relaunched or redesigned to improve performance In this segment, wer refer to Richard Hackman's 6 conditions for effective teams, and to Margaret Heffernan's Superchicken Paradox Ted Talk, and to the episode with Heidi Helfand about Re-teaming. Balancing Delivery Focus with Team Development "Organizations trends go in waves." Arne discusses the pendulum swing in organizational approaches, noting how Agile emerged as a countermovement to process-centric methodologies. Currently, he observes a strong emphasis on delivery, with many organizations repositioning Scrum Masters as delivery leads. This trend, while addressing immediate business needs, often undermines the fundamental team-building aspects of the Scrum Master role. Arne suggests that we need to find balance between delivery pressure and people-centered approaches, treating these as polarities to manage rather than problems to solve. In this segment, we refer to the book Polarity Management by  Barry Johnson, and to Arne's blog post about cross-functional teams. Moving Beyond the Feature Factory "Delivery manager will undermine team responsibility." When organizations want to shift from deadline-driven development to outcome-focused work, Arne recommends examining team design fundamentals first. He cautions that adding delivery managers won't fix teams that haven't been properly designed and launched. Most organizations operate as "feature factories," focusing on output rather than outcomes. Arne suggests two high-impact practices that can help teams deliver more value: Implementing meaningful sprint goals and effective sprint reviews Using OKRs with specific checks on value delivered, not just features completed Arne emphasizes that the Scrum Master role is a full-time position, and when they're pushed to prioritize delivery management, important team-building work gets neglected. Proper team design creates the foundation for shared delivery ownership without requiring additional management roles. In this segment, we talk about an article that explains how to use OKR's with a “value-check” included.  About Arne Roock Arne works as a consultant for Agile methods and (leadership) team effectiveness. As a trainer and coach he supported both startups and big corporations in different industries. For the past ten years he took a deep dive into the tech industry as an embedded coach with Jimdo and Spotify. You can link with Arne Roock on LinkedIn and connect with Arne Roock on Mastodon.