Podcasts about agile coach

What if the real power lies not in choosing a side—but in mastering both? We explore how blending agile and traditional project management is redefining success across industries.In this thought-provoking episode, I'm joined by Lenka Pinka, Chief of Staff to the CEO at Project Management Institute, and Sandy Mamoli, Agile Coach, former Olympian, and Agile Alliance board member, to unpack one of the most persistent tensions in the world of work: agile vs. traditional project management.But what if this debate is outdated—and even unhelpful?Together, Lenka and Sandy challenge the false binary and advocate for a more nuanced, collaborative approach. Drawing from their global experience across industries and methodologies, they explain how today's most successful organizations don't choose sides—they blend practices fluidly based on context, outcomes, and evolving needs.This conversation is full of compelling insights for both project professionals and agile practitioners. From fears of “agile dilution” to misconceptions about governance, we explore how shared values and a focus on delivery can bridge methodological divides. As Sandy puts it, the new PMI–Agile Alliance partnership is like "two fully whole, independent people who together create something magical."Whether you see yourself as a traditional project manager, a scrum master, or somewhere in between, this episode will reshape how you think about frameworks, governance, and the future of work. If you're ready to move past methodology wars and start focusing on what really drives success, this is your episode. Listen now, and join the conversation on how we can build better ways of working—together. In this episode, we discuss:0:00 Introduction and Guest Backgrounds10:41 PMI and Agile Alliance Partnerships18:11 Community Reactions and Concerns27:19 Product Management and Project Convergence39:38 Governance in Agile EnvironmentsSupport the showThank you for listening to Agile Ideas! If you enjoyed this episode, please share it with someone who might benefit from our discussions. Remember to rate us on your preferred podcast platform and follow us on social media for updates and more insightful content.Thank you for listening. If you enjoyed this episode, I'd really appreciate it if you could share it with your friends and rate us. Let's spread the #AgileIdeas together! We'd like to hear any feedback. www.agilemanagementoffice.com/contact Don't miss out on exclusive access to special events, checklists, and blogs that are not available everywhere. Subscribe to our newsletter now at www.agilemanagementoffice.com/subscribe. You can also find us on most social media channels by searching 'Agile Ideas'. Follow me, your host, on LinkedIn - go to Fatimah Abbouchi - www.linkedin.com/in/fatimahabbouchi/ For all things Agile Ideas and to stay connected, visit our website below. It's your one-stop destination for all our episodes, blogs, and more. We hope you found today's episode enlightening. Until next time, keep innovating and exploring new Agile Ideas!Learn more about podcast host Fatimah Abbouchi...

Deniz Ari: Why Great Product Owners Listen—Communication Lessons from Product Ownership Extremes The Great Product Owner: The Power of Clear Communication Deniz describes a truly exemplary Product Owner who excelled through outstanding communication skills. This PO was an exceptional listener who maintained openness throughout all interactions. They ensured the team thoroughly understood requirements and priorities, always clearly articulating the rationale behind decisions. With a well-defined product vision and transparent prioritization process, this PO successfully bridged the gap between the development team and clients. Deniz emphasizes how this clear communication style naturally fostered team motivation, as everyone understood not just what they were building, but why it mattered. The Bad Product Owner: The Tyrant PO Deniz shares a challenging experience with a problematic Product Owner during what initially appeared to be a straightforward public sector migration project with adequate budget and timeline. Despite these favorable conditions, the situation deteriorated when the PO began pushing the team to work overtime, overstepping boundaries by questioning architectural decisions, and inappropriately assuming Scrum Master responsibilities. Described as a "tyrant" or "despot," this PO exhibited extremely poor communication skills and preferred dictating rather than collaborating. When Deniz attempted to address these issues, the situation became so toxic that it affected Deniz's health, ultimately leading to their decision to leave the project. The PO subsequently claimed no Scrum Master was needed. Deniz reflects that sometimes the best option is to recognize when a situation cannot be changed and to move on. Self-reflection Question: What boundaries would you establish with a dominant Product Owner, and at what point would you decide that the situation cannot be improved? [The Scrum Master Toolbox Podcast Recommends]

Deniz Ari: Stakeholder Management Rhythms for Successful Scrum Masters Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. For Deniz, successful Scrum Masters create environments with positive team dynamics, easy communication, and a focus on continuous improvement that leads to valuable deliverables. The key indicators include whether team members can speak freely, whether there's trust between team members, and if the team feels like "a safe place to fail." Deniz recommends admitting your own mistakes in front of the team to model vulnerability, continuously observing team interactions, and noticing whether teams openly discuss obstacles. For stakeholder management, Deniz suggests establishing regular catch-up calls with leaders to keep team messages in the conversation and setting up routine discussions with stakeholders to maintain alignment. Featured Retrospective Format for the Week: The Worst Retro Deniz shares a playful yet effective retrospective format called "The Worst Retro," conducted using a MURAL board. The session begins with an energy/mood check to establish the team's current state. Then it moves into three key sections: what team members remember from the sprint, how they could make the next sprint worse, and finally deciding what actions to take next. Deniz explains that the power of this approach lies in using humor to discuss serious problems—by asking how to make things worse, team members can indirectly highlight what's already not working. This format creates an informal, relaxed environment where people feel comfortable addressing challenging topics that might otherwise remain unspoken. Self-reflection Question: How might introducing an element of humor or "reverse thinking" help your team discuss problems they've been avoiding in traditional retrospective formats? [The Scrum Master Toolbox Podcast Recommends]

Deniz Ari: Why Your Process Changes Are Failing—The Stakeholder Alignment Problem 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. Deniz explores the challenges of implementing change in organizations, emphasizing that change is always a long and difficult process requiring patience and trust. Drawing on the Change Curve concept, Deniz shares a personal experience trying to improve project visibility by cleaning up backlogs in JIRA for 10 in-flight projects. Despite good intentions, Deniz found themselves as the only person using the tool, with team members and Product Owners using different systems that better suited their specific needs—POs wanting only high-level items while the development team needed to split items into smaller tasks. Through this experience, Deniz learned the crucial importance of having all stakeholders (Product Owners, development teams, and managers) aligned on using the same tool, and understanding the unique perspectives of each group before implementing process changes. In this episode, we refer to the Change Curve.  Self-reflection Question: What changes have you attempted to implement that failed because you didn't fully understand the different needs and perspectives of all stakeholders involved? [The Scrum Master Toolbox Podcast Recommends]

Do you want to hear a story about stifling growth and creativity through the lens of one developer's personal story?You're in luck! Join Product Manager Brian Orlando and Enterprise Business Agility Coach Om Patel as they watch and react to Theo's YouTube video: "Being a good engineer kinda sucks," April 28, 2025.It's a tale about the tension between excelling at your craft versus navigating organizational politics and dysfunction. That's right, today, we're talking about themes of career development, team dynamics, and leadership, so feel free to stick around for our thoughts on these and:The sustainability trap of overworking to meet unrealistic expectationsHow organizational politics can punish innovation and excellenceThe importance of product sense vs. documentation-driven developmentFinding and nurturing relationships with like-minded professionals#Leadership #ProductManagement #CareerDevelopment #TechCareersLINKS= = = = = = = = = = = =YouTubeAppleSpotifyREFERENCES= = = = = = = = = = = =Check Out Theo's Video here: https://www.youtube.com/watch?v=3VuM1GCadt4...and his YouTube Channel: https://www.youtube.com/@t3dotgg...and his website: https://t3.gg/MUSIC= = = = = = = = = = = =Toronto Is My Beat (Music Sample)By Whitewolf (Source: https://ccmixter.org/files/whitewolf225/60181)CC BY 4.0 DEED (https://creativecommons.org/licenses/by/4.0/deed.en)

Deniz Ari: Security Team Breakdown—The Devastating Impact of Poor Product Ownership Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. Deniz shares the story of a security project with a team of eight experienced, senior engineers working on mission-critical systems. Despite initial motivation and clear architectural solutions, the team soon exhibited signs of negative behavior including complaints and criticism. The root cause traced back to frequent Product Owner changes—several within less than a year—and poor client management. Instead of shielding the team, the PO directly transferred stress from clients to the team, demanded overtime, and created unnecessary tension by bringing unfiltered conflicts to the team and requesting excessive details. Deniz emphasizes the importance of avoiding unnecessary tensions, being more political when necessary to protect the team, and being mindful of tone in written communications. Self-reflection Question: In what ways might you be failing to set proper boundaries in your role, and how could establishing clearer limits improve both your effectiveness and your team's performance? Featured Book of the Week: Boundaries by Henrik Cloud Deniz recommends "Boundaries" by Henrik Cloud, a book about human relationships and personal limitations. The book addresses crucial questions: Does your life feel out of control? Do you keep saying yes to everyone? Are you taking responsibility for others' feelings and problems? Have you forgotten your own limitations? Deniz explains how this book helped them learn to say "no" while still considering others' realities and feelings, and understanding why we often struggle with setting boundaries. Deniz highlights that being a Scrum Master involves much more than just processes and methods—it requires healthy personal boundaries. [Scrum Master Toolbox Podcast Recommends]

Deniz Ari: How Intense Delivery Pressure Destroyed Team Trust, Culture, and Brought Burnout 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. Working in the public sector, Deniz faced a challenging situation during a particularly busy winter period when the client wanted to combine multiple major initiatives simultaneously: migration, new features, and security improvements. This led to an oversized team of 25 engineers, which ultimately caused significant problems. The pressure to continuously deliver became overwhelming, breaking team trust and leaving members feeling abandoned. Several team members left, the team culture disintegrated, and cases of burnout emerged. After this difficult experience, Deniz conducted a comprehensive retrospective to process what happened and provide feedback to management about the dangers of excessive pressure in Scrum environments. Self-reflection Question: How might you recognize the early warning signs of team burnout before it reaches a critical point, and what boundaries would you establish to protect your team? [Scrum Master Toolbox Podcast Recommends]

EP141 - [Libro] El Arte del Agile Coaching, con Camilo Velasquez y Damián BuonamicoEn el hormiguero nuevamente vamos a hablar de un libro, nuevamente con sus autores, y nuevamente en modo premisa pues este libro aun no se publica.Nos referimos “El Arte del Agile Coaching”, de nuestros amigos Camilo Velasquez y Damián Buonamico.En este episodio platicaremos sobre la inspiración, la motivación y el contenido del libro: explorando desde los modelos tradicionales y en enfoque propio, el valor agregado del libro. Camilo y Damián también revelaron alguna que otra cosilla interesante que hasta ahora no la habían revelado, como por ejemplo de quién es el prologo del libro. También platicamos sobre el público objetivo, y si el libro tiene sentido o no para personas mas allá de los tradicionales roles ágiles, como Scrum Master y Agile Coach.Participan en este episodio, las hormigas: Antonio Gallardo Burgos, Arturo Robles Maloof y Rodrigo Burgos Noceti.Además nos alegra anunciar que pronto vamos a cumplir 6 años de Hormigas Agilistas Podcast y vamos a tenener algunas sorpresitas para los proximos episodios.Si deseas conocer más sobre este episodio y todos los demás, visita el sitio: HormigasAgilistas.CL o en https://medium.com/hormigas-agilistas/¡Gracias por ser parte del Universo de Hormigas Agilistas!IMPORTANTE: Siempre es bueno recordar que en Hormigas Agilistas Podcasts no somos buscadores de la verdad, el objetivo acá no es indicar los que se debe hacer; más bien, abrimos el micrófono para que las personas puedan contar sus experiencias, sus ‘heridas de guerra', y así los oyentes puedan tomar lo que más le haga sentido en sus organizaciones y avanzar en la mejora continua.#AgileCoach #ElArteDelAgileCoaching #Agile #ComunidadesAgiles #AgileCoaching #HormigasAgilistas

