How Limiting Work-in-Progress Saved a Struggling Agile Team | Marina Lazovic

Scrum Master Toolbox Podcast: Agile storytelling from the trenches

Player FM - Internet Radio Done Right

52 subscribers

הוסף לפני four שנים

תוכן מסופק על ידי Vasco Duarte, Agile Coach, Certified Scrum Master, and Certified Product Owner. כל תוכן הפודקאסטים כולל פרקים, גרפיקה ותיאורי פודקאסטים מועלים ומסופקים ישירות על ידי Vasco Duarte, Agile Coach, Certified Scrum Master, and Certified Product Owner או שותף פלטפורמת הפודקאסט שלהם. אם אתה מאמין שמישהו משתמש ביצירה שלך המוגנת בזכויות יוצרים ללא רשותך, אתה יכול לעקוב אחר התהליך המתואר כאן https://he.player.fm/legal.

Tinfoil Swans

1
Encore: Will Poulter, Dave Beran, and The Bear 52:22

לפני 18 ימים52:22

הפעל מאוחר יותר

רשימות

לייק

אהבתי

52:22

Season 3 of the smash hit FX/Hulu show “The Bear” roared to life just days ago, but Will Poulter (the actor who plays fan-favorite Luca) and 2014 F&W Best New Chef Dave Beran had been prepping for weeks. Poulter — like his co-star Jeremy Allen White — staged with Beran at his Santa Monica restaurant Pasjoli to learn how to accurately portray a professional chef onscreen. The lessons went so well, Beran says he’d hire Poulter as a cook — even despite a messy mishap with a pastry bag. The two dished all about getting kitchen culture right on and offscreen, what it takes to be at the top of your craft, and the pure magic of a great restaurant service. Learn more about your ad choices. Visit podcastchoices.com/adchoices…

לפני שנה 17:36

MP3•בית הפרקים

Marina Lazovic: How Limiting Work-in-Progress Saved a Struggling Agile Team

Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.

Marina shares the story of a small team of three developers who were struggling with multiple challenges. The team was primarily working on front-end fixes but faced persistent environment issues that kept breaking their work. Under pressure from a Product Owner pushing for delivery, the team fell into the trap of working on too many things simultaneously, resulting in items staying perpetually "in progress" and never reaching "done." As the situation deteriorated, the PO began micromanaging the team in attempts to unblock work. Marina explains how she helped the team understand the value of limiting work-in-progress (WIP), even when initially both developers and the PO were resistant to the idea. Through experimentation over several sprints, they discovered that limiting WIP actually increased their completion rate rather than reducing it.

Self-reflection Question: What work-in-progress limits might benefit your current team, and how could you experiment with implementing them in a way that addresses stakeholder concerns?

Featured Book of the Week: The Five Dysfunctions of a Team

Marina recommends "The Five Dysfunctions of a Team" as an essential read for Scrum Masters. She describes it as a book filled with valuable lessons and examples that she could easily identify in her workplace. Marina finds particular value in sharing the concepts with her teams and using the book as a framework to discuss dysfunction patterns they might be experiencing. The practical examples provided in the book serve as excellent conversation starters to help teams recognize and address their own challenges.

About Marina Lazovic

Marina is a Scrum Master and Kanban Trainer from Belgrade, Serbia, with nearly a decade in the IT industry. Though not from a technical background, she is passionate about helping development teams and organizations optimize processes and build great products using Agile. She thrives on driving efficiency and fostering collaboration.

You can link with Marina Lazovic on LinkedIn.

203 פרקים

#Tech #News #Tech News #Vasco Duarte #Agile Coach #Certified Product Owner #Certified Scrum Master #Agile #Kanban #Lean #Oikosofy #Scrum #Scrummaster #Team #Teamdynamics #Projectmanagement

How Limiting Work-in-Progress Saved a Struggling Agile Team | Marina Lazovic

Scrum Master Toolbox Podcast: Agile storytelling from the trenches

52 subscribers

published לפני שנה

שתפו

MP3•בית הפרקים

Marina Lazovic: How Limiting Work-in-Progress Saved a Struggling Agile Team

Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.

Self-reflection Question: What work-in-progress limits might benefit your current team, and how could you experiment with implementing them in a way that addresses stakeholder concerns?

Featured Book of the Week: The Five Dysfunctions of a Team

About Marina Lazovic

You can link with Marina Lazovic on LinkedIn.

203 פרקים

#Tech #News #Tech News #Vasco Duarte #Agile Coach #Certified Product Owner #Certified Scrum Master #Agile #Kanban #Lean #Oikosofy #Scrum #Scrummaster #Team #Teamdynamics #Projectmanagement

Alle Folgen

Scrum Master Toolbox Podcast: Agile storytelling from the trenches

1
The Ghost Product Owner vs. The Storytelling Master | Stuart Tipples 17:18

לפני 1 day17:18

17:18

Stuart Tipples: The Ghost Product Owner vs. The Storytelling Master 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 Storytelling Master Stuart describes an exceptional Product Owner who worked with an API team on what could have been a dry, unsexy product. This PO excelled by maintaining clear availability through established office hours, showing up consistently for the team, and avoiding micromanagement. The standout quality was their ability to tell compelling stories that created clarity and got the team onboard with the vision. Through storytelling, this PO helped the team communicate the value of their work, transforming a potentially mundane product into something meaningful and engaging for both the team and stakeholders. The Bad Product Owner: The Ghost with the Most Stuart encountered a problematic Product Owner working with a customer-portal team dealing with edge cases, legacy systems, and messy code. This PO earned the nickname "The Ghost with the Most" because they were never available when needed. They would miss sprint planning sessions, delay or skip backlog refinement entirely, and leave team members to fill the gap while juggling their own responsibilities. Stuart learned to address this directly by outlining how the PO's behavior affected the team and delivery, asking "Can I help you?" The PO initially reacted defensively but eventually admitted they weren't happy in the role. Self-reflection Question: How effectively does your Product Owner use storytelling to create clarity and help the team understand the value of their work? [Scrum Master Toolbox Podcast Recommends] 🚀 Global Agile Summit 2025 Join us in Tallinn, Estonia, from May 18th – 20th, 2025, for an event that will inspire, challenge, and equip you with real-world Agile success stories. 🌍 Connect with global Agile leaders. 💡 Learn practical strategies for impact. 🔥 Break free from Agile fatigue and become a Pragmatic Innovator Check Full Program [Scrum Master Toolbox Podcast Recommends] About Stuart Tipples Stuart is an Agilista, a coach, Scrum Master, agile delivery. A husband, Dog Dad, and as Star Wars nerd. Positive disruptor. Passionate about helping teams and individuals build and ship awesome products to their customers. Stuart also blogs at www.yourebelscrum.com You can link with Stuart Tipples on LinkedIn .…

