PodcastsNewsScrum Master Toolbox Podcast: Agile storytelling from the trenches

Scrum Master Toolbox Podcast: Agile storytelling from the trenches

Vasco Duarte, Agile Coach, Certified Scrum Master, Certified Product Owner
Scrum Master Toolbox Podcast: Agile storytelling from the trenches
Latest episode

436 episodes

  • Scrum Master Toolbox Podcast: Agile storytelling from the trenches

    The Almost Invisible Scrum Master, Why Team Independence Is the Ultimate Success Metric | Iryna Stelmakh

    26/03/2026 | 14 mins.
    Iryna Stelmakh: The Almost Invisible Scrum Master, Why Team Independence Is the Ultimate Success Metric
    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 successful Scrum Master is almost invisible — not because they don't contribute, but because the team is no longer dependent on them for every decision." — Iryna Stelmakh
     
    Iryna offers a powerful definition of success for Scrum Masters: becoming almost invisible. Not because the Scrum Master isn't contributing, but because the system works — with or without them. The team takes ownership of delivery, solves problems collaboratively, and continuously improves its own process. Each team member can propose, vote, and suggest changes because the environment has a high level of trust.
     
    When that happens, Iryna explains, the Scrum Master becomes more of a system observer and catalyst rather than a daily driver. As Vasco adds, this perspective is valuable because it looks beyond personal metrics — it examines behaviors across all the interactions the Scrum Master facilitates: between the team and the product owner, between the team and stakeholders during reviews, and within the team itself. The Scrum Master role sits at the nexus of many interactions, and success means those interactions work well even when you step back.
     
    Self-reflection Question: If you were absent for a full sprint, would your team maintain the same quality of collaboration, decision-making, and delivery — or would things fall apart without you?
    Featured Retrospective Format for the Week: The Energy Retrospective
    Iryna shares her favorite retrospective format — one she calls the Energy Retrospective. Instead of the standard "what went well / what didn't" framing, it asks three questions: What gave us energy this sprint? What drained our energy? And what should we start, stop, or continue doing to keep our energy at the right level?
     
    This approach shifts the conversation from purely technical task problems to real human dynamics. As Iryna explains, closing technical tasks and resolving issues is important, but so is the wellness of the team. The Energy Retrospective creates space for both. She also notes that retrospective format should match the team: for open, trusting teams, a straightforward format works fine. But for new teams or teams with high resistance — those still in the forming stage where the Scrum Master isn't yet a trusted figure — she uses metaphorical approaches, like asking team members to pick pictures that represent their feelings about the sprint. Even a happy, sad, or frustrated monkey picture can surface insights that direct questions might not.
     
    [The Scrum Master Toolbox Podcast Recommends]
     
    🔥In the ruthless world of fintech, success isn't just about innovation—it's about coaching!🔥
     
    Angela thought she was just there to coach a team. But now, she's caught in the middle of a corporate espionage drama that could make or break the future of digital banking. Can she help the team regain their mojo and outwit their rivals, or will the competition crush their ambitions? As alliances shift and the pressure builds, one thing becomes clear: this isn't just about the product—it's about the people.
     
    🚨 Will Angela's coaching be enough? Find out in Shift: From Product to People—the gripping story of high-stakes innovation and corporate intrigue.
     
    Buy Now on Amazon
     
    [The Scrum Master Toolbox Podcast Recommends]
     
    About Iryna Stelmakh
     
    Iryna Stelmakh is a Project & Delivery Leader and Agile Coach who helps leaders turn complexity into clarity. With 10+ years across US, Nordic, and Eastern European environments, she works at the intersection of business transformation and human systems, building resilient organizations and high-performing teams in complex contexts.
     
    You can link with Iryna Stelmakh on LinkedIn.
  • Scrum Master Toolbox Podcast: Agile storytelling from the trenches

    Fighting Agile Theater, When Organizations Adopt the Ceremonies But Not the Mindset | Iryna Stelmakh

    25/03/2026 | 16 mins.
    Iryna Stelmakh: Fighting Agile Theater, When Organizations Adopt the Ceremonies But Not the Mindset
    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.
     
    "Transparency can be uncomfortable, but without transparency, there is no real improvement." — Iryna Stelmakh
     
    Iryna brings a challenge she calls "Agile Theater" — organizations that implement all the visible parts of Agile (the ceremonies, the boards, the terminology) while the underlying mindset remains unchanged. Decisions stay centralized, transparency is avoided, and problems are hidden. As she puts it: "Teams go through the emotions of Agile without actually benefiting from it."
     
    But her real challenge goes deeper. Iryna shares a story about building trust with outsourcing clients. Five days into a new assignment on a project the company had worked on for over ten years, she received an email listing team members to be removed — with no explanation. It was a red flag: the absence of transparency signaled that the client relationship lacked the trust bridge needed for genuine collaboration.
     
    Iryna's response was characteristically direct. She organized a call with stakeholders and discovered the client operated on quarterly budget cycles — these cuts could happen every three months. Instead of accepting the loss, she shifted the cut team members to other projects within the same account, turning the problem into an opportunity. A QA engineer moved to another project that needed one. A developer and two others got upsold into a team extension. Nobody ended up on the bench.
     
    Then came the systemic fix: Iryna set up one-on-one meetings with each stakeholder across different divisions to stay informed in advance. Prevention over reaction — because, as she says, reactions cost more.
     
    Self-reflection Question: In your current engagement, do you have direct relationships with the people who make budget and staffing decisions — or would a surprise email catch you completely off guard?
     
    [The Scrum Master Toolbox Podcast Recommends]
     
    🔥In the ruthless world of fintech, success isn't just about innovation—it's about coaching!🔥
     
    Angela thought she was just there to coach a team. But now, she's caught in the middle of a corporate espionage drama that could make or break the future of digital banking. Can she help the team regain their mojo and outwit their rivals, or will the competition crush their ambitions? As alliances shift and the pressure builds, one thing becomes clear: this isn't just about the product—it's about the people.
     
    🚨 Will Angela's coaching be enough? Find out in Shift: From Product to People—the gripping story of high-stakes innovation and corporate intrigue.
     
    Buy Now on Amazon
     
    [The Scrum Master Toolbox Podcast Recommends]
     
    About Iryna Stelmakh
     
    Iryna Stelmakh is a Project & Delivery Leader and Agile Coach who helps leaders turn complexity into clarity. With 10+ years across US, Nordic, and Eastern European environments, she works at the intersection of business transformation and human systems, building resilient organizations and high-performing teams in complex contexts.
     
    You can link with Iryna Stelmakh on LinkedIn.
  • Scrum Master Toolbox Podcast: Agile storytelling from the trenches

    When Communication Clarity Matters More Than Technical Complexity, A Healthcare Project That Fell Apart | Iryna Stelmakh

    24/03/2026 | 15 mins.
    Iryna Stelmakh: When Communication Clarity Matters More Than Technical Complexity, A Healthcare Project That Fell Apart
    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.
     
    "Communication clarity is more important than technical complexity, because if you do not understand, it's pretty hard to execute." — Iryna Stelmakh
     
    Iryna shares one of her most painful career stories — a project in the healthcare domain focused on cancer treatment research data. When she joined, she was managing around 9 projects simultaneously and agreed to take this one on the condition that a strong technical lead would own the technical direction. The project began with a critical misunderstanding: sales had communicated that the client needed a database redesign, but the client actually needed a migration to a different database type. Similar words, fundamentally different work.
     
    For three months, the team worked through research and discovery phases, trying to understand the actual problem. But communication gaps — compounded by language barriers between the Ukrainian development team and the US-based client — prevented them from identifying the real need in time. Iryna trusted the technical lead's reports that everything was on track. She relied instead of checking. Eventually, the client lost confidence and left. It remains the only project in her career she considers a genuine failure.
     
    The lesson cuts deep: teams must have people who can ask the right questions early. As Vasco observes, the root cause was implicit assumptions that were never discovered or explored by the different people involved.
     
    In this episode, we also talk about the importance of the monitoring and controlling phase in project management.
     
    Self-reflection Question: When you trust a team member's assessment that "everything is fine," what verification steps do you take to confirm that understanding is truly shared across all stakeholders?
    Featured Book of the Week: Team Topologies by Matthew Skelton and Manuel Pais
    Iryna recommends Team Topologies by Matthew Skelton and Manuel Pais as a book that changed how she thinks about Agile leadership. "Great agile leadership is not only about frameworks, but it's about communication, influence, and the ability to align people around shared goals," she explains. The book helped her understand that Agile isn't just about team process — it's about organizational structure, team boundaries, and responsibilities. She also recommends Never Split the Difference by Chris Voss for Scrum Masters who want to sharpen their communication and influence tactics. As Iryna puts it, communication is one of the most important skills a Scrum Master must have.
     
    [The Scrum Master Toolbox Podcast Recommends]
     
    🔥In the ruthless world of fintech, success isn't just about innovation—it's about coaching!🔥
     
    Angela thought she was just there to coach a team. But now, she's caught in the middle of a corporate espionage drama that could make or break the future of digital banking. Can she help the team regain their mojo and outwit their rivals, or will the competition crush their ambitions? As alliances shift and the pressure builds, one thing becomes clear: this isn't just about the product—it's about the people.
     
    🚨 Will Angela's coaching be enough? Find out in Shift: From Product to People—the gripping story of high-stakes innovation and corporate intrigue.
     
    Buy Now on Amazon
     
    [The Scrum Master Toolbox Podcast Recommends]
     
    About Iryna Stelmakh
     
    Iryna Stelmakh is a Project & Delivery Leader and Agile Coach who helps leaders turn complexity into clarity. With 10+ years across US, Nordic, and Eastern European environments, she works at the intersection of business transformation and human systems, building resilient organizations and high-performing teams in complex contexts.
     
    You can link with Iryna Stelmakh on LinkedIn.
  • Scrum Master Toolbox Podcast: Agile storytelling from the trenches

    When "Agile" Becomes a License to Change Everything, The Cost of No Rules in Backlog Management | Iryna Stelmakh

    23/03/2026 | 15 mins.
    Iryna Stelmakh: When "Agile" Becomes a License to Change Everything, The Cost of No Rules in Backlog Management
    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.
     
    "For me, it was pretty hard to explain that Agile is about cost reduction, and not about cost increasing." — Iryna Stelmakh
     
    Iryna shares a story from one of her first projects as a Scrum Master, working with a client from Israel who saw Scrum as an open invitation to add anything to the backlog at any time. For this client, agility meant unlimited flexibility — the freedom to extend not just the product backlog but the sprint backlog, multiple times per sprint. As Vasco points out, this is a pattern many teams recognize: when there's no cost to disrupting a sprint, it becomes effortless to keep piling on work, destroying the very predictability that sprints are designed to create.
     
    Iryna struggled to push back. It was one of her first projects, and the client was confident in his approach. But the experience taught her a lasting lesson: the collaboration with external clients must start with an agreement about how the team works. That means explaining the methodology during the pre-sale phase, documenting it in the contract, and teaching the client the benefits of the process before the work begins. As she puts it, when she checked back with the sales and engagement teams, she realized nobody had set those expectations. She relied instead of checking — and paid the price. Once she held sessions with the client to explain how Scrum works and what it delivers, things shifted. New tasks went into the product backlog and were prioritized properly through refinement, not dumped into active sprints.
     
    Self-reflection Question: When was the last time you verified that your client or stakeholders truly understand how your team works — not just the label, but the actual rules and commitments?
     
    [The Scrum Master Toolbox Podcast Recommends]
     
    🔥In the ruthless world of fintech, success isn't just about innovation—it's about coaching!🔥
     
    Angela thought she was just there to coach a team. But now, she's caught in the middle of a corporate espionage drama that could make or break the future of digital banking. Can she help the team regain their mojo and outwit their rivals, or will the competition crush their ambitions? As alliances shift and the pressure builds, one thing becomes clear: this isn't just about the product—it's about the people.
     
    🚨 Will Angela's coaching be enough? Find out in Shift: From Product to People—the gripping story of high-stakes innovation and corporate intrigue.
     
    Buy Now on Amazon
     
    [The Scrum Master Toolbox Podcast Recommends]
     
    About Iryna Stelmakh
     
    Iryna Stelmakh is a Project & Delivery Leader and Agile Coach who helps leaders turn complexity into clarity. With 10+ years across US, Nordic, and Eastern European environments, she works at the intersection of business transformation and human systems, building resilient organizations and high-performing teams in complex contexts.
     
    You can link with Iryna Stelmakh on LinkedIn.
  • Scrum Master Toolbox Podcast: Agile storytelling from the trenches

    BONUS Why 98% of Innovation Fails Before It Reaches a Single Customer With Lorraine Marchand

    21/03/2026 | 33 mins.
    BONUS: Why 98% of Innovation Fails Before It Reaches a Single Customer
    Lorraine Marchand has spent three decades helping organizations innovate in environments where failure carries real consequences. In this episode, she shares the frameworks, stories, and hard-won lessons from her time at IBM Watson Health and beyond — starting with the summer her father handed her a stopwatch and a problem to solve at a diner.
    The Sugar Cube That Started It All
    "At the age of 12, I learned that problem solving was fun. It was really safe to experiment, and it turned out to be lucrative, because we earned some revenue and royalties from our sugar cube."
     
    Lorraine's innovation journey began with her father — a serial inventor who challenged his kids to identify and solve real problems. One summer, he took Lorraine and her brother to the Hot Shops Cafeteria in the Baltimore-Washington area with stopwatches, graph paper, and 3-color pens. Their assignment: figure out what was slowing down table turnover. After three days of observation and interviews with waitresses, busboys, and the manager, they discovered that sugar packets were the culprit — granules spilling over the table and floor during cleanup. Their solution, the Sugar Cube, was prototyped, sold to the manager, and eventually adopted across the chain — which later became the Marriott Corporation. The lesson stuck: innovation starts with observing problems close to the core, not chasing abstract ideas in a vacuum.
    Inside IBM Watson Health: Customer Co-Creation Over Engineering Brilliance
    "We have fallen in love with our solution. And we have not done our true problem-solving dissection and customer research to make sure that we're solving a problem that a customer wants to pay us to solve."
     
    At IBM Watson Health, Lorraine worked with 250 world-class engineers building solutions for the biggest names in life sciences — Johnson & Johnson, Pfizer, Sanofi, Medtronic. The process started with "garage sessions" where the team would tackle problems directly with a reference customer. But a recurring tension emerged: engineering would want to take what they learned from one customer, disappear into a room, build the perfect solution, and then hand it to marketing to sell. Lorraine had to repeatedly pull them back. A reference customer is an N of 1 — solving their problem doesn't guarantee a marketplace need. The discipline was to keep the customer in lockstep at every stage and continuously open the aperture, bringing in more customers and more feedback to validate that the solution would work at scale.
    The Innovation Mindset: Four Components That Matter
    "Thinking outside of the box means that you step outside of your box and you step into someone else's box."
     
    Lorraine identifies four components of the innovation mindset: problem solving, insatiable curiosity, embracing change, and welcoming diversity. The diversity piece is where most teams fall short. Homogenous groups become echo chambers — smart engineers designing from a technology perspective rather than a customer use perspective. The most innovative organizations Lorraine has worked with embrace cross-functional, multidisciplinary teams where engineering, marketing, and customer experience all have a seat at the table. No idea is a bad idea at the brainstorming stage — the down-selection comes later through structured evaluation.
    The Golden Ratio: Why 10% Drives 70% of Future Growth
    "Five years later, 70% of your growth will come from that 10% that you invested in innovation. So there's an inverse correlation to where you're investing and where that growth is going to come in the future."
     
    Lorraine points to the Golden Ratio framework popularized by Sergey Brin at Google: invest 70% in core business, 20% in adjacencies and new markets, and 10% in net new, transformative ideas that might not work out. The data across companies over the last 15 years consistently shows that the 10% bet on innovation generates the majority of future growth. Companies that invest 100% in core and a little in adjacency stay stuck in single-digit growth. Making innovation a strategic imperative — with dedicated budget and dedicated talent — is what separates companies that break out from those that stagnate.
    Experimentation Done Right: Problem Statement First, Prototype Fast
    "You have to have a really solid problem statement. It has to be clear, measurable, significant, and actionable."
     
    Good experimentation follows the scientific method. It starts with problem deconstruction — using first principles, the series of whys, or reframing to break down the problem until the statement is sharp enough to act on. From there, brainstorm solutions, down-select to the most promising one based on customer input, and build a minimal viable product. Lorraine emphasizes minimal — test the smallest feature possible, get it in front of customers quickly, capture the feedback, and loop it back into the next iteration. The continuous loop of learning is where real progress happens.
    The Watson Health Pivot: When the Customer Changes Everything
    "Even for me, it wasn't until we got this in the customer's hands and we were able to see how it was going to function in real life that we had the aha moment."
     
    At IBM Watson Health, Lorraine's team was developing an algorithm for a large medical device company working on pain intervention. The software used a patient's mobile phone to detect mobility issues — how quickly they got up from a chair, how easily they opened a jar — and determine when to deliver pain relief through the device. The engineering was elegant, the reference customer loved it. But when they put the solution in the hands of actual physicians and patients in their homes, they discovered they were off track in how the tool would function in real life. The pivot was dramatic: instead of the medical device company, they partnered with a pharmaceutical company that used the algorithm to guide patients on when to take pain-related medication. The entire end customer changed — because they did the work of testing with real users.
    Reframing Failure as Learning
    "If failure's in your operating system, you're not going to try these experiments, and you're not going to be willing to get it wrong."
     
    Lorraine's book No Fear, No Failure examines the strategic failure that holds companies back from innovating. One of the five C's in her framework is chance — the willingness to take calculated risks. The key is reframing experiments from "did we get it right or wrong?" to "what can we learn?" When teams set learning objectives for each experiment — what can I learn about this tool, about the customer, about how this works in practice — they remove the fear that prevents action and replace it with a process that compounds knowledge over time.
     
    About Lorraine Marchand
     
    Lorraine Marchand helps senior leaders innovate in high-cost-of-failure environments. An award-winning author, keynote speaker, and innovation advisor, she brings 30+ years of experience, including work at IBM Watson Health. Her book, No Fear, No Failure, offers practical frameworks for learning and growth without undue risk.
     
    You can link with Lorraine Marchand on LinkedIn and find more of her work at LorraineMarchand.com.