Was passiert, wenn eine Logistikabteilung beginnt, sich selbst neu zu erfinden – ganz ohne offiziellen Auftrag von oben, dafür mit echtem Gestaltungswillen? Bei Frankstahl hat Roman Divoky genau diesen Weg eingeschlagen. In dieser Podcast-Folge erzählt er, wie sich die Abteilung Schritt für Schritt von einer klassisch geführten Struktur hin zu einem agilen, selbstorganisierten Team entwickelt hat. Anstatt auf starre Hierarchien und Change-Prozesse mit PowerPoint zu setzen, vertraute das Team auf Peer-Learning, Eigenverantwortung und eine kontinuierliche Weiterentwicklung aus dem Inneren heraus. Roman teilt offen, was diesen Weg möglich gemacht hat, welche Hürden es zu überwinden galt – und warum gerade Logistik ein ideales Umfeld für New Work ist. Ein inspirierender Erfahrungsbericht für alle, die daran glauben, dass echte Veränderung nicht von oben kommen muss, um Wirkung zu zeigen. Über meinen Gesprächspartner Roman Divoky ist Experte für New Work und agile Transformation – insbesondere in der Logistikbranche. Mit über 30 Jahren Erfahrung in Führungs- und Entwicklungspositionen begleitet er Frankstahl bei der erfolgreichen Umsetzung moderner Arbeitskonzepte und agiler Strukturen. Aktuell ist er Logistikleiter bei Frankstahl, einem führenden Stahlhandelsunternehmen in Österreich. Parallel dazu wirkt er intern als TÜV-zertifizierter Agile Coach und extern als Keynote-Speaker, Workshop-Leiter und Berater. Sein Ziel: Teams und Organisationen auf ihrem Weg in die Zukunft der Arbeit zu unterstützen – agiler, effizienter und nachhaltiger. Als Autor des Buchs „New Work Now“ teilt Roman zudem praktische Ansätze und Strategien für neue Arbeitsmodelle. Für ihn steht fest: New Work ist kein Trend, sondern eine notwendige Weiterentwicklung der Arbeitswelt. Über das Unternehmen Frankstahl ist ein europaweit führendes Stahlhandelsunternehmen mit Wurzeln in Wien seit 1880. Unter der Leitung von Marcel Javor in zweiter Generation verbindet das Familienunternehmen Tradition mit Innovation. Mit über 700 Mitarbeiter:innen in zehn Ländern setzt Frankstahl auf Digitalisierung, moderne Technologien und eine starke, wertebasierte Unternehmenskultur. So bleibt das Unternehmen ein verlässlicher Partner der Stahlindustrie – flexibel, effizient und zukunftsorientiert. The post #58 Frankstahl: Wie eine Logistikabteilung den Wandel selbst in die Hand nahm mit Roman Divoky appeared first on Zukunftspioniere der Arbeitswelt.

https://www.cornelia-maria-mohr.comIn dieser hochspannenden und inspirierenden Podcast Serie kommen Menschen wie du und ich zu Wort. Sie lassen uns daran teilhaben, wie sie in den Herausforderungen ihres Lebens durch ihre ganz persönlichen Wege inneres Glück und Frieden gefunden haben und immer wieder finden.

In dieser Episode spreche ich mit Olaf Bublitz über sein neues Buch „Agile Produktentwicklung mit visuellen Methoden“, das er gemeinsam mit Thomas Starz veröffentlicht hat. Olaf gibt uns spannende Einblicke, wie visuelle Methoden dabei helfen können, Kommunikation in der Produktentwicklung effizienter zu gestalten – und wie man eine durchgängige visuelle Landschaft vom ersten strategischen Gedanken bis zur Umsetzung aufbaut. Wir sprechen unter anderem über: Wie Olaf vom Entwickler zum Visual Product Ownership-Experten wurde Warum ein Product Development Canvas ein guter Startpunkt für jedes Produkt ist Welche visuellen Methoden besonders hilfreich sind (z. B. People Interactions Map, Strategy Map) Wie man visuelles Arbeiten auch remote und in hybriden Teams erfolgreich umsetzt Was passieren muss, damit Workshop-Ergebnisse nicht versanden Warum „schöne Visualisierungen“ zweitrangig sind – und es auf etwas anderes ankommt

BONUS: Beyond Frameworks, A Provocative Guide to Real Agility With Erwin Verweij In this BONUS episode, we dive into the provocative world of Erwin Verweij's latest book: 'How the f*ck to be Agile?' Erwin shares his journey from frustration to clarity as he witnesses organizations adopting Agile frameworks without understanding their purpose. With candid stories from his coaching experiences, Erwin reveals what happens when teams wake up to real agility beyond dogmatic practices and how organizations can find their own path to meaningful change. The Wake-Up Call for Agile Adoption "What the f*ck dude! Do you even know what it means? Do you really know what it means?" Erwin's journey to writing this book began with growing frustration at how companies approach agility. He frequently encountered teams proudly declaring "We're Agile!" or "Our department is Agile" without understanding what that truly meant.  This disconnect between label and understanding became the catalyst for his provocatively-titled wake-up call. Erwin describes his exasperation with organizations adopting frameworks halfheartedly, following mindsets that were completely off track, and ultimately "doing stuff without knowing what they're doing and why they're doing it." The F-word in his book title serves dual purposes - expressing his frustration while also functioning as a power word to wake people up from their complacency. Breaking Free from Framework Dogma "We're not gonna do Agile. Forget it. And we're not gonna do Scrum, even though you're doing Scrum. Let's look at what really works for you people." Rather than imposing rigid frameworks, Erwin advocates for teams to discover what actually works in their specific context. He shares a memorable story of tearing down Scrum posters that management had installed, shocking team members who couldn't believe he would challenge the prescribed approach.  In another example, Erwin creatively used a manager's "quarantine" language by posting contamination warnings at a department's entrance with the message: "If you enter this room, you might get contaminated with a new way of working." These disruptive approaches are designed to shake people from blindly following orders and encourage them to think critically about their processes. Finding Your Own Path to Agility "Any coach who goes into a company with a strict plan and a set approach - don't hire them. They don't have a clue what to do." After the wake-up call, Erwin focuses on helping teams discover their own effective ways of working. He believes that the key is to observe what's already working well, emphasize those elements, and discard what doesn't serve the team. This approach stands in stark contrast to consultants who arrive with predetermined solutions regardless of context.  Erwin emphasizes that real transformation happens when teams take ownership of their processes, adapt them to their unique needs, and make them their own. He cautions against hiring coaches who come with rigid, predetermined plans, as they often lack the flexibility to address a team's specific challenges. The Never-Ending Journey of Adaptation "We need to help teams to stay open for the change that is coming." Erwin stresses that agility is not a destination but a continuous journey of adaptation. The world never stops changing, so teams must remain flexible and open to evolving their approaches. He encourages a mindset of experimentation with phrases like "let's try" and "what could we try" to keep teams responsive to new challenges.  According to Erwin, one of the most powerful ways to foster this adaptive culture is to model the behaviors you want to see in the teams you support. By demonstrating openness to change yourself, you help others embrace the continuous nature of improvement. Scaling Without Bureaucracy "Work with the system, learn what is needed, iterate." When discussing scaling Agile across an organization, Erwin questions why companies feel the need to scale in the first place. He uses cities as a metaphor for how complex systems can organize beyond small groups without excessive bureaucracy.  In one organization where he currently coaches, teams have found a pragmatic approach by adopting elements from various frameworks that work for them. They use quarterly planning sessions from SAFe primarily as a networking opportunity that connects everybody and focuses their efforts, even though the planning itself might be "basically bullshit." This practical, results-oriented approach emphasizes what works rather than dogmatic adherence to frameworks. Software as a Creative Process "Software development is basically figuring out how stuff works. It's a creative process that mostly is being dealt with within the brain of people." Erwin views software development fundamentally as a creative process rather than a production line. He explains that it's not about "typing as fast as you can" but about thinking, problem-solving, and creating. This perspective helps explain why iterative approaches with small steps work better than trying to plan everything upfront.  Erwin notes that when complex problems become routine, teams might not need the full framework structure, but they should retain the values that help them coordinate effectively. The essence of frameworks like Scrum, he suggests, is simply "start working, figure it out, and see what happens" - an approach that many organizations have become afraid to embrace. Awakening Organizational Intelligence "We raise children, which is basically programming another human being - it's really complex. And we just take it for granted. And then we go to work, and we don't know how to make decisions anymore." One of Erwin's most powerful insights is how organizational structures can suppress the natural intelligence and decision-making abilities that people demonstrate in their personal lives. He points out the irony that we navigate incredibly complex systems like raising children or driving in traffic, yet when we arrive at work, we suddenly act as if we can't make decisions without higher approval. This disconnect creates frustration and wastes human potential. Erwin challenges organizations to wake up to this contradiction and create environments where people can bring their full capabilities to work, rather than checking their intelligence at the door. In this section, we refer to Jurgen Appelo's Book Management 3.0. About Erwin Verweij Erwin is a seasoned Agile Coach, Certified Enterprise Coach, and author of Viking Law and How the f*ck to be Agile?. With 15+ years' experience driving meaningful change, he helps organizations embrace real agility through coaching, transformation, and workshops—cutting through complexity to spark courage, clarity, and action. You can link with Erwin Verweij on LinkedIn and connect with Erwin Verweij on Twitter.

Richard Brenner: Hypothesis-Driven Product Ownership, The Experimental 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. The Great Product Owner: The Experimenter Richard describes great Product Owners as "experimenters" who understand that everything they do is a hypothesis requiring validation. The best POs establish feedback loops early, actively engage with users and clients, and approach product development with a scientific mindset. Richard shares an experience working with a "coaching PO" who excelled at involving everyone in defining what needed to be done.  This PO was inspiring and helped the team participate in both building and decision-making processes. Richard emphasizes that the relationship between PO and team must be a true partnership—not hierarchical—for success to occur. Great POs facilitate team involvement rather than dictating direction, creating an environment where collaborative problem-solving thrives. In this segment, we refer to the Role Expectation Matrix Retrospective, and the Product Owner Sprint Checklist, a hands-on coaching tool for anyone interested in helping PO's prepare and lead successful Sprints with their teams. The Bad Product Owner: The Tech Visionary Disconnected from Users Richard recounts working with a high-level sponsor, a medical doctor interested in technology, who hired multiple development teams (up to four Scrum teams) to build a product. While technically knowledgeable, this PO had very concrete ideas about both the technology and solution based on assumptions about client needs.  The team developed impressive technology, including a domain-specific language (DSL), and felt they were performing well—until they delivered to actual clients. Only then did they discover users couldn't effectively use the software, requiring a complete rethinking of the UX concept. This experience taught Richard the critical distinction between the customer (the sponsor/PO) and the actual end users, demonstrating how even technically sophisticated Product Owners can miss essential user needs without proper validation. Self-reflection Question: How might you help Product Owners in your organization balance their vision with the practical realities of user needs and feedback? [Scrum Master Toolbox Podcast Recommends]

