Podcasts about Agile

Why do so many projects spiral into stress, shifting priorities, and endless risks while others seem to flow smoothly toward success? What if the difference isn't just about tools or methods, but about how you lead?Thankfully, today's guest brings a fresh, human-centered approach to project management. James Louttit is the author of Leading Impactful Teams: Achieving Low Stress Success in Project Management, a leadership coach, and a former CIO who now trains managers and business leaders around the world. His work blends real-world experience with practical tools to help managers lead projects with clarity, sustainability, and impact.In this episode, James introduces his “eight lenses of project management” and reveals why prioritization is often the missing key to project success. He shares powerful ways to engage stakeholders, identify and manage risks, and avoid common mistakes in estimating time and effort. Along the way, James offers stories and frameworks that any manager, whether formally a project manager or not, can use to keep work on track and teams energized.In the extended members-only conversation, James explains how to properly scope your projects and define quality, two notoriously tricky areas that can make or break your results.Get FREE mini-episode guides with the big idea from the week's episode delivered to your inbox when you subscribe to my weekly email.Join the conversation now!Conversation Topics(00:00) Introduction to Project Management(01:44) The Eight Lenses of Project Management(03:13) The Importance of Prioritization(07:54) Agile vs. Waterfall Project Management Approaches(10:23) Engaging Stakeholders Effectively(17:20) Managing Risks in Projects(24:09) Time Management and Estimating Effort(30:40) Keep Up with James(31:30) [Extended Episode Only] How To Properly Scope Your Projects(33:10) [Extended Episode Only] Defining Quality In Project ManagementAdditional Resources:- Get the extended episode by joining The Modern Manager Podcast+ Community for just $15 per month- Read the full transcript here- Follow me on Instagram here - Visit my website for more here- Upskill your team here- Subscribe to my YouTube Channel here Keep up with James Louttit- Follow James on LinkedIn here- Subscribe to his YouTube channel here- Join the IPM Community with a free 7-day trial hereGuest Bonus: Free Audio Book: Leading Impactful Teams and 3 FREE 1-Year Membership to IMP CommunityLeading Impactful Teams is a lively exploration of the "lenses" of project management – Scope, Prioritisation, Time, Cost, Quality, Risks, Team and Stakeholders – that will enable the reader to develop a "sixth sense" for potential issues that could derail their project. It provides a practical toolkit to help you and your team deliver great project outcomes with minimum stress and maximum fun. The IPM Community helps you deliver projects on time, on budget, and without burnout through bite-sized lessons, tactical tools and weekly peer support. Created by James Louttit, author of Leading Impactful Teams, it's a no-jargon, no-exam space where professionals learn fast, share real challenges, and lead with confidence.  To get this bonus and many other member benefits, become a member of The Modern Manager Podcast+ Community.---------------------The Modern Manager is a leadership podcast for rockstar managers who want to create a working environment where people thrive and great work gets done.Follow The Modern Manager on your favorite podcast platform so you won't miss an episode!#ProjectManagement #Leadership #TeamManagement #TeamSuccess #ProjectPlanning #AgileLeadership #RiskManagement #ProjectManagementTips #LeadershipSkills #TeamPerformance

AI Assisted Coding: Agile Meets AI—How to Code Fast Without Breaking Things, With Llewellyn Falco In this BONUS episode we explore the practice of coding with AI—not just the buzzwords, but the real-world experience. Our guest, Llewellyn Falco, has been learning by doing, exploring the space of AI-assisted coding from the experimental and intuitive—what some call vibecoding—to the more structured world of professional, world-class software engineering. This is a conversation for practitioners who want to understand what's actually happening on the ground when we code with AI. Understanding Vibecoding "You can now program without looking at code. When you're in that space, vibecoding is the word we're using to say, we are programming in a way that does not relate to programming last year." The software development landscape shifted dramatically in early 2025. Vibecoding represents a fundamental change in how we create software—programming without constantly looking at the code itself. This approach removes many traditional limitations around technology, language, and device constraints, allowing developers to move seamlessly between different contexts. However, this power comes with responsibility, as developers can now move so fast that traditional safety practices become even more critical. From Concept to Working App in 15 Minutes "We wrote just a markdown page of ‘here's what we want this to look like'. And then we fed that to Claude Code. And 15 minutes later we had a working app on the phone." At the Agile 2025 conference in Denver, Llewellyn participated in a hackathon focused on helping psychologists prevent child abuse. Working with customer Amanda, a psychologist, and data scientist Rachel, the team identified a critical problem: clinicians weren't using the most effective parenting intervention technique because recording 60 micro-interactions in 5 minutes was too difficult and time-consuming. The team's approach embodied lean startup principles turned up to eleven. After understanding the customer's needs through exposition and conversation, they created a simple markdown specification and used Claude Code to generate a working mobile app in just 15 minutes. When Amanda tested it, she was moved to tears—after 20 years of trying to make progress on this problem, she finally had hope. Over three days, the team released 61 iterations, constantly getting feedback and refining the solution. Iterative Development Still Matters When Coding With AI "We need to see things working to know what to deliver next. That's never going to change. Unless you're building something that's already there." The team's success wasn't about writing a complete requirements document upfront. Instead, they delivered a minimal viable product quickly, tested it with real users, and iterated based on feedback. This agile approach proved essential even—or especially—when working with AI. One breakthrough came when Amanda used the number keypad instead of looking at her phone screen. With her full attention on the training video she'd watched hundreds of times, she noticed an interaction she had missed before. At that moment, the team knew they had created real value, regardless of what additional features they might build. Good Engineering Practices Without Looking at Code "We asked it to do good engineering practices, even though we didn't really understand what it was doing. We just sort of say, okay, yeah, that seems sensible." A critical moment came when the code had grown large and complex. Rather than diving into the code themselves, Llewellyn and his partner Lotta asked the AI to refactor the code to make a panel easy to switch before actually making the change. They verified functionality worked through manual testing but never looked at how the refactoring was implemented. This demonstrates that developers can maintain good practices like refactoring and clean architecture even when working at a higher level of abstraction. Key practices for AI-assisted development include: Don't accept AI's default settings—they're based on popularity, not best practices Prime the AI with the practices you want it to use through configuration files Tell AI to be honest and help you avoid mistakes, not just be agreeable Ask for explanations of architecture and evaluate whether approaches make sense Keep important decisions documented in markdown files that can be referenced later “The documentation is now executable. I can turn it into code” "The documentation is now executable. I can turn it into code. If I had to choose between losing my documentation or losing my code, I would keep the docs. I think I could regenerate the code pretty easily." In this new paradigm, documentation takes on new importance—it becomes the specification from which code can be regenerated. The team created and continuously updated markdown files for project context, architecture, and individual features. This practice allowed them to reset AI context when needed while maintaining continuity of their work. The workflow was bidirectional: sometimes they'd write documentation first and have AI generate code; other times they'd build features iteratively and have AI update the documentation. This approach using tools like Super Whisper for voice-to-text made creating and maintaining documentation effortless. Remove Deterministic Tasks from AI "AI is sloppy. It's inconsistent. Everything that can be deterministic—take it out. AI can write that code. But don't make AI do repetitive tasks." A crucial principle emerged: anything that needs to be consistently and repeatedly correct should be automated with traditional code, not left to AI. The team wrote shell scripts for tasks like auto-incrementing version numbers and created git hooks to ensure these scripts ran automatically. They also automated file creation with dates at the top, removing the need for AI to track temporal information. This principle works both ways—deterministic logic should be removed from underneath AI (via scripts and hooks) and from above AI (via orchestration scripts that call AI in loops with verification steps in between). Anti-Patterns to Avoid "The biggest anti-pattern is you're not committing frequently. I really want the ability to drop my context and revert my changes at a moment's notice." The primary anti-pattern when coding with AI is failing to commit frequently to version control. The ability to quickly drop context, revert changes, and start fresh becomes essential when working at this pace. Getting important decisions into documentation files and code into version control enables rapid experimentation without fear of losing work. Other challenges include knowing when to focus on the right risks. The team had to navigate competing priorities—customers wanted certain UX features, but the team identified data collection and storage as the critical unknown risk that needed solving first. This required diplomatic firmness in prioritizing work based on technical risk assessment rather than just user requests. Essential Tools for AI-Assisted Development "If you are using AI by going to a website, that is not what we are talking about here." To work effectively with AI, developers need agentic tools that can interact with files and run programs, not just chat interfaces. Recommended tools include: Claude Code (CLI for file interaction) Windsurf (VS Code-like interface) Cursor (code editor with AI integration) RooCode (alternative option) Super Whisper (voice-to-text transcription for Mac) Most developers working at this level have disabled safety guards, allowing AI to run programs without asking permission each time. While this carries risks, committing frequently to version control provides the safety net needed for rapid experimentation. The Power of Voice Interaction "Most of the time coding now looks like I'm talking. It's almost like Star Trek—you're talking to the computer and then code shows up." Using voice transcription tools like Super Whisper transformed the development experience. Speaking instead of typing not only increased speed but also changed the nature of communication with AI. When speaking, developers naturally provide more context and explanation than when typing, leading to better results from AI systems. This proved especially valuable in a crowded conference room where Super Whisper could filter out background noise and accurately transcribe the speakers' voices. The tool enabled natural, conversational interaction with development tools. Balancing Speed with Safety Over three days, the team released 61 times without comprehensive automated testing, focusing instead on validating user value through manual testing with the actual customer. However, after the hackathon, Llewellyn added automated testing by creating a test plan document through voice dictation, having AI clean it up and expand it, then generating Puppeteer tests and shell scripts to run them—all in about 40 minutes. This demonstrates a pragmatic approach: when exploring and validating with users, manual testing may suffice; but for ongoing maintenance and confidence, automated tests remain valuable and can be generated efficiently with AI assistance. The Future of Software Development "If you want to make something, there could not be a better time than now." The skills required for effective software development are shifting. Understanding how to assess risk, knowing when to commit code, maintaining good engineering practices, and finding creative solutions within system constraints remain critical. What's changing is that these skills are now applied at a higher level of abstraction, with AI handling much of the detailed implementation. The space is evolving rapidly—practices that work today may need adjustment in months. Developers need to continuously experiment, stay current with new tools and models, and develop instincts for working effectively with AI systems. The fundamentals of agile development—rapid iteration, customer feedback, risk assessment, and incremental delivery—matter more than ever. About Llewellyn Falco Llewellyn is an Agile and XP (Extreme Programming) expert with over two decades of experience in Java, OO design, and technical practices like TDD, refactoring, and continuous delivery. He specializes in coaching, teaching, and transforming legacy code through clean code, pair programming, and mob programming. You can link with Llewellyn Falco on LinkedIn.