Scrum Master Toolbox Podcast: Agile storytelling from the trenches

1
Happy Teams Embrace Obstacles—Building Psychological Safety Through Retrospectives | Stuart Tipples 14:36

לפני יומיים14:36

14:36

Stuart Tipples: Defining Scrum Master Success and the 4L's Retrospective 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 . Stuart redefines success for Scrum Masters, moving beyond organized JIRA boards and well-structured stories to focus on team dynamics and behavior. True success means seeing healthy conflict that leads to insight, having transparent priorities, and watching teams call out their own behavior through self-checking mechanisms. Stuart emphasizes that happy teams aren't just content - they're energized by embracing obstacles and challenges. He stresses the importance of reinforcing great behaviors when you see them, creating an environment where teams can thrive independently. Featured Retrospective Format for the Week: 4L's The 4L's retrospective format is Stuart's favorite because it strikes the perfect balance between warmth and honest feedback. The format covers four areas: Liked (appreciation), Learned (growth opportunities), Lacked (identifying gaps), and Longed for (dreaming big). This structure prevents people from freezing up while uncovering golden moments and building psychological safety. As a bonus, the format allows facilitators to bring fun elements and themes, making retrospectives more engaging while maintaining their effectiveness in driving team improvement. Self-reflection Question: Does your team demonstrate healthy conflict that leads to insight, or are disagreements avoided and issues left unresolved? [Scrum Master Toolbox Podcast Recommends] 🚀 Global Agile Summit 2025 Join us in Tallinn, Estonia, from May 18th – 20th, 2025, for an event that will inspire, challenge, and equip you with real-world Agile success stories. 🌍 Connect with global Agile leaders. 💡 Learn practical strategies for impact. 🔥 Break free from Agile fatigue and become a Pragmatic Innovator Check Full Program [Scrum Master Toolbox Podcast Recommends] About Stuart Tipples Stuart is an Agilista, a coach, Scrum Master, agile delivery. A husband, Dog Dad, and as Star Wars nerd. Positive disruptor. Passionate about helping teams and individuals build and ship awesome products to their customers. Stuart also blogs at www.yourebelscrum.com You can link with Stuart Tipples on LinkedIn .…

Scrum Master Toolbox Podcast: Agile storytelling from the trenches

1
Leading Change Without Hierarchical Power | Stuart Tipples 15:54

לפני 3 ימים15:54

15:54

Stuart Tipples: Beyond Hierarchy—Influencing Agile Adoption Through Setting the Example and Community 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 . Stuart explores the challenging aspect of leading change as a Scrum Master without hierarchical authority. He shares his experience as a chapter lead where he built a community of practice and recruited new Scrum Masters to become change agents. The breakthrough came when he convinced director-level leaders to run their own quarterly retrospectives, creating a powerful example for teams throughout the organization. Stuart emphasizes that change spreads organically - when you change your team, it becomes contagious. His approach involved showing up daily as a change agent, understanding the difference between sponsors and change agents, and initially facilitating leadership retrospectives to demonstrate proper technique. Self-reflection Question: How can you leverage community building and lead by example to create lasting organizational change without relying on formal authority? [Scrum Master Toolbox Podcast Recommends] 🚀 Global Agile Summit 2025 Join us in Tallinn, Estonia, from May 18th – 20th, 2025, for an event that will inspire, challenge, and equip you with real-world Agile success stories. 🌍 Connect with global Agile leaders. 💡 Learn practical strategies for impact. 🔥 Break free from Agile fatigue and become a Pragmatic Innovator Check Full Program [Scrum Master Toolbox Podcast Recommends] About Stuart Tipples Stuart is an Agilista, a coach, Scrum Master, agile delivery. A husband, Dog Dad, and as Star Wars nerd. Positive disruptor. Passionate about helping teams and individuals build and ship awesome products to their customers. Stuart also blogs at www.yourebelscrum.com You can link with Stuart Tipples on LinkedIn .…

Scrum Master Toolbox Podcast: Agile storytelling from the trenches

1
Trust-Based Leadership and Team Implosion | Stuart Tipples 17:25

לפני 4 ימים17:25

17:25

Stuart Tipples: Silent Teams, Explosive Outcomes—Learning to Normalize Disagreement 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 . Stuart tells the story of a team he was brought in to coach that appeared functional on the surface but was struggling beneath. Despite being behind on critical work, the team maintained a facade of happiness while abandoning retrospectives and falling into hero culture patterns. The team had developed "toxic positivity" where members stayed silent about real issues, creating an environment without psychological safety. When problems finally surfaced, the team exploded into unpleasant disagreements. Stuart's key learning: teams usually stay silent until it's too late, making it crucial to foster psychological safety by normalizing disagreement and creating space for honest dialogue. Self-reflection Question: Is your team comfortable with healthy disagreement, or are you maintaining a facade of toxic positivity that prevents real issues from being addressed? Featured Book of the Week: Trust Based Leadership by Mike Ettore Trust Based Leadership by Mike Ettore stands out because it's devoid of corporate fluff and delivers a clear message from a former marine turned executive. Stuart recommends it because it focuses on the fundamental truth that if you don't build trust, you're just managing compliance. The book emphasizes leading with consistency, clarity, and courage, and encourages leaders not to wait for permission to make positive changes. It's a practical guide that moves beyond typical corporate leadership advice to address real-world leadership challenges. [Scrum Master Toolbox Podcast Recommends] 🚀 Global Agile Summit 2025 Join us in Tallinn, Estonia, from May 18th – 20th, 2025, for an event that will inspire, challenge, and equip you with real-world Agile success stories. 🌍 Connect with global Agile leaders. 💡 Learn practical strategies for impact. 🔥 Break free from Agile fatigue and become a Pragmatic Innovator Check Full Program [Scrum Master Toolbox Podcast Recommends] About Stuart Tipples Stuart is an Agilista, a coach, Scrum Master, agile delivery. A husband, Dog Dad, and as Star Wars nerd. Positive disruptor. Passionate about helping teams and individuals build and ship awesome products to their customers. Stuart also blogs at www.yourebelscrum.com You can link with Stuart Tipples on LinkedIn .…

