Podcasts about Agile

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.

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]

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

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]

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]

Joshua McDonald: When Your Agile Enthusiasm Creates Resistance, Start With Trust 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 assume they're as enthusiastic about Agile and Scrum as you are." - Joshua McDonald   Joshua McDonald joins us from the USA with a failure story many Scrum Masters will recognize: stepping into a team and assuming the role, the expectations, and the Agile conversation were already understood. The team had worked with a hands-off Scrum Master before, so Joshua's attempts to facilitate events, talk about metrics, and bring more structure were received as interference. The pushback grew so strong he sensed people were talking to his manager about removing him. The turning point came when Joshua stopped leading with Scrum language and started rebuilding social equity through one-on-ones. He asked what he could have done differently, acted on the feedback, and reminded himself and the team to assume positive intent. His lesson is direct: when we join a new team, trust is the work before the work. Go slow, understand how people operate, and bring suggestions through relationships before bringing them to the whole room.   Self-reflection Question: When you join a new team, what do you do first to understand their relationship with Scrum before you suggest changes?   [The Scrum Master Toolbox Podcast Recommends]

Bob sings The Gambler and turns it into a leadership question. He quit a job after 4 days when he learned he'd been hired as the ax man. Josh called off an office redesign mid-move. A million-dollar pod experiment survived one day. Hold, fold, walk away, run, and the cost of doing none of them. 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!

Wasim Osman: The Agile Product Owner Who Runs Two Quarters Ahead of 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. The Great Product Owner: The Absolute User Who Works Two Quarters Ahead 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 Product Owner needs to be the absolute user of the software—the user's journey so well defined in their mind that every engineer's question already has an answer, with context." - Wasim Osman   Wasim's best Product Owner works ahead of the team without doing the team's work. Their product roadmap is well-defined at least two quarters ahead of the development cycle, so nobody is panicking against tomorrow's deadline. Designers and product people work on concepts months before development starts, which gives them room to show early ideas to engineers and gather feedback while there's still time to change course. Crucially, this PO is the absolute user of the software—so completely inside the user's journey that when an engineer asks "how does this connect to that module?", the answer is ready, with context. Wasim connects this to how his team uses AI today: the PO can run ahead, spin up prototypes, and iterate on the ideas without burdening the team with building throwaway work—while staying the voice of the customer.   Self-reflection Question: How far ahead of your team is your Product Owner really working—and could they answer an engineer's design question today without going back to the drawing board? The Bad Product Owner: When Optimism Overrides the Data 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 were optimistic without any data. We had the data—they were just being wishful." - Wasim Osman   The worst anti-pattern Wasim has seen is the Product Owner whose optimism overrides the evidence. In one company, a customer asked for a delivery estimate, and the product team promised an aggressive date—"optimistic without any data," even though the data existed. When the engineering team sat down with the numbers, it was obvious the date was impossible, but that gap never reached the customer. The product team stayed disconnected from both the engineers and the customer, so expectations kept drifting from reality. Wasim, who held the data, finally bridged the two and told the product team the real timeline was several months later. They "lost their minds"—but by then it was too late to renegotiate gracefully. The deeper anti-pattern: features handed down without enough depth, so the moment engineering hits real questions mid-development, the PO panics and rushes back to the drawing board while development is already in motion. As Wasim says, "optimism just took over too much."   Self-reflection Question: When was the last time optimism—not evidence—set a delivery date on your team, and who had the data that should have been in the room?   [The Scrum Master Toolbox Podcast Recommends]

Wasim Osman: The Scrum Master as a Router, Redefining Success Through Efficient Communication 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 big part of the Scrum Master role is to work as a router—handling a lot of conversations with a lot of different devices, even though the internet is coming in through one cable." - Wasim Osman   For Wasim, success as a Scrum Master looks like a router in a house: many conversations, many stakeholders, all flowing through one point that has to prioritize, schedule, and stay on time. If the router slows down, everything downstream stalls—and the Scrum Master becomes the blocker. Early in his career he was overwhelmed juggling three or four engineering teams, so he built himself a personal Kanban board and ran his own quick standup every morning and again at the end of the day, just to see what moved, what stalled, and why. Getting organized with himself is when the work started to feel satisfying, because he stopped being the bottleneck. But he's honest about the hardest part: people rarely tell you to your face when you're slowing them down. The feedback is already there—you're just not hearing it. So you have to ask for it, react well when you get it (or people stop offering), and sometimes name the awkward truth first: "Our meetings used to be better—what happened?" That opening gives everyone permission to be honest.   Self-reflection Question: If you're the "router" for your teams, where are you quietly becoming the bottleneck—and who would tell you if you were? Featured Retrospective Format for the Week: What Went Well / What Went Wrong / Outliers + Open Discussion Wasim's go-to retrospective is deliberately bare-bones: what went well, what went wrong, and—the part that makes it his own—what were the outliers, followed by open discussion. He added the "outliers" question years ago after noticing that team members kept raising points that weren't clearly good or bad, but were still significant enough to discuss. Outliers give people "a bucket for sharing information that has no polarity"—an early signal about the future, a quiet concern, something that doesn't fit the other two columns but matters. He sometimes pairs it with lightweight metrics: sprint completion rate, or tickets that sat too long in review or QA, surfacing patterns the team wouldn't otherwise notice.   Self-reflection Question: What "outlier" signal has your team been sitting on—neither a win nor a problem yet—that deserves an open conversation before it becomes one?   [The Scrum Master Toolbox Podcast Recommends]