In this episode of The Daily Windup, we explore why project management skills—not just certifications—can make or break your success in business and government contracting. From PMP to Agile to Lean Six Sigma, today's guest explains how learning the language of project management changes the way veterans and small businesses enter the civilian market, build credibility, and drive profitability. Why PMP certification creates instant credibility for veterans and small businesses How Lean and Six Sigma directly improve customer satisfaction and profitability The belt system explained—white, yellow, green, black, and master black belt, karate style Learn more: https://govcongiants.org/ 

Clarity Is the Secret Weapon of Agile!We often mistake transparency for clarity. Transparency just means the information is available. Clarity means you can actually see. Clarity is not dumping everything on the table. It's making sense of it. It's vision. It's seeing...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/

Burnout Is NOT a Agile Problem - It Is A Planning ProblemI remember a sprint planning meeting a few months ago, and I knew the sprint was doomed before it even started. Not because of bugs or blockers — those we could handle. It was the way everyone looked during planning: like we were gearing up for a marathon we hadn't trained for.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/

Tom Molenaar: When Product Owners “Eat the Grass” for Their 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. The Great Product Owner: The Vision Catalyst "This PO had the ability to communicate the vision and enthusiasm about the product, even I felt inspired." Tom describes an exceptional Product Owner who could communicate vision and enthusiasm so effectively that even he, as the Scrum Master, felt inspired about the product. This PO excelled at engaging teams in product discovery techniques, helping them move from merely delivering features to taking outcome responsibility. The PO introduced validation techniques, brought customers directly to the office for interviews, and consistently showed the team the impact of their work, creating a strong connection between engineers and end users. The Bad Product Owner: The Micromanager "This PO was basically managing the team with micro-managing approach, this blocked the team from self-organizing." Tom encountered a Product Owner who was too controlling, essentially micromanaging the team instead of empowering them. This PO hosted daily stand-ups, assigned individual tasks, and didn't give the team space for self-organization. When Tom investigated the underlying motivation, he discovered the PO believed that without tight control, the team would underperform. Tom helped the PO understand the benefits of trusting the team and worked with both sides to clarify roles and responsibilities, moving from micromanagement to empowerment. In this segment, we refer to the book “Empowered” by Marty Cagan. Self-reflection Question: How do you help Product Owners find the balance between providing clear direction and allowing team autonomy? [The Scrum Master Toolbox Podcast Recommends]

Join me for an exclusive talk with entrepreneur Paul LePage of Foundation BTS. Paul shares how his entrepreneurial life unfolded from a burning desire to serve (and a few failures along the way)...