Scrum Master Toolbox Podcast: Agile storytelling from the trenches

1
Breaking Free from Zombie Scrum | Stuart Tipples 15:14

לפני 5 ימים15:14

15:14

Stuart Tipples: From Zombie Scrum to Agile Thinking—Learning from a Failed 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 . Stuart shares a powerful story about joining a team that appeared to be thriving with Scrum ceremonies in place, only to discover they were performing "zombie scrum" - going through the motions without embracing agile thinking. The team functioned as a feature factory, never questioning requirements or truly collaborating. Stuart learned that agile isn't about what you do, but how you and the team think. He emphasizes that frameworks are just guardrails; the real focus must be on coaching people in agile values and principles. His key insight: know the rules before you break them, and remember that no amount of ceremony can rescue a team that lacks the agile mindset. Self-reflection Question: Are your team's agile ceremonies creating real value and fostering collaboration, or are you simply going through the motions of "performative theatre"? [Scrum Master Toolbox Podcast Recommends] 🚀 Global Agile Summit 2025 Join us in Tallinn, Estonia, from May 18th – 20th, 2025, for an event that will inspire, challenge, and equip you with real-world Agile success stories. 🌍 Connect with global Agile leaders. 💡 Learn practical strategies for impact. 🔥 Break free from Agile fatigue and become a Pragmatic Innovator Check Full Program [Scrum Master Toolbox Podcast Recommends] About Stuart Tipples Stuart is an Agilista, a coach, Scrum Master, agile delivery. A husband, Dog Dad, and as Star Wars nerd. Positive disruptor. Passionate about helping teams and individuals build and ship awesome products to their customers. Stuart also blogs at www.yourebelscrum.com You can link with Stuart Tipples on LinkedIn .…

Scrum Master Toolbox Podcast: Agile storytelling from the trenches

1
The No-Scroll Bar Rule—Empowering PO’s Through Constraints | Joel Bancroft-Connors 19:17

לפני 8 ימים19:17

19:17

Joel Bancroft-Connors: The No-Scroll Bar Rule—Empowering PO’s Through Constraints 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 Collaborative Innovator Joel describes an exceptional Product Owner scenario at a large insurance organization where complementary skills created magic. Working with two different people - a business expert who understood insurance but lacked development knowledge, and a designer with user experience expertise - Joel suggested the designer take on the Product Owner role while collaborating closely with the business person. This collaboration between complementary skills produced outstanding results. The great Product Owner understood that their role wasn't to control every detail but to unleash developer creativity by providing problems and context rather than prescriptive solutions. Joel's approach of "give the developers a problem and a canvas" allowed the team to innovate while staying focused on customer needs. This Product Owner fostered innovation rather than preventing it, demonstrating how effective collaboration can transform product development. The Bad Product Owner: The Business Analyst That Couldn’t Let Go Joel identifies a problematic anti-pattern: the Business Analyst who transitions to Product Owner but can't abandon their documentation-heavy approach. While Business Analysts can make excellent Product Owners with proper support, those who insist on documenting everything create communication bottlenecks and slow down delivery. This creates a "telephone game" effect between the BA/PO and developers. Joel encountered one such individual who would declare "the developers can't do that" without giving them the opportunity to explore solutions. Following his "no-scroll bar rule" for documentation, Joel emphasizes that Product Owners should provide just enough information to enable developer creativity, not overwhelming detail that stifles innovation. When the problematic BA was replaced with someone who understood customers and trusted developers, the team's innovation flourished. In this segment, we refer to the book Liftoff, by Larsen and Nies . Self-reflection Question: Are you enabling developer innovation by providing problems and context, or are you stifling creativity with excessive documentation and control? [Scrum Master Toolbox Podcast Recommends] 🚀 Global Agile Summit 2025 Join us in Tallinn, Estonia, from May 18th – 20th, 2025, for an event that will inspire, challenge, and equip you with real-world Agile success stories. 🌍 Connect with global Agile leaders. 💡 Learn practical strategies for impact. 🔥 Break free from Agile fatigue and become a Pragmatic Innovator Check Full Program [Scrum Master Toolbox Podcast Recommends] About Joel Bancroft-Connors Joel Bancroft-Connors is The Gorilla Coach — a Certified Scrum Trainer and Agile disruptor focused on sustainable value and effectiveness. With a background in product, project, and coaching, Joel blends sharp insights with practical tools to help teams thrive. He is a Miro power user and rocks curated classroom playlists. You can link with Joel Bancroft-Connors on LinkedIn .…

Scrum Master Toolbox Podcast: Agile storytelling from the trenches

1
Sustainable Value—Redefining Success Beyond Profit | Joel Bancroft-Connors 17:24

לפני 9 ימים17:24

17:24

Joel Bancroft-Connors: Sustainable Value—Redefining Success Beyond Profit 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 . Joel has evolved his definition of Scrum Master success over time, moving beyond traditional metrics to focus on what truly matters: sustainable value delivery. While Agile principles clearly state the goal of delivering value continuously, Joel emphasizes that success isn't just about making profit - it's about creating sustainable profit through sustainable processes and people practices. He challenges Scrum Masters to consider their "people sustainability metric" and asks whether their approach supports long-term team health and organizational resilience. Joel's definition encompasses three pillars: delivering sustainable value, maintaining sustainable processes, and ensuring sustainability for people. This holistic view of success requires Scrum Masters to think beyond immediate outcomes and consider the long-term impact of their practices. In this segment, we refer to the book Turn the ship around! by David Marquet . Self-reflection Question: What is your people sustainability metric, and how are you measuring whether your Scrum practices support long-term team and organizational health? Featured Retrospective Format for the Week: Back to Basics Joel advocates for returning to the foundational retrospective format outlined in "Agile Retrospectives" by Derby and Larsen. Rather than getting caught up in complex or creative retrospective techniques, he emphasizes the power of following the basic steps: set the stage, gather data, generate insights, decide what to do, and close the retrospective. Joel stresses that there's an important arc to retrospectives that shouldn't be overlooked. By taking time to properly gather data and following the structured approach from the agile retrospectives book, teams can achieve more meaningful and actionable outcomes. Sometimes the most effective approach is simply executing the fundamentals exceptionally well. In this segment, we refer to the book Agile retrospectives, by Derby and Larsen . [Scrum Master Toolbox Podcast Recommends] 🚀 Global Agile Summit 2025 Join us in Tallinn, Estonia, from May 18th – 20th, 2025, for an event that will inspire, challenge, and equip you with real-world Agile success stories. 🌍 Connect with global Agile leaders. 💡 Learn practical strategies for impact. 🔥 Break free from Agile fatigue and become a Pragmatic Innovator Check Full Program [Scrum Master Toolbox Podcast Recommends] About Joel Bancroft-Connors Joel Bancroft-Connors is The Gorilla Coach — a Certified Scrum Trainer and Agile disruptor focused on sustainable value and effectiveness. With a background in product, project, and coaching, Joel blends sharp insights with practical tools to help teams thrive. He is a Miro power user and rocks curated classroom playlists. You can link with Joel Bancroft-Connors on LinkedIn .…