What does an AI-native CI look like? The Semaphore team joins me to talk about their focus on making your agent harness the gateway to testing, fixing, and deploying your code.Video podcast version here: https://youtu.be/HzXAdtVrW70★Show Links★Semaphore https://semaphore.io/Semaphore open source https://github.com/semaphoreio/semaphoreSLSA Security Checklist https://slsa.dev/Creators & Guests Marcos Filipe - Guest Cristi Cotovan - Editor Bret Fisher - Host Beth Fisher - Producer Marko Gaćeša - Guest (00:00) - Introduction (00:29) - AI Native CI Vision (04:54) - Bret's Update (09:03) - Semaphore AI Journey (22:39) - Open Source Platform Shift (37:28) - Plugins CLI MCP Skills (43:11) - Work Until CI Is Green (45:42) - Test Boxes and Agentic CI Loop (57:39) - Sandboxing and Least Privilege (01:10:12) - Roadmap SLSA and Getting Started

https://hpmexam.comAUG 22ND 2026 - RAPID BOOTCAMP

The Wall Street Journal reported that German startup Agile Robots expects to double revenue in 2026, signaling continued automation investment by manufacturers. Germany's robotics adoption and broader demand across automotive, electronics, and logistics support this momentum. Buyers are enforcing pilot phases, measuring cycle time and first pass yield, and targeting payback within one and a half to three years. Financing models are splitting between capex purchases and robotics as a service, which affects vendors' revenue recognition and cash flow. Component lead times, integrator capacity, safety, and cybersecurity remain gating factors. Founders should prepare for tighter buyer expectations on deployment speed, uptime, standardized cells, and remote support as automation budgets expand.Learn more on this news by visiting us at: https://greyjournal.net/news/ Hosted on Acast. See acast.com/privacy for more information.

Wasim Osman: How Agile Teams Can Start Adopting AI in Software Development Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.   "It's like my own software has a voice now. It's telling me—okay, you're going to build me like this? Have you considered this?" - Wasim Osman   Wasim's biggest current challenge is one nearly every team shares: how AI is reshaping software development. He sees a clear split—developers rapidly adopting AI-driven development, and others "not downright rejecting it, but still taking their time." His warning is blunt: even when AI hallucinates and generates garbage code, it lets you deliver an order of magnitude faster, and the quality is only going to improve. The early adopters are heading somewhere the late adopters won't be able to reach. In practice, the resistance shows up as questions no one can answer: if I used to get every requirement nailed down before writing code by hand, what do I do with AI—just ask it for a one-liner and hope? Leadership often can't help, because they lack AI experience themselves. At Orkestra SCS, the head of engineering did holistic research into how companies (like AWS, with its AI-Driven Development Lifecycle) are reshaping the process, documented it, and shared it with every team. Feedback sessions and hands-on experiments followed, until they built a tailored version that fit how they actually work. The mindset shift that unlocked it: treat AI as a partner. Wasim describes his software "having a voice"—asking him questions he'd never think of, the way a pair-programming partner would, so the team explores the solution space instead of guessing at it.   Self-reflection Question: Is your team treating AI as a threat to write around, or as a pair-programming partner that surfaces the blind spots you'd never find alone?   [The Scrum Master Toolbox Podcast Recommends]

Wasim Osman: When a Scrum Team's Silence Becomes a Self-Fulfilling Prophecy 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 team is interested in deliberately destroying their outcome or their team. Nobody does that on purpose." - Wasim Osman   Wasim's team was building a SaaS product with real potential. They followed Scrum, shipped features fast—and quietly let the bugs pile up. When customers finally pushed back ("you built five features, four of them have bugs"), the team made a confident bet: one quarter for new features, then one month to fix everything. It didn't work. The bug-bashing month revealed deeper, structural problems that demanded refactoring, and the roadmap was already packed. Then the fixes got handed to a single team, who felt demoted from the "prestigious" work of building features. Resentment grew between the teams. At the height of that tension, the company was acquired by a waterfall-driven parent company. The head of engineering left, the chief architect and two senior engineers followed, and it became chaos. Wasim's hardest lesson wasn't about the acquisition—it was about voice. The engineers assumed waterfall was being forced on them and stopped pushing back; leadership assumed the engineers were fine with it. Nobody said what they actually thought, and the fear became reality. As Wasim puts it, there was "no captain on the ship."   In this segment, we talk about how even conversations need to be iterative, and how a Scrum Master has to balance speaking up (so the team isn't rudderless) without speaking so much that the team stops voicing their own opinions.   Self-reflection Question: Where on your team is an unspoken assumption quietly hardening into reality, and what would it take for you to name it out loud first? Featured Book of the Week: Difficult Conversations by Douglas Stone, Bruce Patton, and Sheila Heen Wasim's most-recommended book is Difficult Conversations: How to Discuss What Matters Most. What stuck with him is a deceptively simple model: every hard conversation is really made of three conversations—the "what happened" conversation (the content), the feelings conversation, and the identity conversation (what the situation says about whether you're competent, good, or lovable). "When I first read it, I thought there can't be only three types of conversations," Wasim admits. "But once you've gone through the book, you can put any conversation into one of those funnels." He found it especially powerful in retrospectives: when the same issue keeps resurfacing, the real conversation is often about feelings, not action items—someone was never okay with an earlier decision, and that's why the follow-ups never happened.   Self-reflection Question: In your last tense retrospective, which of the three conversations—content, feelings, or identity—was really driving the room?   [The Scrum Master Toolbox Podcast Recommends]