More News podcasts

About Scrum Master Toolbox Podcast: Agile storytelling from the trenches

Every week day, Certified Scrum Master, Agile Coach and business consultant Vasco Duarte interviews Scrum Masters and Agile Coaches from all over the world to get you actionable advice, new tips and tricks, improve your craft as a Scrum Master with daily doses of inspiring conversations with Scrum Masters from the all over the world. Stay tuned for BONUS episodes when we interview Agile gurus and other thought leaders in the business space to bring you the Agile Business perspective you need to succeed as a Scrum Master. Some of the topics we discuss include: Agile Business, Agile Strategy, Retrospectives, Team motivation, Sprint Planning, Daily Scrum, Sprint Review, Backlog Refinement, Scaling Scrum, Lean Startup, Test Driven Development (TDD), Behavior Driven Development (BDD), Paper Prototyping, QA in Scrum, the role of agile managers, servant leadership, agile coaching, and more!
Podcast website

Listen to Scrum Master Toolbox Podcast: Agile storytelling from the trenches, Off Air with Jane & Fi and many other podcasts from around the world with the radio.net app

Get the free radio.net app

  • Stations and podcasts to bookmark
  • Stream via Wi-Fi or Bluetooth
  • Supports Carplay & Android Auto
  • Many other app features
Social
v8.8.4| © 2007-2026 radio.de GmbH
Generated: 3/26/2026 - 2:00:20 PM