Tom Molenaar: Purpose, Process, and People—The Three Pillars of Scrum Master Success 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. "I always try to ask the team first, what is your problem? Or what is the next step, do you think? Having their input, having my input, bundle it and share it." Tom defines success for Scrum Masters through three essential pillars: purpose (achieving the team's product goals), process (effective Agile practices), and people (team maturity and collaboration). When joining new teams, he uses a structured approach combining observation with surveys to get a 360-degree view of team performance. Rather than immediately implementing his own improvement ideas, Tom prioritizes asking teams what problems they want to solve and finding common ground for a "handshake moment" on what needs to be addressed. Featured Retrospective Format for the Week: Creative Drawing of the Sprint Tom's favorite retrospective format involves having team members draw their subjective experience of the sprint, then asking others to interpret each other's drawings. This creative approach brings people back to their childhood, encourages laughter and fun, and helps team members tap into each other's experiences in ways that traditional verbal retrospectives cannot achieve. The exercise stimulates understanding between team members and often reveals important topics for improvement while building connection through shared interpretation of creative expressions. Example activity you can use to “draw the sprint”.  [The Scrum Master Toolbox Podcast Recommends]

Is Scrum Dying? Or Are We Just Doing It Wrong?Scrum used to be king. Now people don't even want it on their CV.Remember when being a Product Owner was cool? When Scrum Masters were change agents, not glorified note-takers?When saying “we use Scrum” signalled progressive, Agile thinking?Fast forward to now, and you'll find Product Owners ashamed of the title, Scrum Masters sidelined, and developers stuck in factory-mode delivery.Teams are jumping ship to SAFe, Kanban, or “whatever Spotify did,” chasing results Scrum couldn't deliver.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/

Before Siri had sass and Alexa started judging your music taste, the original virtual assistant was quietly revolutionizing the '90s—powered by many patents and a whole lot of foresight. Now, as AI goes from buzzword to boss, we ask, will it transform your job, your home… or just steal your knowledge?  This week, Dave, Esmee and Rob speak with Kevin Surace, Futurist, Inventor & "Father" of the Virtual Assistant, about exploring the evolution of AI, what the future might hold, and how disruptive innovation can shake up your organization in ways you might not expect.   TLDR: 00:40 – Introduction of Kevin Surace 05:12 – Rob gets confused by Google Maps reviews and selfies 08:15 – Deep dive into the evolution of AI with Kevin 52:00 – How intelligent agents can help manage digital noise and support mental well-being 1:07:30 – Wrapping up the book the Joy Success Cycle and heading to a concert  GuestKevin Surace: https://www.linkedin.com/in/ksurace/ HostsDave Chapman: https://www.linkedin.com/in/chapmandr/Rob Kernahan: https://www.linkedin.com/in/rob-kernahan/Esmee van de Giessen: https://www.linkedin.com/in/esmeevandegiessen/ ProductionMarcel van der Burg: https://www.linkedin.com/in/marcel-vd-burg/Dave Chapman: https://www.linkedin.com/in/chapmandr/ SoundBen Corbett: https://www.linkedin.com/in/ben-corbett-3b6a11135/Louis Corbett:  https://www.linkedin.com/in/louis-corbett-087250264/ 'Cloud Realities' is an original podcast from Capgemini 

Tom Molenaar: Systemic Change Management—Making the Emotional Side of Change Visible 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. "We tend to skip the phase where we just give the person the space to grieve, to not know, instead of that, we tend to move to solutions maybe too quick." Tom faces a significant challenge as he prepares to start with new teams transitioning between value streams in a SAFe environment. The teams will experience multiple changes simultaneously - new physical locations, new team dependencies, and organizational restructuring. Tom applies systemic change management principles, outlining five critical phases: sense of urgency, letting go, not knowing, creation, and new beginning. He emphasizes the importance of making the emotional "understream" visible, giving teams space to grieve their losses, and helping them verbalize their feelings before moving toward solutions. In this episode, we refer to Systemic Change Management, an approach that views organizations as complex, interconnected systems—rather than collections of independent parts. Instead of focusing only on individual skills, isolated processes, or top-down directives, SCM works with the whole system (people, structures, culture, and external environment) to create sustainable transformation. Self-reflection Question: How comfortable are you with sitting in uncertainty and allowing teams to process change without immediately jumping to solutions? [The Scrum Master Toolbox Podcast Recommends]

AI strategist Tommy Högström, who has guided giants like Spotify, H&M, and McDonald's, reveals the truth about implementing AI, scaling product teams, and the entrepreneurial journey. From founding his own AI consultancy in Sweden to leading financial forecasting at Spotify and now launching a search fund to acquire a software business, Tommy offers a rare look inside the strategic shifts that separate hype from reality. This episode explores the tough transition from services to product, the evolution of Spotify's famous agile culture, and how to build data infrastructure that actually scales. Unlock the full potential of your product team with Integral's player coaches, experts in lean, human-centered design. Visit integral.io/convergence for a free Product Success Lab workshop to gain clarity and confidence in tackling any product design or engineering challenge. In this episode: The Spotify Model, Unfiltered: Learn how Spotify's culture and priorities shifted dramatically when its focus changed from pure user growth to profitability, and what that means for agile teams at scale. Services vs. Product: Tommy breaks down the conflicting incentives between short-term consulting revenue and long-term product value, and why he ultimately sold his shares in the company he founded. AI Isn't Magic, It's Data: Discover why you might need four data engineers for every data scientist and why thinking of AI as just an "IT project" is the biggest mistake companies make. The Search Fund Path: An inside look at the search fund model, where entrepreneurs raise capital to buy an existing profitable business and scale it as the new CEO. Mentioned in this episode: Gab AI  Xego AI  1Password  Tommy's LinkedIn: https://www.linkedin.com/in/tommyhogstroom Subscribe to the Convergence podcast wherever you get podcasts including video episodes to get updated on the other crucial conversations that we'll post on YouTube at youtube.com/@convergencefmpodcast Learn something? Give us a 5 star review and like the podcast on YouTube. It's how we grow.   Follow the Pod Linkedin: https://www.linkedin.com/company/convergence-podcast/ X: https://twitter.com/podconvergence Instagram: @podconvergence  

Jim Benson joined host Jamie Flinchbaugh on People Solve Problems to discuss his approach to collaboration and visual management as the foundation for successful Lean and Agile implementations. As Inquisitor at Modus Institute and creator of Personal Kanban, Jim brings a unique perspective on how organizations can remove workplace toxicity while dramatically improving effectiveness. Jim defines collaboration simply yet powerfully: two or more people working toward a common goal with systems in place that allow everyone to act with confidence. This definition cuts through the confusion often created when collaboration gets mixed up with consensus-building or other diluted interpretations. The key insight Jim shared is that confidence drives everything in business, just as consumer confidence drives the free market economy. Jim illustrated this concept through the story of a young procurement agent at Turner Construction who was responsible for purchasing everything from structural steel to toilet paper for a billion-dollar construction project in New York. Initially working from spreadsheets, he had to justify every decision to three levels of management, creating a cycle of criticism and second-guessing that undermined his confidence. When Jim helped implement an obeya with visual controls, everything changed. He could display his work transparently, allowing managers to see when projects were on track, in trouble but manageable, or requiring their expertise. The transformation was remarkable. Instead of commenting on everything he did, managers could now apply their expertise strategically when needed. He could act with confidence, knowing that everyone had visibility into his work and could provide help when necessary rather than criticism after the fact. Jim emphasized that this visual management approach removes toxicity from the workplace by creating clarity around roles, responsibilities, and when intervention is needed. Jim challenged the current trend of CEOs instituting longer work weeks while people are already working at 300% capacity, but only 25% effectiveness. He argued that most knowledge workers are operating far beyond sustainable levels, and the solution isn't more hours but better systems. By creating a better understanding of what people can handle and properly defining work upfront, organizations can increase effective throughput by 200-300% while making work easier and more enjoyable. The conversation touched on problem-solving approaches, where Jim distinguished between everyday operational issues and strategic thinking opportunities. He noted that most bottlenecks in modern business are actually collaborative opportunities that get addressed through non-collaborative means like new software or individual assignments. Instead, these issues often stem from information flowing between people in the wrong formats, which can be fixed simply by understanding what each person in the value stream actually needs. Jim offered a provocative alternative to traditional strategic planning, where leadership teams retreat to develop strategy in isolation. He suggested that companies have exponential strategic value equal to the number of employees raised to the power of the number of employees. Rather than excluding people from strategic planning, Jim advocates for involving everyone in developing strategies, tactics, and measures collaboratively. When people understand how their daily tasks connect to broader strategic goals, achieving corporate objectives becomes much easier. The underlying theme throughout Jim's insights is that most workplace dysfunction stems from people wanting to contribute meaningfully but lacking the systems and clarity to do so effectively. By implementing visual management and collaborative approaches, organizations can tap into this existing motivation while removing the barriers that create frustration and inefficiency. Jim's work can be explored further at modusinstitute.com, and he can be found on LinkedIn at linkedin.com/in/jimbenson.

Enrollment for the Focus Room October Sprint closes tomorrow!

Tom Molenaar: How to Spot and Fix Lack of Trust in Scrum 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. "When people don't speak up, it's because there's no trust. The team showed that they did not feel free to express their opinions." Tom describes working with a team that appeared to be performing well on the surface - they were reaching their goals and had processes in place. However, deeper observation revealed a troubling dynamic: a few dominant voices controlled discussions while half the team remained silent during ceremonies. Through one-on-ones, Tom discovered team members felt judged and unsafe to express their ideas. Using the Lencioni Pyramid as a framework, he helped the team address the fundamental lack of trust that was preventing constructive conflict and genuine collaboration. Featured Book of the Week: Empowered by Marty Cagan Tom recommends "Empowered" by Marty Cagan as a book that significantly influenced his approach to team coaching. The book focuses on empowering teams and organizations to deliver great products while developing ordinary people into extraordinary performing teams. Tom appreciates its well-structured approach that covers all necessary elements without getting lost in details. The book provides practical tools for effective coaching, including techniques for regular one-on-ones, active listening, constructive feedback, setting clear expectations, celebrating success, and creating a culture of learning from failure. [The Scrum Master Toolbox Podcast Recommends]

Tom Molenaar: When To Stop Helping Agile Teams To Change—A Real Life Story 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. "Instead of slowing down and meeting the team in their resistance, I started to try and drag them because I saw the vision of the possible improvement, but they did not see it." Tom shares a powerful failure story about a team that didn't feel the urgency to improve their way of working. Despite management wanting the team to become more effective, Tom found himself pushing improvements that the team actively resisted. Instead of slowing down to understand their resistance, he tried to drag them forward, leading to exhaustion and ultimately his decision to leave the assignment. This episode explores the critical lesson that it's not our job to save teams that don't want to be saved, and the importance of recognizing when to step back. Self-reflection Question: When you encounter team resistance to change, how do you distinguish between healthy skepticism that needs addressing and fundamental unwillingness to improve? [The Scrum Master Toolbox Podcast Recommends]

On today's Daily Windup, I dive into how certifications can be the catalyst for massive growth in government contracting. From real-world success stories like Sarah scaling her 8A business to $30M, Marcus building his SDVOSB to $25M, and Lisa cracking $40M through combined certifications, this episode reveals why credentials aren't just paper—they're profit multipliers. I also unpack why certifications like PMP, Agile, and Lean Six have become essential in today's government contracting landscape, with over 600,000 project management roles available and the DoD increasingly requiring PMP for leadership. Whether you're a veteran translating military skills or a contractor chasing scale, you'll learn how credibility and capability must align to win. Key topics covered: Real success stories of entrepreneurs scaling to $25M–$40M with certifications (8A, SDVOSB, and combined approaches). The rising necessity of professional certifications like PMP, Agile, and Lean Six in the government space. Why credibility, combined with capability and relatability, is critical for winning government contracts. Learn more: https://govcongiants.org/

In this episode, Josh and Bob dive into the uncomfortable but powerful role of intuition in leadership. Data-driven decision-making has become the default, but what happens when the data runs out—or worse, when it misleads you? Both share personal stories of times they ignored their gut and paid the price, and times when trusting that inner signal made all the difference.This isn't about rejecting data. It's about recognizing intuition as another form of input—one that leaders often suppress out of fear it won't “sound logical.” Josh and Bob challenge listeners to remember times they silenced their inner voice, reflect on the outcomes, and start treating gut instincts as signals worth listening to.If you've ever wrestled with the balance between logic and instinct, this episode will push you to rethink how you make decisions. Stay Connected and Informed with Our NewslettersJosh Anderson's "Leadership Lighthouse"Dive deeper into the world of Agile leadership and management with Josh Anderson's "Leadership Lighthouse." This bi-weekly newsletter offers insights, tips, and personal stories to help you navigate the complexities of leadership in today's fast-paced tech environment. Whether you're a new manager or a seasoned leader, you'll find valuable guidance and practical advice to enhance your leadership skills. Subscribe to "Leadership Lighthouse" for the latest articles and exclusive content right to your inbox.Subscribe hereBob Galen's "Agile Moose"Bob Galen's "Agile Moose" is a must-read for anyone interested in Agile practices, team dynamics, and personal growth within the tech industry. The newsletter features in-depth analysis, case studies, and actionable tips to help you excel in your Agile journey. Bob brings his extensive experience and thoughtful perspectives directly to you, covering everything from foundational Agile concepts to advanced techniques. Join a community of Agile enthusiasts and practitioners by subscribing to "Agile Moose."Subscribe hereDo More Than Listen:We publish video versions of every episode and post them on our YouTube page.Help Us Spread The Word: Love our content? Help us out by sharing on social media, rating our podcast/episodes on iTunes, or by giving to our Patreon campaign. Every time you give, in any way, you empower our mission of helping as many agilists as possible. Thanks for sharing!

Give Us FeedbackOne of the biggest challenges facing the Agile community today is the way tools are used. Too often, they become a substitute for conversation and collaboration, rather than a support for them, leaving us falling short of the intent behind Agile's values and principles.  In this episode, we discuss this issue and offer strategies to avoid falling into this trap. Join Shawna Cullinan, Jörg Pietruszka,  Diana Larsen,  Sheila Eckert, Sheila McGrath, April Mills,  Hendrik Esser, Ray Arell, and all the callers to the monthly live event as we explore this topic.  For details on the next live event or how to support our show, please visit  acnpodcast.org.Support the show

NASA selected Blue Origin to (maybe) deliver the once-cancelled VIPER rover, modified Sierra Space's ISS resupply contract which likely puts the nail in the coffin of Dream Chaser, and released the draft of its new commercial space station strategy. All different stories with one message: prove it. But maybe not in a good way.This episode of Main Engine Cut Off is brought to you by 34 executive producers—Jan, Kris, Lee, Will and Lars from Agile, Theo and Violet, Better Every Day Studios, Josh from Impulse, Joakim, Bob, Donald, Creative Taxi, Frank, Pat, Joonas, Fred, Heiko, Warren, Matt, Joel, The Astrogators at SEE, Tim Dodd (the Everyday Astronaut!), David, Ryan, Russell, Stealth Julian, Steve, Natasha Tsakos, and four anonymous—and hundreds of supporters.TopicsNASA Selects Blue Origin to Deliver VIPER Rover to Moon's South Pole - NASAVIPER Might Have A New Ride to the Moon on Blue Origin – SpacePolicyOnline.comBlue Origin only bidder for new VIPER lander award - SpaceNewsNASA, Sierra Space Modify Commercial Resupply Services Contract - NASASierra's Dream Chaser is starting to resemble a nightmare - Ars TechnicaNASA releases details on revised next phase of commercial space station development - SpaceNewsVast backs new NASA commercial space station strategy - SpaceNewsThe ShowLike the show? Support the show on Patreon or Substack!Email your thoughts, comments, and questions to anthony@mainenginecutoff.comFollow @WeHaveMECOFollow @meco@spacey.space on MastodonListen to MECO HeadlinesListen to Off-NominalJoin the Off-Nominal DiscordSubscribe on Apple Podcasts, Overcast, Pocket Casts, Spotify, Google Play, Stitcher, TuneIn or elsewhereSubscribe to the Main Engine Cut Off NewsletterArtwork photo by NASAWork with me and my design and development agency: Pine Works

Terry Haayema: The Product Owner Who Made Retros Unsafe (And How We Fixed It) 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. "The biggest anti-pattern was that he made the retro unsafe... he would come to the retro and called people out for things that had not been done." The Bad Product Owner: The PO Who Made Retros Unsafe Terry describes a product owner who came from a management background focused on widgets and KPIs, completely unprepared for the collaborative nature of the product owner role. This person's biggest anti-pattern was making retrospectives unsafe by calling out individual team members for things not completed or not done to his satisfaction. When gentle coaching interventions failed, Terry took the dramatic step of excluding the PO from retrospectives entirely. Surprisingly, this shock treatment worked - when the PO asked why he wasn't invited, Terry used SBI feedback (Situation, Behavior, Impact) to help him understand how his actions were destroying team dynamics. The story has a positive ending, with the PO eventually understanding and changing his approach. In this segment, we refer to the Retrospective Prime Directive, and the SBI feedback framework. The Great Product Owner: The Customer Connector Terry's best product owner example saw their role not just as the voice of the customer, but as the connector between team and customers. Instead of relying solely on user stories and personas, this PO organized regular informal events where real customers and team members could meet, share pizza and beer, and have genuine conversations. These social connections led to deep customer understanding and resulted in their best feature ever - a simple addition that showed customers their last six orders for easy reordering. This feature increased both order frequency and size while dramatically improving the team's ability to empathize with their users. Self-reflection Question: How might you help your product owner move from being the voice of the customer to being the bridge that connects your team directly with real users? [The Scrum Master Toolbox Podcast Recommends]

This interview was recorded at GOTO Copenhagen 2024.https://gotocph.comMartin Fowler - Pioneer of Various Topics around Object-Oriented Technology & Agile MethodsJames Lewis - Software Architect & Director at Thoughtworks  @thoughtworks  RESOURCESMartinhttps://x.com/martinfowlerhttps://www.martinfowler.comhttps://toot.thoughtworks.com/@mfowlerhttps://www.linkedin.com/in/martin-fowler-comJameshttps://bsky.app/profile/boicy.bovon.orghttps://twitter.com/boicyhttps://linkedin.com/in/james-lewis-microserviceshttps://github.com/boicyhttps://www.bovon.orgLinkshttps://agilemanifesto.orghttps://martinfowler.com/articles/designDead.htmlhttps://martinfowler.com/articles/on-pair-programming.htmlRead the full abstract hereRECOMMENDED BOOKSMartin Fowler • RefactoringScott W. Ambler & Pramod Sadalage • Refactoring DatabasesMartin Fowler & Pramod Sadalage • NoSQL DistilledMartin Fowler • Patterns of Enterprise Application ArchitectureMartin Fowler • Domain-Specific LanguagesMartin Fowler • UML DistilledCrossing BordersCrossing Borders is a podcast by Neema, a cross border payments platform that...Listen on: Apple Podcasts SpotifyBlueskyTwitterInstagramLinkedInFacebookCHANNEL MEMBERSHIP BONUSJoin this channel to get early access to videos & other perks:https://www.youtube.com/channel/UCs_tLP3AiwYKwdUHpltJPuA/joinLooking for a unique learning experience?Attend the next GOTO conference near you! Get your ticket: gotopia.techSUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted daily!

Rebecca Grant of Lexington Institute WITH GORDON CHANG explained China uses gray zone harassment strategy. The US counters by establishing agile defense "nodes" and adapting Army and Marine Corps doctrine to operate from small terrain features. 1921 MANILA

Terry Haayema: Why "Working Myself Out of a Job" Is Wrong for Scrum Masters 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. "Success for a Scrum Master is to do myself out of a job... which I don't buy into at all, because a team will always need a coach." Terry challenges the common belief that Scrum Masters succeed by working themselves out of a job, arguing instead that teams always need coaching as they continuously improve. He emphasizes the importance of separating his outcomes from the team's success to avoid becoming part of the system he's trying to help. For Terry, success is measured by the visible joy he can create in people - when leaders approach him with happiness, when team members are excited to see him, when absenteeism drops because people actually want to come to work. He shares a powerful story of how helping teams find joy not only improved their performance but reduced their stress-related sick days from the highest to the lowest in their division. Featured Retrospective Format for the Week: Drawing Retrospectives Terry loves retrospective formats that use drawings and visual metaphors, like Draw Your Feelings, or the Sailboat retrospective. He explains that when teams draw pictures instead of immediately processing thoughts through language, they generate much richer and deeper insights. The approach works by having people first draw their thoughts, then asking "What led you to draw that picture?" This method bypasses the analytical mind and taps into more intuitive understanding. For longer-term retrospectives, Terry recommends Open Space Technology, which allows groups to self-organize around the most important questions they need to answer. Self-reflection Question: How do you measure your own success as a Scrum Master, and does that measurement inspire you to do your best work? [The Scrum Master Toolbox Podcast Recommends]

 We're back! In this Season 5 premiere, the team reunites after their summer break to kick off an exciting new chapter. Join us as we catch up, share bold predictions for the year ahead, and explore big questions, like whether 2026 will be the year of the autonomous organization. Expect candid reflections, lively discussion, and a sneak peek at what's coming up this season.  We are very keen this season to establish a feedback loop with listeners, so will be doing shows exploring listener questions and challenges - something we are really looking forward to.  Please get in touch with us, via LinkedIn, Substack or cloudrealities@capgemini.com, if you have questions or challenges for us, we'd love to hear from you!TLDR: 00:20 – We're back! 00:35 – Catching up on what we did during the summer break 10:48 – Planning ahead until Christmas: Microsoft Ignite, AWS re:Invent, an AI mini-series and cool guests 20:27 – Tech talk: iPhone 17, deep democracy training, and the human impact of innovation 32:10 – Will autonomous organizations powered by agents emerge within 12–18 months? 40:45 – Reflections inspired by Jaws, climbing adventures, and Bruce Springsteen  HostsDave Chapman: https://www.linkedin.com/in/chapmandr/Rob Kernahan: https://www.linkedin.com/in/rob-kernahan/Esmee van de Giessen: https://www.linkedin.com/in/esmeevandegiessen/ ProductionMarcel van der Burg: https://www.linkedin.com/in/marcel-vd-burg/Dave Chapman: https://www.linkedin.com/in/chapmandr/ SoundBen Corbett: https://www.linkedin.com/in/ben-corbett-3b6a11135/Louis Corbett:  https://www.linkedin.com/in/louis-corbett-087250264/ 'Cloud Realities' is an original podcast from Capgemini 

nullEDGE is a first of its kind virtual conference for ServiceNow professionals with a 40 speaker lineup focusing on delivering valuable insights you can use in your instances NOW.nullEDGE is on Oct 17, so REGISTER NOW. MENTIONED IN THIS EPISODE:- Jace Benson- Jeff Jessie- The Chuck Tomasi You Never KnewABOUT USCory and Robert are vendor agnostic freelance ServiceNow architects.Cory is the founder of TekVoyant.Robert is just some guy.Sponsor Us!

In this episode of the Scrum.org Community Podcast, Patricia Kong hosts a discussion with Elaine Lin Hering, author of  USA Today Best Selling Book "Unlearning Silence," and Ravi Verma, a Professional Scrum Trainer. They examine how workplace culture and cultural norms influence who speaks up and why intentional communication matters.Elaine explains that silence can be strategic or damaging, depending on context, and emphasizes the need for leaders to create environments where all voices are heard. Ravi shares his experiences with reactive versus reflective decision-making and the importance of transparency. They discuss practical strategies for encouraging voice and the significance of designing inclusive meeting practices.Tune in to this inspiring episode that anyone can relate to!Get more insights about Unlearning Silence in this article on the Professional Scrum Unlocked Substack!About Elaine Lin Hering:Elaine Lin Hering a facilitator, writer, and speaker. She works with organizations and individuals to build skills in communication, collaboration, and conflict management. She has worked on six continents and facilitated executive education at Harvard, Dartmouth, Tufts, UC Berkeley, and UCLA. She is the former Advanced Training Director for the Harvard Mediation Program and a Lecturer on Law at Harvard Law School. She has worked with coal miners at BHP Billiton,micro-finance organizers in East Africa, mental health professionals in China, and senior leadership at the US Department of Commerce. Her clients include American Express, Chevron, Google, Nike, Novartis, PayPal, Pixar, and the Red Cross. She is the author of the USA Today Bestselling book Unlearning Silence: How to Speak Your Mind, Unleash Talent, and Live More Fully (Penguin, 2024).About Ravi Verma:Ravi Verma is a Public Speaker, Agile Coach, Scrum.org Professional Scrum Trainer, Evidence Based Management Consultant and Blogger with a passion for helping teams recapture the magic of making I.T. As the Founder and Chief Org Whisperer at The Org Whisperers, Ravi blends ideas from the world of Technology, Entrepreneurship and Organizational Development to develop strong teams and inspiring leaders at all levels of an organization. He recently co-founded his second startup - Al Dente, a platform that helps Agile Coach's and organizations empirically improve business outcomes in tandem with Agile delivery frameworks like Scrum. 

Terry Haayema: When Consensus Becomes Paralysis—The Nemawashi Challenge For Agile Software Development 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. "The problem I'm facing is 'too much consensus'... we talk, bounce ideas, but we don't get going." Terry shares his current coaching challenge in a Japanese company where their cultural practice of Nemawashi (consensus building) has become a barrier to progress. While working across the entire organization, he's discovered that quality is suffering because teams aren't clear about desired outcomes before starting work. The excessive focus on building consensus means initiatives bounce between stakeholders without ever gaining momentum. Terry explains how he's experimenting with delaying detailed refinement to build shared understanding as teams progress, rather than trying to achieve perfect consensus upfront. He uses the metaphor of flying a plane - pilots don't stick rigidly to flight plans but constantly make small course corrections based on real-time feedback. Self-reflection Question: In your organization, what well-intentioned practices have become obstacles to the very outcomes they were designed to achieve? [The Scrum Master Toolbox Podcast Recommends]

In this episode, Emily is joined by guest Chad Engstrom to unpack how agile role expectations have shifted over the last few years and where the industry is heading. They discuss how to understand the hiring organisation in interviews and what candidates can do to improve their chances of securing their dream job.   About the Featured Guest Chad Engstrom is an Account Manager at TEKsystems. Across his almost 3 years with TEKsystems, Chad has held both recruiting and customer facing roles. As a recruiter, Chad specialized in the Agile space and he now helps his customers navigate their Agile Maturity and help them achieve their Agile goals and journeys.    Follow Chad Engstrom on LinkedIn (https://www.linkedin.com/in/chad-engstrom/) The Women in Agile community champions inclusion and diversity of thought, regardless of gender, and this podcast is a platform to share new voices and stories with the Agile community and the business world, because we believe that everyone is better off when more, diverse ideas are shared. Podcast Library: www.womeninagile.org/podcast Women in Agile Org Website: www.womeninagile.org  Connect with us on social media! LinkedIn: www.linkedin.com/company/womeninagile/ Instagram: www.instagram.com/womeninagile/ Please take a moment to rate and review the Women in Agile podcast on your favorite podcasting platform. This is the best way to help us amplify the voices and wisdom of the talent women and allies in our community! Be sure to take a screenshot of your rating and review and post it on social media with the hashtag #womeninagile to help spread the word and continue to elevate Women in Agile.   About our Host Emily Lint is a budding industry leader in the realm of business agility. Energetic and empathetic she leverages her knowledge of psychology, business, technology, and mindfulness to create a cocktail for success for her clients and peers. Her agile journey officially started in 2018 with a big move from Montana to New Mexico going from traditional ITSM and project management methodologies to becoming an agile to project management translator for a big government research laboratory. From then on she was hooked on this new way of working. The constant innovation, change, and retrospection cured her ever present craving to enable organizations to be better, do better, and provide an environment where her co-workers could thrive.  Since then she has started her own company and in partnership with ICON Agility Services serves, coaches, and trains clients of all industries in agile practices, methodologies, and most importantly, mindset. Please check out her website (www.lintagility.com) to learn more. You can also follow Emily on LinkedIn (https://www.linkedin.com/in/emilylint/). 

On the show this week, Nadia Uberoi, Head of People at Garner Health, joins us to explore how HR can move beyond compliance to become a solution-centric and outcome-driven function, aligning closely with the business's mission and deliverables.Nadia shares practical details on how Garner Health has developed agile people systems and cultivated a high-candor culture rooted in real-time feedback and organizational transparency. We discuss how conscious alignment between HR and business strategy depends on both robust systems and hiring people with the right agile mindset.You'll hear more about Nadia's unique approach to performance management, Garner's decision to publicly share 360 feedback, and how a culture of candor empowers everyone, not just HR, to take ownership of change. Nadia also offers an inside look at the mechanics of building and scaling an intentional organizational culture, and the lessons she's learned from fast-growing companies.You will want to hear this episode if you are interested in...[05:16] Aligning HR with business strategy and high candor cultures.[07:28] Seeking CEO buy-in for strategic alignment.[10:37] Balance short-term solutions and long-term infrastructure planning.[13:48] Focus on continuous improvement and clarity of responsibilities.[21:23] Quarterly planning with smaller, manageable initiatives enables better adaptability and faster impact.[29:04] Real-time feedback improved HR-business alignment by enabling quick adjustments.[33:31] Real-time feedback and collaboration enable immediate improvements.[48:22] Intentionally build and systematize culture for business impact.Resources & People MentionedPrinciples by Ray DalioLatticeGarner Health   Connect with Nadia Uberoi Nadia Uberoi on LinkedIn Connect With Red Thread ResearchWebsite: Red Thread ResearchOn LinkedInOn FacebookOn TwitterSubscribe to WORKPLACE STORIES

A company spends $10M over two years on a critical software product, but after firing one vendor and hiring a second, they still have nothing to show for it. This case study details the 5-step action plan used to rescue a failing project, restore internal credibility, and get product delivery back on track. From revamping the product roadmap and redefining vendor contracts to empowering a true product owner, this episode is a masterclass in turning around a high-stakes technology transformation. Discover how to shift from analysis paralysis to momentum and learn why strategy is meaningless without an execution engine you can trust. We also uncover how the team found a surprise opportunity to build new AI products by leveraging decades of institutional data they already had. In this episode: How to create a living technology and product roadmap that aligns both business stakeholders and frontline users. The critical shift from project management (Gantt charts and deliverables) to product management (business outcomes and priorities). Actionable strategies for vendor governance, including tying payment milestones to the delivery of working software. Using incremental delivery and weekly demos to catch misunderstandings early and de-risk the development process. How to move from "analysis paralysis" to action by designing small experiments to test new AI product ideas. Unlock the full potential of your product team with Integral's player coaches, experts in lean, human-centered design. Visit integral.io/convergence for a free Product Success Lab workshop to gain clarity and confidence in tackling any product design or engineering challenge. Subscribe to the Convergence podcast wherever you get podcasts including video episodes to get updated on the other crucial conversations that we'll post on YouTube at youtube.com/@convergencefmpodcast Learn something? Give us a 5 star review and like the podcast on YouTube. It's how we grow.   Follow the Pod Linkedin: https://www.linkedin.com/company/convergence-podcast/ X: https://twitter.com/podconvergence Instagram: @podconvergence  

Callsign MASTER, Col. Donn Yates served for 25 years as an Air Force fighter pilot and Army infantryman. During his storied career, he commanded a Joint Special Operations Aviation Detachment, a fighter squadron, an operations group, and the largest F-15 fighter wing in the Air Force. He is a graduate and former instructor of the US Air Force Fighter Weapons School, the Air Force equivalent of TOPGUN. Following his retirement from the Air Force, Donn served as the Chief Operating Officer for the 5th largest private jet charter company in the United States. Following that, he led Business Development & Strategy efforts for the Air Dominance Division at the Boeing Company. His portfolio included F-15, F/A-18, E/A-18, MQ-25, T-7 and Phantom Works. Donn is currently Vice President of Government Programs for Electra.aero, developing incredible ultra-short t/o aircraft for the next generation of air transportation. “SocialFlight Live!” is a live broadcast dedicated to supporting General Aviation pilots and enthusiasts during these challenging times. Register at SocialFlightLive.com to join the live broadcast every Tuesday evening at 8pm ET (be sure to join early because attendance is limited for the live broadcasts). Aspen Avionics www.aspenavionics.com Avemco Insurance www.avemco.com/socialflight Avidyne www.avidyne.com Continental Aerospace Technologies www.continental.aero EarthX Batteries www.earthxbatteries.com Hartzell Engine Technologies https://hartzell.aero Hartzell Propeller www.hartzellprop.com Lightspeed Aviation www.lightspeedaviation.com Michelin Aircraft https://aircraft.michelin.com/ Phillips 66 Lubricants https://phillips66lubricants.com/industries/aviation/ Tempest Aero www.tempestaero.com Titan Aircraft www.titanaircraft.com Trio Avionics www.trioavionics.com uAvionix www.uavionix.com Wipaire www.wipaire.com

In this episode of the Mob Mentality Show, we dive into the growing tension between the fast rise of Agentic AI systems and the foundational principles of Extreme Programming (XP) and Lean Software Development. As more teams experiment with multi-agent LLM orchestrators like Claude, GPT-4, and others, does the risk of generating untested, low-quality "AI slop" increase—unless guided by tight feedback loops, small batch sizes, and real tests? We ask: - Can Agentic AI truly support Agile and XP practices—or is it working against them - Are we moving toward AI-driven productivity or just automating chaos faster? - What practices can keep teams grounded as tools grow more autonomous? Join hosts Austin Chadwick and Chris Lucian as they explore: - The difference between AI-assisted XP excellence and Agentic AI slop - Real-world dev experiences using multi-agent architectures - How to apply small iterations, pairing/mobbing, and test-first thinking in AI-augmented workflows - The pitfalls of Agentic orchestration without lean guardrails - Why mob programming and XP might be the missing link in managing AI complexity - Tips for maintaining engineering rigor in a world of AI copilots and task runners If you're experimenting with AI in software teams—or trying to balance automation with craftsmanship—this conversation is packed with insights, practical takeaways, and a few strong opinions.

Terry Haayema: The High Cost of Unsafe Agile Retrospectives 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. "She was kind of like the mum for the team... she was actually the glue that held the team together." Terry tells the story of a team that was functioning like a feature factory until a business analyst became their champion and "team mom." This BA supported everyone through agile transformation and helped build trust and healthy conflict. However, when she mentioned something in a retrospective that led to her being put on performance management and eventually leaving, the team rapidly self-destructed. They lost their sense of belonging and teamness, retreating back to working as independent professionals rather than collaborating. The story illustrates how leadership actions can instantly destroy weeks or months of trust-building work, and how critical psychological safety is for sustainable team performance. For more critical points on how to be a great leader, check this episode with Captain David Marquet, a thought leader in the leadership space who wrote Turn the Ship Around!  Featured Book of the Week: The Five Dysfunctions of a Team by Patrick Lencioni Terry credits The Five Dysfunctions of a Team by Patrick Lencioni as massively influential in his career, particularly praising how Lencioni demonstrates that without trust as a foundation, teams cannot achieve anything else. The book's framework shows how lack of trust prevents healthy conflict, which prevents commitment, which prevents accountability, which prevents results. Terry found the way Lencioni illustrates these dysfunctions and their cascading effects to be incredibly valuable for understanding team dynamics and what's needed to build high-performing teams. In this segment, we also refer to Agile Software Development with Scrum, by Schwaber and Beedle. Self-reflection Question: What would happen to your team's dynamics if your most supportive, trust-building team member suddenly left tomorrow? [The Scrum Master Toolbox Podcast Recommends]

Too often, the role of a panel moderator is perceived as logistics—keeping time and reading questions from a list. But the best moderators know it's much more than that. Great moderating is strategy. It's a chance to showcase presence, leadership, and personal brand. Done well, moderation shapes the audience's experience, amplifies the panelists, and demonstrates your leadership in real time.With conference season underway, it's the perfect time to talk about how to elevate when you moderate. My guest, Nicole Lester Arrindell—an accomplished attorney, community leader, and frequent moderator—knows how to turn preparation, presence, and pace into a brand-building advantage.In this episode of Branding Room Only, Nicole and I break down how moderation itself can become a personal branding tool. We share practical tips for prep calls, audience engagement, and managing Q&A, and introduce the PACE framework—being Prepared, Agile, Conscientious, and Engaged—so you can approach your next panel with confidence and leave a lasting impression.2:19 — Nicole on personal branding, three words that describe her, her favorite Paulo Coelho quote, and the Nas track that fuels her7:37 — How Nicole's career transitions connect and build on each other13:11 — The role fellowships and leadership programs play in professional growth15:58 — Why a moderator's approach shapes the success of a panel24:48 — Strategies to prepare as a moderator and create a better experience for panelists and the audience34:42 — How moderation highlights your skills and elevates your personal brand41:35 — Keys to running an effective and balanced panel Q&A47:10 — Ways to close a panel with strength and make it memorable49:55 — Nicole's non-negotiable branding value and her “standing room only” magicMentioned In How Panel Moderation Helps You Build Visibility and Influence with Nicole Lester ArrindellNicole Lester Arrindell | LinkedIn“Everyday People Can Be Everyday Leaders” | Nicole Lester Arrindell | TEDxUStreetWomenCurated Resources from PaulaHow to Prepare for a Conference to Maximize Your Personal Brand ImpactPersonal Branding Boosters and Bruisers: Attending ConferencesPersonal Branding Bruisers: Paula's Professional Pet PeevesLearn More About Paula's Personal Branding Strategy Session OfferCall to ActionFollow & Review: Help others find the podcast. Subscribe and leave a quick review.Want more ways to grow your personal brand? Make sure you're signed up for my upcoming webinars and workshops.Sponsor for this episodePGE Consulting Group LLC empowers individuals and organizations to lead with purpose, presence, and impact. Specializing in leadership development and personal branding, we offer keynotes, custom programming, consulting, and strategic advising—all designed to elevate influence and performance at every level.Founded and led by Paula Edgar, our work centers on practical strategies that enhance professional development, strengthen workplace culture, and drive meaningful, measurable change.To learn more about Paula and her services, go to www.paulaedgar.com or contact her at info@paulaedgar.com, and follow Paula Edgar and the PGE Consulting Group LLC on LinkedIn.

We are continuing our conversation with Nevine White, Senior VP of Finance at Greater Technology Together and a member of the Beyond Budgeting Round Table. Nevine has spent nearly two decades guiding organizations through the shift from rigid annual budgets to adaptive, rolling financial frameworks that enable true business agility.In this episode, Nevine discusses the shift from traditional budgeting to agile financial planning, highlighting the benefits of continuous planning, operational agility, and real-time decision-making. She details the challenges and successes of implementing these changes, including the breakdown of old processes and the empowerment of frontline leaders. Nevine also shares insights into handling project funding, resource allocation, and fostering collaborative decision-making. Her approach showcases how rethinking budget processes can enhance creativity, collaboration, and agility in organizations.00:00 Introduction to Agile Tales02:05 Transforming Financial Planning03:18 Empowering Decision-Making04:39 Navigating System Infrastructure06:46 Changing Corporate Conversations09:46 Handling Change Fatigue13:11 Efficient Forecasting and Planning17:29 Dynamic Decision-Making27:39 Capital Investment Strategies28:20 ConclusionNevine's insights highlight that there's no one-size-fits-all playbook for financial agility. Instead, transformation requires experimentation, iteration, and courage to question the sacred cows of yearly budgets. Her experiences demonstrate how finance - often seen as the last function to change - can become a catalyst for business agility, resilience, and innovation.About Nevine White:Beginning her 35-year career in telecom engineering, Nevine moved on to leading the FP&A function for TW Telecom for two decades. There she championed powerful changes in financial planning that enabled an agile and effective management structure by eliminating traditional budgets. After the sale of the company, Nevine continued this work with Live Future Ready, leveraging her experience to support organizations in their financial transformation efforts across various industries. In 2019, Nevine joined Hargray Communications Group as the VP Accounting, before taking on building the Finance and Administrative functions for a broadband start-up. She is currently the Senior Vice President of Finance at Greater Technology Together, a leading network and security as a service firm. Recognized for her experience in finance agility and building effective teams, she has been featured at conferences and on podcasts, and enjoys sharing her learnings and experiences with all who are seeking to meaningfully change and enable their teams. You can follow Nevine on LinkedIn at https://www.linkedin.com/in/nevinewhite/Podcast music courtesy of www.purple-planet.comVisit us at https://www.ouragiletales.com/about

Terry Haayema: When Scrum Practices Aren't Enough - Learning to Sense the System 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. "I didn't know how to 'sense' the system. I was focused on the scrum practices, I thought when practices were there all would be fine." Terry shares a powerful failure story from his second engagement as a Scrum Master, where he discovered that implementing Scrum practices isn't enough if you don't understand the underlying system driving team behaviors. He describes how individual KPIs were causing conflict between developers and testers - developers were measured on fewer defects while testers were measured on finding more defects. This systemic issue created dysfunction that no amount of daily standups or retrospectives could fix. Terry learned the hard lesson that Scrum Masters must be coaches for both the team and the organization, understanding how metrics and structures shape behavior before trying to implement agile practices. Self-reflection Question: What systemic forces in your organization might be working against the collaborative behaviors you're trying to foster in your teams? [The Scrum Master Toolbox Podcast Recommends]

In this episode, Josh and Bob wrap up their exploration of Stephen Covey's 7 Habits of Highly Effective People by tackling the final three habits: Seek First to Understand, Then to Be Understood, Synergize, and Sharpen the Saw.They unpack what these really mean for leaders today. From the trap of talking too much and forgetting to listen, to why “playing Legos” with people never works, to the absolute necessity of investing in your own growth—this is a conversation full of practical insights and unfiltered stories. Bob and Josh don't just reference Covey; they translate his timeless principles into the messy, real-world challenges of modern leadership.If you're a leader looking for clarity, alignment, and a reminder that your growth sets the ceiling for your team's success, this episode is a masterclass. Stay Connected and Informed with Our NewslettersJosh Anderson's "Leadership Lighthouse"Dive deeper into the world of Agile leadership and management with Josh Anderson's "Leadership Lighthouse." This bi-weekly newsletter offers insights, tips, and personal stories to help you navigate the complexities of leadership in today's fast-paced tech environment. Whether you're a new manager or a seasoned leader, you'll find valuable guidance and practical advice to enhance your leadership skills. Subscribe to "Leadership Lighthouse" for the latest articles and exclusive content right to your inbox.Subscribe hereBob Galen's "Agile Moose"Bob Galen's "Agile Moose" is a must-read for anyone interested in Agile practices, team dynamics, and personal growth within the tech industry. The newsletter features in-depth analysis, case studies, and actionable tips to help you excel in your Agile journey. Bob brings his extensive experience and thoughtful perspectives directly to you, covering everything from foundational Agile concepts to advanced techniques. Join a community of Agile enthusiasts and practitioners by subscribing to "Agile Moose."Subscribe hereDo More Than Listen:We publish video versions of every episode and post them on our YouTube page.Help Us Spread The Word: Love our content? Help us out by sharing on social media, rating our podcast/episodes on iTunes, or by giving to our Patreon campaign. Every time you give, in any way, you empower our mission of helping as many agilists as possible. Thanks for sharing!

In this episode, Ricardo questions whether Agile is still sufficient in the face of the speed of artificial intelligence. Created in 2001, the Agile Manifesto introduced short iterations and continuous learning to address the unpredictability of software development. However, today, tools become obsolete in days, raising questions about the relevance of 2- to 4-week cycles or a quarterly backlog. Vargas doesn't criticize Agile—on the contrary, he recognizes its essential role for organizations in dealing with volatility. The point is to reflect on how to apply it intelligently in the face of the rapidity of AI: smaller microcycles? More discipline? An "Agile 2.0" that includes governance, ethics, and social responsibility? The challenge is adapting to the current intensity of change. Listen to the podcast to learn more!

Neste episódio, Ricardo questiona se o Ágil ainda é suficiente diante da velocidade da inteligência artificial. Criado em 2001, o Manifesto Ágil trouxe interações curtas e aprendizado contínuo para enfrentar a imprevisibilidade do desenvolvimento de software. Porém, hoje, ferramentas tornam-se obsoletas em dias, levantando dúvidas sobre a relevância de ciclos de 2 a 4 semanas ou de um backlog trimestral. Vargas não critica o Ágil — ao contrário, reconhece seu papel essencial para organizações lidarem com volatilidade. O ponto é refletir sobre como aplicá-lo de forma inteligente frente à rapidez da IA: microciclos menores? Mais disciplina? Um “Ágil 2.0” que inclua governança, ética e responsabilidade social? O desafio é adaptar-se à intensidade atual das mudanças. Escute o podcast para saber mais!

Shawn Dsouza: Beyond Product Knowledge—The Hidden Skills Every Product Owner Needs 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. Shawn explores both ends of the Product Owner spectrum through real experiences. On one side, he addresses the "Forced" or "Accidental" Product Owner—a common but problematic pattern where organizations appoint someone based solely on product knowledge. He shares the story of a QA professional thrust into the PO role who knew the product inside out but lacked other essential PO skills, frustrating the team with inadequate responses. Through coaching questions inspired by "The Advice Trap," Shawn helped this reluctant PO reflect on responsibilities and develop confidence beyond technical knowledge. The Great Product Owner: The Story-Crafting Superstar Shawn celebrates a Product Owner who elevated user story writing to an art form—"the Picasso of writing user stories." This exceptional PO co-crafted clear, well-structured stories with the team and used AI to refine stories and acceptance criteria. Her meticulous preparation included intensive refinement sessions before vacations and expert story slicing techniques. By handling requirements clarity superbly, she freed the team to focus entirely on problem-solving rather than deciphering what needed to be built. The Bad Product Owner: The Forced/Accidental Product Owner Organizations frequently make the mistake of appointing the person with the highest product knowledge as Product Owner, assuming technical expertise translates to PO effectiveness. However, the Product Owner role requires diverse skills beyond product knowledge—stakeholder management, prioritization, communication, and strategic thinking. When a QA professional was thrust into this role, their deep product understanding couldn't compensate for underdeveloped PO competencies, leading to team frustration and project complications. In this segment, we refer to the Coach Your PO e-course published by your Scrum Master Toolbox Podcast! Self-reflection Question: What skills beyond domain expertise should you develop or look for when transitioning into or selecting someone for the Product Owner role? [The Scrum Master Toolbox Podcast Recommends]

Shawn Dsouza: The Marathon Mindset—Building Agile Teams That Last Beyond Sprint Deadlines 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. Shawn defines himself as a "people-first Scrum Master" who measures success not through metrics but through daily interactions and team growth. He contrasts two teams: one that hit deadlines but lacked collaboration (unsustainable success) versus another that struggled with deadlines but excelled in conversations and continuous improvement (sustainable growth). For Shawn, protecting deep work and fostering genuine team collaboration indicates true success. He emphasizes that product development is a marathon, not a sprint, and warns that lack of meaningful conversations will inevitably lead to team problems. In this segment, we refer to the book Clean Language by Sullivan and Rees.  Featured Retrospective Format for the Week: Sprint Awards Shawn champions the Sprint Awards retrospective format, moving beyond viewing retrospectives as just another Scrum event to recognizing them as critical team development opportunities. In this format, team members give awards to colleagues for various contributions during the sprint, with each award recipient explaining why they were chosen. Shawn prefers face-to-face, offline retrospectives and always starts with ice breakers to gauge how the team feels—whether they feel heard and connected. He believes in experimenting with different retrospective formats since no single approach works for every situation. Self-reflection Question: How do you balance achieving deliverable outcomes with building sustainable team relationships and collaboration patterns? [The Scrum Master Toolbox Podcast Recommends]

Dave, Esmee, and Rob are strapping in for another season of bold, brain-bending conversations—and they're bringing the flux capacitor with them from Back to the Future.Season 5 beams in global leaders and innovators who challenge how we think about technology, business, and humanity. From AI disruption to digital sovereignty, from leadership to culture—this season's guests are ready to shake things up.Our first full episode drops on September 25, but before we hit 88 miles per hour, here's a quick trailer to set the timeline straight, or at least bend it a little.HostsDave Chapman: https://www.linkedin.com/in/chapmandr/Rob Kernahan: https://www.linkedin.com/in/rob-kernahan/Esmee van de Giessen: https://www.linkedin.com/in/esmeevandegiessen/ProductionMarcel van der Burg: https://www.linkedin.com/in/marcel-vd-burg/Dave Chapman: https://www.linkedin.com/in/chapmandr/SoundBen Corbett: https://www.linkedin.com/in/ben-corbett-3b6a11135/Louis Corbett:  https://www.linkedin.com/in/louis-corbett-087250264/'Cloud Realities' is an original podcast from Capgemini

Shawn Dsouza: From AI Anxiety to AI Advantage: A Scrum Master's Experimental Approach 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. Shawn faces the massive AI transformation currently reshaping the tech industry, acknowledging both its benefits and the fear it creates among professionals questioning their relevance. In his organization, he witnesses AI delivering wonders for some teams while others struggle and lose projects. Rather than viewing AI as an overwhelming wave, Shawn advocates for experimentation. He shares practical examples, like helping a Product Owner streamline story creation from Excel to JIRA using AI tools, and leveraging MIRO AI for team collaboration. His approach focuses on identifying friction points where AI experiments could add value while keeping conversations centered on possibilities rather than fears. Self-reflection Question: Instead of fearing technological changes like AI, how can you create small experiments to explore new possibilities and reduce friction in your current work processes? [The Scrum Master Toolbox Podcast Recommends]

Shawn Dsouza: The Database Migration Disaster— Why Software Development Teams Need Psychological Safety 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. Shawn worked with a skilled team migrating a database from local to cloud-based systems, supported by a strong Product Owner. Despite surface-level success in ceremonies, he noticed the team avoided discussing difficult topics. After three months of seemingly smooth progress, they delivered to pre-production only to discover 140 critical issues. The root cause? Unspoken disagreements and tensions that festered beneath polite ceremony facades. The situation deteriorated to the point where a senior engineer quit, teaching Shawn that pausing to address underlying issues doesn't cost time—it builds sustainability. In this segment, we refer to the episodes with Mahesh Jade, a previous guest on the Scrum Master Toolbox podcast. Featured Book of the Week: The Advice Trap by Michael Bungay Stanier Shawn discovered this transformative book when he realized he was talking too much in team meetings despite wanting to add value. The Advice Trap revealed how his instinct to give advice, though well-intentioned, was actually self-defeating. The book taught him to stay curious longer and ask better questions rather than rushing to provide solutions. As Shawn puts it, "The minute you think you have the answer you stop listening"—a lesson that fundamentally changed his coaching approach and helped him become more effective with his teams. Self-reflection Question: When working with teams, do you find yourself jumping to advice-giving mode, or do you stay curious long enough to truly understand the underlying challenges? [The Scrum Master Toolbox Podcast Recommends]

The Agile Family Tree: Theme, Epic, Feature and User Story Explained“Let's group this into a theme, break it down into epics, then into features and finally user stories.”Sure. Cool. Great.Just one question: what does any of that actually mean?If you've ever nodded along in a backlog grooming session while secretly wondering whether an epic is bigger than a feature or the other way around — you're in good company.It's time we cut through the jargon and talk real Agile clarity.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/

In this episode of Building Better Developers with AI, hosts Rob Broadhead and Michael Meloche revisit an earlier conversation—this time through the lens of AI—to explore how constructive communication in software development creates healthier teams and better code. By analyzing their original “Advocating vs. Arguing” discussion, they uncover new ways to transform conflict into collaboration. “The goal is never to win. The goal is to find the best solution.” – Rob Broadhead What Constructive Communication Really Means Rob draws a clear line between two mindsets: Constructive communication invites evidence, empathy, and openness. Defensive arguing focuses on winning, often shutting down valuable ideas. This subtle difference determines whether a team works together to solve problems or gets stuck in endless debates. Why Constructive Communication Improves Software Development Software projects depend on diverse skills and experiences. When team members communicate constructively: Blind spots shrink. Different perspectives uncover hidden issues. Technical debt decreases. Shared understanding prevents costly rework. Client trust grows. Positive dialogue strengthens long-term relationships. Rob highlights how even an outsider's insight—like a .NET developer's idea on a Python project—can spark innovative solutions. Practical Steps to Encourage Constructive Communication Michael offers proven techniques to keep discussions positive and productive: Ask clarifying questions. Instead of “That won't work,” try “How do you see that working in this context?” Restate what you heard. Confirm understanding before you respond. Stay curious. Open-ended questions invite deeper exploration. “No is a conversation killer. Replace it with ‘Let's consider that.'” – Michael Meloche Spotting When Communication Turns Unproductive Arguments often start subtly. Watch for these warning signs: Absolutes such as “always” or “never.” Interrupting or talking over teammates. Ego-driven choices that ignore user needs or project goals. Rob recommends slowing the pace when tempers rise—pause the meeting, schedule a follow-up, or ask everyone to write down their thoughts before reconvening. Agile Practices Support Constructive Communication Rob and Michael agree that Agile's built-in rituals—backlog refinement, iterative feedback, and sprint reviews—naturally encourage constructive communication in software development. If a team frequently argues, it may be skipping these essential steps. Michael also suggests a weekly “water-cooler” session where team members share new ideas or lessons learned. These informal gatherings nurture creativity and trust. Leadership Sets the Tone Managers and leads can reinforce constructive habits by: Checking in with teammates who seem defensive or frustrated. Offering mentoring or personal support when tension surfaces. Encouraging team traditions—from inside jokes to shared hobbies—that build rapport. Rob observes that the best teams always share a unique bond, whether it's dad jokes or a favorite game, which helps them weather stressful moments. Reader Challenge: Practice Constructive Communication This Week Your Mission: Over the next seven days, pick one team interaction—a stand-up, code review, or planning meeting—and intentionally practice constructive communication in software development. Steps to Try: Listen First. Before offering your idea, restate someone else's point to confirm understanding. Replace “No” with Curiosity. When you disagree, ask an open question like “How do you see that working with our current sprint goals?” Log the Outcome. After the meeting, jot down what changed: Did the discussion stay more positive? Did new solutions surface? Share your results with your team—or even comment on the blog post—to inspire others. Challenge yourself: Can you turn at least one potential argument into a moment of advocacy this week? Key Takeaway: Build a Culture of Constructive Communication This episode underscores that constructive communication in software development is more than a soft skill—it's a project-saver. By listening first, asking better questions, and validating every voice, teams can replace conflict with collaboration and move projects forward with confidence. “Choosing one approach together is better than arguing endlessly about the perfect one.” – Rob Broadhead Whether you're leading a sprint, conducting a code review, or gathering requirements, focusing on constructive communication ensures that every idea is heard—and the best solutions rise to the top. Stay Connected: Join the Developreneur Community We invite you to join our community and share your coding journey with us. Whether you're a seasoned developer or just starting, there's always room to learn and grow together. Contact us at info@develpreneur.com with your questions, feedback, or suggestions for future episodes. Together, let's continue exploring the exciting world of software development. Additional Resources Honest Communication Is Critical For Consultants When To Vent (never) as part of Consulting Communication Use Written Communication To Improve Your Standing And Career Communication Noise vs. Content The Developer Journey Videos – With Bonus Content Building Better Developers With AI Podcast Videos – With Bonus Content

Shawn Dsouza: When Scrum Masters Forget to Listen - A Team Trust Crisis in Agile Implementation 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. Shawn shares a powerful lesson about the importance of listening before implementing. Working with a young, talented team drowning in firefighting, he rolled out Scrum in "full" without taking time to understand the team's context. Going through the motions of Scrum ceremonies without genuine team ownership led to dropping energy levels and lost trust. The turning point came when Shawn realized the team had lost faith in his approach, prompting him to rebuild the process collaboratively with team ownership at its core. This story highlights how good intentions can backfire when we prioritize frameworks over people. Self-reflection Question: Before implementing any new process or framework, how do you ensure you truly understand your team's current challenges and context rather than jumping straight to solutions? [The Scrum Master Toolbox Podcast Recommends]

Is Your Team Heading For a Win? It's officially the end of summer here in the U.S. Part of me is sad. Cooler temps mean it's time for me to hang up my wakeboard and store my boat for the season.But part of me welcomes the move to falling leaves, long sleeves, and Major League Baseball playoffs. I'm a big Dodgers fan, and I'm hoping they make it to the post-season again this year.But even if my team doesn't go, I'll still watch the playoffs and World Series–both because I'm a fan and also to see if I can predict the winning team. And while I'm no Nostradamus, I do have a bit of a superpower. After just one or two innings, I can often tell who is going to win the game.Why? Because it's usually clear that one team is trying just a little bit harder. They're not pitching any better or getting more hits–they're just more engaged.They're running down every foul ball, even when it's already crossed into the stands. They're moving toward every hit, only backing off when a teammate yells, “Mine.” From the superstars to the backup right fielder, everyone on the field is looking for ways to contribute, even when it's outside their role.It's a thrill to watch teams like this: Teams who have put their individual egos aside to win the game. I've seen the same thing happen with successful agile teams, too.Agile teams thrive when team members let go of their egos and do what needs to be done. Agile teams struggle when people stay too rigidly in their most comfortable role–a programmer who refuses to do anything but code or an architect who won't come down from the ivory tower to dirty his or her hands with actual code.The Best Agile Teams Operate without Ego“Agile teams thrive when team members let go of their egos and do what needs to be done.”I'm not saying that everyone needs to be a generalist–that would be like having your pitcher also play first base! What I am saying is if that first baseman has to field the ball, I expect the pitcher to hustle over and cover first to make the out. And if the testers are behind or someone has run into a roadblock, I expect to see anyone who is able help out.On high-performing teams, each person plays their part as best as they can, and looks for opportunities to back up their teammates when they need help.On these teams, it seems as if everyone starts each day thinking: “How can I best help the team win today?”When team members have a winning attitude, I'm willing to bet they're on the move from good to great.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/

Caleb Henry, Director of Research at Quilty Space, joins me to talk about EchoStar's spectrum sales and constellation cancellation, SpaceX's spectrum purchase, and the financials of Starlink.This episode of Main Engine Cut Off is brought to you by 34 executive producers—Bob, Heiko, Creative Taxi, Josh from Impulse, Russell, Donald, Will and Lars from Agile, Matt, Steve, Lee, Joel, Tim Dodd (the Everyday Astronaut!), Frank, Natasha Tsakos (pronounced Tszakos), The Astrogators at SEE, Better Every Day Studios, Ryan, Kris, Pat, Joakim (Jo-Kim), Stealth Julian, Warren, Theo and Violet, Jan, Joonas, Fred, David, and four anonymous—and hundreds of supporters.TopicsQuilty Space (@QuiltySpace) / XStarlink Financial & Strategic Analysis 2025 1H | Quilty SpaceSign Up Form | Quilty SpaceEchoStar sells spectrum to SpaceX, cancels MDA satellite contract - SpaceNewsEchoStar's $23 billion spectrum sale clears path for direct-to-device constellation - SpaceNewsEchoStar orders initial MDA satellites for $5 billion LEO constellation - SpaceNewsThe ShowLike the show? Support the show on Patreon or Substack!Email your thoughts, comments, and questions to anthony@mainenginecutoff.comFollow @WeHaveMECOFollow @meco@spacey.space on MastodonListen to MECO HeadlinesListen to Off-NominalJoin the Off-Nominal DiscordSubscribe on Apple Podcasts, Overcast, Pocket Casts, Spotify, Google Play, Stitcher, TuneIn or elsewhereSubscribe to the Main Engine Cut Off NewsletterArtwork photo by CMSEOWork with me and my design and development agency: Pine Works