Wasim Osman: From Finance to Scrum Master, a Deliberate Career Pivot 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 homework should start a lot earlier than that. The person looking for a particular role should already be moving in that direction before they even start the journey." - Wasim Osman   Wasim never planned to become a Scrum Master. He trained in finance and stock markets in the UK, but the pull toward software—and even 3D animation—had been there since he was young. When he realized the finance world wasn't for him, he made a move that looked like a detour and turned out to be a runway: he joined the people team at a tech company in Bangladesh, a branch of a New York-based firm. He didn't have the leverage to be picky, so he took the opportunity, learned how the engineering teams actually worked, and made himself useful. When the company started shifting from waterfall to agile and hosting Scrum certification events, Wasim was in the room organizing them. One day the head of engineering asked a "random question"—would he consider becoming a Scrum Master? For Wasim, it was an easy yes, because it was the direction he'd quietly been aiming at all along. He shadowed a senior engineer for a quarter, then took over a team of senior-most engineers who were patient with his mistakes. That patience built his confidence, and his willingness to keep his prior curiosity alive made the transition feel organic rather than forced.   Self-reflection Question: What direction are you quietly moving toward right now, and what "homework" could you start today so the next opportunity feels organic instead of accidental?   [The Scrum Master Toolbox Podcast Recommends]

Agile Is Not Dead. AI Didn't Kill It. And Waterfall Is Not BackA recent article claimed that Agile is dead, AI killed it, and Waterfall is back.It is a strong headline. It is also the kind of headline built to provoke a reaction. Yet beneath the noise lies a useful challenge that leaders should not dismiss too quickly. The article takes aim at ceremony-heavy Agile, vague user stories, weak delivery theatre, and the belief that feedback loops can replace serious thinking. Some of that criticism lands because many organisations have allowed Agile to become a label for meetings, boards, points, and process compliance rather than a way to deliver better outcomes.Bad Agile deserves to be challenged. Ceremony without impact should be removed. Estimation that does not improve decisions should be questioned. Product roles without real authority should be redesigned. Retrospectives that surface the same problems every sprint, with no change to the system around the team, are not agility. They are frustration with a calendar invite.How to connect with AgileDad:- [website] ⁠https://www.agiledad.com/⁠- [instagram] ⁠https://www.instagram.com/agile_coach/⁠- [facebook] ⁠https://www.facebook.com/RealAgileDad/⁠- [Linkedin] ⁠https://www.linkedin.com/in/leehenson/

No amount of tooling makes an organization go faster or do better. AI has made that clearer than anything else I’ve watched in nine years of doing this. What it has produced instead is what people are now calling the human wreckage of AI. How I Met Angela Dugan So one day I’m cruising around LinkedIn, in a market where nobody can get hired and companies swear they can’t find anyone, and here’s someone doing something simple. She posted about a role she wasn’t hiring for. Didn’t have the requisition, and said so right in the post. It felt awkward, it felt vulnerable…and she put it up anyway, Because she wasn’t willing to wait until she desperately needed somebody before she started meeting people. She got dozens of replies in days. Almost every one of them said the same thing. “It’s a relief to talk to a human.” That’s Angela Dugan. She’s VP of Product Delivery at Red Foundry in Chicago, and she went first while everyone else was feeding resumes into a machine. Stop Looking For Your Past Roles You’ll hear about the advice that ended her own job search, which is the part I want you to sit with: stop looking for your past roles. Look for the activities you want to do, the outcomes you want to drive, the impact you want to have. She stopped hunting for anything with “agile” in the title. That’s how she got a director job at Microsoft, and the VP job she has now. She shares the story of her layoff. She was cut from Microsoft when the AI money started moving and the people money stopped. Two days later she left a comment on somebody else’s post. Not an ask, just empathy for someone in the same wave. And her future CEO saw it. Someone she’d consulted for back in 2014 and never stopped talking to. Ten years of keeping one relationship warm. That’s the whole story. The Human Side of Business and Tech This episode is about the human side of tech, AI and Agile. Right now the job market is breaking, but it won’t stay that way. Know why? Because results speak. And what we learn from Angela Dugan is that doing things the right way (which could mean leveraging AI, but not just throwing tasks carelessly over the fence to AI) gets noticed. Because the RIGHT people make impact. They touch the bottom line. And isn’t that what we’ve been talking about here on Badass Agile? Outcomes. Not frameworks, nor conventions. Not fashion or trends or fast money. Find Angela Dugan: LinkedIn – https://www.linkedin.com/in/andugan/ (Put a note in the request.) She’s also at the local Chicago events and at VS Live. Show Notes **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.