Richard Brenner: Contracting for Success,  Establishing Clear Agile Coaching Outcomes 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. Richard reflects on his evolution in defining success as a Scrum Master and Agile Coach. Initially, he believed that if his team was successful, he was successful—but soon realized this perspective was incomplete. Top management wanted tangible evidence of coaching impact, which became problematic without clearly defined metrics. Richard now advocates for establishing a coaching agreement at the beginning of any engagement, with both management and teams defining what success looks like for the coach. He emphasizes the importance of dual-sided accountability as a natural outcome of proper contracting, using metrics that matter to the organization such as flow metrics and outcome metrics to demonstrate coaching value. Self-reflection Question: How are you measuring your own success as a coach or Scrum Master, and have you created explicit agreements with both teams and management about what success looks like? Featured Retrospective Format for the Week: Solution Focused Retrospective Richard recommends the Solution Focused Retrospective from the book "Solution Focused Coaching for Agile Teams." While traditional retrospective formats from books like "Agile Retrospectives" typically open a topic and dig deeply into the problem space, the solution-focused approach suggests spending only a short time discussing problems before pivoting to designing the desired future state. This format focuses on identifying the next step and emphasizing what positive outcomes the team wants to achieve, rather than dwelling on what's wrong. Richard values this approach for its ability to maintain a positive, forward-thinking mindset within teams. [Scrum Master Toolbox Podcast Recommends]

Richard Brenner: When Individual Performance Metrics Block Agile 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. Richard shares an experience of implementing Agile methods in a large organization that initially showed promising signs with management "pull" for change. The transformation began well with cross-functional teams created through self-selection workshops. However, unexpected resistance emerged during the kick-off day, particularly from a line manager and his team. When investigating the source of this resistance, Richard discovered that the company's bonus structure was tied to individual performance metrics, fundamentally conflicting with Agile's team-oriented approach.  This insight led to developing a pilot for a team-focused performance management system. After three months, the team held a retrospective with all stakeholders, where management demonstrated remarkable leadership by empowering teams to redesign their structure when the initial setup wasn't working. This flexibility allowed even the most vocal critics to become part of the solution. Self-reflection Question: In what ways might your organization's reward structures be unintentionally blocking successful Agile adoption? [Scrum Master Toolbox Podcast Recommends]

In this episode of Cloud Unplugged, Jon talks with Thomas Boltze—CTO at Santander's PagoNxt, former CTO of Funding Circle, Agile Coach, and cloud/fintech leader with 15+ years experience—about fixing broken tech teams. They cover rebuilding systems from scratch, cutting through technical debt, and why culture trumps code every time. Lessons from fintech, startups and hard-won engineering battles.Guest LinkedIn: https://www.linkedin.com/in/thomasboltze/Follow us on social media @cloudunplugged https://www.tiktok.com/@cloudunpluggedhttps://twitter.com/cloud_unpluggedhttps://www.linkedin.com/company/cloud-unplugged-podcast/Listen on All Platforms: https://cloud-unplugged.transistor.fm/Listen on Spotify: https://bit.ly/3y2djXaListen on Apple Podcasts:  https://bit.ly/3mosSFTJon & Jay's start-up: https://www.appvia.io/Hosts:https://www.linkedin.com/in/jonathanshanks/https://www.linkedin.com/in/jaykeshur/https://www.linkedin.com/in/lewismarshall/ Podcast sponsor inquires, topic requests: Hello@cloudunplugged.ioWelcome to The Cloud Unplugged Podcast, where hosts Jon Shanks (CEO of a Cloud Platform Engineering and Developer Platform Company), Lewis Marshall (Developer Evangelist, AI enthusiast, and science devotee), and occasionally Jay Keshur (COO, championing business modernisation and transformation) explore the latest in cloud technology.Each week, they investigate developments in AI, data, emerging cloud platforms, and cloud growth, occasionally highlighting the geo-political and global commercial pressures shaping the industry. Drawing on their extensive experience helping customers adopt, scale, and innovate in the cloud (and managing their own Internal Developer Product), Jon, Lewis, and Jay share insights and welcome industry experts to discuss new trends, tackle business challenges, and offer practical solutions.

Richard Brenner: How Small Signs of Cynicism Can Destroy Agile Team Cohesion 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. Richard shares a powerful story about how team dysfunction often starts with small steps. During a joint retrospective with three agile teams, Richard witnessed a moment where a team member made a cynical comment toward a manager who was attempting to participate. This revealed a damaged relationship between management and the team, creating tension that Richard initially chose to ignore. Looking back, he would now immediately address such comments and tackle the "elephant in the room." Richard explains how seemingly minor behaviors like cynicism or passive-destructive actions (such as consistently being late to stand-ups) can significantly impact team health. He recommends establishing conflict resolution protocols early and using impact feedback without judgment to address these issues before they escalate. In this segment, we refer to Lysa Adkins' conflict resolution protocol.  Self-reflection Question: What small signs of dysfunction might you be overlooking in your team that could develop into larger problems? Featured Book of the Week: Solution Focused Coaching for Agile Teams Richard recommends "Solution Focused Coaching for Agile Teams" by Ralph and Veronika. This book describes the solution-focused approach to many common situations that Agile coaches face in their work. Richard values this resource for its practical guidance on addressing challenges through a positive, solution-oriented perspective rather than dwelling on problems. [Scrum Master Toolbox Podcast Recommends]

Richard Brenner: Skipping the Vision, How Not to Introduce Kanban 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. Richard shares an important learning experience from introducing Kanban to teams using a top-down approach. Without clearly articulating why the change was needed, team members questioned what they were doing wrong that necessitated change. Richard found himself unable to connect the organizational vision to the methodology shift, leading to resistance. He emphasizes the importance of first understanding the problem before applying Scrum or Kanban, defining what success looks like, and involving people early in the change process. Richard also recommends thorough contracting with client organizations to assess their current state and understand who is trying to change what, and why. In this episode, we refer to Kotter's book Leading Change. Self-reflection Question: How might your change initiatives be improved by spending more time defining the "why" before introducing new methodologies? [Scrum Master Toolbox Podcast Recommends]

#5amMesterScrum Lightning Talk 1,256 Live - Scrum Master Continuous Learning (4R Thursdays) - Today's topics: (1) Talking the Scrum Master and even Agile Coach role today and what we do to challenge others to grow and learn but don't do it ourselves.  We should be challenging ourselves 1st and a great way is Reading 10 pages a day from a growth or tech book.  I give away my Change Vol 20 book (in PDF form) to my connections as a nice little start to such a challenge. Please like and subscribe and share 5amMesterScrum.  Please send me your topics.   You are are doing Great Please Keep on Sharing. 5am Mester Scrum 5am Mester Scrum Lightning Talk 1,256 went live on Youtube, LinkedIn and Facebook 4R (Requirements, Reviews, Retros, Roles) Thursday 4/10/2025 from Philadelphia, PA  Happy Scrumming, Please Don't forget to sign up to our 5amMesterScrum newsletter for freebies.  Definitely a free copy of Change Volume 20 in PDF form.  Watch the video in our YouTube Library as well. Social Media: - search 5amMesterScrum or #5amMesterScrum  and you should find us and if not please let us know LinkedIn, Youtube, Facebook, Instagram, Twitter, TikTok     Podcasts: (search 5amMesterScrum)    Spotify, Pandora, Google Podcasts, PodBean, iTunes, Stitcher, iCatcher, Airr, PlayerFM, Breaker, Apple, Amazon, Alexa, iHeartRadio, Listen Notes, Firefox, Overcast, radio de, PodcastAddict, Bullhorn, iVoox, Podchaser

Zvonimir Durcevic: How Feedback Transforms Product Owners 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: Embracing Feedback and Adapting Over Time  Zvonimir shares his experience with a Product Owner who demonstrated exceptional growth over a two-year period. What made this PO stand out was their willingness to receive feedback from the team and adjust their behavior accordingly. When the team expressed difficulty accessing the PO for questions and early feedback, the PO responded by rearranging their schedule to sit near the team part-time. Zvone emphasizes how these incremental changes, driven by openness to feedback, transformed this person into an exemplary Product Owner. The key insight: great Product Owners honor past practices while embracing necessary changes for the future. Self-reflection Question: How might your willingness (or reluctance) to accept feedback be affecting your development as a Product Owner? The Bad Product Owner: The Reluctant Subject Matter Expert In this segment, Zvonimir describes working with a Subject Matter Expert who was assigned the Product Owner role despite not wanting the responsibility. While this person excelled at documenting requirements from their extensive knowledge, they resisted taking on core PO duties. The organization assigned them the role but didn't push for proper adoption of responsibilities. Consequently, the team and Scrum Master were forced to assume PO duties to fill the gap. Although this arrangement functioned temporarily thanks to the team's capabilities and the SME's knowledge, it created an unsustainable situation where role accountability was unclear. [Scrum Master Toolbox Podcast Recommends]

Zvonimir Durcevic: The Solution-Focused Retrospective for Agile Teams, Turning Problems Into Goals 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. Zvonimir defines Scrum Master success as being explicit and intentional about defining and achieving goals. He references Richard Hackmann's model of team effectiveness as a framework to evaluate whether he's helping teams become truly effective. For Zvone, success comes from creating structures that provide teams with feedback about their performance and being explicit about the team's purpose through practices like chartering. By focusing on these elements, Scrum Masters can help teams build the foundation for sustainable success. Featured Retrospective Format for the Week: Problems Are Disguised Goals This solution-focused retrospective format, inspired by the work of Ralph Miata and Veronika Jungwirth, allows teams to briefly acknowledge problems before pivoting quickly to what they want to achieve instead. Zvonimir explains that while teams need space to express challenges, the format redirects energy toward envisioning a better future through solution-focused questions. The process includes validating problems, using scale questions (0-10) to assess current status, reviewing past attempts at reaching goals, and designing small experiments to move toward desired outcomes. This approach helps teams shift from problem-orientation to goal-orientation. Self-reflection Question: How might reframing your team's persistent problems as goals change your approach to addressing them? [Scrum Master Toolbox Podcast Recommends]

Zvonimir Durcevic: From Command to Collaboration, An Agile Leadership Team's Transformation Story Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. In this episode, Zvonimir discusses his experience supporting a leadership team transitioning from a traditional command-and-control management style to a more collaborative approach involving people in change decisions. Drawing from EDGE Theory of Change (based on Arnold Mendel's work) and Organization and Relationship Systems Coaching (ORSC) training, Zvone helped the leadership team understand what awaited them on the "other side" of this transformation. Through multiple half-day coaching sessions, he guided them in defining their new leadership identity and developing self-reflection skills. A critical element of this work was creating a conflict protocol that allowed leaders to discuss different perspectives constructively. Zvone emphasizes the importance of helping teams create a "third identity" – a new collective self that emerges through transformation. Self-reflection Question: What elements of your current leadership identity would you need to let go of to embrace a more collaborative approach to change? [Scrum Master Toolbox Podcast Recommends]

Zvonimir Durcevic: Context Diagramming, Helping Agile Teams See Their Complex Communication Network 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. Zvonimir shares a story about a five-person team developing an important product who maintained good internal dynamics but limited their interaction with the rest of the organization. Despite delivering quality work, they were viewed as a "difficult team" by stakeholders. When Zvone joined, he conducted assessments and introduced context diagramming to map the team's relationships and dependencies. This exercise revealed the complexity of their communication network and helped the team understand that cutting off relationships with stakeholders was counterproductive. The breakthrough came when the team began using the context diagram to explain their situation to others, helping stakeholders recognize how organizational factors were affecting the team's work. Self-reflection Question: How might mapping your team's communication network reveal disconnects that are affecting your effectiveness? Featured Book of the Week: Agile Transformation by Michael Spayd Zvonimir recommends "Agile Transformation" by Michael Spayd as a resource that helped him understand how to examine systems through different lenses. The book provides multiple perspectives for gaining deeper insights into the systems we work with. Zvone particularly values the book's ability to help practitioners look beyond surface-level issues and understand underlying dynamics in organizations undergoing Agile transformations. In this section we talk about the Integral agile transformation framework. [Scrum Master Toolbox Podcast Recommends]