Scrum Master Toolbox Podcast: Agile storytelling from the trenches

1
The 90-Day Rule—Building Trust Before Disrupting the Status Quo | Joel Bancroft-Connors 14:20

לפני 10 ימים14:20

14:20

Joel Bancroft-Connors: The 90-Day Rule—Building Trust Before Disrupting the Status Quo 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 . Joel shares his first experience as a CSM at a traditional hard drive manufacturing company, where he learned the art of patient change management. Tasked with bridging the gap between a rigid mothership company and their agile startup division, Joel discovered the power of focusing on principles rather than processes. For six months, he concentrated on creating transparency and shifting focus from status reporting to "getting to done" without ever mentioning Scrum or Agile. His approach followed what he calls the 90-day rule: "In the first 90 days - do no harm, but then have a plan to do something." By listening first and building trust, Joel helped the team deliver a product in just three months. He emphasizes the importance of making people feel valued and using "future perfect thinking" to envision desired outcomes before introducing change. In this episode we refer to Luke Hohmann’s Innovation Games, the website and resource Manager-Tools.com , and Daniel Pink’s book Drive . Self-reflection Question: Are you rushing to implement changes, or are you taking time to build trust and understand the current state before introducing new practices? [Scrum Master Toolbox Podcast Recommends] 🚀 Global Agile Summit 2025 Join us in Tallinn, Estonia, from May 18th – 20th, 2025, for an event that will inspire, challenge, and equip you with real-world Agile success stories. 🌍 Connect with global Agile leaders. 💡 Learn practical strategies for impact. 🔥 Break free from Agile fatigue and become a Pragmatic Innovator Check Full Program [Scrum Master Toolbox Podcast Recommends] About Joel Bancroft-Connors Joel Bancroft-Connors is The Gorilla Coach — a Certified Scrum Trainer and Agile disruptor focused on sustainable value and effectiveness. With a background in product, project, and coaching, Joel blends sharp insights with practical tools to help teams thrive. He is a Miro power user and rocks curated classroom playlists. You can link with Joel Bancroft-Connors on LinkedIn .…

Scrum Master Toolbox Podcast: Agile storytelling from the trenches

1
How Performance Reviews Killed a Great Agile Team | Joel Bancroft-Connors 12:52

לפני 11 ימים12:52

12:52

Joel Bancroft-Connors: How Performance Reviews Killed a Great Agile Team Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes . Joel tells the story of a team caught in the crossfire of a poorly executed large-scale agile transformation. While the CTO championed going agile, they quickly checked out, leaving the organization without clear direction or understanding of why they were adopting agile practices. The company measured success through output metrics like "number of teams trained" rather than meaningful outcomes. Joel worked with an exceptional team that had built their own collaborative workspace and was performing well, but external forces kept pulling them out of flow. Performance reviews created internal conflict, leading team members to focus on individual success rather than collective achievement. The team ultimately fell into their own traps, with everyone "focusing on themselves and throwing others under the bus." Joel recommends balancing performance evaluations with 50% team-based and 50% individual metrics to prevent this destructive pattern. Self-reflection Question: Does your team truly understand why they are using Scrum, or are they just going through the motions of the framework? Featured Book of the Week: Start with Why by Simon Sinek Joel credits Simon Sinek's "Start with Why" as a transformational influence on his coaching approach. The book's central principle that "people don't buy what you do, they buy why you do it" fundamentally changed how Joel teaches Scrum. He realized he had been teaching Scrum incorrectly by focusing on the mechanics rather than the purpose. Now Joel listens to this book annually and has shifted his focus to helping teams and organizations understand why Scrum matters and why it's important. This shift from teaching the "what" to emphasizing the "why" has made his coaching significantly more effective and meaningful. Joel also mentions the book Coaching Agile Teams by Lyssa Adkins . [Scrum Master Toolbox Podcast Recommends] 🚀 Global Agile Summit 2025 Join us in Tallinn, Estonia, from May 18th – 20th, 2025, for an event that will inspire, challenge, and equip you with real-world Agile success stories. 🌍 Connect with global Agile leaders. 💡 Learn practical strategies for impact. 🔥 Break free from Agile fatigue and become a Pragmatic Innovator Check Full Program [Scrum Master Toolbox Podcast Recommends] About Joel Bancroft-Connors Joel Bancroft-Connors is The Gorilla Coach — a Certified Scrum Trainer and Agile disruptor focused on sustainable value and effectiveness. With a background in product, project, and coaching, Joel blends sharp insights with practical tools to help teams thrive. He is a Miro power user and rocks curated classroom playlists. You can link with Joel Bancroft-Connors on LinkedIn .…

Scrum Master Toolbox Podcast: Agile storytelling from the trenches

1
When Great Scrum Masters Fail—The Hidden Cost of Poor Value Communication | Joel Bancroft-Connors 15:24

לפני 12 ימים15:24

15:24