Football's back. And on the first day of the 2026 preseason, Josh and Bob take one of the oldest lines in coaching and point it straight at leadership.Good teams don't win on trick plays. They win because they run the routine plays routinely. Block, tackle, catch the ball, do it again next week, do it while everybody else is chasing something clever.So what are the routine plays of leadership? The habits that quietly work when you do them consistently and quietly fall apart when you don't?Bob made a list. Josh made a list. Bob's was longer, and he made sure everybody knew it. 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!

This year's Agile 2026 theme was “shaping the future with agility,” and that is exactly where Kate Megaw and Anu Smalley found the industry: mid-shift, still deciding what comes next. Back from the conference, they sit down with Ryan Smith for an honest field report. The partnership between PMI and the Agile Alliance has solidified, so the room was no longer split into project managers on one side and Scrum Masters on the other.  AI, meanwhile, has stopped being the shiny new thing bolted onto every session title and settled into the operating system of how we work, though “don't forget the human” is still treated as a footnote.  Kate and Anu wrestle with an industry in flux where no one has put a finger on what is broken yet, the Scrum Master role morphing into a dozen job titles, and Anu's growing conviction that the psychology of AI is the work that matters.  The phrase that stuck with Kate from one of the sessions says it all: we are in the age of perpetual transformation.

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.

Havva Sevay: From "Scrum Master Is the Secretary" to True Co-Leadership Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. The Great Product Owner: The Co-Leader Who Mastered the PO Stances 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.   "Co-leadership means both sharing leadership in a lateral way, not a disciplinary way—the PO owns the technical part, the Scrum Master the organizational part." - Havva Sevay   Havva's best Product Owner already understood co-leadership—and went further. He used the Product Owner stances from Scrum.org as a feedback tool, asking the team to rate him on each stance (customer representative, company representative, and so on) with a percentage, then using that input to improve his skills deliberately. It's the same mindset Scrum Masters can adopt with their own stances: be aware of the options, get honest feedback, and adapt to the context, because the right stance changes over time. A great PO, in Havva's experience, treats their role as a skill set to be developed in partnership—not a title to defend.   Self-reflection Question: Could the PO stances become a feedback tool in your team—and would you be willing to be rated on your own Scrum Master stances? The Bad Product Owner: "The Scrum Master Is My Secretary" 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 worst is the PO who believes he's the product manager and the Scrum Master is the secretary. I said: I'm not your assistant, I don't bring your coffee." - Havva Sevay   The worst anti-pattern Havva has lived through is the Product Owner who treats the Scrum Master as a secretary—there to share the screen, organize the meeting, and take orders. Havva confronted it directly in a one-on-one: this is upside down. My job is to teach self-organization, not to be your assistant. But she didn't stop at the boundary—she helped the PO understand her role and walked in his shoes too, even sending him to a Scrum Master training while she experienced his responsibilities. Her strongest recommendation: from the very first meeting with a Product Owner, talk explicitly about who does what, surface expectations, and agree how you'll work together. Don't assume they know your job—or that you know theirs. The way out of the "secretary" trap is co-leadership: lateral, shared leadership built on time and trust.   Self-reflection Question: Have you ever explicitly agreed with your Product Owner on who is responsible for what—or are you both operating on untested assumptions?   [The Scrum Master Toolbox Podcast Recommends]

Havva Sevay: Success Is Feedback, Not Metrics—And the Power of Standing in Someone Else's Shoes 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 success is not metrics or numbers—that was my controller past. I measure myself through feedback, and through team satisfaction." - Havva Sevay   As a former project controller, Havva could have defined success in numbers. Instead, she measures it through feedback and team satisfaction. As long as people keep talking to her—telling her how she can be a better Scrum Master—she considers that success, and she treats even hard feedback as learning. But the most striking part of her definition is the discipline of standing in someone else's shoes. When a developer suggested she'd give better advice if she understood programming, she took the Scrum Developer training—the hardest training she's ever done—just to feel the team's daily reality. Vasco connects it to coaching a team that builds tools for other teams: the role isn't to produce the system, it's to make the other teams' lives easier. Havva's takeaway for every Scrum Master: put your shoes in a different position. Understanding the work from the other person's perspective is what drives team success.   Self-reflection Question: How do you measure your own success as a Scrum Master—and when did you last experience your team's work from their perspective?   [The Scrum Master Toolbox Podcast Recommends]

Agile Practitioners and Future JobsThere are insights that only come to me after a good conversation. My earlier self would have said “too late, a missed opportunity, again less than perfect”. Right now I rather think “moving forward mentally, another opportunity will come, great”. Recently, in the breaks between the recording, we had chatted about how wrong and unattractive the idea of “Scrum Masters should work themselves out of a job” is.How to connect with AgileDad:- [website] ⁠https://www.agiledad.com/⁠- [instagram] ⁠https://www.instagram.com/agile_coach/⁠- [facebook] ⁠https://www.facebook.com/RealAgileDad/⁠- [Linkedin] ⁠https://www.linkedin.com/in/leehenson/