Zvonimir Durcevic: Establishing Communication Channels, Lessons From a Scrum Master's Failure  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. In this episode, Zvonimir shares a pivotal experience that shaped his approach as a Scrum Master. His team started strong with excellent stakeholder relationships, but gradually team members began missing refinement meetings as they took on more outside responsibilities. Despite conversations with management, the issue persisted, leading to a growing backlog that no one wanted to trim down. Zvone learned critical lessons about the importance of establishing clear working agreements with stakeholders and sponsors from the beginning. He emphasizes the need to create proper communication channels, as successful Agile work depends on reaching the right people when problems arise. Self-reflection Question: How might the communication agreements in your organization be contributing to your team's ability to focus on their work? [Scrum Master Toolbox Podcast Recommends]

We're exploring the false dichotomy between being good at your job and being seen as valuable by leadership!The framework for this conversation was an eye-opening yet brutally honest post about the tactics one product manager claims to use to advance his career without delivering real impact. We ask, "is success about making an impact or just being seen as valuable," while we explore the tactics described in the article:Focusing on vision while ignoring executionUsing positivity to mask problemsAvoiding accountabilityDealing with the Inevitable burnoutWhether you're a product manager, leader, or team member, you won't want to miss our conversation around building sustainable career success without sacrificing integrity.References:Ronald Westrum: A typology of organisational cultures, 2004AA201 - Mastering Stakeholder Communication and ManagementAA199 - W. Edwards Deming's Profound Knowledge for Transforming OrganizationsAA195 - Tyranny of Plans & Planning in Software DevelopmentAA117 - You Should Do Time-Based Estimates (Article Review)AA87 - Burnt-Out Product ManagersAP52 - Taylorism: The Principles of Scientific Management#ProductManagement #LeadershipCulture #AgileTeams= = = = = = = = = = = =YouTubeApplehttps://podcasts.apple.com/us/podcast/agile-podcast/id1568557596Spotifyhttps://open.spotify.com/show/362QvYORmtZRKAeTAE57v3= = = = = = = = = = = =Toronto Is My Beat (Music Sample)By Whitewolf (Source: https://ccmixter.org/files/whitewolf225/60181)CC BY 4.0 DEED (https://creativecommons.org/licenses/by/4.0/deed.en)

Is it better to hire someone with deep domain expertise and teach them product management, or to bring in an experienced PM who can learn the domain? Today, we're debating the strengths and weaknesses of both approaches across critical areas like business impact, product discovery, stakeholder management, and leadership!Listen (or watch) as Product Manager Brian Orlando and Enterprise Business Agility Coach Om Patel discuss why domain experts excel at identifying immediate pain points but may struggle with deeper product methodologies... or listen/watch as we discuss how experienced PMs can bring fresh perspectives while also facing steeper learning curves in specialized industries. This podcast is all about exploring the real-world tradeoffs Product Leaders face when building product teams and providing insights for both hiring managers and product professionals!#ProductManagement #CareerDevelopment #AgileLeadershipReferences:Boiler Room (film), 2000Marty Cagan - Inspired: How to Create Tech Products Customers Love, 2008AA120 - Did AirBnB Fire Their Product Managers?AA199 - W. Edwards Deming's Profound Knowledge for Transforming OrganizationsAA201 - Mastering Stakeholder Communication & Management= = = = = = = = = = = =YouTubeSubscribe on YouTube:https://www.youtube.com/channel/UC8XUSoJPxGPI8EtuUAHOb6g?sub_confirmation=1Applehttps://podcasts.apple.com/us/podcast/agile-podcast/id1568557596Spotifyhttps://open.spotify.com/show/362QvYORmtZRKAeTAE57v3= = = = = = = = = = = =Toronto Is My Beat (Music Sample)By Whitewolf (Source: https://ccmixter.org/files/whitewolf225/60181)CC BY 4.0 DEED (https://creativecommons.org/licenses/by/4.0/deed.en)

S4EP8, Explore Life's Paradoxes with Seye Kuyinu