Joel Bancroft-Connors: When Great Scrum Masters Fail—The Hidden Cost of Poor Value 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 . Joel shares a powerful lesson about the critical importance of communicating value beyond team performance. Despite achieving remarkable success with multiple teams as an agile coach, Joel and his colleagues ultimately failed because they couldn't effectively demonstrate their value to leadership. The teams were thriving, but when budget cuts came, the coaching support was eliminated first. Without ongoing support, these successful teams began to deteriorate. Joel emphasizes that as Scrum Masters and agile coaches, we must actively communicate our impact and connect team success to business outcomes. Simply assuming that good team performance speaks for itself is not enough - we need to interact more with stakeholders and clearly articulate the value we create. In this episode, we refer to the TV series Ted Lasso , and the books Start with Why by Simon Sinek , and Coaching Agile Teams by Lyssa Adkins . Self-reflection Question: How effectively are you communicating the business value of your Scrum Master activities to leadership, and what specific metrics or stories could better demonstrate your impact? [Scrum Master Toolbox Podcast Recommends] 🚀 Global Agile Summit 2025 Join us in Tallinn, Estonia, from May 18th – 20th, 2025, for an event that will inspire, challenge, and equip you with real-world Agile success stories. 🌍 Connect with global Agile leaders. 💡 Learn practical strategies for impact. 🔥 Break free from Agile fatigue and become a Pragmatic Innovator Check Full Program [Scrum Master Toolbox Podcast Recommends] About Joel Bancroft-Connors Joel Bancroft-Connors is The Gorilla Coach — a Certified Scrum Trainer and Agile disruptor focused on sustainable value and effectiveness. With a background in product, project, and coaching, Joel blends sharp insights with practical tools to help teams thrive. He is a Miro power user and rocks curated classroom playlists. You can link with Joel Bancroft-Connors on LinkedIn .…

Scrum Master Toolbox Podcast: Agile storytelling from the trenches

1
BONUS Martti Kuldma: How to Transform Century-Old Organizations Through Product-Driven Agile Transformation 44:05

לפני 14 ימים44:05

44:05

BONUS: Martti Kuldma shares how to transform century-old organizations through product-driven agile transformation In this BONUS episode we explore the remarkable transformation journey at Omniva with CEO Martti Kuldma. From traditional postal services to innovative logistics solutions, we explore how a 100+ year old company embraced product thinking, DevOps practices, and agile transformation to become a competitive force in modern logistics. Omniva's Digital Evolution—IT as a Revenue Center "We innovated the parcel machine business for a few years, and software has been an area of investment for us - software as a separate vertical in our business." Omniva represents a fascinating case study in organizational transformation. While many know it as Estonia's post office, the company has evolved into an international logistics powerhouse with significant revenue streams beyond traditional postal services. Under Martti's leadership, the organization has reimagined software not as a support function but as a core revenue driver, positioning itself for the dramatic shifts expected in logistics delivery over the next five years. The Vision: Physical Mailing as the Next IP Network "The Vision: physical mailing as the next IP network - this will give us a lot more freedom to adapt to changes in delivery demand." Martti's strategic vision extends far beyond conventional logistics thinking. By conceptualizing physical delivery networks similar to internet protocols, Omniva is preparing for a future where logistics companies leverage their physical infrastructure advantages. This approach addresses the fundamental challenge of fluctuating demand in e-commerce and traditional logistics, creating opportunities for crowd delivery solutions and gig economy integration that capitalize on existing network effects. Breaking Down Waterfall Barriers "When I came we had waterfall processes - annual budgeting, procurement for software development. It took a couple of weeks to do the first rounds, and understand what could be improved." The transformation from traditional procurement-based software development to agile product teams required dismantling entrenched processes. Martti discovered that the contractor model, while seemingly cost-effective, created expensive knowledge transfer cycles and left the organization vulnerable when external teams departed. His engineering background enabled him to recruit talent and build sustainable development capabilities that keep critical knowledge within the organization. Creating Cross-Functional Product Teams "We started to create cross-functional product area teams. We are not going to tell you what you need to build. You are accountable for the logistics efficiency." The shift from eleven distinct roles in software development to autonomous product teams represents more than organizational restructuring. By empowering teams with accountability for business outcomes rather than just deliverables, Omniva transformed how work gets planned and executed. This approach eliminates traditional handoffs and role silos, creating teams that own both the problem and the solution. The Product Manager Evolution "For me, the PM is directly accountable for the business results. The final step of the transformation started when I took the CEO role." Martti identifies a critical challenge in agile transformations: the misunderstanding of Product Manager responsibilities. Rather than falling into delivery or project management patterns, effective PMs at Omniva own business results directly. This shift required company-wide transformation because technical changes alone cannot sustain organizational evolution without corresponding changes in mindset and accountability structures. Leadership Through Storytelling "My main tool is just talking. All I do is story-telling internally and externally. I needed to become the best salesman in the company." The transition from technical leadership to CEO revealed that transformation leadership requires different skills than technical management. Martti discovered that his primary value comes through narrative construction and communication rather than direct technical contribution. This realization highlights how senior leaders must evolve their impact methods as organizations scale and transform. Real-Time Feedback Philosophy "The feedback needs to be given immediately. ‘Last year, in May your performance was not the best’ - this is completely useless feedback." Martti's rejection of annual reviews stems from practical experience with feedback effectiveness. Immediate, personal feedback creates learning opportunities and course corrections that annual cycles cannot provide. Anonymous 360 feedback systems often dilute accountability and actionability, whereas direct, timely conversations enable meaningful professional development and relationship building. Essential Transformation Practices "You need to tell the story - and convince people that this transformation is essential and needed. You need to trust and let them make their own decisions." Drawing from experiences at both Pipedrive and Omniva, Martti identifies three critical elements for leading complex organizational change: Compelling narrative: People need to understand why transformation is necessary and how it benefits both the organization and their individual growth Distributed decision-making: Trust enables teams to solve problems creatively rather than waiting for hierarchical approval Business accountability for engineers: When technical teams understand and own business outcomes, they innovate more effectively toward meaningful goals The dynamic team formation model used at Pipedrive, where engineers and PMs pitched ideas and assembled mission-focused teams, demonstrates how organizational structure can enable rather than constrain innovation. About Martti Kuldma Martti Kuldma is CEO of Omniva, leading its transformation into a product-driven logistics company. A former engineering leader at Pipedrive and CTO at Omniva, he brings deep expertise in scaling teams, agile transformation, and digital innovation. Martti is also a startup founder and passionate advocate for high-impact product organizations. You can link with Martti Kuldma on LinkedIn.…