AI is joining teams faster than most organizations have frameworks to support it and that's actually an exciting opportunity, if you approach it thoughtfully. In this episode of the Scrum.org Community Podcast, Scrum.org COO Eric Naiburg and executive advisor Darrell Fernandes pick up where their popular webinar Managing Your AI Teammate left off, tackling the audience questions that didn't make it into the live session.The conversation draws smart parallels between AI adoption and the cloud journey most organizations have already navigated, explores how to set your team up for secure and effective AI collaboration, and unpacks what it really means to treat AI as a strategic partner rather than just a tool. Eric and Darrell also take on a forward-looking question most teams haven't gotten to yet: how do we use AI efficiently and responsibly, not just effectively?If your team is starting to work alongside AI (and it almost certainly is), this episode will give you practical language and frameworks to do it with confidence.

Havva Sevay: AI vs. Real People—Helping Teams Avoid Information Overload 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.   "It's still a tool. It can make mistakes, it can hallucinate. People don't really question it—and that's the danger." - Havva Sevay   This week's coaching conversation tackles a challenge Havva—and many Scrum Masters—are living right now: AI vs. real people. For some, AI is a useful tool; for others, it's a magic oracle that solves everything and makes people replaceable. Havva sees the real risk in teams that accept AI's confident answers without double-checking, and in leaders who use AI to generate massive documents and dump them on teams as finished decisions. Vasco pushes the conversation into the practical: when a flood of AI-generated information, requirements, and tool changes lands on a busy team, how do you help them cope? Havva's answer is to step back and ask the human questions first—what is the epic? what does the stakeholder actually want? what do we really need right now? Then she pulls out a deliberately low-tech move: forget AI for one second. Her team uses the Eisenhower matrix manually to separate what's important now from what can wait. AI is a great tool—but the filtering of what matters is still human work.   Self-reflection Question: When AI floods your team with information and options, what is your practice for helping them separate what matters now from the noise?   [The Scrum Master Toolbox Podcast Recommends]

This week Shawn Tierney meets up with Filippo Boido of Agile Automation to discuss their PLC Coding AI Agent, TcAgent, in this episode of #TheAutomationPodcast. Special thanks to our members for supporting our work! Learn more about becoming a member here: https://theautomationblog.com/join

Justin Fiaschetti, Co-Founder and CEO of Inversion Space, joins me to talk about the company's plan to store maneuverable reentry vehicles in orbit for rapid cargo delivery, the design and architecture decisions driving Arc including cross-range requirements and payload accomodations, and how they see the market for these services. This episode of Main Engine Cut Off is brought to you by 32 executive producers—Russell, Fred, Natasha Tsakos, Matt, Joonas, Matt from Built, Josh from Impulse, Pat, Steve, David, Tim Dodd (the Everyday Astronaut!), Joel, Stealth Julian, Ryan, Theo and Violet, Kris, The Astrogators at SEE, Miles O'Brien, Jan, Donald, Joakim, Frank, Will and Lars from Agile, Warren, Lee, and four anonymous—and hundreds of supporters. Topics Inversion Arc - Inversion Anduril, Team of Partners to Work on Space Force's Space-Based Interceptors for Golden Dome for America | Anduril Arc Orbital Supply Capsule Aims To Put Military Supplies Anywhere On Earth Within An Hour 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

Havva Sevay: The Car Configuration Team That Spiraled Into Silence—and the Workshop That Saved It Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.   "First they tell you their opinion. Then they start shouting, getting emotional. And the third one is silence—and resignation. That's the worst part." - Havva Sevay   Havva remembers a highly motivated development team working on a car configuration system so complex it began to wear them down. They asked for training. The Product Owner waved it off—they've had enough training, they should understand it. What followed was a three-stage spiral Havva now recognizes anywhere: first the team shares opinions and solutions, then frustration turns to emotion and shouting, and finally comes silence and resignation. The team even kicked the Product Owner out of their daily—a low point Havva calls the worst she has seen in her career. The turning point was a LEGO Serious Play workshop. By getting both sides to build how they wanted to work together, the Product Owner did active listening for the first time, recognized the team needed an experienced developer to guide them, and the relationship transformed. The lesson: Scrum Masters are the facilitators of those moments of coming together—and there need to be many, at every level.   Self-reflection Question: Is a team you support moving through opinion → emotion → silence right now? What moment of coming-together could you facilitate before they reach resignation?   [The Scrum Master Toolbox Podcast Recommends]

