Podcasts about Agile

BONUS: The Hidden Dangers of AI at Work With Ari-Pekka Skarp AI is usually sold as a productivity tool, but Ari-Pekka Skarp argues that the real story is what it does to the conversations, skills, and purpose that hold teams together. In this BONUS episode, Ari-Pekka explores why organizations are rushing to use AI "as efficiently as possible" without defining what efficiency means, and what that rush is quietly costing us. Organizations Are Conversations "The organizations are actually conversations, conversational patterns between people."   Ari-Pekka's path from software engineering in 1999 to psychology, psychotherapy, and change leadership was driven by one thread: how the mind works, both individually and socially. Meeting Ralph Stacey, Esko Kilpi, and Douglas Griffin at Nokia changed how he saw organizations. Instead of a machine made of parts, an organization is a living pattern of conversations — people responding to each other's gestures, again and again. George Mead added the idea that the human mind itself is not individual but relational. This matters for AI because a large language model is a new kind of player in those conversations, not just a tool that moves data between them. The Efficiency Fetish "It's like how much people are pressing the acceleration pedal in the car. It doesn't tell anything where the car is going."   Many organizations are trying to use AI "as efficiently as possible," but Ari-Pekka points out that few have defined what efficiency means. What he sees instead is measurement of AI usage itself — how many people are prompting, how many tokens are flowing. He calls this tokenmaxxing. The car metaphor is the key: pressing the accelerator harder says nothing about direction, and going fast in the wrong direction is more costly than going slow. Efficiency only has meaning against a purpose, and purpose is itself a conversational achievement — something a team has to talk its way into. De-Skilling Is the Hidden Cost "If there's nobody in the room who could review what AI has produced and say whether it's correct or not, it's not an AI strategy. It's a liability."   The risk Ari-Pekka worries about most is de-skilling. When we offload cognitive work to AI, we lose the friction that builds learning. There is neurological evidence that people who rely heavily on AI do not develop the same brain structures as those who work through challenges manually. Some skills are fine to lose — nobody needs machine code anymore — but the ability to review and judge AI output is critical, and it is exactly what erodes when we skip the slow work. The result is a double bind: senior experts burn out under the review burden of fast-produced AI output, while juniors never get the time to build the expertise they would need to review it. We Need Speed Limits for AI "We can't optimize individual going as fast as possible... we need a collective... boundaries for individuals."   Ari-Pekka reaches for a historical analogy. Our biological rate of processing information is roughly ten bits per second, and it is not going to change. When we only had horses, we did not need speed limits. When we built cars that could go 200 kilometers per hour, we had to invent rules and boundaries to protect the system. AI is the same: we have reached a threshold where optimizing individual output — more code, more stories, more messages — can damage the whole organization. The control mechanism Ari-Pekka proposes is cognitive friction, deliberately added back into the system so that speed serves the system rather than breaking it. The Tokenization of Work "It's very easy to lose the purpose where you are going if you are only doing fragments of work."   Ari-Pekka's article The Tokenization of Work describes what happens when the unit of work is no longer a job, a profession, or even a task. Digital tools make it easy to fragment work into tiny pieces and spread them across AI agents, and in the process the boundaries that gave work its meaning vanish. Purpose is what protects us from burnout: with a clear purpose, people can do very demanding work without burning out, because the work feeds them. Without purpose, exhaustion arrives fast. For Scrum Masters, this means grounding the work in why it matters is more important now, not less. AI Is an Echo Chamber, Not a Mirror "The AI is more kind of an echo chamber in a sense that it doesn't push back so much."   Ari-Pekka compares AI to George Mead's "generalized other" — the internalized sense of how others see us. AI can play that role, but with a dangerous twist: it is programmed to be agreeable, so it behaves more like an echo chamber than a mirror. Real people push back, point out mistakes, and keep disagreeing. That friction is where learning, competence, and self-awareness grow. Ari-Pekka's practical move is to prompt AI for three different and conflicting perspectives rather than one, using it to go wider rather than only faster. It is not a perfect fix — the model still tries to merge them into one — but it is better than a single agreeable answer. A Three-Second Pause "Take a three-second pause... and just ask yourself, what are you doing?"   Ari-Pekka leaves listeners with a small challenge. A few times a day, when you are about to prompt an AI, pause for three seconds and ask what you are actually doing: are you seeking information, or seeking confirmation? Then consider whether it would be better to call a person and have a real conversation. It is a tiny practice, but it points at the whole episode's message: AI is not neutral infrastructure. It changes the conversations, the skills, and the purpose of work, and the people who notice that — Scrum Masters and Agile coaches especially — are the ones who can keep it from quietly reshaping their teams. About Ari-Pekka Skarp Ari-Pekka Skarp is a psychologist, psychotherapist, Lead Change Coach, organizational psychologist, and author. He wrote Mindfulness, mielenselkeys ja myötätunto, hosts Mielen laboratorio, and researches nondualism. His work connects psychology, complexity, Agile, and AI at work.   You can link with Ari-Pekka Skarp on LinkedIn. You can read Ari-Pekka's Finnish writing at tietoisuustaidot.com and his English blog at Fractal Sauna. You can also find Ari-Pekka's previous Scrum Master Toolbox Podcast episodes on his guest page.

Deborah Colombari: Product Owners Who Protect Focus and Enable Ownership In this episode, we refer to INVEST criteria and Behavior Driven Development. The Great Product Owner: Clear Outcomes, Strong Refinement, and Space for the Team 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.   "He doesn't say how. That allows the team to own the solution." - Deborah Colombari   Deborah describes a great Product Owner who came from project management, but learned to work deeply with upstream discovery and refinement. This PO uses INVEST criteria, Behavior Driven Development-style acceptance criteria, and explicit policies so that developers understand what needs to be done and why. He writes down expected outcomes at the epic and feature level, not only at the story level. Because he does not have a developer background, he depends on the tech lead, and Deborah sees that as a strength when the collaboration works. The PO brings business outcomes and clarity. The team brings technical options and owns the solution. That split creates room for trust.   Self-reflection Question: Does your Product Owner make the outcome clear while still leaving the solution to the team? The Bad Product Owner: Adding Work Without Understanding the Consequences 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.   "He was doing whatever he wanted without thinking of the consequences." - Deborah Colombari   Deborah's Product Owner anti-pattern is a cross-team PO who accepted incoming requests and simply added them to the Sprint. There was no clear requirement discussion, no Definition of Done check, no Definition of Ready conversation, and no technical refinement with someone who could expose complexity. The PO treated every request as urgent, even when it was not, and told developers to stop their current work to pick up the new item. The result was more parallel work, broken Sprint Goals, less predictability, and a destabilized team system. Deborah eventually had to step partly into the Product Owner space to limit WIP and protect delivery. The lesson is blunt: Product Owners who ignore consequences turn priority into chaos.   Self-reflection Question: What is the cost of every "small urgent request" your team accepts mid-Sprint?   [The Scrum Master Toolbox Podcast Recommends]

Control Plane CEO Doron Grinstein joins me to discuss how they've created an AI-native cloud API that virtualizes multi-cloud and hybrid cloud to simplify management and ship faster.Watch the video of this episode.

Deborah Colombari: Stable Agile Teams Make Delivery Predictable 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 I have a stable team, I have reliable data." - Deborah Colombari   For Deborah, success as a Scrum Master comes down to one word: stability. A stable team communicates better, shares knowledge, avoids hero-driven delivery, and becomes predictable enough that the Scrum Master can use historical data instead of wishful thinking. Deborah connects stability with flow metrics and statistical thinking. When an expedite request appears, a stable team can look at its own history and forecast with a useful level of confidence. An unstable team, by contrast, creates silos, overloads key people, and turns every new request into a crisis. Vasco connects Deborah's answer to systems thinking and statistical process control: the team is part of a wider system, and its delivery capability reflects that system. The point is not to force the team to commit beyond what the system can support. The point is to observe the system, improve it, and use real data to forecast what is likely to happen.   Self-reflection Question: Do you know your team's delivery capability from evidence, or are you still depending on optimistic commitments? Featured Retrospective Format for the Week: The 4Ls Retrospective Deborah recommends the 4Ls retrospective: liked, learned, lacked, and longed for. She adds one practical extension: an action-items column. Deborah likes the 4Ls because the quadrants help the team see the same issue from different angles. Something the team longed for may connect to something they learned. Something they liked may expose what was previously missing. The action-items column matters because complaint is easy, but turning a complaint into a concrete experiment is harder. Deborah uses those actions to create or update team agreements, making the retrospective outcome last beyond the meeting.   [The Scrum Master Toolbox Podcast Recommends]

AI speeds up building. It doesn't speed up deciding. The real bottleneck has moved to management, and organizations don't see it yet.In this episode, Peter and Dave talk with Bernie Maloney about why AI adoption is exposing a critical gap in organizational leadership. AI is accelerating delivery and implementation. But the pressure for deciding what's worth building has moved upstream faster than most companies can adapt. That means managers can't just be administrators anymore. They need to understand the work hands-on (the "player" part) while coaching teams to see the bigger strategic picture.Bernie walks through a three-dimensional view of Agile: output (how to build), outcome (how to solve problems), and impact (what problems are worth solving). Most organizations only operate in one. He also explains why the discovery plane—figuring out what to build in the first place—has to move closer to teams instead of staying locked at the management layer. That's where the real bottleneck lives now, not in engineering.This week's takeaways:Agile moved the bottleneck from production to deployment. AI is moving it again, this time to deciding what's worth building in the first place.Managers need to become player coaches: staying close to the actual work so they understand what's possible, while coaching people to think strategically about the system they operate in.Psychological safety and tolerance for intelligent failure have to come before speed. Without them, faster delivery just means faster mistakes.Listen to the full episode at definitelymaybeagile.comSubscribe so you never miss an episode.Have a question or topic you'd like us to cover? Reach out at feedback@definitelymaybeagile.com

Deborah Colombari: Coordinating Global Agile Teams Around One MVP 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 scope is clear. How we are going to deliver it is not clear." - Deborah Colombari   Deborah brings a live challenge from a new global project. Her team carries the deadline, but three other teams must contribute, and those teams do not share the same priority or urgency. The question becomes: how do you align teams when only one of them feels the pressure? Deborah has already tried management alignment meetings, but they have not worked as well as needed. Her next experiment is a one-week workshop inspired by Lean Inception, where managers and teams can write down what is needed, when it is needed, and what each team can realistically contribute. Vasco and Deborah explore three practical moves: define the MVP as a real vertical slice, ask whether a person from each dependent team can join for a Sprint or a few days per week, and reduce dependencies by moving ownership closer to the team that holds the deadline. The coaching conversation ends with a useful image: even vertical slices contain thinner vertical slices. When the deadline is fixed, scope must become flexible.   In this episode, we refer to Lean Inception and Minimum Viable Product.   Self-reflection Question: When your team depends on others, are you managing the dependency or trying to reduce it?   [The Scrum Master Toolbox Podcast Recommends]