Scrum Master Toolbox Podcast: Agile storytelling from the trenches

1
BONUS Entertainment That Makes Change: Lessons in Product Thinking from Believe Ltd. With Patrick James Lynch 41:43

לפני 16 ימים41:43

41:43

BONUS: Patrick James Lynch on Entertainment That Makes Change - Lessons in Product Thinking from Believe Ltd. In this BONUS episode we explore how Patrick James Lynch, filmmaker, media executive, and rare disease advocate, has built Believe Limited around a powerful mission: entertainment that effects change. Patrick shares his journey from personal experience with his brother's hemophilia to creating award-winning content that empowers rare and chronic disease communities, offering valuable lessons for product managers on human-centered design, stakeholder alignment, and building emotionally viable products. The Genesis of Entertainment That Effects Change "This is more than a product." Patrick's journey began with a deeply personal question about his brother who had hemophilia. As an entrepreneur, he set out to respond to an identified need with one product to meet that need, but quickly realized the scope was much larger. His curiosity about what was different between him and his brother led him to understand that he needed to help people like his brother. This realization drove him to create valuable online videos to engage their audience, marking the beginning of Believe Ltd.'s mission of entertainment that effects change. Essential Product Lessons: Listen, Learn, and Do No Harm "The fact that I am my audience, does not mean that I'm an expert." Patrick emphasizes the critical importance of conducting thorough needs assessments and truly understanding your community before building products. Key insights include: Embed yourself in the community you're serving rather than making assumptions Follow the principle of "listen, learn and do no harm" as your starting point Involve community engagement as a dedicated role - Believe Ltd. has a VP of community engagement Define clear phrases that explain the value you deliver to your audience Use your personal story to establish credibility and relate experiences to your audience The goal is to get as familiar with your community as possible, then conduct your own research and development based on those deep insights. Navigating Multi-Stakeholder Complexity "Collaboration only succeeds when all points of view are respected." Working with patients, funders, healthcare professionals, and pharmaceutical companies requires careful orchestration. Patrick's approach centers on prioritizing the end game and identifying the north star goal that aligns all parties. He emphasizes focusing on combined skills and networks rather than trying to accomplish everything at the start. The key is ensuring that aligning stakeholders becomes a central part of the process, with everyone being accounted for throughout the journey. Human-Centered Storytelling as Product Strategy "What's the story that shows the value add of your product?" Patrick advocates for human-centered storytelling as a fundamental product approach. Rather than leading with features or specifications, he suggests crafting stories that demonstrate real value - like how a thermos saved someone's life while hiking. Stories have been humanity's primary communication tool since the beginning of time, and they remain the most effective way to show product value and connect with audiences on a meaningful level. Being a Value Fundamentalist "At any given moment, if anyone takes a screen grab, and set it against our five core values as a company - you see it's playing out." Patrick describes himself as a value fundamentalist, meaning that their company's core values are always present in everything they do. This requires courage, including the willingness to say "no" when opportunities don't align with their values. As CEO, he believes in embodying these values consistently, even when it's challenging, because who they are must always be visible in their work. Balancing Vision with Community Feedback "When you ask the audience for a solution, there's no innovation." Patrick warns against sacrificing vision simply because you're working closely with your audience. While being in the sandbox with your community is essential, maintaining your original vision for entertainment that changes minds is equally important. He recommends having someone you can bounce ideas off to help maintain this balance, and remembers that all great things start small and are inherently iterative. Creating Emotionally Viable Products "We can't develop emotional connection by going through a list of features." Beyond minimum viable products, Patrick focuses on emotional viability - the hook that makes people truly care. Emotional connection cannot be built through feature lists but rather through compelling stories that capture people's imagination. When audiences engage with products outside of direct supervision, storytelling becomes the bridge that helps them discover new uses and applications. This creates a dance between product creators and their audience, leading to better product design. The Currency of Attention "Attention is the only currency - there's great wisdom in that." Patrick recognizes that in today's landscape, capturing and maintaining attention is the fundamental challenge. Since everyone is an audience member at different times, this perspective helps inform both strategy and tactics. Products must compete not just on functionality but on their ability to engage and maintain audience interest over time. As a recommended reading, Patrick suggests that we should read “Save The Cat! The Last Book on Screenwriting You'll Ever Need” to understand how to better tell stories about our products. About Patrick James Lynch Patrick James Lynch is a filmmaker, media executive, and rare disease advocate. CEO of Believe Limited and founder of BloodStream Media, he uses his experience with hemophilia to drive award-winning storytelling, health advocacy, and mission-driven content that inspires and empowers rare and chronic disease communities worldwide. You can link with Patrick James Lynch on LinkedIn and follow Patrick James Lynch’s work on his website .…

Scrum Master Toolbox Podcast: Agile storytelling from the trenches

1
BONUS The Startup CTO's Handbook With Zach Goldberg 41:01

לפני 17 ימים41:01

41:01