In this episode of The Fearless Mindset Podcast, host Mark Ledlow continues his conversation with captive insurance and risk-management expert Kyle Sweet about protecting businesses, family offices, and generational wealth in an increasingly unpredictable world.Kyle explains how captive insurance can help business owners gain greater control over risk, reduce dependence on the commercial insurance market, and potentially transform an uncontrollable expense into a financial asset. He also discusses how family offices can preserve wealth by diversifying investments, involving qualified experts, maintaining responsible governance, and preparing future generations to become capable stewards rather than dependent beneficiaries.The conversation also explores the growing security challenges facing high-net-worth families and businesses. Mark and Kyle discuss continuous threat assessments, AI-generated reputational attacks, economic disruption, and the importance of combining security, insurance, and enterprise risk management. Kyle emphasizes that tomorrow's risks require agile professionals who can anticipate second-, third-, and fourth-order consequences before the damage occurs. Learn about all this and more in this episode of The Fearless Mindset Podcast.KEY TAKEAWAYSCaptive insurance can transform risk management from an expense into a financial asset.Business owners can operate more like family offices without immediately selling their companies.Generational wealth should produce capable heirs, not dependent beneficiaries.Family-office decisions should never be controlled by one dominant personality.Diversification and expert guidance help protect wealth from poor investment decisions.Money does not eliminate risk. It creates new personal, financial, security, and reputational exposure.Security assessments must be continuous because threats evolve constantly.AI can create fake images, emails, receipts, and political associations that damage a company's reputation.Security professionals should participate in broader enterprise risk and captive-insurance discussions.Agile and independent teams are often better positioned to anticipate emerging threats than large bureaucratic organizations.QUOTES “Money does not insulate them from risk. It creates infinitely more types of risk.”“This is not your trust fund. This is a family fund.”“You want your heirs to give more than they take.”“You don't get security one time and then think you're good.”“There's nothing more intimate with somebody than their money.”“You can't do that unless you have an assessment.”“This is an injury that you don't even know you're being cut until you've bled out.”“Bureaucracy kills innovation.”“Innovation comes from people who are nimble, agile, and can change on a dime.”“What we know today will be a completely different thing tomorrow.”Get to know more about Kyle Sweet through the link/s below.https://www.linkedin.com/in/kyle-sweet-08b97173/To hear more episodes of The Fearless Mindset podcast, you can go to https://the-fearless-mindset.simplecast.com/ or listen on major podcasting platforms such as Apple, Google Podcasts, Spotify, etc. You can also subscribe to the Fearless Mindset YouTube Channel to watch episodes on video.

Havva Sevay: When Doing Your Best Isn't Enough—The Scrum Master Lesson That Changed Everything Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.   "I didn't really acknowledge that the team is important, or what a team needs. I thought I was only focusing on getting the job done." - Havva Sevay   When Havva took her first Scrum Master job, she knew the framework cold and she was highly motivated. So she did exactly what the framework told her to do—and failed. Frustrated, she kept asking herself the same question: why did I fail? I really did my best. The turning point came from a mentor who asked her something she hadn't considered: did you ever think about what the team needed? In this episode, Havva walks us through the slow, honest work of realizing she had been judging instead of listening, pushing instead of stepping back. Her mentor introduced her to active listening—writing down what people actually said, not her interpretation of it—and to the discipline of silence. Becoming a better Scrum Master, she learned, is an everyday process that takes its time. We also explore how she stayed grounded: taking courses outside her bubble, networking, and learning from other people's experience.   Self-reflection Question: When you face a team problem, are you observing what is actually happening, or are you already judging and rushing to the next step?   [The Scrum Master Toolbox Podcast Recommends]

Bob opens with a metaphor about window blinds. Truth isn't a switch, he says, it's a set of slats you're constantly adjusting. Closed all the way, open all the way, and every shade of dim in between. He argues we're all doing this already, whether we admit it or not, because nobody walks around spewing 100% of what they know to every person they meet.Josh's picture is different. His light switch is taped to the on position with a sign that says "Do not touch!" The filtering happens somewhere else, in deciding who gets which truth and when.That gap turns into an actual disagreement, which almost never happens on this show. 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!

Danil Chernyshev: The MIA Product Owner vs. The One Who Owned the Outcome Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. The Great Product Owner: Communicating Value, Inviting the Right People 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.   "It's basic Scrum—but it's not basic." - Danil Chernyshev   The best Product Owner Danil ever worked with was Jamie Spence, on a Master Data Management re-architecture at Canadian Tire. The goal wasn't only to upgrade a system—it was to rethink how a major retailer with many different banners should work across all of them. Jamie didn't write user stories; the BAs did that. What he did was communicate, in a super-clear way, the value expected at every step. He didn't attend every daily Scrum, but he was there whenever the team wanted him, allocating his time on demand. He cared about user experience and lived for the feedback loop—"this sprint I want to deliver this part and see how it goes." And he invited the proper stakeholders to each sprint review: a small, deliberately varied group chosen by what had been delivered and whose feedback the team actually needed. As Danil and Vasco agree, it sounds obvious—and that's exactly why it's worth celebrating. Obvious and common are not the same thing.   Self-reflection Question: Does your Product Owner communicate expected value at every step—or just hand over user stories and disappear? The Bad Product Owner: Present on Paper, Missing in Action 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.   "On paper, you have a Product Owner. But you don't have a Product Owner." - Danil Chernyshev   The most common—and worst—anti-pattern Danil sees is the MIA, or "missing in action," Product Owner: a person with the title who doesn't actually own the product. Sometimes it's a BA or a tech lead wearing the label; sometimes it's someone who simply can't make decisions, or doesn't understand what they're responsible for because they're busy doing another job. The fix starts with clarity: first understand what the product even is, then put in place a Product Owner who makes decisions, owns the end-user experience, and maximizes value. Danil also flags a structural trap—one Product Owner per product, not one per team. He stretches the idea with vivid examples: an Agile coach leading a transformation is effectively the Product Owner of the process, with Scrum Masters as the developers; and Steve Jobs was the Product Owner of the iPhone while also being a customer for other Product Owners building pieces of it. Ownership is about maximizing value for the customer—not about who writes the user stories.   In this segment, we refer to the great Product Owner pattern Danil shares above, and how the Scrum Master's job is to help the Product Owner grow into real ownership.   Self-reflection Question: Is your Product Owner empowered to make decisions and own outcomes—or just a title on an org chart?   [The Scrum Master Toolbox Podcast Recommends]

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! Money Making Conversations Master Class with Rushion McDonald is America's premier entrepreneurship, business leadership, financial literacy, and wealth-building podcast featuring successful entrepreneurs, executives, founders, celebrities, and industry experts sharing actionable insights for professional and financial success. Business Podcast Entrepreneurship Small Business Business Growth Financial Literacy Wealth Building Black Entrepreneurs Minority Business Leadership Executive Leadership Business Funding Marketing Strategies Personal Development Startup Advice Sales Training CEO Interviews Founder Stories Professional Development Economic Empowerment Business Success Networking Brand Building Innovation How to start a business Small business funding Entrepreneur success stories Business leadership podcast Wealth building strategies Black entrepreneur podcast Minority business development Marketing for small businesses Business growth strategies Startup funding opportunities Executive leadership training Financial literacy education Success mindset podcast Two-time Emmy and Three-time NAACP Image Award-winning, television Executive Producer Rushion McDonald interviewed Everett Swain.