Many organizations have sustainability goals, but turning them into project decisions is where the work gets harder. How can project professionals build sustainability into requirements and design before options narrow? How should they weigh cost, schedule, quality and long-term value when priorities compete? And what changes when stakeholder trust or new information requires a different path? We discuss this with Preston Welker, PMP, global climate program and operations lead at The Nature Conservancy, and Ayman Zaki, CSPP, PMP, PMO project manager at EllisDon. What You'll Learn:How to turn sustainability goals into project decisions early, from requirements and design through executionWhy stakeholder trust, community engagement and clear expectations can shape long-term project valueHow to navigate trade-offs between cost, schedule, quality and sustainable outcomesWhy clarifying sponsor priorities upfront helps teams make better decisions when pressures competeHow project management skills and an adaptive mindset help teams turn sustainability expertise into better outcomesPreston Welker, Global Climate Program and Operations Lead at The Nature Conservancy Preston Welker, PMP, is Global Climate Program and Operations Lead at The Nature Conservancy, where he helps teams deliver projects that advance global conservation and climate strategies. With more than 10 years of experience in project management, operations, portfolio systems, and stakeholder engagement, Preston has supported nature-based carbon projects across five continents, designed systems to track progress and impact, and trained teams in Lean, Agile, and facilitation methods. His experience also includes work connected to a $100 million Bezos Earth Fund grant, the development of Naturebase.org, and graduate research on stakeholder engagement for green infrastructure and climate resilience projects. Ayman Zaki, PMO Project Manager at EllisDon Ayman Zaki is a Certified Sustainable Project Professional and PMO Project Manager at EllisDon, with more than 20 years of experience delivering complex construction and development projects across the Middle East. His work spans hospitality, mixed-use, residential, commercial, aviation, and government projects, with expertise in PMO leadership, governance, risk management, stakeholder engagement, FIDIC contract administration, project controls, and value engineering. Across his career, he has contributed to projects exceeding AED 6 billion in cumulative value, including Royal Atlantis Resort & Residences, Gran Meliá Hotel, Tadawul Tower at KAFD, Deira Waterfront Development, Al Dhafra Hotel & Resort, and Sports Hotel on Hudayriyat Island. Episode Resources:Ayman Zaki on LinkedInPreston Welker on LinkedInMelissa Khan-Blackmore on LinkedInProject Management Institute WebsiteProject Management Institute LinkedIn

Deborah Colombari: The Agile Team Destroyed by a Toxic Feedback Loop 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.   "Whenever we almost started to achieve norming, we went back to storming." - Deborah Colombari   Deborah shares the story of a team of about twelve developers and QA specialists that kept losing people one by one. The early signal was not a technical problem. It was turnover. A toxic direct leader created pressure, blame, and snarky responses whenever the team tried to explain what was happening. Because that leader's own manager behaved the same way, Deborah saw a reinforced pattern rather than an isolated personality problem. The team could not stabilize. Every time it moved toward norming, someone left or someone new arrived, sending the team back into storming. Knowledge walked out the door with the people who left, delivery dates slipped, morale dropped, and a fixed-date call center project was eventually canceled. Deborah's story is a sharp systems thinking reminder for Scrum Masters: sometimes the problem is not inside the team. The team may be showing the symptoms of a system that punishes honesty, overloads people, and teaches them that leaving is safer than speaking.   In this segment, we talk about Russell Ackoff, his systems thinking interview with Haynes Media Works, and the Tuckman model.   Self-reflection Question: What turnover or morale signals are you treating as team problems when they may be system problems? Featured Book of the Week: Russell Ackoff Interview by Haynes Media Works Instead of a book, Deborah recommends an old Russell Ackoff interview from Haynes Media Works. She connects Ackoff's thinking to Donella Meadows and to the practical work of Scrum Masters. Deborah highlights how Ackoff explains that the outcome a system is designed to produce affects how the whole system behaves. Her example is health care: if the system rewards treating sickness, it becomes a disease-care system instead of a health system. For Scrum Masters, the lesson is direct. Teams are systems, companies are systems, and the incentives around them shape what they do. Deborah uses Ackoff's work to remind us to look at feedback loops before assuming people are the problem.   [The Scrum Master Toolbox Podcast Recommends]

Deborah Colombari: When Agile Principles Became a Fight With 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 was trying to go against the system, but you cannot go against the system." - Deborah Colombari   Deborah Colombari's Scrum Master journey started with a sense that Agile gave her permission to work differently. After early project management work, a year in Canada exposed her to Agile, and the Scrum Master role soon "felt like a glove." But her failure story starts when a supportive leader left and a more command-driven manager arrived. Deborah pushed back hard, trying to protect the Agile practices she believed were right: dailies, burn-down and burn-up charts, transparency, and team focus. The problem was that she was fighting the manager instead of first understanding the system around him. That conflict spilled into the team and damaged morale. Looking back, Deborah says she would now sit down with the manager first, understand the goals and pressures behind the change, and look for compromise before escalating into resistance. Her key learning was pragmatic: Scrum Masters need principles, but they also need diplomacy. The work is not only helping the team inside the Agile bubble, but also translating between that bubble and the wider organization.   In this episode, we refer to ITIL, the Dunning-Kruger effect, and Thinking in Systems by Donella Meadows.   Self-reflection Question: Where are you fighting the system before you have understood the pressure it is trying to respond to?   [The Scrum Master Toolbox Podcast Recommends]