BONUS: Zach Goldberg shares how to build high-performing engineering teams and master the startup CTO role In this BONUS episode, we dive deep into the world of startup leadership with Zach Goldberg, author of The Startup CTO's Handbook . We explore the critical transition from engineering to leadership, the art of balancing technical debt with startup urgency, and the communication skills that separate great CTOs from the rest. The Genesis of The Startup CTO's Handbook "My original training in software engineering was not enough for being a leader. All the people and leadership skills, I had to learn on my own." Zach's journey to writing The Startup CTO's Handbook began with a stark realization about the gap between technical training and leadership reality. Despite his classical software engineering background, he discovered that the people and leadership skills required for CTO success had to be self-taught. The book emerged from a growing Google Doc of topics and frameworks addressing the leadership and management challenges that CTOs consistently face - from hiring and performance management to making strategic decisions under pressure. Today, we can either buy the digital/print book on Amazon, or read the book on GitHub . In this segment, we also refer to the book The Great CEO Within . Learning to Truly Learn: The Max Mintz Story "Max only cared about my ability to learn - to get curious about something hard. He wanted to help me deal with complexity." Zach opens his book with a deeply personal story about his mentor, Max Mintz, who fundamentally changed his approach to learning during what he calls "the most impactful single coffee" of his life. Over 1.5 years of conversations, Max taught him that true learning isn't about accumulating facts, but about developing curiosity for hard problems and building the capacity to handle complexity. This lesson forms the foundation of effective CTO leadership - the ability to continuously learn and adapt in an ever-changing technical landscape. The Three Critical CTO Mistakes "As a CTO, the most important 3 things: people, people, people. Do the people have the right energy, the right passion? Assemble the right team." Zach identifies consistent patterns in startup CTO failures across his experience. The first and most critical mistake is undervaluing people decisions - failing to prioritize team energy, passion, and the right assembly of talent. The second category involves investment mistakes, particularly the challenge of balancing short-term survival needs with long-term technical goals. In startups, the ROI timespan is exceptionally short, requiring optimization for immediate objectives rather than hypothetical scale. The third mistake is treating technology as religion rather than tools, losing sight of what the business actually needs. Optimizing for Velocity and Developer Experience "You are optimizing for velocity! What are you doing to help developers get their work done? Look at developer experience as a metric." Successful startup CTOs understand that velocity - the time from idea to valuable market delivery - is paramount. This requires a fundamental shift in thinking about technology decisions, focusing on features that deliver real customer value rather than technical elegance. Zach emphasizes measuring developer experience as a key metric, recognizing that anything that helps developers work more effectively directly impacts the company's ability to survive and thrive in competitive markets. The Professional Skill Tree Concept "It's like a character progression in an RPG. When we learn one type of skills, we don't learn other types of skills. We make investments every day and we have a choice on where we learn." Drawing from gaming metaphors, Zach explains how technical professionals often reach Level 100 in engineering skills while remaining Level 1 in management. The skill tree concept highlights that every learning investment is a choice - time spent developing one skill area means less time available for others. For engineers transitioning to leadership, the key is recognizing opportunities to serve as tech leads, where they can begin setting culture and quality standards while still leveraging their technical expertise. Balancing Kaizen with Startup Urgency "Pick the high-impact debt, and pay that down. This is not always easy, especially because we also need to pick what debt we don't invest on." The tension between continuous improvement and startup speed requires sophisticated thinking about technical debt. Using financial analogies, Zach explains that technical debt has both principal and interest components. The key is identifying which debt carries the highest interest rates and can be paid down most quickly, while consciously choosing which debt to carry forward. This approach maintains the healthy tension between quality and speed that defines successful startup engineering. The Power of Audience Empathy "The single hardest skill, especially for very tech leaders is that of 'audience empathy.' When you explain ideas to people, you usually assume a lot - but they might not." According to Zach, the most undervalued communication habit for startup tech leaders is developing audience empathy. Technical leaders often suffer from the curse of knowledge, assuming their audience shares their context and understanding. The solution requires deliberately considering what the audience already knows before crafting any communication, whether it's explaining technical concepts to non-technical stakeholders or providing clear direction to team members. In this segment we refer to the concept of “ the curse of knowledge ”, a cognitive bias that occurs when a person who has specialized knowledge assumes that others share in that knowledge. About Zach Goldberg Zach Goldberg is a seasoned technical entrepreneur, executive coach, and author of The Startup CTO's Handbook. With a founder's mentality and a passion for systems thinking, Zach helps engineering leaders build high-performing teams. He also founded Advance The World, a nonprofit inspiring youth in STEM through immersive experiences. You can link with Zach Goldberg on LinkedIn , and visit Zach’s website at CTOHB.com .…

Scrum Master Toolbox Podcast: Agile storytelling from the trenches

1
BONUS Tom Gilb: Building True Engineering Culture and Delivering Value Through Evolutionary Methods 42:39

לפני 18 ימים42:39

42:39

BONUS: Tom Gilb on Building True Engineering Culture and Delivering Value Through Evolutionary Methods In this BONUS episode, we dive deep into the world of true engineering discipline with Tom Gilb, a pioneer who was writing about Agile principles before Agile was even named. We explore his latest book "Success - Super Secrets & Strategies for Efficient Value Delivery in Projects and Programs, and Plans" and uncover the fundamental flaws in how organizations approach project delivery and stakeholder management. The Genesis of Success-Focused Engineering "People were failing at project deliveries - even when using Agile. I saw there was very little about setting clear goals and reaching them, it had nothing to do with being successful." Tom's motivation for writing his latest book stems from a critical observation: despite the widespread adoption of Agile methodologies, project failure rates remain unacceptably high. The core issue isn't methodology but rather the fundamental lack of clarity around what success actually means. Tom emphasizes that true success is about achieving the improvements you want at a price you can afford, yet most organizations fail to define this clearly from the outset. In this segment, we refer to the book How Big Things Get Done by Bent Flyvbjerg who published statistics on the poor performance of projects in general. Beyond OKRs: The Power of Quantified Multi-Dimensional Objectives "First you need to have a definition of what it means to succeed. And that needs to be multi-dimensional. And you need to clarify what they are." While many organizations believe they're already quantifying objectives through frameworks like OKRs, Tom reveals significant weaknesses in these approaches. True value isn't just profit—it encompasses multiple dimensions including security, usability, and other stakeholder-specific benefits. The key insight is learning to quantify what needs to be achieved across all critical dimensions, as you simply cannot design for high-quality attributes like security without first quantifying and designing for them explicitly. In this segment, we talk about Tom’s paper on OKR’s titled "OKR Objectives and Key Results: what's wrong and how to fix it" . The Missing Engineering Discipline "Why is the failure rate of our projects so high?" Tom identifies a paradoxical problem: engineering organizations often lack true engineering discipline. This fundamental gap explains why project success rates remain low despite technological advances. Real engineering requires systematic approaches to design, stakeholder analysis, and incremental value delivery—disciplines that are often overlooked in favor of rushed implementations. Stakeholder Analysis: Beyond User Stories "Stakeholders have a requirement - even if we don't know it. They might be people, but also law, contract, policies, etc. They all have requirements for us." Traditional user-centered methods like user stories can lead to failure when critical stakeholders are overlooked. Tom advocates for comprehensive stakeholder analysis as the foundation of engineering discipline. Stakeholders aren't just people—they include laws, contracts, policies, and other constraints that have requirements for your system. The practical tip here is to use AI tools to help identify and list these stakeholders, then quantify their specific requirements using structured approaches like Planguage . The Gilb Cycle: True Incremental Value Delivery "Get things done every week, next week, until it's all done. We need to decompose any possible design into enough increments so that each increment delivers some value." What distinguishes Tom's evolutionary approach from popular Agile frameworks is the focus on choosing the most efficient design and then systematically improving existing systems through measured increments. Each increment must deliver tangible value, and the decomposition process should be aided by AI tools to ensure optimal value delivery. This isn't just about iteration—it's about strategic improvement with measurable outcomes. Building Engineering Culture: A Two-Leader Approach "There are two leaders: the tech leaders and the management leaders. For management leaders: demand a value stream of results starting next week. To the tech leaders: learn the engineering process." Creating a true engineering culture requires coordinated effort from both management and technical leadership. Management leaders should demand immediate value streams with weekly results, while technical leaders must master fundamental engineering processes including stakeholder analysis and requirement quantification. This dual approach ensures both accountability and capability development within the organization. Further Resources During this episode we refer to several of Tom’s books and papers. You can see this list below Software Metrics by Tom Gilb Principles of software engineering management - Also available in PDF Evo book About Tom Gilb Tom Gilb, born in the US, lived in London, and then moved to Norway in 1958. An independent teacher, consultant, and writer, he has worked in software engineering, corporate top management, and large-scale systems engineering. As the saying goes, Tom was writing about Agile, before Agile was named. In 1976, Tom introduced the term "evolutionary" in his book Software Metrics, advocating for development in small, measurable steps. Today, we talk about Evo, the name that Tom used to describe his approach. You can link with Tom Gilb on LinkedIn .…