What’s next for Agile coaching? Brian Milner and Andreas Schliep dive into the shifting landscape of Agile coaching, the differences between Scrum Masters and Agile Coaches, and how to carve out a sustainable career in a changing industry. Overview In this episode of the Agile Mentors Podcast, Brian Milner and Andreas Schliep explore the evolving role of Agile coaching, the challenges coaches face in today’s market, and the skills needed to thrive in a shifting industry. They break down the differences between Scrum Masters and Agile Coaches, discuss how to develop a personal coaching style, and emphasize the importance of integrity and resilience. From navigating layoffs to redefining what it means to be an Agile leader, this conversation offers valuable insights for anyone looking to grow in their Agile career. References and resources mentioned in the show: Andreas Schliep Certified ScrumMaster® Training and Scrum Certification Certified Scrum Product Owner® Training Mountain Goat Software Certified Scrum and Agile Training Schedule Join the Agile Mentors Community Subscribe to the Agile Mentors Podcast Want to get involved? This show is designed for you, and we’d love your input. Enjoyed what you heard today? Please leave a rating and a review. It really helps, and we read every single one. Got an Agile subject you’d like us to discuss or a question that needs an answer? Share your thoughts with us at podcast@mountaingoatsoftware.com This episode’s presenters are: Brian Milner is SVP of coaching and training at Mountain Goat Software. He's passionate about making a difference in people's day-to-day work, influenced by his own experience of transitioning to Scrum and seeing improvements in work/life balance, honesty, respect, and the quality of work. Andreas Schliep is a Certified Scrum Trainer and executive partner at DasScrumTeam AG, helping organizations navigate complex projects with agile methodologies. A thought leader and co-author on Enterprise Scrum, he empowers teams—from startups to Fortune 500 companies—through high-impact coaching, training, and a passion for continuous learning. Auto-generated Transcript: Brian Milner (00:00) Welcome in Agile Mentors. We are back here for another episode of the Agile Mentors Podcast. I'm here as always, Brian Milner, and today I have someone we've been trying to get on here for a little bit, and I'm excited to have him here. Mr. Andreas Schliepp is with us. Andreas, thank you for being on. Andreas Schliep (00:17) Thank you for inviting me. Brian Milner (00:19) Yeah, very excited to have Andreas on here. Andreas has been in the community here for a long, time. He's been just really generous with his time and he's mentored a lot of people. He's a CST, a Scrum trainer. He's also a certified enterprise coach. So he has kind of those dual high level certifications with the Scrum Alliance. But he mentioned to me earlier, he's kind of always considered himself a Scrum trainer. But he's also a coach in this group called the Leadership Gift, or there's also another name here that they've used recently, Responsibility Immersion. So that might come to play in our conversation here because we wanted to talk about sort of the future of agile coaching and agile coaches in general. There's a lot of turmoil, there's a lot of upheaval and things that are shifting and changing every day in our profession. So I guess, you know, let's just dive into the topic here. Andreas, how do you see things currently? And, you know, in a broad sense, where do you see them going? Andreas Schliep (01:18) Yeah, so first of all, why am I concerned? So typically I say that I kind of, train coaches and I coach trainers. So most of my work is centered around the path of scrum masters and how they can kind of acquire the necessarily skills and insights to become actual coaches themselves. Or scrum coaches as I would prefer to say it. And that includes a lot of stuff like we want to equip them with facilitation, with training skills, with coaching skills, with systemic observations and other methods. And we've been doing that for a couple of years. And so of course we came across lots of good people, good coaches and good trainers, good consultants out there. And we kind of kept our community open. So it's not like people attend our classes and then we forget them or we only have closer relationships to our corporate customers. It's like we kind of managed to build some kind of little community. People keep coming back and we keep chatting about what's going on, what's happening in their environment. And as a mainly training focused company, one of the first effects that we notice is that our classes are getting emptier and emptier. So what's going on, especially advanced classes are not that well. So we still have some, well, yeah. basic attendance, but it's not as it used to be. well, a couple of years ago, we had like full classes and everything, and then COVID hit and we could say, okay, so COVID kind of reduced the demand for edutraining. And then the next crisis came and the next catastrophe and the next disaster. But there have also been some structural changes. I think that we are currently experiencing two effects that happen at the same time. So the one thing is that, well, Diana Larsen put it that way, Agile has won. So there's no doubt that organizations employ Agile methods and want to use Agile practices, some of them with, some of them without any clue about what that even means or what Agile thinking or Agile attitude behind it is, but still, there's no shortage on like the use of Agile or the, but there's also no shortage of the Agile basic training or educational videos, content or whatever. So people get lots of more resources than we used to get back then when we had like this one scrum book by Ken Schwabe. So read this and then you went out and said, how do I do that? So. And then came the second book by Mike Cohen and the third book and so on. had to, had all these puzzle pieces coming together where we needed to find our own way and build our proficiency. And now you get a flood of books and stuff going on, which is fine. So the one thing is that of course our profession is developing and it's kind of natural that you will notice some kind of within that. But there's another effect and this is one thing where we scrum trainers can kind of take responsibility for our own contribution. It's the fact that organizations can hire an unlimited number of low-level agile coaches nowadays. There's been no quality control. Anyone who went through a two-day CSM class could call themselves agile coaches and they got hired for lots of money and eventually produced nothing. some of them, some agile coaches or people who call themselves agile coaches even caused chaos. So, and the systems. that they were affecting started to kind of fix themselves and heal themselves from the Agile coaches by expelling those. So, and of course, maybe you have a third effect, which is sometimes it just doesn't work and you blame the Agile coaches. So if you just lay on your couch and you do nothing and your doctor tells you, you have to get moving, you have to get up and get moving and say, yeah, it's a bad doctor because... I still lie on my couch and my health is deteriorating and this doctor doesn't help me. He doesn't give me what I want. What do you want? Yeah, I want just, I would just want a pill that I can swallow that I'm healthy. It doesn't work that way. And then we had those people who were selling those pills, yeah, who were telling people, here we got a, we got a safe way that you can do this. All you need to do is implement this process, hire our consultants. Brian Milner (05:26) Yeah. Andreas Schliep (05:43) We kind of made all the thoughts and the heavy thinking ourselves beforehand and you just need to install it. Here's the roadmap, here's the process manual, here's the 300 page guide. Just do it this way. And this is also detrimental. now we have, I've been talking to many people, many great people, you've been laid off, who are looking for a new orientation. Brian Milner (06:05) Yeah, yeah, I agree. I mean, I think you laid that out really, really well because there's I think you're right. It's kind of a multi effect scenario. There's a lot of things affecting it. And I know I've had conversations with with friends and colleagues about this. And, you know, we've talked a lot about the I think more kind of the second thing that you're talking about, just that and It's sort of a chicken and egg thing because the industry has built up and spread agile concepts through offerings of usually two day classes. You and I both do those quite regularly. And I think we probably both would say that's a very valuable thing. to go through sort of that immersion kind of a couple of days to learn it and get a foundation in it. But there may have been sort of a misconception or it may have been sold incorrectly to say, now you're ready to lead an organization and transforming from zero to 60 in Agile. when you're not, right? I mean, you've got a good grounding. You're ready to begin learning with a team, but it's the first step. There's gotta be some sort of ongoing support system that when you come up against something that you don't really know how to handle, that you have someone to ask. You have somewhere to go to get help and get answers. Even the, you I work with Mike Cohn, I think he's a great trainer. But even a two day class with Mike Cohn, I don't think is gonna make anyone an expert that now you're ready to, you know, take on the huge challenge of cultural change within the organization, you know? Andreas Schliep (07:53) Yeah, yeah, it's like with anything agile, these classes are a starting point or a waypoint and not a designation. It's not the goal. So when I made my driving license, my driving instructor told me, and in Germany you have to spend lots of hours with your driving instructor. And my driving instructor told me gladly, now you can get to practice on your own. He was happy that he didn't have to co-practice with me any longer because I wasn't the best driver. So I actually aced the theory test, but the practical driving was a little more difficult and kind of probably was bad for the blood pressure of my driving instructor. yeah. And that way, but I never thought about this. So the idea was I get the permission or I get the next level to the next step. And the next step will be, I want to learn proper driving. And that's something that you need to do on your own. And with this understanding, we try to kind of provide a path for people to become better scrum masters and agile coaches by kind of revamping the CSP path, the scrum aligns and other things. A glorious project that also failed gloriously. I'm still not entirely sure why, but probably because the Scrum Alliance and many other people failed to understand the similarities between Agile Coach as a profession and the Scrum Master as a role. So they claimed that there were two different things. And I think that's also a structural issue in organizations. Brian Milner (09:16) Yeah. Andreas Schliep (09:25) that they see Scrum Masters and Edge of Coaches as different things. So the Scrum Masters work on the team level and they just know their Scrum and they facilitate the meetings and then they come up with nice cookies for the retrospective so that everybody on the team is happy. And occasionally they take one of the team members aside when they have some issues and help them go through that. That's totally fine, but the Edge of Coaches do the real stuff. release train engineers and the others, do the organizational thing and they don't bother with what's happening on the team level because they need to do the important things on the higher level. And with this attitude somehow fueled by some decisions by Scrum Alliance and other organizations like, yeah, in order to become a certified team coach or certified enterprise coach, you have to kind of prove that you're... had coached like 2000 hours or 2500 hours. But by the way, the scrum master worked. It doesn't count towards this coaching, which is totally ridiculous. So that means the misunderstanding of the role is a structural problem. Another structural problem is that the organizations that would need the most experienced scrum masters, they attract all the rookies. Brian Milner (10:16) you Andreas Schliep (10:34) because they don't even know what a good scrum master would cost like. They have those two day or even less day. I heard about a transformation at a large automobile builder in Germany. They had something like a half day class for scrum master training within the safe environment. And they wonder why they fail. They wonder why they're failing. Brian Milner (10:53) Ha Andreas Schliep (10:54) On the other hand, we have organizations, even here in Germany, they have great leadership and coaching concepts. So they develop the Scrum Masters. They have the finest Scrum Masters ever on such a high level that the teams actually don't need them because the teams also evolved by taking care and taking responsibility for themselves and paying attention to the work. So they're kind of over-coached. So like, I think it was at Rally 10 or 15 years ago. There was a period when the external rally coaches didn't get so many contracts. And so they went inside and coach all the software teams and rallies at Rally. And after three or four months, the software team said, please, please give us a timeout, give us a break. We over coach. It's just too much. We just want to do some work and maybe not get better for like a month or two before we, because it's Brian Milner (11:42) Yeah. Andreas Schliep (11:47) It's hard always to get better and even better and you're so excellent coaches, cut us some slack. So that's so, but this is the structure. So on the individual level, it's just the same as with any major shift in any kind of industry. If your current profession or your current job title doesn't fit any longer, focus on what you're good at and see that you Brian Milner (11:54) Yeah, yeah, yeah, right. Andreas Schliep (12:13) become excellent at that. So that's, it's an old formula. It's an old formula and it can be different things. So I know about some scrum trainers who go and went into software development again, because they said, actually, I'm passionate about software development. I can understand that. I have a developer background as well. So sometimes I'm not that unhappy about taking care of a website and other stuff. It's a nice distraction. But some are really great facilitators. But if they only go out with a label, agile coach, and do not let the facilitation skills and experience shine, then they might get a mis-hired. So we have great personal coaches in there. So people with various skill sets. And if you take a look at the agile coaching growth, we have Biomark, some of them others. Brian Milner (12:37) Right. Andreas Schliep (13:00) You see that it's a vast field. So you cannot expect anyone, maybe the two of us, but you cannot expect anyone to be, not even me, so anyone to be excellent in all these knowledge areas and to be such a light and catalyst in everything. So the idea is to find your own way how you can contribute best. and then collaborate with others in their fields. So for me, the most interesting areas in that field are training and facilitation. Because I think that's the main thing that agile coaches or scrum masters can shine in. Brian Milner (13:41) Yeah, I've always loved, know, Lisa Atkins has that kind of different aspects of a coaching stance. And one of the ones that she had there that I've always loved is the idea of having a signature presence. And I remember when I first kind of encountered that, was, when it kind of sunk in, it was a very freeing idea for me. Andreas Schliep (13:49) See you. Brian Milner (14:01) to, you know, kind of like you're describing there, there's so many different aspects that you could, you know, try to do and you could do well, but it's too much for any one person to do all of it. So that signature presence to me, one of the things that I really kind of took away from that was know what you're good at, right? I mean, there's something about you that you bring from your own personality and your history and and everything that's made you who you are that is unique. And when you can find what that is, then it's almost like prior to that recognition to me, I was almost even a little ashamed that that was where my strength was. And I felt like I had to make up on these other areas that I struggle with or I didn't do as well. But that concept to me, Andreas Schliep (14:47) Mm-hmm. Brian Milner (14:52) kind of help me see, no, there's something that's really unique about how you approach things. And if you recognize that, lean into it because nobody else can offer that, right? Nobody else brings that to the table because that's uniquely you. Andreas Schliep (15:06) Yeah. Yeah. I have to admit, well, we're both with Scrum Alliance and I've been with Scrum Alliance for more than 20 years now. But some of the biggest insights about Scrum and the role of Scrum Master were some things that I actually learned by looking through the Scrum.org certification parts. So just out of curiosity, I started digging into the... Professional Scrum Master Series by Scrum.psm1. Okay, PSM1 is a walking part, so that's no big deal. 50 minutes without preparation, A's are done. Okay, next thing, PSM2, was a little more chilling. Okay, there are some different concepts in the way they address Scrum. And I completely faded PSM3. So that's interesting. So I should have known that. And the point is that... Brian Milner (15:52) Huh. Yeah. Andreas Schliep (15:58) There are differences in the message and the Scrum Master and the Scrum.org framing of Scrum is far more of a leader. So they take far more responsibilities. They are much closer to a sports team coach actually, even taking care of the crew and even throwing people out of the team if necessary. Then the fluffy Scrum Master social worker thing. with no real responsibility always in the background that we appear to propagate sometimes that I even have propagated lots of times. And I see this in my own style as well. So I'm rather strong at the facilitation part and working from the side of the background of people. But sometimes I see, and I think that's a big challenge for many agile coaching scrummers out there. Brian Milner (16:32) Yeah. Andreas Schliep (16:48) When it comes to the situation where I should take the lead, I'm still reluctant when I say, okay, yeah, somehow I don't want to step under the feet of others. I want to give them room. I want to be in my facilitator stance because I love that stance and that's my personal brand or whatever. The calm way and listening to people and integrating all voices. But all of a sudden, I encounter situations where say, my voice first. So, yeah. So let's do it that way. this week, I kind of stopped the client workshop in the middle. I said, so yeah, what is that? here you booked me for the entire day, but I noticed that you're very upset about important stakeholders missing. Brian Milner (17:19) Yeah. Andreas Schliep (17:39) I also noticed that you don't see the point in reiterating some other concepts that I prepared. you could use these methods and then talk to your stakeholders, but you rather want me in this room with your stakeholders and have this discussion together. So let's just stop this now. And I offer you a gift. I will come back for another half of days. So we stop this half day. You can use your time for something else. I can use my time for something else. And then I come back, but only if you have your manager in here. So if you bring your boss, I will come for another half day and then we finish this and deal with these questions. And they were kind of impressed that I was offering them. But where's the point? I needed to change the mode. I couldn't stay and I think this is something Brian Milner (18:20) you Yeah. Andreas Schliep (18:29) which is another great opportunity for Scrum Masters or agricultural coaches to say, what if I stepped into this leadership role? Brian Milner (18:37) Yeah. Yeah, that's a great kind of approach to it. And I know we've had some similar things at Mountain Goat as well, where we've worked with some clients and you kind of show up and you start to get into the things. Or even sometimes in the kind of just pre-work calls where you're trying to arrange things and talk through what is it you want to get out of this. And you sort of get that feedback and understanding that this is really just checking a box, right? They wanna check the box that they did this, but really making the change. No, they really don't wanna make the change. They really don't wanna have to change what they do on a day-to-day basis. you kind of are, as a coach or a trainer, you kind of get to that decision point where you have to say, at what point do I call this out? At what point do I say, you know what? You're gonna waste your money. Right? mean, I can come and do this. I can take your check. I can go away, but it's not going to make any difference. And you're not ready for it yet. and, that's, that's always a really hard decision. When you get to that point, when you realize, you know what? It's not serving your needs for me to, move forward here. You know, it's, it's, you're not going to be happy with me. Andreas Schliep (19:48) Yeah. I think it's important to maintain the personal integrity. the whole point about resilience is that you kind of are able to change while you maintain your own identity. So the path that you are trying to. And this change can mean a lot of things. So if someone would tell me, you've got to stop with Scrum now because Scrum is now forbidden everywhere. I would kind of dig into the facilitation. So I joined the IAF, the International Association for Facilitators. I don't have a credential there yet, but this is something if I would go into more facilitation gigs, this would be very interesting for me. I also became a coach in the responsibility program with Christopher Avery. First of all, I think that was a nice addition to my training or to my work with leaders. But then I also discovered that this is kind of navigation aid for myself. So whenever I do something, I start with what do I want? So what do I want? How do I want the situation to evolve? What is the outcome that I want to achieve? And how am I blocking myself from that? So what is kind of my inner blocker that prevents me from getting what I want? Brian Milner (21:03) Yeah. Andreas Schliep (21:04) So I could also talk about external blockers, but these external blockers are sometimes just things on my path that I choose to say, okay, I can't go there because there's this blocker. And when I found these two things, so what do I really want and what is blocking me? I can go and make a decision. I can confront myself. And with this ability, I'm pretty sure that I'm able to respond to any kind of situation. So, and... whether I pursue the facilitator part further or whether I go into the coaching way. I love to work with groups so that just the one-on-one coaching is not so interesting for me. But these are kind of independent from what I'm doing now, but also based on what I'm doing now. So I can derive lots of good skills and insights and approaches from what I did as a scrum trainer so far, what I have done as a scrum trainer. Brian Milner (21:58) Yeah. Well, I think when I'm hearing and tell me if I'm misquoting this or saying it or misunderstanding, but it feels like there's sort of an element here that, you know, I think a lot of us sometimes, have some kind of a title that we've earned. and we, we sort of inherit from that, set of, activities or things that we feel empowered to do. based on that title. And what it sounds like I'm hearing from you is it should kind of be the reverse. You should think about what you do well and the titles may come and go. They may change the descriptors that people use to describe what you do, it might change, but what you love to do with the activity, what you're good at, that can shift and change a little bit and don't be so concerned with the title. Andreas Schliep (22:45) Yeah, so edge-hired coaches still can keep this kind of title for the tribe to identify a peer group. And I've also joined edge-hired coach camps even as a scrum trainer. because this identification is important to say, okay, I know a couple of people who have different skills or different things who are some more similar to me, but I don't think we should stick to Agile Coach as a job title and only look for Agile Coach offers. But rather go out and see what's out there, what opportunities do we see. Apply for weird stuff. So at the beginning of this year, I applied as a facilitator for United Nations volunteer program and even made an extra language proficiency exam before that because I had to kind of prove that I'm at least at level C1. for this job. I just did it because it was there because this opportunity came through the International Association for Facilitators. I just said, okay, I don't know. They didn't even throw me back. I don't have anything, but I just, I want to apply for this. I want to get this material together. I want to show that I'm potentially able to do this. I will be far too expensive with my current rate, but yeah. And I think anyone currently in the situation as an edge on coach being laid off or looking for another job should kind of step back and go through these steps. So what do I want? What are the activities that I'm really passionate about? Brian Milner (24:13) Yeah. Andreas Schliep (24:13) And the answer might be surprising. So sometimes, it's actually coding. Maybe we'll get back to the basics. Brian Milner (24:19) Yeah, yeah, you're right. I've known a lot of people or I've known several people, I guess I should say, that have kind of maybe migrated backwards. If you think of it in that way, I don't know that's backwards, but migrated to their roots a little bit more, you know, and maybe left training, but went back to doing, you know, managing software teams or even coding just because they enjoy it. And I think that's a great thing if that's... Andreas Schliep (24:41) Yeah. Brian Milner (24:45) brings them happiness, you know? Andreas Schliep (24:47) Yeah, you know, when the whole agile thing started, they came up with a little website and the website says something like, we're discovering better ways to sort fire customers or so. I don't have a probably and helping others to do it. And if even if you go back or if you go to actually start working as a developer again. You still bring the edge of spirit and you still bring the ideas and methods of collaboration. It's going to be so helpful in your environment. Especially with new technologies, AI stuff and remote work and all these things kicking in. Everything looks like it's making your work more difficult. Massive layers like even media firing developers now, not only edge of coaches. So we have... so many disruptions to deal with. And I think that, well, kind of resilient HR coaching tribe stance is helpful in whatever role you fulfill afterwards. Brian Milner (25:43) That's really good. Yeah. Well, this has been great. I really enjoyed the conversation. Sometimes you're not really quite sure where we're going to end up and where we're going to travel, but I've really enjoyed all the directions we've taken here, Andreas. So I can't thank you enough. Thank you for making time and coming on and sharing your experience and wisdom with everyone. Andreas Schliep (26:00) Mm-hmm. Yeah, was great fun and thanks for the opportunity and I hope that this will help some people find little more guidance, least a little more confidence if they don't find guidance yet. Brian Milner (26:13) Yeah, I agree. Thank you very much. Andreas Schliep (26:15) Thank you.