Danil Chernyshev: Success Is Synergy—When the Team and the Product Both Win Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.   "Success is when team members say thank you, and praise others for delivering a successful product." - Danil Chernyshev   For Danil, success as a Scrum Master is never one thing—it's a combination. It's the moment team members thank each other and credit the whole group for a product that actually landed with customers. As he reminds us, Scrum Masters, Product Owners, and developers are all there for the same reason: to deliver a product and solve real problems for the end user. A healthy team that has fun together but ships nothing has only spent time and money. A team that delivers but burns everyone out, until no one wants to see each other again, isn't a success either. Real success is the synergy of both: a productive team, happy customers and stakeholders, and people who still have the energy to keep going. Danil also turns the lens inward—success means understanding where you are in your own journey. And it grows from action: when teams get stuck overthinking, he guides them back to what's inside their control, helps them find the smallest valuable step, and gets them experimenting. Start where you are, do what you can, then learn from it.   Self-reflection Question: Are you optimizing for a happy team, a delivered product, or the synergy of both—and how would you know the difference? Featured Retrospective Format for the Week: Lean Coffee (paired with 1-2-4-All and 5 Whys) Danil doesn't lock himself into a single retrospective format—he chooses based on the sprint, guided by "common sense in Scrum." His default is to keep a running list of topics gathered throughout the sprint, then open the retrospective with a Lean Coffee session to democratically decide what to discuss. From there, a light topic gets a quick Lean Coffee conversation, while a deeper one moves into 1-2-4-All from Liberating Structures or a 5 Whys. The non-negotiable for Danil: every retrospective must end with actionable action items. A retro that produces only conversation and no change, he says, was a waste of time—maybe fun, but still a missed opportunity to reflect, learn, and adapt.   [The Scrum Master Toolbox Podcast Recommends]

Danil Chernyshev: Coaching the Outsider In—Helping a Distrustful Team Through Transformation 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.   "Developers and QAs know each other very well, but they don't trust anybody else." - Danil Chernyshev   This week's coaching conversation starts with a hard situation. A subcontractor's developers—people who had always worked isolated from the business, with no plans and no communication—were brought back inside the "mother firm" as part of a digital transformation. Overnight they faced new teams, Scrum, SDLC, CI/CD, and full transparency. The developers and QAs trusted each other completely and trusted no one else: not the Scrum Master, not the Product Owner, not the BAs. Forced to estimate with story points, every story came back as a 3 or a 5, with no conversation. When Danil asked why, the answer was always "we'll discuss internally and tell you tomorrow"—he suspected a second, hidden daily Scrum without him. As he and Vasco unpack it, the real issue is transparency itself: a team used to hiding now feels exposed and doesn't know the consequences of being open. Vasco offers an experiment—build a "trio" of the Product Owner, the Scrum Master, and one friendly insider from the team to prepare refinements together. The Product Owner is always the outsider; pairing them with a trusted insider lets ideas and experiments spread faster. Before you can improve the Scrum, you first have to bring the outsiders in.   Self-reflection Question: Where on your team is trust the real bottleneck—and who is the "insider" who could help an outsider earn it?   [The Scrum Master Toolbox Podcast Recommends]