Scrum Master Toolbox Podcast: Agile storytelling from the trenches

1
BONUS Solution-Focused Coaching for Agile Teams With Ralph and Veronika 44:17

לפני 19 ימים44:17

44:17

BONUS: Solution-Focused Coaching: The Game-Changing Method Every Scrum Master Needs With Ralph Miarka and Veronika Jugwirth In this BONUS episode, we dive deep into solution-focused coaching with Ralph and Veronika, co-authors of "Solution Focused Coaching For Agile Teams." This conversation explores how to shift from problem-solving to solution-building, helping Agile teams thrive through a forward-looking approach that empowers teams to find their own path to success. Understanding Solution-Focused Coaching "Solution focus, focuses on the goal itself. We are not talking about 'how', but first start with 'what we want to achieve'." Solution-focused coaching represents a fundamental shift from traditional problem-solving approaches. Rather than diving into root cause analysis and retrospectives focused on what went wrong, this methodology centers on the future and desired outcomes. It operates as a communication system that recognizes the complexity of modern work environments where simple cause-effect relationships don't always apply. In engineering, root causes make sense when dealing with predictable systems, but in complex organizational dynamics, solution-focused coaching acknowledges that we often can't identify clear root causes and instead focuses on creating a "preferred future." In this segment we refer to Solution-focused brief therapy and the Cynefin model. The Power of Not-Knowing "Instead of suggesting solutions, we should start by asking questions. The “Not-knowing position” is about accepting this." The "not-knowing position" challenges coaches and leaders to resist the urge to immediately diagnose problems and offer solutions. When someone shares their story, they're not sharing the version we think we know. This approach transforms coaching conversations by starting with questions like "What difference would it make for you to solve this problem?" This shift toward asking questions about a positive future can even help identify advocates among those who initially resist change, creating unexpected allies in transformation efforts. Everyone as an Expert "When we help teams change by themselves, they change much faster." The principle that "everyone is an expert in their situation" fundamentally changes how coaches approach team dynamics, especially during periods of pressure or conflict. Instead of imposing external solutions, this approach involves asking teams what they already like about their current practices. For example, when observing daily standups with their natural diversity of approaches, focusing on what teams appreciate about their existing practices creates a foundation for sustainable change. Teams that discover their own path to improvement implement changes more rapidly and with greater commitment than those following prescribed solutions. The Miracle Question Technique "What would be a very small first sign that tells you that there was a small miracle during the night?" The Miracle Question emerges from real coaching conversations where clients express that "only a miracle can help." Rather than dismissing this statement, solution-focused coaches embrace the client's language to create powerful exploration opportunities. The technique involves asking teams to imagine their situation after a small miracle has occurred overnight, then identifying the first small signs they would notice. This approach helps teams explore possibilities and envision concrete steps toward their preferred future, making abstract goals tangible and achievable. Unlearning the Fix-It Mentality "Don't work by yourself in the problems of others, let them work." For Agile practitioners trained to identify and fix problems, solution-focused coaching requires a significant mindset shift. Instead of jumping into problem-solving mode, coaches must learn to hold space for solutions to emerge naturally from the team. This involves trusting that team members are experts in their own situations and developing strong questioning skills. Coaches and Scrum Masters need to clarify their own goals and resist the urge to solve problems for others, instead creating conditions where teams can work through challenges themselves. Practical Questions for Immediate Implementation "What do we want to achieve? What is our goal, and why?" Teams can immediately begin incorporating solution-focused approaches by bringing specific questions into their regular ceremonies. Key questions include exploring what the team wants to achieve and understanding the underlying purpose behind their goals. Additionally, asking "What works already?" helps teams build on existing strengths rather than focusing solely on problems. Confidence-building questions like "How confident are we?" and "What would make you more confident?" create opportunities for teams to identify specific actions that would increase their likelihood of success. About Ralph and Veronika Ralph Miarka is an Agile coach, trainer, and co-author of the book that is our topic for today's episode: Solution Focused Coaching For Agile Teams. Ralph helps teams thrive through solution-focused coaching. With a background in engineering and leadership, he bridges structure and empathy to spark real change. You can link with Ralph Miarka on LinkedIn. Veronika Jungwrith is a coach, consultant, and facilitator, Veronika blends solution-focused coaching with leadership development. Her work empowers individuals and teams to navigate complexity with clarity, meaning, and lasting impact. You can link with Veronika Jungwrith on LinkedIn.…

ברוכים הבאים אל Player FM!

Player FM סורק את האינטרנט עבור פודקאסטים באיכות גבוהה בשבילכם כדי שתהנו מהם כרגע. זה יישום הפודקאסט הטוב ביותר והוא עובד על אנדרואיד, iPhone ואינטרנט. הירשמו לסנכרון מנויים במכשירים שונים.