We're exploring the growing anti-Agile sentiment among developers as the agile-industrial complex has stitched together a grotesque imitation of what was once a vibrant movement. Like Frankenstein's creation, what began with noble intentions has transformed into something both villagers and developers flee from in horror!Before lighting our torches and brandishing our pitchforks, we examine the common complaints: lightning-rod meetings that drain life force, the monster of micromanagement wearing agile's skin, the cruel illusion of self-organization, and the chains of cross-team dependencies binding teams to their suffering. We dissect the organizational structures that, like misguided scientists, fundamentally misunderstand the natural advantages of agility, creating abominations that shamble through corporate hallways.#AgileLeadership #ProductDevelopment #TeamEmpowermentReferences:AA199 - W. Edwards Deming's Profound Knowledge for Transforming Organizations, 2025Eric Ries - The Lean Startup: How Today's Entrepreneurs Use Continuous Innovation to Create Radically Successful Businesses, 2011Jeffrey Bezos - Bezos API Mandate, 2002Who Moved My Cheese - Spencer Johnson, 1998Extreme Ownership: How U.S. Navy SEALs Lead and Win - Jocko Willink, 2017= = = = = = = = = = = =YouTube= = = = = = = = = = = =Subscribe on YouTubeAppleSpotify= = = = = = = = = = = =Toronto Is My Beat (Music Sample)By Whitewolf (Source: https://ccmixter.org/files/whitewolf225/60181)CC BY 4.0 DEED (https://creativecommons.org/licenses/by/4.0/deed.en)

Season Hughes: How To Be A Data-Driven Scrum Master Or Agile Coach 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. Season approaches Scrum Master success by regularly referring back to the Scrum Guide and measuring progress against its principles. She emphasizes the importance of collecting data and measuring key indicators like self-management, which she tests by occasionally stepping back from daily Scrum meetings to observe team autonomy. Season also stresses the value of one-on-one conversations to understand individual goals and assess team event effectiveness. Self-reflection Question: How do you measure the effectiveness of your role as a Scrum Master beyond just following ceremonies? Featured Retrospective Format for the Week: Lean Coffee Season recommends the Lean Coffee format for retrospectives as it puts control directly in the hands of participants who decide the discussion topics. This approach naturally increases engagement and ownership of the retrospective process. She emphasizes the importance of including warm-up activities to set the right mood and ensuring everyone speaks early in the session, while also following up on previous retrospective actions. [The Scrum Master Toolbox Podcast Recommends]

We're taking a critical look at the Double Diamond model, aka. Dual Track Development, aka. Dual Track Agile.This widely-adopted model might be leading leadership and/or teams astray, so we're taking some time to explore its limitations in real-world applications. From the misconception of linear progression to the crucial importance of keeping customers involved throughout the process, Brian tries to convince Om that the model needs significant rethinking!Other things we discuss are:Why the "messy middle" is where the real magic happensHow to properly involve your whole team in both discovery and deliveryThe importance of continuous customer involvementWhy organizational support is crucial for success#ProductManagement #AgileMethodology #ProductDevelopment #Leadership #ProductStrategyproduct management, agile methodology, product development, leadership, team development, double diamond, product discovery, product delivery, agile coaching, product strategy= = = = = = = = = = = =Watch on YouTubeSubscribe on YouTubeAppleSpotify= = = = = = = = = = = =Toronto Is My Beat (Music Sample)By Whitewolf (Source: https://ccmixter.org/files/whitewolf225/60181)CC BY 4.0 DEED (https://creativecommons.org/licenses/by/4.0/deed.en)

In this episode of the Team Katanu podcast, Kate Megaw (Certified Scrum Trainer, Agile Coach, and CEO of Arclight Agile) and Ryan Smith (Certified Product Owner and Scrum Master) dive into a common struggle among Agile teams: lack of accountability, unclear ownership, and role confusion.  They explore how natural hierarchies form within teams, why product owners and Scrum Masters often step on each other's toes, and how organizations unintentionally erode clarity.Kate and Ryan share real-world experiences, practical exercises, and techniques to help teams better define accountabilities without rigid role restrictions.  From Scrum Guide fundamentals to the gravitational pull of traditional project management, they uncover the root causes of dysfunction and offer actionable strategies to improve alignment.If you've ever wondered “Who should be doing what on my team?” or struggled with stepping on each other's responsibilities, this episode is for you.

BONUS: The Future of Agility, Insights from Industry Research with Simon Powers Is Agile really dead? What does this wide research from industry reveal?  In this detailed, and insightful episode, we explore the current state and future of agility with Simon Powers, founder of The Deeper Change Academy. Simon shares insights from his comprehensive survey conducted between October and December 2024, which included 311 survey responses, 15 case studies, and 8 in-depth interviews with senior leaders. The Current State of Agility The research reveals that while there's been a decline in traditional agile roles and certifications since October 2023, approximately 70% of organizations continue to invest in agile practices and transformations. However, these initiatives are often being rebranded and restructured, moving away from traditional "agile transformation" terminology. "Organizations are still embracing agility and moving forward with change, but what they're doing is that the names they're using are changing. People aren't necessarily being employed as agile coaches, but the agile coaching responsibilities are still required within organizations." Leadership Development and Organizational Structure A critical finding shows that leadership development in many organizations has stalled, creating two distinct organizational patterns: Organizations focused primarily on operational efficiencies, resulting in decreased agility Companies that have embraced coaching as a management tool and invested in leadership development "The culture is very different depending on where you sit. When you're constantly competing against a head count of a developer versus that of a coach, you're less able to take the necessary risks, talk to the right people, do bolder experiments, and have more of an effect within the organization." The Impact of Funding Models The research identified that the funding model for agile initiatives significantly impacts their success. Centrally funded transformation efforts tend to be more successful than those funded through departmental headcount, as they provide greater authority and ability to drive change across the organization. "Where people are hired or paid for within the head count, the overwhelming majority - like 90% of people who are in that position - are reporting that they do not have the authority to actually carry out the roles that they have responsibility for." Collaboration and Remote Work The survey revealed interesting insights about optimal collaboration patterns in the post-pandemic era: The sweet spot for office presence appears to be 2-3 days per week Full remote work can significantly reduce collaboration effectiveness Physical presence remains important for developing leadership skills and team dynamics "Being at home 100% of the time is a big reduction of collaboration and working on things and growing these skill sets that are needed in leadership as well as within the teams." Future Trends and Challenges Looking ahead, the research highlights several key areas that will shape the future of agility: Team structures remain a critical factor in software delivery capability The need for better strategy tools at senior leadership levels The importance of breaking down silos in software development The continued evolution of agile practices to meet increasing complexity "Organizations are going to need to sort out these problems that we've been slowly solving through agility for the last 20 years. We're just going to be continuing on, but what flavor? I don't know." About Simon Powers Simon Powers is the founder of The Deeper Change Academy and author of "Change: A Practitioner's Guide to Enterprise Coaching." With over 20 years of leadership experience, Simon empowers HR leaders and department heads to create thriving, human-centered workplace cultures through tailored coaching, strategic advisory, and transformational programs. You can link with Simon Powers on LinkedIn.