Danil Chernyshev: Why Teams Always Adapt—And How Bad Rules Push Them Into Zombie Scrum 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.   "Teams always adapt. You only get to decide what they adapt to." - Danil Chernyshev   Most dysfunction doesn't start with the team—it starts with the structure around them. Danil shares the story of a classic metrics-driven organization where Scrum Masters reported to a dedicated manager who measured their success by team velocity. That manager tracked retrospectives in a separate log, and would show up at the daily Scrum to confirm everyone answered the three questions. The result was predictable: the retrospective became a clock to survive, the daily became a checkbox with no real conversation, and velocity turned into theater—stories closed as "done," then reopened as "part two" in the next sprint. There was never a real done increment. Danil refuses to blame the team. They were doing exactly what teams always do—adapting to survive the rules and boundaries handed to them. As he and Vasco explore, the only real choice a leader has is not whether a team adapts, but what they adapt to. Dictate bureaucracy, and they'll adapt to surviving it. That's how productive, enjoyable work quietly turns into zombie Scrum. Servant leadership exists precisely so someone helps the team adapt toward value—not toward compliance.   In this segment, we talk about User Story Mapping by Jeff Patton and Peter Economy, and you can hear Jeff Patton on the podcast.   Self-reflection Question: Look at a behavior on your team you find frustrating—what rule or structure might that team be adapting to in order to survive? Featured Book of the Week: Actionable Agile Metrics for Predictability by Daniel Vacanti Danil calls this book eye-opening. It changed how he thinks about metrics—not as a reporting tool for executives, but as something teams can use for themselves to understand what to do next and how to improve. As he puts it, "after that book, you will probably know that a lot of cumulative flow diagrams that you saw in your past, they doesn't work well, and need to be rebuilt." The book makes flow metrics serve the team first, while still giving leadership the transparency they need. You can also hear Daniel Vacanti on the podcast, and get the book here: Actionable Agile Metrics for Predictability by Daniel Vacanti.   [The Scrum Master Toolbox Podcast Recommends]

Danil Chernyshev: Forged in the Fire—Why the Scrum Master Role Tests Even Experienced Leaders 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.   "From my story, you can probably say that I was forged in the fire." - Danil Chernyshev   Danil had already climbed the ladder. He started with Scrum in 2010 as a developer, grew into a development manager, and reached executive level, running a department of 70 developers in his home country. Then he immigrated to Canada and had to start his career fresh. Certified by Scrum.org as both Scrum Master and Product Owner, the first role he landed was Scrum Master—and that's where the trouble began. He knew SDLC inside out, he knew how developers think, he knew Scrum from the trenches. What he didn't know was how to be a servant leader: how to balance serving and leading, how to measure his own success, how to even notice the small wins. After years at the top, he was suddenly the person who knew the least. In this episode, Danil shares why he stayed in the role instead of walking away—he loves building processes that help teams evolve, and he couldn't resist a real challenge. His advice to anyone at that same crossroads: be patient, reflect, build a feedback loop, and never stop learning. A certification proves you understand the base theory. Everything that matters comes after.   In this episode, we refer to the Tuckman model of team development, and how the storming phase tests every team—and every newcomer.   Self-reflection Question: When was the last time you were the person on the team who "knew the least"—and what did that teach you about your own growth?   [The Scrum Master Toolbox Podcast Recommends]

Alf Dobbert-Baums: The Too-Technical PO and the One Who Was Willing to Experiment In this episode, we refer to Shift: From Product to People and the value of keeping the PO–developer conversation at the goal level. The Great Product Owner: The PO Who Was Willing to Drop the Spec and Trust the Developers 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.   "Let's ditch the technical part, and let's see what happens." - Alf Dobbert-Baums   The Great PO, in Alf's experience, is willing to experiment with letting go. She stopped writing detailed technical specifications and started writing plain user stories. Then — and this is the harder move — she stopped throwing them over the fence and walked into the developers' space to have the conversation. Alf had coached her toward it, and he watched the trust compound. Because she trusted the developers on the how, she had less work to do (the developers were closer to the system anyway) and the developers had room to make real decisions. The conversation stayed where it belonged: on the goal. Alf names the pattern this great PO embodied — open to experiments, willing to say "let's see what happens," and quietly resisting the seductive pull of getting technical because it feels safer. The Scrum Master's job is partly to make that letting-go feel safe enough to try.   Self-reflection Question: Where is your PO still writing the "how" — and what would it take for them to trust the developers enough to write only the "why" and the "what"? The Bad Product Owner: The PO Who Thinks They Know More Than the Developers 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 said: 'developers can retrieve the information from the archive database.' The developer said: 'the information is not in the archive database.'" - Alf Dobbert-Baums   The anti-pattern is the PO who is too technical — the one who writes specs full of implementation detail and treats the developers as executors. Alf calls him John. John wrote a user story that told the developers exactly where to fetch the data from: the archive database. Then he tried to hand the story to Alf to present, the way a memo gets handed across a desk. Alf refused. He insisted John present it to the developers himself. John did. The first developer to speak said the information wasn't in the archive database. Alf hopes that moment humbled John a little. The point isn't whether John was right about the database — the point is the dynamic. When the PO writes the technical answer into the story, the developers stop being collaborators and become receivers. The translation work that creates real value — between user goal and technical option — never happens. The PO ends up with more work, less ownership from the team, and worse outcomes.   In this segment, we refer to Shift: From Product to People and the idea that great POs facilitate the conversation between user goal and team, rather than dictating it.   Self-reflection Question: When was the last time your PO wrote a technical detail into a story and the developers had to walk it back — and what would change if the PO trusted them to design the "how"?   [The Scrum Master Toolbox Podcast Recommends]