The hottest take on LinkedIn right now is that coding was never the bottleneck. Josh and Bob have hired hundreds of developers, sat through the "why is this taking so long" meetings, and lived through waterfall, so they're calling it: coding was slow, expensive, and scary, and pretending otherwise rewrites history.But that's just the opening argument. The real conversation is about what happens after the bottleneck moves. Bob walks through the waterfall phases most of the audience never lived through (the 3-inch binder on the shelf, the Gantt charts, the near-infinite bug triage loop) and admits there's something from that era worth keeping. Josh shares a debate he's having with himself about whether code readability still matters when neither he nor his cofounder will ever read the code again, and traces it back to the day he argued his boss out of Hungarian notation because IntelliSense had made it pointless.From there: the "ilities" and which one AI still struggles with most (Josh's answer is usability, by a wide margin), Bob's claim that the industry has been producing less skilled engineers for 25 years and AI just turned up the volume, a CTO who replaced a 9-year-old website in 3 months instead of a year, and why "AI plus HI" only works if the human intelligence part is still growing.If you're an engineering leader deciding which standards to enforce on AI-generated code and which ones to retire, this is the episode. 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!

https://clearmeasure.com/developers/forums/ Today I'm joined by Robert C. Martin, known to most of the industry as Uncle Bob - a programmer since 1970, co-author of the Agile Manifesto, and the first chairman of the Agile Alliance. He's the founder of Uncle Bob Consulting LLC and has written many of the field's defining books, including Clean Code, Clean Architecture, Clean Agile, and his newest release, Functional Design. Lately he's been deep into a project called swarm-forge, an open-source tool he built for coordinating teams of AI coding agents through disciplined, tmux-based workflows, and he's been documenting his experiments running it on real projects on X. This is actually Robert's fourth time on the show - we've previously talked about Agile and Extreme Programming, about clean code, and about being a software leader - I'm looking forward to hearing how his thinking on AI and software programming has evolved. Clean Coder Website - https://cleancoder.com Uncle Bob Github - https://github.com/unclebob Swarm Forge Github - https://github.com/unclebob/swarm-forge X Account - https://x.com/unclebobmartin Clean Coder LinkedIn - https://www.linkedin.com/company/cleancoder Previous Appearances on the Azure & DevOps Podcast: Episode 105 Episode 283 Episode 357  Want to Learn More? Visit AzureDevOps.Show for show notes and additional episodes.

Last time it was the WHO: customers, businesspeople, face to face.  This time it is the HOW.  @Kate Megaw, @Anu Smalley and @Ryan Smith finish the Back-to-Basics run through the 12 Agile Principles with numbers 7 through 12, asking the same question of each: what wording would keep someone in legal, marketing, or finance reading?  Working software becomes delivered value in about ninety seconds, no notes.  Sustainable development turns out to be the most ignored principle of the twelve, partly because it says development and partly because people think sustainable means 40+ hours a week.  Technical excellence loses the C-suite at the word technical, and then the three hosts split on whether design has to go too.  Simplicity and the retrospective principle survive untouched, which raises the obvious question of why the retrospective is the first event teams drop. 

Send us Fan MailHow can Agile and Lean transform productivity in advanced manufacturing?In this episode of the Enterprise Excellence Podcast, Brad Jeavons speaks with Matt Oakley, Head of Operations at Ferra Group Australia, about how Ferra has combined Agile at Scale, Lean Manufacturing, Scrum, Six Sigma and continuous improvement to transform the way it operates.Over approximately four years, Matt explains that Ferra achieved around 25% average annual growth, approximately 220% EBITDA growth, doubled revenue while increasing staff by only around 30%, and roughly doubled the value generated per employee.In this episode, Brad and Matt explore:

Sheik Meeajaun: Product Owners Need the Justified No to Protect Customer Value In this episode, we refer to Vasco's Product Owner episodes, where Product Owners share their own lessons from the role. The Great Product Owner: Owning the Product and Practicing the Justified No 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.   "No, you cannot have this, but this is why." - Sheik Meeajaun   Sheik's model for a great Product Owner came from a mentor he worked with early in his career. That PO owned his slice of the product, delivered consistently, and taught Sheik the power of the "justified no." A strong PO does not simply reject stakeholder requests. They explain the trade-off, ask what should be removed from the sprint, and make business value visible. If a stakeholder wants urgent work, the PO can ask them to get agreement from the person whose work would be displaced. That shifts the conversation from pressure to prioritization. For Sheik, great Product Owners understand that their job is to bring value to the business and delight customers. They care deeply enough about the product to protect it from random requests, HiPPO decisions, and backlog noise. They know success is not only delivery. It is the visible appreciation that comes when people recognize a product decision created real value.   Self-reflection Question: Does your Product Owner have a practical way to say no that protects value without turning every request into conflict? The Bad Product Owner: The Executor Who Cannot Say No Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.   "A Product Owner's primary job is to bring value." - Sheik Meeajaun   The anti-pattern Sheik warns about is the Product Owner as executor. This PO does not own the product, does not know the customers deeply enough, and does not push back when leadership changes direction. They become a project manager with a backlog, accepting whatever the highest-paid person in the room asks for next. The team then loses coherence, the product loses a clear direction, and the Scrum Master is left helping the team manage the consequences of weak ownership. Sheik is careful not to blame only the individual. Many POs are placed in the role without mentoring, without a clear understanding of product ownership, and without the organizational support to say no. The result is predictable: a mountain of requests, no clear value conversation, and a team delivering work without a strong product story behind it.   Self-reflection Question: Where is your Product Owner being treated as an order taker instead of the person accountable for product value?   [The Scrum Master Toolbox Podcast Recommends]

Remembering September 11thSome days pass into history.Others remain with us forever.September 11, 2001 was one of those days.In this special episode of The Agile Daily Standup, we're setting aside our normal conversation to pause, reflect, and remember.We remember the innocent lives lost.We honor the firefighters, police officers, paramedics, military members, first responders, and ordinary citizens who demonstrated extraordinary courage when it mattered most.We remember the families whose lives changed forever.And we remember what happened in the days that followed—when differences seemed smaller, neighbors became more important, strangers helped strangers, and countless people simply asked:“What can I do?”This episode isn't about Agile.It's about people.It's about courage, service, sacrifice, compassion, resilience, and the responsibility we have to carry those lessons forward.Twenty-five years later, an entire generation has grown up knowing September 11th only through photographs, recordings, classrooms, and the stories of those who lived through it.That makes remembering even more important.

August prepayments strengthened the view that the 2026 refinance wave has peaked, with Fannie 30-year speeds falling 12 percent to 7.1 CPR and Ginnie II also slowing, leaving subdued near-term runoff and greater extension risk, while higher-coupon VA pools and recent Ginnie vintages remain the key latent prepayment risks if mortgage rates decline materially. Robbie interviews Agile's Greg Vacura on connecting mortgage lenders and broker-dealers to make MBS trading faster, more efficient, transparent, and less reliant on phone-based processes. And rates remain caught between an oversold Treasury market and persistent inflation, fiscal, supply, and geopolitical pressures, with the selloff pushing the 30-year above 5.30 percent and MBS underperforming even after a strong 30-year auction, while rising oil, firm economic data, and a heavy corporate calendar keep the focus squarely on CPI and the Fed's upcoming decision. This week's podcasts are sponsored by NFTYDoor, the white-label HELOC platform for banks, credit unions, and  brokers. Close in zero days with warehouse funding. Power your home equity lending with NFTYDoor.Welcome to The Chrisman Commentary, your go-to daily mortgage news podcast, where industry insights meet expert analysis. Hosted by Robbie Chrisman, this podcast delivers the latest updates on mortgage rates, capital markets, and the forces shaping the housing finance landscape. Whether you're a seasoned professional or just looking to stay informed, you'll get clear, concise breakdowns of market trends and economic shifts that impact the mortgage world.

Sheik Meeajaun: Scrum Master Success Starts With Trust and Ends With Teams Delivering 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 try to build trust before I build anything else." - Sheik Meeajaun   For Sheik, Scrum Master success is simple to describe and hard to earn: the team delivers what it committed to, demos happen, customers are impressed, and the Scrum Master has protected the team from avoidable disruption. He sees himself as a shield, pushing back when stakeholders bypass the team or when a Product Owner wants to interrupt the sprint without acknowledging the cost. But when he joins a new team, Sheik does not start with burndown charts or velocity. He starts with one-on-one conversations. He tells people his job is to make their work easier, then asks what help they need. Those conversations reveal the real blockers that charts often hide. Trust comes first because teams deliver through people, not dashboards. When people know each other, help each other, and pick up work when someone is away, they become more than a collection of roles. They become a team with a shared future.   Self-reflection Question: What do your first conversations with a new team tell people about the kind of Scrum Master you intend to be? Featured Retrospective Format for the Week: Three Words to Sum Up the Sprint Sheik starts retrospectives by asking each person for three words that sum up the sprint. The words can be simple: productive, boring, repetitive. The value comes from asking people to explain what sits behind those words. Instead of stopping at "I could not finish my story," Sheik wants the team to walk back through what happened: who was unavailable, what help was missing, where the Product Owner did not clarify, and which impediment stayed hidden too long. For him, a good retrospective creates a safe place to talk honestly about the details before the failure. The format is intentionally plain. The goal is not novelty. The goal is a conversation that finds the friction early enough for the team to do something about it.   [The Scrum Master Toolbox Podcast Recommends]

Sheik Meeajaun: Scrum Masters Must Learn by Experimenting When AI Joins the Agile Team 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.   "Never be afraid to admit you don't know something." - Sheik Meeajaun   Sheik brings a current challenge that goes beyond one team: the gap between Scrum theory and real work when the context changes faster than the playbook. His example is AI. Scrum Masters are now asked to help teams where AI agents contribute to delivery, but no certification course can fully prepare us for that. Sheik's starting point is humility: say "I don't know," learn the domain, run small experiments, and reflect quickly. In one team, two human developers worked alongside several AI agents. They could not run a normal standup with Claude, so the team created a status report and reviewed it with the human team members. Sheik framed the agents as junior developers: useful, fast, and still requiring clear instructions, review, and guardrails. That framing helped experienced developers see AI collaboration as coaching and oversight, not as magic productivity. The key lesson is practical empiricism: try, inspect, adapt, and keep learning as the work changes.   In this episode, we refer to Scrumling's AI Product Owner course and the need to adapt Scrum practice to AI-enabled work.   Self-reflection Question: What new reality is your team facing where the honest Scrum Master answer should start with "I don't know yet"?   [The Scrum Master Toolbox Podcast Recommends]

Sheik Meeajaun: When Spillover Becomes Normal, Scrum Teams Stop Seeing the Cost Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.   "A good Scrum Master makes their Product Owner look like a superstar." - Sheik Meeajaun   Sheik describes a team pattern many Scrum Masters recognize: spillover had become so normal that finishing the sprint felt like a special event. Refinement was weak, stories were often written during refinement instead of before it, and Product Backlog Items were sometimes little more than one-line titles. The Product Owner was not consistently engaged, standups had become update sessions for the PO, and nobody was connecting non-delivery to business impact. Sheik brought his Product Owner background into the Scrum Master role and started asking a more pragmatic question: what is the cost per sprint when we do not deliver? By making cost of delay visible, he helped the team see that spillover was not just a process issue. It was lost value. The experiments were practical: protect focus, prepare stories before refinement, and tackle the gaps at ground level instead of pretending the organization would fix everything first.   Self-reflection Question: What does your team treat as normal today that is quietly costing the product money every sprint? Featured Book of the Week: The Scrum Guide by Ken Schwaber and Jeff Sutherland Sheik does not pretend to have a long reading list. He says experience shaped him more than any single book, because contracting exposed him to many organizations and many versions of Scrum in practice. Still, he points listeners back to The Scrum Guide as the minimum reference every Scrum Master should know. For Sheik, the guide gives the vocabulary and foundation, but experience teaches the translation work: how those ideas survive contact with real teams, weak refinement, Product Owners who are stretched thin, and organizations that say "Agile" while still behaving like escalation machines.   [The Scrum Master Toolbox Podcast Recommends]

Is Transparency Really the Answer? Is Transparency Really the Answer?We hear it constantly in Agile: “We need more transparency.”But does transparency really mean sharing everything?In Episode 1647 of The Agile Daily Standup, we explore an important leadership lesson: more information does NOT automatically create more understanding.Long status reports, endless project updates, detailed explanations, milestones, metrics, and mountains of data may technically make us transparent—but they can also bury the one thing our audience actually needs to know:Why does this matter?Great communication isn't about proving how much work happened. It's about making the impact impossible to miss.

Sheik Meeajaun: The Scrum Master Who Let Standups Stay Silent Until the Team Took Ownership 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.   "You can't fix something until it breaks." - Sheik Meeajaun   Sheik Meeajaun joins us from Bulgaria with a failure story about silence, escalation, and the uncomfortable work of helping a team own its own communication. He stepped into a hybrid team where the previous Scrum Master had led the Daily Scrum like a status meeting. When Sheik stopped driving the conversation, the team simply stopped speaking. For two weeks, the standups were painfully quiet. The Product Owner tried to take over, managers escalated complaints, and Sheik had to explain that the silence was exposing the real problem: the team had learned to wait for someone else to lead. The breakthrough came when one quiet team member finally spoke up and said what she was working on. Sheik asked her to pass the conversation to the next person, and the team slowly built the habit of talking to each other. His lesson is clear: sometimes the Scrum Master must resist rescuing the team long enough for the team to see what needs to change.   Self-reflection Question: Where are you stepping in so quickly that your team never has to build the muscle of ownership?   [The Scrum Master Toolbox Podcast Recommends]

There's a squeeze on right now, and it's landing hardest on middle managers and senior leaders. Do more with less. Do more with the same. Lead the team and ship the code. The player-coach role used to be a startup thing, something you did because there were 6 of you and someone had to. Now it's being handed to leaders at scale, and most of them didn't ask for it.Bob comes out swinging. He's fine with it in a small company, but past a certain size, he wants you to wear one hat and be excellent at it. He walks through what actually breaks when a CTO is also a team member: it's less about time and more about the role conflicts nobody talks about, like having to put your own architect on a PIP while you sit next to them every day.Josh admits his first run as a leader was a failed player-coach experiment. He wasn't good at either job, and his team paid for it.The conversation turns to capacity, and that's where it gets uncomfortable. Bob's first question in any agile engagement was "do you know your capacity?" and almost nobody did. Josh tells a story from his college weight room, a strength coach, and a set of 25 squats that should've been mathematically impossible, to argue that people have more in them than they think. Bob answers with the difference between stretching internally and committing externally, and why he'll happily overload anyone who never says no.Then executive math. The belief that a million dollars or 10 new reqs turns into capacity on the day you sign the paperwork. Bob has a story from a financial services project where the plan assumed 120 people and the floor had 38, and nobody said a word until he did. Josh connects it to GitHub's outage problem in 2026: you can do more and still be getting worse.What's in this episode:Two contexts where player coach is fine, and the size where it stops being fineDilution vs tension: the hidden cost of leading people you also code withBob's rule: if you keep saying yes, he'll keep loading you up, and that's his rightThe 25 squats story and what it says about untapped capacityInternal stretch goals vs external commitments (and why they're different numbers)Why Bob hates reserves and gives extra capacity straight to the businessCapacity in 2026 is a moving target, and it doesn't only move upExecutive math, and how it wins when you can't defend your own numberBad news never ages wellBob's Badass Agile Coaching Days runs September 29 through October 1, 2026, virtual, 3 time zones, 12 speakers, all proceeds to Women in Agile and African Agility. Details at agile-moose.com.

The 12 principles behind the Agile Manifesto are the most skipped page in agile. Plenty of people can quote the four values.  Far fewer know there are 12 principles sitting underneath, and fewer still could name one. Kate Megaw, Anu Smalley and Ryan Smith continue the Back-to-Basics series by working through the first six, one at a time, asking the same question of each: what wording would make this land for someone in marketing, finance, or HR?  Software becomes value, then the three of them discuss whether value is too vague.  Business people and developers becomes stakeholders and teams, because “I am not a developer” is a very easy way to leave a conversation.  The word project shows up twice and nobody minds anymore, which is a shift from five years ago. And face to face gets a defense from Alistair Cockburn that is worth quoting the next time someone tells you a remote team cannot do it.  The point is not a new set of principles. It is that people shut down when the words do not fit their world, so hand them words that do.

BONUS: Why Software Projects Fail When Everyone Keeps Quiet Software projects rarely fail because no one noticed the problem. More often, people see the missing database, the wrong assumptions, the broken process, or the weak product ownership, but the organization has trained them to stay quiet. In this BONUS episode, Mark Stringer, author of Delivering the Impossible, helps us understand how Scrum Masters can make reality visible again. The Problem Of Intention In Software Projects "You've got here a problem of intention, and you can't fix that by coming up with new, more magical marks on the page."   Mark starts with a story from the mid-1990s, before Agile was a common word in software teams. In a software development course, he heard the familiar promise: if only requirements could be captured with the right notation, the project would go correctly. His reaction was different. Software is not only a problem of documentation or process, it is a problem of translating intent into reality. That gap between marks on a page and what people actually need is where many projects begin to drift. Point Of View Can Make Smart People Miss Reality "If we see things in the wrong way, then point of view can take 80 IQ points off us."   Mark uses Alan Kay's idea that point of view is worth 80 IQ points to explain why good people can still make poor project decisions. A methodology can help, but only if it helps the team see what is actually happening. When the model becomes more important than reality, teams start defending the plan instead of learning from the system they are trying to change. Scrum Masters can help by asking what the current point of view hides, not only what it explains. The Swamp: Why Project Complexity Is Not On The Diagram "The fastest way between two points in a real organization is not necessarily a straight line."   In one banking project, Mark found two realities that had not survived the diagrams. First, a transaction database shown on every architecture diagram did not exist. Second, after six months of requirements work and several million pounds spent, a simple show and tell revealed that the design was organized around accounts when stakeholders needed it organized around people. The point was not that the team had failed to write enough requirements. The point was that the real environment was a swamp of legacy systems, power shifts, competing groups, regulations, users, and assumptions. You only discover that swamp by starting, showing real work, and letting stakeholders react. Agreed Activity: When The Rituals Keep Going But The Project Is Already Lost "Everybody knows why the project's failing. It's not a mystery at all."   Mark calls one common failure mode "agreed activity." The team keeps attending standups, planning meetings, status reviews, and retrospectives, even when people privately know the project is not going anywhere. Often they have tried to raise the real issue before and were punished for it. After that, silence becomes rational. The organization keeps reporting activity, expenditure, and compliance with the process, while the real blockers stay untouched. For Scrum Masters, this is a warning: ceremonies are useful only when they let reality enter the conversation. Product Ownership, Bad News, And The Message Leaders Send "The message that the development team hears is: don't rock the boat, just keep taking the money."   The Product Owner role can help break agreed activity, but only if the person has enough authority to make decisions and enough proximity to the team to learn. Mark describes two common anti-patterns: appointing someone junior who can be pushed around, or appointing someone so senior they have no time for the work. Worse, when someone points out a fundamental problem and gets metaphorically shot, the team learns the real rule: stay quiet. Leaders may think they are asking for positivity or commitment, but the team hears permission to cut corners, hide bad news, and treat spending as progress. Make Scrum A Hypothesis Testing Framework Again "That kind of unexpected feedback, that's the hope. That's the machine working."   Mark's practical advice is to keep the cadence, but make the meetings real. A show and tell should expose assumptions. A retrospective should make uncomfortable feedback usable. Scrum works best when it is treated as an empirical, hypothesis-testing framework, not a list of meetings to implement. Mark also points to user research as a way to extend learning back into the environment. Teams cannot guess how users will react, which buttons they will press, what they will ignore, or what market and organizational changes are shaping the work. They have to test, learn, and adjust. About Mark Stringer Mark Stringer is the author of Delivering the Impossible, a 2026 Apress book on better ways of seeing software project management. He has spent 30 years in software delivery as a developer, application researcher, and project manager, working with IBM, Xerox, and Cambridge University.   You can link with Mark Stringer on LinkedIn and follow Mark's writing at markstringer.github.io. You can find Delivering the Impossible on Amazon and Springer.

In this episode of the Comparative Agility Podcast, Dee Rhoda welcomes author, consultant, and transformation leader David Ramesh to explore why organizations can adopt Agile practices and still struggle to achieve meaningful alignment.Drawing from his book Finish the Journey and the development of the D*RAM Organizational Alignment Index, David explains why successful transformation requires more than standups, sprints, and maturity scores. He explores the balance between psychological safety, empowered teams, organizational direction, and a clear understanding of how individual contributions connect to the bigger picture.

BONUS: How Scrum Masters Turn AI Into a Thinking Partner, Not a Magic Answer Box Everybody talks about AI in theory. In this BONUS episode, Dave Westgarth talks about it in practice — the boring, everyday ways a Scrum Master and Agile Coach actually puts AI to work. From t-shirt sizing to sprint reports to a self-coded Monte Carlo forecaster, Dave shares what works, what doesn't, and the one mindset shift that separates people who get value from AI from those who just generate more noise. From "Magic Answer Box" to Personalised Partner "Instead of taking it as a magic answer box, using it as a personalised partner to work through problems, look at your ideas, and really hold them in the cold light of day before proposing things."   Dave came into agile from a development background, moved through project delivery, and had already worked at AI and ML companies long before ChatGPT made the technology personal and accessible. Like most people, he first met these tools as a "magic answer box" — ask a question, get an answer, run with it. The real shift came when he stopped optimizing for output and started using AI to drive better outcomes: ping the model, get a response, then interrogate it, refine the thinking, and go around again. The value isn't the first answer. It's the conversation that sharpens your own reasoning. These Tools Aren't Neutral — So Corner Them Into Being a Critic "If you ask it to be punishing, negative, and brutal, it gives you a lot more relevant feedback."   One of Dave's sharpest points: AI tools are not neutral guides. Because of their system prompts and the incentives baked in by the providers, they're relentlessly positive — they want to affirm you and keep you around, a little like social media. That makes them weak for anything where you need honest pushback: personas, user stories, feedback on ideas. Dave's fix is to flip it on its head. Rather than asking "is this any good?" (which reliably earns an "8 out of 10, but to make it a 10…"), he tells the model to be as harsh and brutal as it can and really try to punish the idea. You don't want a partner that always agrees with you — you want one that pinpoints the areas you haven't thought about. The First Real Time-Saver: Reports, and the Themes You Missed "Are there any themes that have emerged over the last 4 weeks that I might have missed in this latest deck?"   The first thing that stopped feeling like a party trick was the one we all know: project documentation and reporting — sprint reports, status updates, review decks. Instead of letting AI invent the structure, Dave feeds it his own structure plus Teams recordings, notes, and existing docs, and lets it populate the format he already uses. The trick that goes a level deeper: after several sprints, feed all the AI-assisted reports back in and ask what themes have emerged across the last four weeks that this latest deck might have missed. Again, it stops being an answer box and becomes a partner and critic. AI Is Part of the Job Now — Like Spreadsheets Once Were "The way to get ahead now is figure out how to use it as effectively as you can in your role."   Dave sees the early resistance movement against AI as a false economy. For delivery professionals — project managers, Scrum Masters, agile coaches — knowing how to use these tools well is fast becoming a core expectation, not a nice-to-have. Vasco draws the parallel to spreadsheets: once dismissed as too complicated and "not my kind of thing," until people started building real forecasting and capacity models with them and the work changed. AI is on the same arc — still a little mystical today, genuinely useful tomorrow, and eventually just another tool in the box. A Week With AI in the Loop "The power that these prompt-to-product tools give you to create these hyper-personalized tools that make you more effective is, in a lot of ways, magic."   Dave walked through what his week actually looks like with AI in the loop:   Monday primer: a scheduled ChatGPT task emails him a scene-set every Monday — last week's plan and top priorities — so he isn't spending the first half hour reconstructing where things stood. Priority calls: which items are the toughest, where the quick wins are, where he can get early traction, and where risks might be emerging that he can squash early. Everyday comms: drafting the bones of emails, pings, and project updates so he spends almost no time formatting. Prompt-to-product tools: using Base44, Lovable, and Replit to build his own tools — including a Monte Carlo forecaster that takes his team's sprint throughput and projects the remaining backlog, replacing an ugly spreadsheet with a clean web app. He also builds AI-powered widgets in Miro for retrospectives, mood check-ins, and planning poker.   The theme running through all of it: hyper-personalized tooling, shaped by your team and your own skills, rather than one-size-fits-all software. The Myth That AI Makes Scrum Masters Worse "I can't see any role of a knowledge worker where having an LLM at your disposal makes you less capable, less knowledgeable, less skilled than someone that doesn't."   Dave sees the same adoption spectrum among developers and Scrum Masters — from "I'll never touch it" to "I'll never write code by hand again." And he pushes back hard on an emerging prejudice that echoes the old "technical Scrum Masters are worse" debate: the idea that Scrum Masters who use AI are somehow weaker. Used well, AI lets you elevate your strengths and cover your gaps — a people-centered Scrum Master can become far more technical, and a technical one far more people-centered, each with a trusted teaching guide right there. The key competency isn't avoidance; it's discernment about when to reach for the tool and when not to. From More Output to Better Outcomes "The bottleneck has never really been typing code. The bottleneck has been understanding the problems and the customers well enough to define a solution that fixes them."   Dave's clearest reframe: AI is driving the price of output down. When volume is easy — more features, more emails, more documents on demand — churning out more of it stops being a differentiator, because everyone can do it. What matters is deciding which problems are worth solving and finding the most effective solution. Experienced agile professionals have always known the real bottleneck was understanding the customer well enough to define the right solution, not the typing. AI just exposes that in a much starker way: there's nowhere left to hide behind sheer volume. What to Pay Attention To — and a Monday Experiment "It can do a lot of that manual, low-thinking, high-effort work to free you up to do more of the really impactful stuff."   For Scrum Masters being told to "adopt AI," Dave's advice is to let it take the joyless work — the end-of-sprint collateral, the Jira monitoring, the reports and charts — so you can spend your time on the coaching, the strategic thinking, and the organizational-level impact that's harder to reach when you're buried in tactical chores. His concrete Monday-morning experiment: take the two or three prioritized actions from your next retrospective, bring them to ChatGPT or Claude, and ask, "which of these could you really help me with, and how could you help me move the needle?" Start a conversation. You don't have to accept its answers — the point is to sharpen your own thinking about where you can add the most value next sprint. Developing "Taste" With AI "One element of taste is being able to judge it fairly harshly — getting through the beige as quickly as you can to find the little nuggets and gems."   Both Dave and Vasco land on the same skill for the year ahead: taste. These tools produce a lot of text, and not all of it is useful. Vasco shares his own aha moment — asking for ideas, getting the obvious ones, then repeating "give me more, don't repeat any" until the model finally surfaced something genuinely unexpected. That simple move turns AI into an engine for exploring the solution space until something clicks. The competency to build is the ability to move through the beige quickly and recognize the gems that materially change what you do next.   About Dave Westgarth   Dave Westgarth is a product and Agile practitioner exploring how AI transforms product development, experimentation, and team workflows. He shares practical insights on leveraging tools to accelerate value delivery and innovation.   You can link with Dave Westgarth on LinkedIn and find him in the Miro community and on Miroverse.

BONUS: How AI Took the Boring Out of Agile Coaching—Where Scrum Masters Should Actually Start, With Michael Dougherty Today we speak with Michael Dougherty — "Agile Mike" — about how a 30-year veteran of solution development and product leadership made AI a working part of his Agile coaching practice. Michael walks us through the journey from early ChatGPT curiosity, to documentation as the first real win, to the personal-passion project that built his comfort with the tools, and finally to where every Scrum Master should start: the retrospective. From Curiosity to Toolbox: A Slow Burn That Started With User Stories "I tried, and I thought it sucked at that. I'd rather write this by hand."   Michael's AI journey started in late 2022 with ChatGPT — like most coaches, he tried to make it write user stories and acceptance criteria. It didn't work. The output wasn't usable, and he went back to writing them by hand. What looks like a failure was actually the first lesson: not every coaching task is a good fit for AI, and the way to find out is to try. He kept experimenting in the background through 2023 and 2024 — Claude, Grok, Perplexity — while keeping personal use and business use cleanly separated. The real shift came at the Department of Homeland Security, where he sat alongside ex-Googlers, ex-OpenAI people, and an Anthropic alumnus on the team building DHS's internal chatbot. Watching what AI could do inside a heavily-protected enterprise environment changed his frame: this wasn't a productivity hack anymore, it was infrastructure. The Boring, Tedious, Now Quicker: Documentation as the First Real Win "AI has taken all those boring, tedious tasks and made them quicker, more valuable, and more fun to boot."   The first AI practice that stuck was documentation — the part of Agile coaching nobody enjoys but every client demands. Michael had spent years writing SDLC docs from blank pages, and his co-author on Shift: From Product to People used to look at empty docs and ask for help getting started. AI removed that blank-page problem. He'd give the model the team context, the client's documentation requirements, and a template — and get a draft to edit. He stayed in the loop as the human, bringing context, judgment, and final shape, but he no longer started from zero. The same shift happened with presentations: instead of fighting PowerPoint spacing, he tells the AI to drop content into a template and gets back a formatted deck. Small tasks, but multiplied across a coaching week, they bought back real time. The Personal Project Trick: Find Something You Love First "Find something you have a passion with, something you really enjoy. That made me feel comfortable with AI so I could do more."   Michael's strongest advice for coaches who feel intimidated by AI isn't to start at work — it's to build something for yourself, in a domain you care about. His own example: the Nordic Metal Tour Tracker, a personal AI agent for tracking heavy metal bands across Northern Europe (and Spain and Portugal). It plays music. It maps tours by country. It exists purely because he loves heavy metal. The trick isn't the tool — it's that working on something he actually cared about removed the fear and built the muscle memory. Once the comfort was there, transferring it to work became a small step instead of a leap. He references the rundown AI as a daily input that keeps him aware of how others — even people in their 80s — are using AI for everything from gardening to balanced school lunches. A Week With Preppy Paul: Agents, Connectors, and the End of Inbox Drudgery "Preppy Paul gives me a list of all my meetings today and the top three items I should have on each one — based on my notes, my email, my calendar."   Michael's current weekly routine looks nothing like his Agile coaching week from three years ago. He works at Zion Cloud Solutions as a Tier 1 Google AI partner, splitting time across three roles: about 20–30% traditional Agile project management (coaching a Scrum Master on a state of Illinois project), and the rest as an AI Growth Engineer and AI delivery lead on short 4–6 week projects with 3–5 person teams. The backbone is Google Gemini Enterprise — a platform that lets him run Claude, ChatGPT, or any major model behind enterprise protection (Model Armor, the SAIF framework). Inside it, connectors pull in Gmail, Outlook, Calendar, Confluence, Jira, Slack, Teams, monday.com, and thousands of other tools — each agent inherits only the permissions the user already has. A few practical patterns he runs every week:   Preppy Paul — an agent that prepares him for the day's meetings, pulling top topics per meeting from his notes, email, and calendar. Meeting-to-email — AI records and summarises every meeting, and he asks the agent to draft updates to specific team members directly from the summary. LinkedIn drafts in his voice — hashtags, formatting, and tone all match his style; he edits lightly and posts.   The pattern across all of these: the agent isn't replacing the work. It's removing the friction between the meeting and the next conversation. The Retrospective: The Best Place for Every Scrum Master to Start "Don't have it be the same darn Jira spreadsheet of the same darn three questions every time. Go to AI and eat your heart out with it."   When pushed for one thing a Scrum Master could try tomorrow morning, Michael was clear: the retrospective. It's the one Scrum event where creativity is usually welcome, where format experimentation has a low cost, and where teams are already expecting something new. Ask AI for retrospective formats that fit the team's current situation — review five or ten options, pick one, run it. The signal you watch for within a week is double: how many improvements the team generated, and how many of them actually got done. The simpler signal is the team's reaction. If at the end someone says "that was fun" — and then you tell them you used AI to design the format — you've shown the team what AI is good for without a single slide or framework. It's the smallest possible experiment with the largest possible upside. Experiment Like a Scientist, Not a Spectator "Don't be afraid of it. Try whatever you can with it. Have the viewpoint of a scientist."   The trap Michael sees most coaches falling into is curiosity without commitment — reading about AI, watching demos, talking about it, but never building anything. His framing is the opposite: be a scientist. Run experiments. Some will fail (his user-story attempt did). Some will quietly become essential (documentation did). The way to find out which is which is to keep trying, in low-stakes contexts, with both personal projects and small work experiments. The coaches who'll be useful to their teams in 18 months aren't the ones who can describe AI accurately — they're the ones who've built enough small things to know what AI is bad at, what it's surprisingly good at, and where the human in the loop has to stay.   About Michael Dougherty   "Agile Mike" has over 30 years of experience with solution development and product leadership, working in nearly every IT role that exists and literally hundreds of companies during his career. Michael has taught multiple Agile courses to over 1000 people, spoken at multiple events and podcasts, written dozens of blogs, and has been recently serving the US Government. He is the other co-author of Shift: From Product to People.   You can link with Michael Dougherty on LinkedIn and find more about his work at shiftingpeople.com and AP8XGlobal.com.

Why AI Isn’t Making Companies Faster Why AI isn’t making companies faster? Common question I get these days, and the answer isn’t that mysterious. Everybody bought the tools, and ran the pilots, but nothing sped up. That doesn’t mean the money was wasted, and it doesn’t mean AI is a fraud. AI is an amplifier. What it amplified is a problem we had ten years ago and still haven’t addressed. The gap between a decision and a customer There’s a lag between the moment an executive team decides something and the moment a customer actually feels it…the moment it converts to revenue, or to something valuable. So ask yourself this question – “When did your company last make a real decision? And how long before anyone outside the building noticed?” Most leaders can’t answer that. That’s the whole problem, and it’s the reason AI isn’t making companies faster no matter how much they’re investing right now. It was never the technology Agile is supposedly finished. Has been for a few years now. And yet…lack of agility still shows up in the top five concerns CEOs report every year. They don’t call it agile. They call it speed-to-market, nimbleness, adaptability…the ability to respond when the market moves. Meanwhile every organization I know is being asked to do the impossible. Extract more value from fewer people. Make cuts where no cuts remain. Faster and cheaper while somehow getting better. That runs straight into what I learned in my project management days — the holy triangle of budget, time and scope. You don’t get all three. And you certainly don’t cut one and keep quality where it was. The practical maximum Here’s where it actually stops. Here’s why AI isn’t making companies faster. Resistance to change. Risk aversion. No autonomy. Nobody is allowed to make the call. Fear. Those human factors combine into a practical maximum, and no amount of technology can help you move past it. Give someone a goal tied to their job, their pay and their longevity, and then deny them the authority to make trade-offs, to negotiate, to prioritize. They disengage. They learn to be helpless. Losing control over your own destiny is what makes folks check out, and it’s happening everywhere right now. And…nobody is doing a good job of addressing it, and it’s costing companies. Pushing harder doesn’t shrink the lag. The people side of what we do was never ready for the speed of the technology we already had five years ago, and it’s no more ready today, because we haven’t changed anything. That’s the honest answer to why AI isn’t making companies faster. What leaders actually control A large part of this has nothing to do with the teams. It’s the voice of the leader. The answer is not making things sound more urgent. Pressing harder won’t help. Communicating what’s being built, why it’s being built, and who it’s for directly to the crews responsible for doing it, rather than from a board deck or a shareholder report. Creating a better tolerance for small failures, and giving people the tools to minize risk…that’s how teams can claim the autonomy, the authority and the courage to move. Speed comes from putting the important things at the top of the pile and letting the rest wait. Not from sweating harder. Not outsized consequences. Because if teams don’t feel authorized to do what’s necessary, they won’t do it. And we’ll keep covering the failures with dashboards and nonsense metrics, which serves nobody. If the honest answer to how long before a customer felt it is embarrassingly long, then the change begins with you. Want to learn more about how you can capitalize on this trend and help companies deal with the disarray and fallout of unsupported AI investment? It might be time to start something of your own. Check out Forge Genesis – newest cohort starting September 2026. **FORGE GENESIS IS HERE** All the skills you need to stop relying on job postings and start enjoying the freedom of an Agile career on YOUR terms. First cohort starts in Q1 2026 https://learning.fusechamber.com/forge-genesis **THE ALL NEW FORGE LIGHTNING** 12 Weeks to elite leadership! https://learning.fusechamber.com/forge-lightning **CHECK OUT ALL MY PRODUCTS AND SERVICES HERE:** https://learning.fusechamber.com We’re also on YouTube! Follow the podcast, enjoy some panel/guest commentary, and get some quick tips and guidance from me: https://www.youtube.com/c/BadassAgilea ****** Follow The LinkedIn Page: https://www.linkedin.com/showcase/badass-agile ****** Our mission is to create an elite tribe of leaders who focus on who they need to become in order to lead and inspire, and to be the best agile podcast and resource for effective mindset and leadership game. Contact us (contact@badassagile.com) for elite-level performance and agile coaching, speaking engagements, team-level and executive mindset/agile training, and licensing options for modern, high-impact, bite-sized learning and educational content. If you liked this episode, you might also like… The Real AI Opportunity AI Agile Hype Creates a Leadership Trap

Bob and Josh take on expectation inflation, the widening gap between what executives believe AI can do and what your team can actually deliver. Bob tells the bourbon and cigar story about a date he was committed to before anyone asked him. Josh makes the case that pushing back and accelerating aren't a choice, they're both the job. They argue about the 80/20 split, land on why you should narrate your team's improvements instead of burying them, and name the 3 rooms every engineering leader needs to be in. 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!

Many Scrum Masters and Agile Coaches have been cut loose, organizations are changing how they deliver products and services, and AI has landed on top of both. Kate Megaw, Anu Smalley and Ryan Smith open a new Back to Basics series with the document that started all of it, the Manifesto for Agile Software Development. They start with the obvious question. If it was written for software, what word belongs there now? Ryan says iterative development. Anu says iterative fill in the blank, because coaching a leader is iterative too. Then they go to the four values and pick favorites, and pretty much land on the same pair. Individuals and interactions, and responding to change, come out as the bookends that give the middle two somewhere to stand. Meanwhile AI is quietly pulling attention back toward the tools on the right and working software and customer collaboration are where teams are slipping.  The close is the useful part. This is not a rulebook to recite at people. It is a short piece of text that gives a team permission to work better.

SpaceX officially announced Starbase Louisiana, and I break down why the site fits Starship's launch, landing, and orbital architecture so perfectly. I also look at the transition from Falcon to Starship, and the new launch vehicles on the verge of debut. This episode of Main Engine Cut Off is brought to you by 32 executive producers—Warren, Matt from Built, Theo and Violet, Tim Dodd (the Everyday Astronaut!), Natasha Tsakos, Lee, Donald, David, Matt, Joonas, Russell, Steve, Frank, Will and Lars from Agile, The Astrogators at SEE, Josh from Impulse, Fred, Joel, Kris, Pat, Joakim, Miles O'Brien, Stealth Julian, Jan, Ryan, and four anonymous—and hundreds of supporters. Topics SpaceX Launches New Era of Commercial Spaceflight with $100 Billion Louisiana Campus - Louisiana Economic Development SpaceX intends to invest up to $100 billion in massive Louisiana spaceport - Ars Technica Episode 245 - Polar Bears and Penguins (with Jonathan Goff and Mike Loucks) - Off-Nominal AAS Paper Review: RAAN Agnostic 3-Burn Departure Methodology for Deep Space Missions from LEO Depots (Part 1 of 2) | Selenian Boondocks AAS Paper Review: Practical Methodologies For Low Delta-V Penalty, On-Time Departures To Arbitrary Interplanetary Destinations From A Medium-Inclination Low-Earth Orbit Depot | Selenian Boondocks An Updated Propellant Depot Taxonomy Part V: Human Spaceflight Fixed Depots (Low-Orbit) | Selenian Boondocks SpaceX on X: Ship 40 Reaches Christmas Island Ship 40 arrives at Christmas Island, Plans Return to Starbase - NASASpaceflight SpaceX on X: Ship 41 Single-Engine Static Fire Ship 41 Completes Engine Testing Ahead of Flight 14 - NASASpaceflight Satellite operators are in panic mode due to a worsening launch crisis - Ars Technica Nova payload module, second stage, and Andromeda engine fit check - Stoke Space First three flight-one Zenith engines ready for acceptance testing - Stoke Space Rocket Lab Announces Second Quarter 2026 Financial Results: Posts Record Revenue and Record Backlog, Guides To Another Record Revenue Quarter in Q3 2026 - Rocket Lab Rocket Lab Unveils GHOST Deployable Launch System to Enable Responsive Space Missions Worldwide - Rocket Lab Firefly Aerospace Announces Second Quarter 2026 Financial Results With Record Revenue Of $117.7 Million, Up 659% Year-Over-Year - Firefly Aerospace Tank problem delays first RFA launch - SpaceNews Relativity Space engine integration milestone for Terran R first stage - NASASpaceflight The Show Like the show? Support the show on Patreon or Substack! Email your thoughts, comments, and questions to anthony@mainenginecutoff.com Follow @WeHaveMECO Follow @meco@spacey.space on Mastodon Listen to MECO Headlines Listen to Off-Nominal Join the Off-Nominal Discord Subscribe on Apple Podcasts, Overcast, Pocket Casts, Spotify, Google Play, Stitcher, TuneIn or elsewhere Subscribe to the Main Engine Cut Off Newsletter Artwork photo by Zhou Quan Work with me and my design and development agency: Pine Works

Arun Parameswaran: Product Owners Who Create Better Product Conversations in Scrum In this episode, we refer to Arun's AI prompt library for Scrum Masters and project managers. The Great Product Owner: Curiosity, Clear Direction, and Outcome Focus Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.   "A great PO doesn't only ask, did we deliver? They ask, do people communicate openly?" - Arun Parameswaran   Arun describes great Product Owners as collaborative, curious, and close enough to the team to understand how delivery really works. The best POs he worked with did more than check whether items were delivered. They asked whether knowledge was distributed, whether people communicated openly, and whether everyone had a chance to contribute. They gave the team clear product direction, supported prioritization, managed stakeholders, and stayed available when the team needed context. Arun emphasizes outcome focus: value for the customer expressed in a way the team can understand. A strong PO becomes the bridge in both directions, helping stakeholders understand the team and helping the team understand the customer.   Self-reflection Question: Does your Product Owner help the team understand customer value, or only the next ticket? The Bad Product Owner: Turning the Team Into a Ticket Factory 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 Scrum Master shouldn't just help the PO write better tickets. We should help create better product conversations." - Arun Parameswaran   The anti-pattern Arun warns about is the Product Owner as ticket distributor. Stakeholders ask for something, the PO turns it into a ticket, and the team delivers without understanding the problem, the outcome, or why the work matters. Over time, the team becomes a delivery factory, and Scrum starts to look like waterfall with smaller batches. Arun's coaching move is to shift the conversation away from "better tickets" and toward better product thinking. What problem are we solving for customers? What outcome do we expect? What should we prioritize? What can we say no to? For Scrum Masters, this means coaching the PO and the team to bring customer context, stakeholder feedback, and prioritization into the same conversation.   Self-reflection Question: What product conversation is your team avoiding by hiding behind ticket writing?   [The Scrum Master Toolbox Podcast Recommends]

In this tutorial, you will learn the absolute basics of Agile, building on your initial project management understanding to master the critical concepts and techniques you must look out for as you prepare for the PMP exam. We will break down the essential terminology and mindset shifts that make up half the test, giving you the exact blueprint you need to pass on your first try—so don't forget to like and subscribe for more PMP success strategies!

Andrew Jones returns to the show to catch up on the Chinese space industry—the landings of Zhuque-3 and Long March 10B first stages, Chang'e-7 and its delay, and more. This episode of Main Engine Cut Off is brought to you by 32 executive producers—Steve, Joakim, Ryan, Tim Dodd (the Everyday Astronaut!), Joonas, Josh from Impulse, Fred, Will and Lars from Agile, Miles O'Brien, Natasha Tsakos, Lee, Warren, Russell, Stealth Julian, Kris, The Astrogators at SEE, Frank, Matt from Built, Theo and Violet, Joel, Donald, Pat, David, Jan, Matt, and four anonymous—and hundreds of supporters. Topics China's Landspace recovers booster with second orbital launch of Zhuque-3 rocket - SpaceNews Landspace aims to refly recovered Zhuque-3 booster within six months - SpaceNews LandSpace's Zhuque-3 topples following milestone landing - NASASpaceFlight.com China becomes second country to recover orbital booster with Long March 10B - SpaceNews China lines up methalox Long March 10C as commercial workhorse after first booster recovery - SpaceNews Chinese Long March 7A rocket explodes shortly after liftoff - SpaceNews Long March 12 launches despite recent 7A failure, Long March 2C launches satellite for UAE - SpaceNews China delays Chang'e-7 lunar south pole landing mission launch - SpaceNews Long March 6C launches 7 satellites, Chang'e-7 rocket rolled back to assembly building - SpaceNews The Show Like the show? Support the show on Patreon or Substack! Email your thoughts, comments, and questions to anthony@mainenginecutoff.com Follow @WeHaveMECO Follow @meco@spacey.space on Mastodon Listen to MECO Headlines Listen to Off-Nominal Join the Off-Nominal Discord Subscribe on Apple Podcasts, Overcast, Pocket Casts, Spotify, Google Play, Stitcher, TuneIn or elsewhere Subscribe to the Main Engine Cut Off Newsletter Artwork photo by Zhou Quan Work with me and my design and development agency: Pine Works

Arun Parameswaran: Success for Scrum Masters Means Teams Ask Better Questions Without You 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.   "My goal isn't to become indispensable. My goal is to create a team that doesn't depend on me." - Arun Parameswaran   For Arun, Scrum Master success is not measured by how many meetings he runs or how often the team asks him for help. It is measured by the team's ability to solve problems without depending on him. If he has to remind everyone to update Jira, facilitate every difficult conversation, or resolve every obstacle, he is creating dependency. A healthier signal is when team members talk directly to each other: "This is blocked. Who can help me?" or "Let's finish this before starting something else." Arun compares the Scrum Master to a football coach watching the match from the side. The team needs space to play, make decisions, and learn. The Scrum Master still observes and coaches, but the goal is to intervene less often and more intentionally. As Vasco summarizes, this requires learning to wait before stepping in.   Self-reflection Question: What would your team do differently if you waited one more minute before intervening? Featured Retrospective Format for the Week: What? So What? Now What? Arun's favorite retrospective format is "What? So What? Now What?" because it moves the team from facts to meaning to action. "What happened?" helps the team describe reality. "So what?" asks why it matters. "Now what?" turns the discussion into a small experiment for the next sprint. Arun also avoids using the same format every time. He often shares the board two or three days before the retrospective so people can reflect before the meeting, add observations, and appreciate teammates. That preparation saves time in the session and makes space for a short fun activity before the team works through the real topics. His goal is simple: every retrospective should produce learning and at least one concrete experiment.   [The Scrum Master Toolbox Podcast Recommends]

Arun Parameswaran: Using Scrumban and WIP Limits to Help Agile Teams Find Focus 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 WIP limit helped the developers not context switch." - Arun Parameswaran   Arun brought a practical challenge to the Wednesday coaching conversation: a team doing both operations and development work needed more visibility and focus than their Scrum board was giving them. The trigger was context switching. Work stayed "in progress" even when blocked, people picked up new topics before finishing old ones, and stakeholders kept asking what was actually happening. Arun helped the team experiment with Scrumban, keeping useful Scrum events while adding a Kanban-style board and explicit WIP limits. The breakthrough was not just visualizing the work. It was helping the team own the limits. They created an "operator of the week," rotating the responsibility for watching WIP and calling out when the team was taking on too much. That small practice made focus a team responsibility instead of a Scrum Master lecture.   Self-reflection Question: Who owns your team's WIP limits in practice, not just on the board?   [The Scrum Master Toolbox Podcast Recommends]

Arun Parameswaran: How Powerful Questions Help Scrum Teams Handle Stakeholder Conflict 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.   "Sometimes the best thing a Scrum Master can give the team isn't the answer. It's a question." - Arun Parameswaran   Arun describes a team pattern many Scrum Masters recognize: stakeholders bypassing the Product Owner and going straight to developers with new requests after the sprint had already started. The developers wanted to help, so they accepted the interruptions. The result was context switching, broken priorities, and a quiet loss of focus. Arun worked with the customer team, Product Owner, and developers to create a simple agreement: new work had to come through the PO, be clarified, and be prioritized before it reached the team. That agreement gave developers permission to protect the sprint without turning every conversation into a personal conflict. Arun also shares how he handled the classic misunderstanding that "being Agile" means accepting every change immediately. For him, adaptability still needs timing, clarity, and shared agreements.   In this segment, we talk about the coaching stance and how Scrum Masters can use questions to help teams think together.   Self-reflection Question: What agreement would help your team protect focus without shutting stakeholders out? Featured Book of the Week: Coaching Agile Teams by Lyssa Adkins Arun recommends Coaching Agile Teams by Lyssa Adkins because it helped him move beyond ceremony facilitation. The book gave him a clearer picture of the Scrum Master as a coach for individuals, the team, and the wider organization. One question stayed with him: am I solving the problem for the team, or helping the team learn to solve it themselves? That shift changed how Arun worked. Instead of telling teams what to do, he began asking questions such as "What do you think is causing this?", "What options do we have?", and "What are we not seeing?" For Arun, the book is a practical reminder that coaching is not about leading people to your answer. It is about helping people think.   [The Scrum Master Toolbox Podcast Recommends]

In this episode of Making Risk Flow, host Juan de Castro brings together eight leaders from across insurance, technology, insurtech, and brokerage to explore how AI, operating model transformation, and modern technology architecture are reshaping the future of insurance.Ann Haug, David McMillan, Christian Stobbs, Kristoffer Lundberg, Greg Brown, Sam Lewis, Allison Hamilton, and Nick Zerbib examine why insurers need more than new technology to gain a competitive advantage. The discussion explores building operating models for scale, creating decision-led technology architectures, accelerating underwriting workflows, and using AI to augment human judgment rather than simply automate existing processes.The group also considers AI-driven claims transformation, intelligent submission routing, the future role of underwriters, customer obsession, and how brokers can prepare for growing market and private equity pressures. Together, these perspectives reveal how culture, technology, speed, and strategic clarity can help insurers become more agile, scalable, and resilient in an increasingly competitive market.Fan Mail: Got a challenge digitizing your intake? Share it with us, and we'll unpack solutions from our experience at Cytora.To receive a custom demo from Cytora, click here and use the code 'Making Risk Flow'.Our previous guests include: Bronek Masojada of PPL, Craig Knightly of Inigo, Andrew Horton of QBE Insurance, Simon McGinn of Allianz, Stephane Flaquet of Hiscox, Matthew Grant of InsTech, Paul Brand of Convex, Paolo Cuomo of Gallagher Re, and Thierry Daucourt of AXA.Check out the three most downloaded episodes:The Five Pillars of Data Analytics Strategy in Insurance | Craig Knightly, Inigo20 Years as CEO of Hiscox: Personal Reflections and the Evolution of PPL | Bronek MasojadaImplementing ESG in the Insurance and Underwriting Space | Simon Tighe, Chaucer, and Paul McCarney, Moody's

Public health agencies are being asked to do more with less while responding to rapidly changing health threats, technologies, and community needs. Danny Staley, ASTHO senior vice president of Public Health Practice and Programs, discusses how innovation and capacity building can help health departments adapt by identifying successful practices, scaling proven solutions, strengthening the workforce, and using data in new ways. He also explores how artificial intelligence could help public health professionals make sense of massive amounts of data and information, and how measuring the impact of new tools and strategies will be critical to demonstrating their value by 2029.ASTHO's Strategic Plan | ASTHOEquipping Community Health Workers to Address Alzheimer's Disease and Related Dementias in Their Communities | astho prodIt's not just a gut feeling: Foodborne illness outbreaks are especially bad this summer | CNN

Ever work on a team where there was one, maybe two people who could be counted on to drag a project across the finish line just before the stroke of 12:00? That’s what happens when you work at scale. People work hard, but the last thing they have time for is proper orchestration to help them land safely under pressure. Cutting people with an appropriate dialing back of scope makes the problem even worse. Dave Borzillo is a graduate of my Forge Genesis program. In the time we spent together, he advanced a business idea (or two), but he also conceived and wrote his latest book – “Sanity At Scale – How Engineering Leaders Move from Heroic Firefighting to Systemic Excellence”, now available on amazon.com or from his website, betterwaysofworking.com. Dave joins me for this one-on-one interview, where he reveals the dangers of heroic firefighting, why it can’t work at scale, and some of the strategies for ensuring your team doesn’t entrench these patterns. Make sure you grab this book – its no nonsense, crisp and useful for any team leader or agile practitioner! **FORGE GENESIS IS HERE** All the skills you need to stop relying on job postings and start enjoying the freedom of an Agile career on YOUR terms. First cohort starts in Q1 2026 https://learning.fusechamber.com/forge-genesis **THE ALL NEW FORGE LIGHTNING** 12 Weeks to elite leadership! https://learning.fusechamber.com/forge-lightning **CHECK OUT ALL MY PRODUCTS AND SERVICES HERE:** https://learning.fusechamber.com We’re also on YouTube! Follow the podcast, enjoy some panel/guest commentary, and get some quick tips and guidance from me: https://www.youtube.com/c/BadassAgilea ****** Follow The LinkedIn Page: https://www.linkedin.com/showcase/badass-agile ****** Our mission is to create an elite tribe of leaders who focus on who they need to become in order to lead and inspire, and to be the best agile podcast and resource for effective mindset and leadership game. Contact us (contact@badassagile.com) for elite-level performance and agile coaching, speaking engagements, team-level and executive mindset/agile training, and licensing options for modern, high-impact, bite-sized learning and educational content.

Arun Parameswaran: The Scrum Master Mistake of Fixing Trust With Process 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.   "Don't confuse activity with progress." - Arun Parameswaran   When Arun Parameswaran stepped into one of his first Scrum Master assignments, he joined a distributed team where everything looked normal from the outside. Meetings were happening, Jira was updated, and work appeared to be moving. Underneath that surface, knowledge was unevenly shared, communication between locations was weak, and trust was not yet strong enough for people to speak openly. Arun's first instinct was to add more structure: more meetings, more activities, more process. Looking back, he saw the real mistake. He was creating activity, not progress. The shift came when he stopped trying to provide answers and started listening through one-on-one conversations. He learned where people were struggling, what they expected from him, and what the team needed to own for itself. In this episode, Arun shares why Scrum Masters must understand people before changing the process, and why the best coaching often starts by asking better questions.   Self-reflection Question: Where are you adding process today because the real issue feels harder to talk about?   [The Scrum Master Toolbox Podcast Recommends]

This week, Ivy Slater, host of Her Success Story, chats with her guest, Victoria Strickland. The two discuss the evolving role of technology in healthcare, the importance of mentorship and sponsorship for women in tech, and the innovative work PwC is doing to help major healthcare organizations navigate complex business and technology transformations. In this episode, we discuss: How technology serves as the backbone for innovation and operational efficiency in healthcare, impacting everything from administrative processes to patient outcomes. What unique challenges and opportunities exist in integrating tech with healthcare, especially as new entrants continually reshape the field alongside legacy platform companies. Shifting from traditional healthcare roles to technology-driven careers can open new doors for impact, highlighted by the journey from pre-med aspirations to industry consultancy. Why it is vital to have women, and especially diverse voices, represented in tech leadership, particularly as AI and automation become more central to healthcare. How embracing continuous change—both personally and within companies—is essential in the rapidly evolving tech and healthcare landscape.   Victoria Strickland is a Director in PwC's Health Industries Advisory practice, where she has spent the last 14 years helping some of the nation's largest healthcare organizations navigate complex business and technology transformations. She specializes in payer modernization, healthcare operations, and technology-enabled transformation, with a particular passion for how AI and emerging technologies can reshape the future of care. An Agile-certified leader known for guiding organizations through complexity, Victoria has stood up and scaled enterprise Agile operating models, led Agile governance and delivery across 300+ person programs, and driven maturity across some of the most ambitious transformation efforts in the industry. She works shoulder-to-shoulder with executive teams to turn bold goals into practical, sustainable outcomes that improve both business performance and the experiences of the patients and members behind every system. Victoria's impact hasn't gone unnoticed: she was recognized by Women We Admire as one of The Rising Star Women Leaders in Healthcare for 2025, a nod to the fresh thinking and technical depth she brings to a field that's being rewritten by data and AI. Originally from Washington, DC, Victoria's passion for healthcare started early and led her to the University of Pennsylvania, where she earned her degree in Public Health with minors in Healthcare Management and Neuroscience. That blend of healthcare, business, and behavioral science still shapes how she leads and solves problems today, balancing strategy, technology, and the very human side of change. Outside of work, Victoria loves staying active, trying new things, and planning her next trip. A fun fact: she competed in the 2012 Olympic Trials for track, which explains why she's still just a little competitive. She's also a devoted travel enthusiast who proudly names her mom as her favorite travel partner. Together they've explored more than 25 countries across Southeast Asia, South America, and Europe. Website:https://www.pwc.com/us/en.html Social Media Links: https://www.linkedin.com/in/victoriastrickland/      

Today's guest is Dianne Kokotoff, Executive Director, Enterprise Solutions and Automation at Wellstar Health System. Founded in 1993, Wellstar is one of the largest nonprofit healthcare systems in the Southeast, serving communities across Georgia through more than 400 care locations, including 11 hospitals. With more than 35,000 team members, Wellstar provides comprehensive, patient-centered care across a wide range of specialties, while also investing in innovation, research, technology and community health.Dianne is an experienced technology executive with a strong track record across financial services and healthcare. She leads ServiceNow and Automation teams, driving IT operational excellence, platform strategy, governance and continuous improvement across ITSM, ITOM, ITBM and SecOps. Her expertise also spans Robotic Process Automation, Agile transformation, enterprise architecture, process improvement and requirements analysis, with a focus on delivering technology strategies aligned with business goals.In the episode, Dianne talks about:0:00 Her journey from military communications to pioneering ServiceNow leadership5:04 Transforming ServiceNow adoption across Wellstar Health System6:32 How strong processes and quality data drove ServiceNow success10:58 Expanding ServiceNow into an enterprise-wide transformation platform12:53 Getting stakeholder buy-in to drive successful technology implementations15:47 How her lean ServiceNow team delivers enterprise-scale success17:45 Expanding ServiceNow with AI agents and innovation

Listen and subscribe to Money Making Conversations on iHeartRadio, Apple Podcasts, Spotify, www.moneymakingconversations.com/subscribe/ or wherever you listen to podcasts. New Money Making Conversations episodes drop daily. I want to alert you, so you don’t miss out on expert analysis and insider perspectives from my guests who provide tips that can help you uplift the community, improve your financial planning, motivation, or advice on how to be a successful entrepreneur. Keep winning! Two-time Emmy and Three-time NAACP Image Award-winning, television Executive Producer Rushion McDonald interviewed Everett Swain.

Listen and subscribe to Money Making Conversations on iHeartRadio, Apple Podcasts, Spotify, www.moneymakingconversations.com/subscribe/ or wherever you listen to podcasts. New Money Making Conversations episodes drop daily. I want to alert you, so you don’t miss out on expert analysis and insider perspectives from my guests who provide tips that can help you uplift the community, improve your financial planning, motivation, or advice on how to be a successful entrepreneur. Keep winning! Two-time Emmy and Three-time NAACP Image Award-winning, television Executive Producer Rushion McDonald interviewed Everett Swain.

Joshua McDonald: Product Owners Earn Team Loyalty By Showing Up, Learning, And Deciding The Great Product Owner: Vulnerable Enough To Learn The Technical Details 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've seen developers be fiercely loyal to their product owner who makes that type of effort." - Joshua McDonald   Joshua describes the great Product Owner as someone who connects with the team even without a technical background. They do not pretend to know everything. Instead, they get into refinement with curiosity, write stories with the developers, and say, "I think this is what needs to be done, but correct me if I'm wrong." That vulnerability creates a strong partnership. Developers see the effort and often respond with loyalty, to the point where they may refuse to continue important discussions without the Product Owner in the room. The lesson is useful for Scrum Masters coaching Product Owners: deep technical expertise is not the entry ticket. Presence, curiosity, and the willingness to learn with the team are what create trust.   Self-reflection Question: How does your Product Owner show the team they are willing to learn the product with them? The Bad Product Owner: The Dependent Note Taker 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.   "Sometimes you ask the product owner, you're the bus driver, where do you want us to go? And they say, let me go talk with the product manager." - Joshua McDonald   The Product Owner anti-pattern Joshua highlights is the dependent PO: the person who shows up as a note taker rather than a decision maker. This often happens when a Product Manager sits behind the PO and every decision has to be checked elsewhere. The day-to-day symptoms are easy to spot: camera off, muted, disconnected, asking people to repeat questions, missing meetings they scheduled themselves, and leaving the team without timely answers. Joshua's coaching response starts with one-on-ones, support, and curiosity. He asks how they are doing, what support they need, and what signals would help the team see they are engaged. When the product feels too technical, he sits beside them, learns with them, and helps them build confidence instead of leaving them exposed.   Self-reflection Question: Where is your Product Owner dependent on someone else for decisions, and how is that affecting the team?   [The Scrum Master Toolbox Podcast Recommends]

Joshua McDonald: Scrum Master Success Means People Feel Heard, Respected, And Safe To Speak Up 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 hope you can feel heard and respected at the end of the day." - Joshua McDonald   Joshua defines Scrum Master success through the team's comfort with self-organization, respectful pushback, and asking for help when they do not know what they do not know. For him, a successful team is not drama-free because nothing hard happens. It is low-drama because people can raise problems without fear, communicate openly, and keep moving forward even on bumpy roads. Joshua keeps himself honest by reviewing retrospective notes, one-on-one notes, and the commitments he made to follow up. He keeps a running to-do list from Slack messages, meetings, and team conversations so feedback does not disappear after someone shares it. Periodically, he brings past retrospectives back to the team and asks what they accomplished, what changed, and whether anything fell through. That ledger matters because Scrum Masters work through people. If people feel heard and respected, they are more likely to keep working with you, regardless of your title.   Self-reflection Question: What system do you use to make sure team feedback turns into visible follow-up? Featured Retrospective Format for the Week: Personalized AI-Themed Retrospectives Joshua's favorite retrospective format is never using the same format twice. He noticed teams getting bored and agitated when the same sailboat or standard board appeared every sprint. His answer was to personalize retrospectives around team members' interests: a BMW theme for a developer who liked cars, a beach theme after someone's vacation, or a TV-show theme tied to a person's hobby. He uses tools like Mural, Zoom whiteboards, Microsoft Teams, and AI-generated visual themes to make each retro feel like it was designed for someone in the team. The point is not decoration. The point is listening. When people recognize their interests in the retro, they feel seen as people before they reflect on the work.   [The Scrum Master Toolbox Podcast Recommends]

Joshua McDonald: Using Cycle Time As A Storyteller, Not A Scorecard In 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.   "Metrics is not about telling people do better. It's about telling that story." - Joshua McDonald   Joshua brings cycle time as his biggest current coaching challenge. The problem is familiar: when a Scrum Master points to a story with high cycle time, developers can feel blamed, even when the intent is learning. Joshua reframes the metric as a storyteller. Instead of asking why someone took too long, he asks what journey the story went through, where it changed hands, where it waited, and what the team now knows that it did not know at the start. He also describes practical tactics: warn people in advance before discussing specific stories, keep the language gentle, avoid forcing people to explain themselves publicly, and sometimes skip the metric conversation entirely when the team needs encouragement more than analysis. Metrics matter because they move coaching away from gut feeling and toward observable patterns. Used well, cycle time becomes a barometer for stress, bottlenecks, missing product owner review, and places where the team needs support.   Self-reflection Question: How do you introduce metrics so the team becomes curious about the system instead of defensive about individual performance?   [The Scrum Master Toolbox Podcast Recommends]

Joshua McDonald: The Distributed Agile Team That Hid Problems Behind Follow-Up Stories 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.   "They started to separate and call each other out, which is definitely not Agile." - Joshua McDonald   Joshua shares the story of a 17-person distributed team spread across time zones, cultures, and communication styles. Some team members were direct and ready to challenge problems in public. Others preferred quieter, one-on-one conversations. Over time, those differences created a blame environment where people stopped asking for help and started hiding problems. Long-running work was closed and replaced with follow-up stories, then part two, then part three, until the real issue disappeared under Jira housekeeping. The result was not better flow, but delayed learning, missed upskilling opportunities, and a stressful team environment where quieter people stopped speaking in standups and retrospectives. Joshua explains what he would do differently now: split the team by communication patterns, listen to what each group needs, act as a mediator, and only bring the whole group together once people feel heard.   In this segment, we talk about different communication styles.   Self-reflection Question: What signals tell you that people are hiding problems because the team environment does not feel safe enough? Featured Book of the Week: Never Eat Alone by Keith Ferrazzi Joshua recommends Never Eat Alone by Keith Ferrazzi because it reframed networking as a relationship practice, not a transaction. The book helped him see that staying connected with people creates learning, support, and a safety net over time. He also mentions the Bible as a daily source for reflecting on respect, peace, and conflict resolution, especially because Scrum Masters often need more than process knowledge to help teams work well together. For Joshua, both recommendations point to the same deeper idea: our work improves when we treat relationships as something to maintain before we urgently need them.   [The Scrum Master Toolbox Podcast Recommends]

Jose Martinez, Global Chief Data Officer at Coca-Cola FEMSA, says customers don't experience an AI system's mistake as a data problem — they experience it as a company that doesn't know them. Recorded live at Ai4 at the Venetian in Las Vegas, he and Greg Kihlström get into what has to be true underneath before AI systems can act on your data at all.A data foundation AI can act on is a different thing from one that produces reports. Martinez on what actually separates the two, and why a company can have working dashboards and still not have the foundation an automated decision requires.Across many markets and millions of points of sale, consistency is the constraint — not speed. Agility isn't really about moving faster; it's being able to change repeatedly without the company starting to contradict itself. Martinez on what keeps decisions consistent as more of them get automated.Foundational data work has to be justified without a campaign-shaped payoff. How to make the case internally when the return doesn't show up as a lift number, and what enterprise leaders can use instead.About Jose MartinezJose De Jesus Martinez Camara, MS, PMP, is an innovative executive currently serving as the Global Chief Data Officer at Coca-Cola FEMSA. Previously, he served as the Americas Head of Data & Analytics at Nissan North America for Finance, with a dual track record as well as Chief Information Officer.With over 20 years of experience driving organizational excellence, Jose specializes in managing complex IT portfolios and commercializing technology products across the consumer goods, automotive, finance, entertainment, and consultancy sectors. He is a visionary professional known for aligning technology initiatives with long-term business objectives and fostering Agile and DevOps cultures.In his current global role at Coca-Cola FEMSA, he leads the enterprise data strategy, governance, and advanced analytics capabilities to drive digital transformation and value creation at scale. Prior to this, as Americas Head of Data & Analytics for Nissan Finance, Jose oversaw the data landscape across Mexico, Canada, and the United States, ensuring strategic alignment with corporate needs. Jose Martinez on LinkedIn---------- Resources ----------Coca-Cola FEMSAThe Agile Brand podcast is brought to you by TEKsystems.We're proud to be a media partner for #MAICON26 - Oct. 13-15! Learn how AI can power your marketing and business and help you grow smarter. Use code AGILE150 to save!Reach your customers with Reddit. Spend $500 in ad spend, get $500 back in ad credit!Chaser is the only Slack-native project management platform that helps teams turn messages into tracked tasks, automate follow-ups, and maintain team-wide visibility, without adopting another tool. Now integrated with Claude and other GenAI tools. Learn more at trychaser.com and use code AGILEBRAND for a 3-month free trial (normal trial is 14 days).The most influential minds in software, AI, and engineering leadership will be at WeAreDevelopers World Congress North America, September 23-25 in San Jose.Start building your own apps with Replit and get $20 off.Enjoyed the show? Tell us more at and give us a rating so others can find the show.Connect with Greg on LinkedInDon't miss a thing: get the latest episodes, sign up for our newsletter and more.Check out The Agile Brand Guide website with articles, insights, and Martechipedia, the wiki for marketing technology.The Agile Brand is produced by Missing Link—a Latina-owned strategy-driven, creatively fueled production co-op. From ideation to creation, they craft human connections through intelligent, engaging and informative content. Hosted on Acast. See acast.com/privacy for more information.