BONUS: Beyond Process, How Psychology is Reshaping Modern Leadership with Ari-Pekka Skarp In this BONUS episode, we dive deep into the evolving landscape of Agile leadership with Ari-Pekka Skarp, an experienced Agile Coach, Psychotherapist, and Organizational Psychologist. Drawing from his unique blend of expertise, Ari-Pekka shares his lessons learned on how leadership has transformed over the past decades and what the future holds for Agile organizations. The Evolution of Agile and Social Complexity "We replaced authority with collaboration, this was revolutionary." The journey of Agile adoption over the past 16 years has been marked by two significant developments: technological advancement and increasing social complexity. Ari-Pekka reflects on how Scrum introduced a revolutionary "shared" aspect of collaborative work, fundamentally changing how hierarchies are established in modern organizations. This shift represents a departure from traditional command-and-control structures towards more collaborative approaches. The Therapeutic Turn in Leadership "Nowadays we are almost talking about the leaders as some sort of therapist." One of the most significant shifts in organizational dynamics has been the "therapeutic turn" in leadership. Where leaders were once expected to be commanders, today's leaders must embody the qualities of a therapist - demonstrating empathy, emotional intelligence, and a deep understanding of their team members' well-being. This transformation reflects broader societal changes, with mental health awareness becoming increasingly central to workplace dynamics. The Rise of Humanistic Leadership "We need a more humanistic leadership, but what does that look like in practice?" As organizations become more networked and complex, the need for humanistic leadership approaches becomes evident. Ari-Pekka shares his experience as an organizational psychologist, highlighting how traditional role definitions often fall short in addressing modern workplace challenges. The integration of tools from family therapy and other psychological disciplines is becoming crucial for effective leadership. The Future of Organizations "In order to compete you have to have a very well functioning organization!" Looking ahead, Ari-Pekka emphasizes the importance of viewing organizations through a psychological lens. He argues that organizational mental health culture and the psychological aspects of work are becoming critical competitive advantages. This perspective extends beyond processes and tools to encompass the holistic growth and well-being of people within organizations. A New Paradigm for Work "The biggest change was from a mechanistic world-view to a more humanistic world-view." As Agile evolves beyond its origins as a protest movement, Ari-Pekka explores how organizations are increasingly forming around purposes rather than just profits. He advocates for generative planning processes that foster creativity and human flourishing, suggesting a shift toward viewing work and organizations as social processes rather than mechanical systems. Leading Through Conversations "Why don't we look at work, organizations as social processes?" The conversation concludes with a powerful metaphor of leaders as gardeners, nurturing growth and development through meaningful conversations. This approach represents a fundamental shift in how we think about leadership and organizational development, emphasizing the importance of creating environments where people can thrive. In this segment, we refer to the work of Esko Kilpi, a thought leader and business philosopher who helped introduce complexity to the Agile community. About Ari-Pekka Skarp Ari-Pekka is a highly experienced Agile Coach, Psychotherapist, and Organizational Psychologist with over 20 years of experience working with organizations. As an author of several books on topics such as Complexity, the mind, and Mindfulness, Ari-Pekka blends deep psychological insight with practical expertise to help leaders and teams navigate the evolving landscape of work. You can link with Ari-Pekka on LinkedIn and connect with Ari-Pekka on Twitter.

“We're starting to see that lightbulb moment in folks' minds to say, ‘It's okay to be a little bit vulnerable. It's okay to talk about some painful things.' It's hard to do that within the government world because of the old ways of thinking and working, but we're starting to break those barriers down.” In this episode, Adam talks to Scott Sinclair, Agile Coach within the U.S. Army PEO and Shawn Lowe, SPCT at Accenture about driving successful transformations in a government context. The trio dives into topics including the need for strong leadership to overcome cultural resistance to change, clearly communicating to explain the why behind the transformation, and the importance of defining and measuring the impact of the changes, rather than just monitoring metrics. Like what you hear? Connect with Scott and Shawn on LinkedIn. Explore SAFe courses here. This podcast panel was recorded in October 2024.  --- On October 1, 2024, PEO EIS rebranded to PEO Enterprise to reflect a more modern, Agile organization that includes enterprise software and technology services. To learn more about PEO Enterprise, visit their website.

Antti Horelli: Balancing Product Owner Responsibilities with Team Empowerment 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: Sharing Responsibility with the Team The great Product Owner excels by being present and actively sharing knowledge with the team. While the PO role can be overwhelming due to its responsibility to abstract complexity from the team, the best POs find ways to share responsibilities appropriately. They understand that their role goes beyond making decisions and includes enabling the team to participate in the product discovery process. The Bad Product Owner: The Absent Decision Maker In this anti-pattern, the Product Owner was only available for planning and sprint reviews due to other commitments. This limited availability severely impacted the team's ability to make progress, especially given the complex nature of software development where requirements are discovered rather than pre-defined. The absence of business knowledge during development led to delays and misunderstandings, highlighting how critical continuous PO involvement is for team success. For tips on how to help PO's be more present, check out our Sprint PO Checklist which includes tips on how to lead that conversation and a clear set of questions to go through together with your PO.  Self-reflection Question: How can you help ensure more presence and better collaboration between the Product Owner and the development team? [The Scrum Master Toolbox Podcast Recommends]

Antti Horelli: Achieving Productive Serenity - Sign of Scrum Master Success Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. Antti describes success for Scrum Masters through the concept of "productive serenity" - a state where teams maintain high productivity while remaining calm and focused. This is characterized by frequent small discussions, excited but not stressed team members, and the ability to address challenges with serious calmness. The team operates with the mindset of "be quick, but don't hurry," demonstrating maturity in problem-solving and collaboration. Featured Retrospective Format for the Week: The Timeline Retrospective The Timeline Retrospective format is particularly effective for longer deliveries or projects, serving as an excellent reflection tool. Antti emphasizes keeping participants active and encouraging them to share "fuzzy" observations that could be early signals for better decision-making. The format helps teams identify patterns and insights that might otherwise go unnoticed. Self-reflection Question: How can you help your team achieve a state of productive serenity? [The Scrum Master Toolbox Podcast Recommends]

Antti Horelli: Balancing Delivery Pressure with Agile 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. Antti shares his experience leading an agile transformation across three siloed organizations: development, QA/testing, and support. The transformation involved establishing cross-functional teams and implementing visual management through a comprehensive planning wall. Despite initial progress with joint planning days and rolling wave planning, the pressure to deliver led to reverting to traditional project management approaches. This story highlights the challenge of maintaining agile principles while under delivery pressure and the importance of focusing on reliable delivery rather than agile for agile's sake. Self-reflection Question: How do you balance the need for immediate results with long-term agile transformation goals? [The Scrum Master Toolbox Podcast Recommends]

On this episode of the Women in Agile podcast, Emily Lint sits down with Paula Susman to discuss people managers and agile transformations; what is and is not necessary as an Agilist to help managers transform and how do you set yourself and managers or leaders up for success in the long run to let go of command-and-control. About the Featured Guest Paula Susman is an accomplished and solutions-driven Agile Coach with 8 years of multifaceted experience in Agile transformations, process improvement and team management. Proven track record of success in blending and building highly evolved teams with Agile approaches within the SDLC.  Follow Paula Susman on LinkedIn The Women in Agile community champions inclusion and diversity of thought, regardless of gender, and this podcast is a platform to share new voices and stories with the Agile community and the business world, because we believe that everyone is better off when more, diverse ideas are shared. Podcast Library: www.womeninagile.org/podcast Women in Agile Org Website: www.womeninagile.org    Connect with us on social media! LinkedIn: www.linkedin.com/company/womeninagile/ Instagram: www.instagram.com/womeninagile/ Twitter: www.twitter.com/womeninagileorg  Please take a moment to rate and review the Women in Agile podcast on your favorite podcasting platform. This is the best way to help us amplify the voices and wisdom of the talent women and allies in our community! Be sure to take a screenshot of your rating and review and post it on social media with the hashtag #womeninagile to help spread the word and continue to elevate Women in Agile.   About our Host Emily Lint is a budding industry leader in the realm of business agility. Energetic and empathetic she leverages her knowledge of psychology, business, technology, and mindfulness to create a cocktail for success for her clients and peers. Her agile journey officially started in 2018 with a big move from Montana to New Mexico going from traditional ITSM and project management methodologies to becoming an agile to project management translator for a big government research laboratory. From then on she was hooked on this new way of working. The constant innovation, change, and retrospection cured her ever present craving to enable organizations to be better, do better, and provide an environment where her co-workers could thrive.  Since then she has started her own company and in partnership with ICON Agility Services serves, coaches, and trains clients of all industries in agile practices, methodologies, and most importantly, mindset. Please check out her website (www.lintagility.com) to learn more. You can also follow Emily on LinkedIn (https://www.linkedin.com/in/emilylint/).    About our Sponsor Scrum.org is the Home of Scrum, founded in 2009 by Scrum co-creator Ken Schwaber focused on helping people and teams solve complex problems by improving how they work through higher levels of professionalism. Scrum.org provides free online resources, consistent experiential live training, ongoing learning paths, and certification for people with all levels of Scrum knowledge. You can learn more about the organization by visiting www.scrum.org.

In this podcast, two tech industry veterans reflect and share candid insights from 20 years of navigating the ever-changing world of tech and software development. Join Product Manager Brian Orlando and Enterprise Business Agility Coach Om Patel as they talk strategies for recession-proofing your career, the critical importance of talking to customers, and the role leadership plays in driving organizational success. Come for the positive experiences, but stay for the cringe-worthy tangents - we also explore the all-too-common pitfalls of tech such as confusing utilization with progress, the prevalence of Tayloristic management, and the emotional toll of accruing technical debt. Whether you're at the start of your career or a 20-plus year veteran like us, we'd love to hear if our experiences are similar to your own and we hope you enjoy our discussion on spending 20 years in tech!#TechCareers #LeadershipLessons #ProductManagement #SoftwareDevelopment #AgileReferencesWeapons of Mass Instruction by John Taylor GattoPunished by Rewards by Alfie KohnTurn the Ship Around! by L. David MarquetThe New Economics for Industry, Government, Education by W. Edwards Deming= = = = = = = = = = = =Subscribe on YouTube:https://www.youtube.com/channel/UC8XUSoJPxGPI8EtuUAHOb6g?sub_confirmation=1YouTubehttps://youtu.be/I_LF4QUU-XMApplehttps://podcasts.apple.com/us/podcast/agile-podcast/id1568557596Spotifyhttps://open.spotify.com/show/362QvYORmtZRKAeTAE57v3= = = = = = = = = = = =Toronto Is My Beat (Music Sample)By Whitewolf (Source: https://ccmixter.org/files/whitewolf225/60181)CC BY 4.0 DEED (https://creativecommons.org/licenses/by/4.0/deed.en)

Antti Horelli: The Challenge of Breaking Silos, And Building Collaborative Agile Teams Remotely 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. Antti shares a story about a team of solo workers who struggled to collaborate effectively. Despite having technical expertise, the team faced challenges in delivering value due to conflicting views on "good tech work" and communication issues. The remote working environment further complicated their interactions, ultimately leading to the team's dissolution. This experience emphasizes the importance of focusing on team cohesion and establishing clear ways of working, especially in distributed teams. Featured Book of the Week: "Lean, Resolving the efficiency paradox" Antti recommends "This is Lean: Resolving the Efficiency Paradox” by Modig et al., an approachable book for its clear explanation of flow efficiency versus resource efficiency in Scrum and Kanban. The book helped him understand the counterintuitive benefits of optimizing for one-piece flow and completing single value-delivering items, offering valuable insights for process improvement. Self-reflection Question: How can you help your team transition from individual work patterns to effective collaboration? [The Scrum Master Toolbox Podcast Recommends]

Antti Horelli: The Three-Day Sprint Planning Nightmare - Learning from Agile Failure 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. In this episode, Antti shares a critical learning moment from his early Scrum Master days when a sprint planning session extended to three days due to poor preparation. The team discovered that backlog items were much larger and different than expected, while unexpected background decisions further complicated the planning. This experience highlighted the vital importance of proper refinement work and maintaining clear communication channels about decisions affecting the team. Self-reflection Question: How do you ensure your team has sufficient context about upcoming decisions while avoiding information overload? [The Scrum Master Toolbox Podcast Recommends]

Wird eine Frau Mutter, verdient sie fortan weniger. Über dieses Phänomen, welches als „Motherhood Penalty“ bekannt ist, haben wir in unserer neuen Podcastfolge gesprochen. Im Gespräch mit Sabine, Change Managerin & Agile Coach eines Chemiekonzerns und Mutter von vier Töchtern spricht finanz-heldin Alicia über dieses Phänomen. Denn nach über einem Jahrzehnt im klassischen Familienmodell – Papa arbeitet Vollzeit, Mama Teilzeit – kehrte Sabine in Vollzeit während der Pandemie zurück und das veränderte ihren Blick auf die Rollenverteilung und die Notwendigkeit struktureller Veränderungen in Politik und Wirtschaft, aber auch in unserer Gesellschaft. Sie berichtet von Herausforderungen und wie sie diese gemeistert hat, teilt Tipps zur Aufteilung der Care-Arbeit und gibt einen Einblick in die Berechnung ihres Lebenserwerbseinkommens. Im Gespräch erwähnte Folgen: [#243 Familie und Beruf: ein Work-Life-Balance-Traum?](https://finanz-heldinnen.de/podcast-schwungmasse/243-familie-und-beruf-ein-work-life-balance-traum) Bleib mit uns in Kontakt! - [Website](https://finanz-heldinnen.de/) - [Instagram](https://www.instagram.com/finanzheldinnen/) - [Finanzplaner](https://finanz-heldinnen.de/planer)planer

In this episode of the Aspire and Achieve In Your Agile Career podcast series, Emily Lint speaks with Anne Monteiro about her global transitions in coaching and product management. Together they explore how to navigate uncertainty in your Agile career and identify business areas that align with your skills as well as how to identify emerging trends to stay on the top of your game in the product management and coaching space.    About the Featured Guest Anne Bravieira Monteiro is an expert in Agile methodologies, project management, and product development. As a Product and Agile Coach at HelloFresh with over ten years at IBM, Anne led agile transformations to boost team performance and customer satisfaction. Anne advocates for diversity, openness, and empathy believing these values are key to overcoming challenges and is passionate about creating tech products that simplify life.   Follow Anne Bravieira Monteiro on LinkedIn (www.linkedin.com/in/anne-bravieira)   The Women in Agile community champions inclusion and diversity of thought, regardless of gender, and this podcast is a platform to share new voices and stories with the Agile community and the business world, because we believe that everyone is better off when more, diverse ideas are shared.   Podcast Library: www.womeninagile.org/podcast Women in Agile Org Website: www.womeninagile.org    Connect with us on social media! LinkedIn: www.linkedin.com/company/womeninagile/ Instagram: www.instagram.com/womeninagile/ Twitter: www.twitter.com/womeninagileorg    Please take a moment to rate and review the Women in Agile podcast on your favorite podcasting platform. This is the best way to help us amplify the voices and wisdom of the talent women and allies in our community! Be sure to take a screenshot of your rating and review and post it on social media with the hashtag #womeninagile to help spread the word and continue to elevate Women in Agile.   About our Host Emily Lint is a budding industry leader in the realm of business agility. Energetic and empathetic she leverages her knowledge of psychology, business, technology, and mindfulness to create a cocktail for success for her clients and peers. Her agile journey officially started in 2018 with a big move from Montana to New Mexico going from traditional ITSM and project management methodologies to becoming an agile to project management translator for a big government research laboratory. From then on she was hooked on this new way of working. The constant innovation, change, and retrospection cured her ever present craving to enable organizations to be better, do better, and provide an environment where her co-workers could thrive.    Since then she has started her own company and in partnership with ICON Agility Services serves, coaches, and trains clients of all industries in agile practices, methodologies, and most importantly, mindset. Please check out her website (www.lintagility.com) to learn more. You can also follow Emily on LinkedIn (https://www.linkedin.com/in/emilylint/).    About our Sponsor Scrum.org is the Home of Scrum, founded in 2009 by Scrum co-creator Ken Schwaber focused on helping people and teams solve complex problems by improving how they work through higher levels of professionalism. Scrum.org provides free online resources, consistent experiential live training, ongoing learning paths, and certification for people with all levels of Scrum knowledge. You can learn more about the organization by visiting www.scrum.org.

Why is visual communication essential for leadership and driving business success? In this episode of The CEO Project, Jim Schleckser speaks with Olina Glindevi, the Visual Agile Coach and author of The Visual Agile Coach Playbook. Olina shares her unique approach to integrating visual communication techniques into Agile practices to foster better engagement, communication, and value delivery within teams. Drawing on her extensive experience in IT and Agile roles such as Scrum Master and Agile Coach, Olina showcases how visual tools can help leaders and teams streamline their processes, adapt Agile frameworks to their contexts, and align organizational goals effectively. She also provides insights into the cultural and practical applications of visual techniques, ensuring they remain accessible and impactful regardless of individual artistic skill. Key Takeaways: → Visual communication clarifies and enhances Agile practices, making them more engaging and effective. → Using visuals helps leaders and teams identify the core of complex processes and align their strategies. → Practical tools like Miro and Procreate support hybrid and digital collaboration in Agile environments. → Simplifying communication through visuals fosters stronger alignment across diverse organizational cultures. → Conducting retrospectives is essential for continuous improvement and adapting Agile practices to specific needs. More from Olina Glindevi Olina Glindevi is a visual communicator, trainer, and project manager with extensive experience in leadership roles, including Agile Coach, Scrum Master, and Release Train Engineer (RTE). Driven by a passion for Agile methodologies and coaching leadership, Glindevi brings creativity, structure, and a focus on business value to every project. With a proven ability to inspire and motivate, Glindevi excels at bringing people together to achieve common goals. Her coaching-led approach emphasizes communication, visualization, and transparency, creating an environment where teams thrive and deliver high-quality outcomes. She has successfully supported teams and organizations at all levels, fostering alignment, collaboration, and engagement. Find her book Online: The Visual Agile Coach Playbook Website: https://thevisualagilecoach.com/ LinkedIn: @thevisualagilecoach Instagram: @the_visual_agile_coach Contact: olinasmail@gmail.com If you are an experienced CEO looking to grow your company, visit https://www.TheCEOProject.com You can also reach Jim by email: Jim@TheCEOProject.com LinkedIn: @theceoproject Instagram: @the_ceoproject Twitter/X: @the_CEO_Project Facebook:  @IncCEOproject  

BONUS: A Coaching Masterclass - How Our Language Affects Our Leadership Style, And The Culture We Create, With Michelle Pauk and Victor Pena In this BONUS episode, Victor Pena and Michelle Pauk dive deep into the power of language in shaping our work as leaders, Agile Coaches, and Scrum Masters. Together, we explore how the words we use influence relationships, decisions, and the success of Agile practices. From navigating the ambiguity of language to fostering effective communication, this episode provides actionable insights to help you thrive in a constantly changing workplace. Language as a Culture Carrier “Language is how we carry culture, but without clarity, it can lead to misalignment and conflict.” Victor and Michelle discuss how language reflects and shapes workplace culture. Misaligned terminology—like “servant leader”—can create tension between teams and executives. They highlight the importance of achieving shared understanding and the role of language in fostering trust and collaboration. “Start by asking what others mean by key words—it's the first step toward alignment.” Feedforward vs. Feedback “Feedback gets us stuck in the past, while feedforward builds a path to a better future.” Drawing inspiration from Marshall Goldsmith, we discuss how focusing on future-oriented improvement (feedforward) avoids the blame game and builds positive momentum. As Agile practitioners, shifting from root cause analysis to solution-focused coaching allows teams to move forward effectively. “Ask yourself, what can we do better tomorrow instead of dwelling on what went wrong yesterday?” The Ambiguity of Language in Collaboration “Words mean different things to different people—be curious about how others see the world.” Victor and Michelle unpack how language ambiguity impacts communication and decision-making. They emphasize the need to explore the assumptions behind others' words and how Agile principles like #NoEstimates challenge traditional views on planning and work management. “When you encounter a term that seems obvious, ask: What does this mean to you?” Semiotics and the Language of Work “Symbols are the silent drivers of collaboration.” Semiotics, the study of symbols, plays a vital role in Agile practices like visual management. From story cards to team boards, symbols help teams communicate and navigate their work. The duo discusses how the language of Agile evolves through symbols and how to introduce these effectively in organizations. “Create visual symbols that align with your team's values—they'll anchor your collaboration.” Beyond the “Agile is Dead” Debate, Raising The Bar Of Our Shared Conversation “What's trying to come forward in the evolution of Agile?” While some criticize Agile as outdated, Victor and Michelle argue that its core principles—delivering value faster and improving quality—remain timeless. They explore how Agile can evolve to meet current challenges while retaining its essence. “Instead of asking if Agile is dead, ask what the next evolution looks like.” About Victor Pena and Michelle Pauk Victor Pena is an Agile Coach dedicated to helping organizations achieve business agility. With a focus on innovation, collaboration, and delivering great customer value, Victor transforms practices to ensure long-term success in a dynamic environment. You can link with Victor Pena on LinkedIn and connect with him via email at victor@vpena.com. Michelle Pauk is the founder of Streamside Coaching, helping leaders and organizations thrive through change. With over 15 years of experience in Agile environments and certifications from the International Coaching Federation, Michelle specializes in leadership development and organizational growth. You can link with Michelle Pauk on LinkedIn and connect with her at StreamsideCoaching.com.

Aliona Zapanovici: Helping Agile Teams Be Passionate About Their Products, A Product Owner Superpower Read the full Show Notes and search through the world's largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. The Great Product Owner: Helping Agile Teams Be Passionate About Their Products, A PO Superpower A standout Product Owner embodies a blend of deep product knowledge, market insight, and trust in the development team. Aliona highlights how such a PO remains accountable while empowering the team to excel, ensuring they see their value reflected in the product. This dynamic builds passion and commitment within the team. Self-reflection Question: How do you work with the Product Owner to ensure that your team feels trusted and valued while maintaining accountability? The Bad Product Owner: The Challenges of a Proxy PO Aliona shares an experience with a proxy PO lacking real decision-making power. This situation led to confusion, delays, and rework, ultimately ending in the PO's departure and a demotivated team. This story underscores the necessity for Product Owners to possess both authority and clear accountability to effectively guide the team. Self-reflection Question: Does your PO have the necessary authority and trust to lead effectively? [The Scrum Master Toolbox Podcast Recommends]

Aliona Zapanovici: How To Help Agile Teams Own Their Work, And Be Independent Read the full Show Notes and search through the world's largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. When it comes to successful approaches for great Scrum Masters and Agile Coaches, Aliona strives for teams to be proactive, care deeply about the product, and value the impact they create. This approach, though sometimes daunting, fosters independence and strong ownership among team members. Self-reflection Question: What steps can you take to empower your team to be more independent? Featured Retrospective Format for the Week: Well / Not So Well / Improve / Actions Aliona prefers simplicity in retrospective formats to maintain focus. The “Well / Not So Well / Improve / Actions” structure allows teams to zero in on what truly matters without getting lost in complex frameworks. She also supports the use of anonymous boards for candid feedback, while cautioning their use if team trust is low. About Aliona Zapanovici  Aliona is an Agile Coach and Scrum Master with a background in architecture who transitioned to IT to pursue her passion. She values impactful contributions over years of experience. Balancing her roles as a coach, mentor, and mother, she focuses on empowering teams and guiding individuals to achieve their best. You can link with Aliona Zapanovici on LinkedIn.

Aliona Zapanovici: Co-creation As The Transformative Approach To Agile Change Read the full Show Notes and search through the world's largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. Aliona reflects on the essence of change management: change cannot be forced. An experience with a resistant team taught her that involving the team in co-creation fosters acceptance and lasting transformation. By listening first and suggesting incremental adjustments, she found that building trust and making the team part of the solution makes change not just possible, but welcomed. Self-reflection Question: How do you involve your team in shaping changes that impact them? [The Scrum Master Toolbox Podcast Recommends]