Podcasts about Scrum

Anh Vu: From Project Mindset to Product Thinking - Leading Client 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. Anh describes a transformative collaboration experience while building multiple websites for a client. Over time, his team recognized significant commonalities between projects and saw the opportunity to create reusable components for future work. However, they faced resistance when trying to shift the client's mindset from short-term project delivery to long-term product thinking. The business stakeholders remained focused on immediate project completion rather than investing in sustainable, reusable solutions.  Anh's approach to leading this change involved presenting concrete evidence from previous projects to demonstrate the tangible benefits of component reusability. Rather than just proposing the idea theoretically, they suggested implementing reusable components immediately within the current project, showing rather than just telling. His strategy centered on providing clear evidence of benefits and demonstrating achievability, making the transition from project to product mindset more tangible and less risky for the client. In this episode, we refer to the book “From Project to Product” by Mik Kersten.  Self-reflection Question: How might you help your stakeholders see beyond immediate deliverables to recognize the long-term value of sustainable practices and reusable solutions? [The Scrum Master Toolbox Podcast Recommends]

Anh Vu: From Individual Stars to Team Players - Transforming Competitive Developers Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. Anh recounts his first Scrum project as a Scrum Master for a payment company, leading a team of five developers working on a new product with new technology and devices. The challenge was compounded by the fact that this was a completely new team where members didn't know each other. What started as an attempt to make work visible quickly deteriorated when developers began competing to prove they were the best rather than collaborating toward shared goals. Each developer focused solely on their individual tasks without considering the overall outcome, and when bugs appeared at the end of sprints, blame games began.  This anti-pattern of developers not prioritizing team results created a cycle where team members wouldn't help each other, ultimately undermining the project's success. Anh's key learning was that the root problem wasn't process-related but trust-related, and as a Scrum Master, addressing surface-level issues isn't enough - the real work lies in building foundational trust within the team. Self-reflection Question: In your current team, are individual achievements being celebrated more than collective success, and how might this be affecting overall team trust and collaboration? Featured Book of the Week: The Five Dysfunctions of a Team Anh recommends "The Five Dysfunctions of a Team" as essential reading for understanding team dynamics. He emphasizes that trust is the basic foundation for people to succeed together, and this book provides both the why and the how for building that trust. According to Anh, trust serves as the foundation for all teams, making it crucial knowledge for both Scrum Masters and Project Managers who need to facilitate effective team collaboration. [The Scrum Master Toolbox Podcast Recommends]

Limitations of the Sprint Retrospective...Back in my Scrum days — yes, with 20+ years of experience, I am allowed to say that — I genuinely enjoyed facilitating Retrospectives. It was a perfect moment to pause and identify areas for improvement.How to connect with AgileDad:- [website] https://www.agiledad.com/- [instagram] https://www.instagram.com/agile_coach/- [facebook] https://www.facebook.com/RealAgileDad/- [Linkedin] https://www.linkedin.com/in/leehenson/

Anh Vu: The Hidden Cost of Skipping Scrum Ceremonies 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. Anh shares his experience as a new Project Manager who was confident about understanding Scrum but quickly discovered the complexity of implementing it effectively. His team's daily meetings turned into lengthy debates about solutions, consuming excessive time and energy, leading team members to complain about meeting overload. When the team suggested moving discussions to Slack to avoid meetings, this created new problems with missed insights and additional coordination challenges.  Anh explains how they fell into the "Scrum-but" anti-pattern, where teams claim to use Scrum while avoiding its core practices. The real learning came when he realized that successful framework implementation requires connecting core values with mechanics - for example, linking transparency from Scrum values to actual practices. His key insight: always share the "why" behind everything you do, and remember the Shu-Ha-Ri principle - make it work first before making changes. Self-reflection Question: How might you be unconsciously implementing "framework-but" patterns in your current role, and what core values should you reconnect with your daily practices? [The Scrum Master Toolbox Podcast Recommends]

Avoid Getting Good at AgileI know the agile universe has been around for a long time. You may have even been using agile concepts since XP or Scrum in the mid-90s, I get it. But if you were to line up every single person in your whole country that works at all the organizations, large or small, and ask them how well they understood what it means to be agile, what do you think you'd find?How to connect with AgileDad:- [website] https://www.agiledad.com/- [instagram] https://www.instagram.com/agile_coach/- [facebook] https://www.facebook.com/RealAgileDad/- [Linkedin] https://www.linkedin.com/in/leehenson/

Joelle Tegwen: Business Analyst to Product Owner—More Than a Title Change Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. The Great Product Owner: The Collaborative Visionary Joelle worked with an exceptional Product Owner at a medical company who was leading their team into a new way of working. This PO understood both the vision piece of the work and the importance of experimentation, recognizing that the team was responsible for figuring out how to solve the problems they were trying to tackle. Working within a Large Scale Scrum framework, they demonstrated patience while collaborating with skilled team members to improve how they worked together. Rather than complaining to the team about performance issues, this PO collaborated directly with the Scrum Master to address challenges. Most importantly, they maintained crystal clear focus on customer value, ensuring every decision and direction connected back to what would truly benefit the end user. The Bad Product Owner: The JIRA Manager Joelle describes the problematic pattern of Business Analysts who receive a title change to Product Owner without understanding the fundamental shift in role and responsibilities. These individuals continue to see themselves as scribes rather than visionaries, treating their primary job as managing JIRA instead of setting a vision for where the product should go. They typically lack understanding of meaningful metrics and rely on gut-feel prioritization rather than data-driven decisions. Most critically, they fail to communicate about problems to solve or establish a clear North Star for the team. Joelle recommends providing these POs with structured formats for Epics and features that start with hypothesis, problem, and measures, helping them think at higher levels than just user story management. Self-reflection Question: Whether you're a Product Owner or work closely with one, how might you help elevate the conversation from task management to vision and problem-solving? [The Scrum Master Toolbox Podcast Recommends]

Joelle Tegwen: Building High-Performing Teams Through Three Essential Elements 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. Joelle identifies three essential characteristics for Scrum Master success: psychological safety, collaboration, and cross-skilling with role blurring. She emphasizes the importance of teams being comfortable with conflict, drawing from Amy Edmondson's work and Google's Project Aristotle research. Her approach involves mapping where a team currently stands and focusing on one of these three characteristics at a time. The key is building relationships where challenging each other becomes positive behavior, being clear about what you're trying to achieve with the team, and regularly checking in for feedback. Success comes from creating an environment where team members can grow beyond their individual silos while maintaining strong collaborative relationships. Featured Retrospective Format for the Week: Sailboat Retrospective As a consultant frequently joining new teams, Joelle relies on the Sailboat retrospective format to quickly understand where teams are positioned. Teams use the sailboat metaphor to explain their current situation, which gives her rapid insight into their challenges and strengths. This format is particularly valuable because it helps her identify what not to change - understanding what the team considers their strengths prevents well-intentioned interference with what's already working well. The visual metaphor makes it easy for teams to express complex dynamics while providing the facilitator with actionable intelligence for coaching direction. Self-reflection Question: Looking at your current team through the sailboat metaphor, what would you identify as the wind in your sails versus the anchors holding you back, and how might this perspective change your improvement priorities? [The Scrum Master Toolbox Podcast Recommends]

A strong project kickoff strategy can make or break your software project. In this episode of Building Better Developers with AI, Rob Broadhead and Michael Meloche revisit and expand upon their earlier episode, Mastering the Project Kickoff – Setting the Stage for Success. This time, they use AI not to redefine strategy, but to reflect on what worked, what's changed, and what new insights can improve how teams approach kickoffs today. The result is a deeper, more refined look at launching software projects with intention and clarity—before writing a single line of code. Why Your Project Kickoff Strategy Still Matters “Two weeks in, and no one agrees on the goal.” It's a story most developers know too well. The reason? A weak or nonexistent project kickoff strategy. Rob and Michael break down how early misalignment on goals, responsibilities, or MVPs can derail projects quickly. To avoid this, teams need a consistent, structured approach that starts before the first line of code is written. How AI Improves Your Project Kickoff Strategy AI can't replace a good team conversation, but it can support a better project kickoff strategy by helping structure discussions, define deliverables, and highlight gaps in planning. Some examples AI tools can generate: Stakeholder role outlines Risk assessment prompts Project objective statements Kickoff meeting checklists With good prompting, AI becomes a partner in better planning. Core Elements of a Strong Project Kickoff Strategy A repeatable project kickoff strategy should include the following: 1. Purpose and Objectives What are we building, and why? Define the business problem and expected outcome clearly. 2. Team Roles and Ownership List all stakeholders, assign responsibilities, and clarify decision-makers. Misunderstood roles create avoidable blockers. 3. Process and Delivery Plan Establish your delivery method (Agile, Scrum, Kanban) and how progress will be tracked, tested, and shared. 4. MVP and Scope Control Rob and Michael emphasize: everything must map to the MVP. If it doesn't, reconsider the feature. 5. Documentation and Visibility Centralize everything. Use Notion, Confluence, or shared drives, and record meetings for searchability and auditability. Warning Signs of a Poor Kickoff Strategy Michael and Rob call out red flags that reveal when your project kickoff strategy is weak or broken: No written MVP or goals Absent stakeholders during planning Overlapping roles with unclear boundaries “We'll figure it out later” mindset No documentation or decision logs Ignoring these signs leads to confusion, rework, and a breakdown in team trust. Anchor Your Kickoff Strategy with an MVP “If your feature doesn't pass a test, it's not part of your MVP.” Michael shares a practical tip: create user stories first, then turn them into pass/fail tests. This ensures that your project kickoff strategy stays laser-focused on outcomes—not distractions like UI polish or edge-case bells and whistles. Challenge: Audit Your Project Kickoff Strategy Before your next launch, hold a quick strategy review. Ask: Do we have a clearly defined MVP? Are team roles written and confirmed? Are meeting notes and decisions documented? Does every feature connect to project goals? If not, revise your strategy now—before you waste time. Stay Connected: Join the Developreneur Community We invite you to join our community and share your coding journey with us. Whether you're a seasoned developer or just starting, there's always room to learn and grow together. Contact us at info@develpreneur.com with your questions, feedback, or suggestions for future episodes. Together, let's continue exploring the exciting world of software development. Additional Resources Working The Project – Consulting Success CYA Documentation: Getting Started With Consulting Winning Your First Project: A Developer's Guide to Starting Your Side Hustle A Project Management and Pricing Guide for Success Building Better Developers With AI Podcast Videos – With Bonus Content

Before he was in the dugout watching Richie McCaw lift the 2011 Rugby World Cup, forwards coach Mike Cron had spent years working as a police detective. 

Aaron Woods, Wade Graham & Emma Lawrence are in to talk all the latest from the Knights, we go inside how R360 will impact the NRL & preview every game of round 20!See omnystudio.com/listener for privacy information.

Aaron Woods, Wade Graham & Emma Lawrence are in to talk all the latest from the Knights, we go inside how R360 will impact the NRL & preview every game of round 20!See omnystudio.com/listener for privacy information.

Seringkali disalahpahami sebagai sekadar "sekretaris tim" atau biaya tambahan, peran Scrum Master sebenarnya adalah katalisator transformatif dalam kerangka kerja Agile. Mereka bukan hanya fasilitator rapat, melainkan ahli pola pikir Agile yang berdedikasi untuk membangun tim yang mandiri dan berkinerja tinggi. Tujuan utama seorang Scrum Master adalah mendorong swa-organisasi, menumbuhkan kepemilikan dan akuntabilitas, serta secara aktif menghilangkan hambatan dengan memberdayakan tim untuk menemukan solusi mereka sendiri, bukan hanya menyelesaikannya secara langsung.                                                                                                                           Dampak seorang Scrum Master melampaui batas tim individu. Melalui konsep #ScrumMasterWay, mereka menggeser fokus dari tim pengembangan ke hubungan yang lebih luas dan akhirnya ke seluruh sistem organisasi. Ini berarti mereka memandu adopsi prinsip-prinsip Agile di seluruh perusahaan, bertindak sebagai agen perubahan yang menyebarkan budaya, filosofi, dan pola pikir empiris Scrum. Mereka adalah pemimpin yang membangun pemimpin lain, mendorong desentralisasi, dan memastikan organisasi tetap tangkas dan adaptif.   Untuk mencapai semua ini, seorang Scrum Master yang hebat dilengkapi dengan berbagai metaskill dan kompetensi esensial, mulai dari mengajar, mendengarkan, dan membina, hingga pemahaman mendalam tentang manajemen perubahan dan analisis akar masalah. Peran Scrum Master adalah investasi strategis dalam modal manusia dan budaya organisasi, yang secara kausal berkontribusi pada inovasi berkelanjutan dan ketahanan yang dinamis

Joelle Tegwen: Breaking Knowledge Silos Through Strategic Skill Sharing 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 as a Scrum Master on a team rewriting an old application, Joelle faced a significant challenge: experienced developers were located in India while new, experienced developers brought in locally lacked familiarity with the medical domain. Drawing inspiration from The Phoenix Project, she implemented a skills matrix to address the knowledge silos that were preventing new team members from contributing effectively.  Using a teacher-student model, initially frustrated leaders who had to work with "students" discovered within 2-3 sprints that they were also learning new things and no longer carried the pressure of being the only ones with critical knowledge. The new team members brought fresh ideas that improved the codebase, and when the team eventually grew too large, the skills matrix facilitated smooth self-selection for team reorganization. What started as a solution to get new hires productive evolved into a comprehensive approach to knowledge sharing and team scalability. Self-reflection Question: Where do knowledge silos exist in your current team or organization, and how could you implement structured knowledge sharing to transform those constraints into learning opportunities? [The Scrum Master Toolbox Podcast Recommends]

In this episode of the Scrum.org Community Podcast, host Dave West sits down with Tyson Bertmaring, Head of Partnership Success and Adrian Veres, Chief Scientific Officer from Dyno Therapeutics, a cutting-edge gene therapy startup. They share how Dyno applies the ideas of the Agile Product Operating Model (APOM) to complex scientific research—shifting from traditional structures to empowered, cross-functional teams aligned to clear goals.You will hear how Dyno integrates APOM principles such as product-centric team design, continuous planning, and aligned incentives to drive innovation in a high-stakes environment. The conversation highlights how adopting a product mindset, supported by an enabling organization, creates the conditions for focus, adaptability, and breakthrough scientific results. 

Steve Sarkisian meets with the Texas media at SEC Media Days!  

Texas Longhorns QB Arch Manning met with the Texas media at SEC Media Days!  

Texas Longhorns LB Anthony Hill & DB Michael Taaffe met with the Texas media at SEC Media Days!  

Joelle Tegwen: How to Break Through the 'Not My Problem' Mentality 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. As a consultant often entering teams when problems already exist, Joelle encountered a team that took months to get anything into production. While some IT leaders and QA folks didn't see this as problematic, Joelle discovered the QA team was actually struggling with constant retesting due to work coming back repeatedly. She helped the team articulate the value of needed changes and discovered they didn't know how to split stories effectively. By focusing on what they could do rather than what they couldn't, and implementing test automation to enable smaller stories, the team began making meaningful progress toward more sustainable delivery practices. Featured Book of the Week: How Minds Change by David McRaney David McRaney, who runs the podcast “You Are Not Smart” about cognitive biases, presents a powerful insight in “How Minds Change”: we don't actually change other people's minds through arguments or facts. Instead, we need to create space for others to reflect and change their own minds. Joelle recommends this book because it fundamentally shifted her approach to working with teams. The book introduces techniques like Deep Canvassing, which focuses on asking people to tell their story and share what's happening to them, rather than trying to convince them with logic alone. This approach aligns perfectly with Joelle's belief in allowing space for people to reflect while trusting that they have good answers within themselves. Self-reflection Question: How might your current approach to influencing change shift if you focused more on creating space for reflection rather than presenting arguments and facts? [The Scrum Master Toolbox Podcast Recommends]

Joelle Tegwen: Why Your Scrum Master Job Needs a Reset with Every Leadership Change 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. Joelle shares her experience as a coach and Scrum Master at a small startup where multiple companies had merged over several years. When a new VP with a conservative approach replaced her original sponsor who favored significant change, Joelle failed to adapt her tactics and align with the new leadership's direction.  She emphasizes the critical importance of listening to feedback from leaders and avoiding the anti-pattern of only listening to peers and direct managers instead of higher-level leadership. Joelle explains that whenever you get a new leader, your job essentially starts over again, requiring you to discover their goals and style through interviews about their priorities. She stresses that change happens through people, not just actions, and that pushing too hard creates more resistance. In this segment, we refer to the book The First 90 Days by Michael D. Watkins and the Deep Canvassing Technique.  Self-reflection Question: How do you currently assess and adapt to new leadership styles in your organization, and what steps could you take to better align your change management approach with leadership expectations? [The Scrum Master Toolbox Podcast Recommends]

In this episode of the Roofing Technology Think Tank (RT3) podcast, Karen Edwards welcomes Ben Fiedler from Benchmark to explore the intriguing intersection of Agile methodology and the roofing industry. Discover how Agile principles, traditionally used in software development, are being adapted to enhance efficiency and innovation in roofing projects. Ben shares his unique journey from broadcast television engineering to roofing consultancy, and how Agile practices like Scrum are transforming project management. Tune in to learn how contractors can adopt an Agile mindset to stay ahead in a rapidly changing market. Learn more at: https://rt3thinktank.com/

Is your software development process stuck on a conveyor belt? Discover how to break free from outdated manufacturing mindsets and build truly high-performing, agile teams that “Move Fast and Break Silos.”In this episode, experienced CPTO, Klaus Breyer, introduces a revolutionary approach to software development. He explains why treating software engineering like a factory assembly line leads to inefficiency, micromanagement, and disempowered teams. Learn how to slice work effectively—from objectives down to delivery—and align small, empowered teams to solve real customer problems and ship value faster.Key topics discussed:Why software development is a design process instead of a manufacturing processHow Agile and Scrum has become micromanagement toolsWhy ticketing systems can create communication silosHow to slice work into objectives, problems, solutions, and deliveryGiving teams problems to solve, not just solutions to buildThe concept of empowered teams that own their outcomesWhy small, dynamic groups of 2-3 people work bestAligning your teams' work with company goals and business objectives Timestamps:(00:00) Trailer & Intro(02:10) Career Turning Points(05:26) Critical Key Skills as CPTO(07:40) Juggling Between Being Optimistic vs Pessimistic(09:15) Move Fast and Break Silos(13:08) The Difference Between Manufacturing and Software Development(16:51) The Problems with the Status Quo of Software Development Practices(23:50) Key Practice 1: Slicing Work(25:51) Slicing Objectives(28:30) Slicing Problems(33:25) Slicing Solutions(38:03) Slicing Delivery(41:09) Key Practice 2: Aligning Teams(43:21) The Effective Teams Alignment Practices(48:10) Working in Small Teams at a Time(51:07) Alignment with the Value Streams(53:15) Mapping the Sliced Work to the Organization(56:41) The Importance of Reporting Structure in the Large Organization(58:52) 3 Tech Lead Wisdom_____Klaus Breyer's BioKlaus Breyer is an experienced B2B SaaS CPTO who specializes in bridging the gap between technical delivery and agile product strategy, driven by a passion for breaking down silos. His career includes founding and leading the startups Buddybrand (a digital agency) and BuzzBird (a B2B marketplace), as well as building corporate startups and business units for major companies like Voith and edding in the IoT and B2B SaaS sectors.Based in Berlin, he has extensive experience working with diverse and primarily remote teams. In addition to his leadership roles, he sometimes invests in and advises leadership teams on building effective interdisciplinary teams themselves. He is also a speaker, blogger, and book author who champions the philosophy of “Move Fast And Break Silos!”Follow Klaus:LinkedIn – linkedin.com/in/klaus-breyerTwitter – twitter.com/klausbreyerWebsite – v01.ioEmail – kb@v01.ioLike this episode?Show notes & transcript: techleadjournal.dev/episodes/224.Follow @techleadjournal on LinkedIn, Twitter, and Instagram.Buy me a coffee or become a patron.

Tony Squires is joined by Wade Graham, Jason Demetriou and Michael Chammas as we looked back at Queensland's Origin series victory, Kieran Foran joined the show after announcing his retirement, and we looked ahead to the Run Home to the finals. Plus, Sharks star Toby Rudolf discussed the Sharks win over the Dolphins, Tony's Quiz and Believe It Or Not along with plenty more!See omnystudio.com/listener for privacy information.

#162. Unlocking hidden Microsoft partner benefits? Now that's my kind of secret! In this episode, I spill the beans on how Dynamics 365 and Power Platform partners can get their teams Scrum trained and certified — on Microsoft's dime, without touching your training budget, thanks to Microsoft Incentive co-op funds.I walk you through what co-op funds are, how to check your eligibility, and exactly how to claim full reimbursement for my Successful Scrum for Microsoft Business Apps course. The course is tailored specifically for your teams building Microsoft business apps, not just any software project. I share stories from the trenches, like $4 million Dynamics implementations and global customer service transformations, to show the practical impact of genuine Scrum on delivery teams, customer satisfaction, and project profitability.You'll hear testimonials from consulting partners and students who have used these tactics to become Microsoft Partner of the Year winners—and happier, lower-stress teams as well.There's even an Exam Pass Guarantee (so your team can certify with confidence), plus step-by-step instructions on using those mysterious co-op funds before they expire.Curious if it really works? Microsoft themselves give it the green light—and I'll show you how to make it happen. Listen to this episode to discover how to turn unused partner benefits into highly skilled, adaptable delivery pros, and set your practice apart. Ready to build amazing apps, supercharge your team, and let Microsoft foot the bill?Book a call with NeilScrum for Microsoft Business AppsHow to get your training investment reimbursed

Tony Squires is joined by Wade Graham, Jason Demetriou and Michael Chammas as we looked back at Queensland's Origin series victory, Keiran Foran joined the show after announcing his retirement, and we looked ahead to the Run Home to the finals. Plus, Sharks star Toby Rudolf discussed the Sharks win over the Dolphins, Tony's Quiz and Believe It Or Not along with plenty more!See omnystudio.com/listener for privacy information.

Pascal Papathemelis: The Mobile Product Owner—Why Great POs Move Around and Talk to People Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. The Great Product Owner: The Visionary Communicator Pascal describes great Product Owners as excellent communicators who possess the courage to confront stakeholders when necessary. These exceptional POs thrive as decision makers and understand the importance of being mobile - they have "legs and walk around to meet stakeholders" rather than remaining isolated in their offices. Great Product Owners maintain a clear vision and excel at breaking down products into granular items that teams can easily pull from the backlog. They demonstrate superior backlog management skills and understand how to focus on creating systems that collect valuable feedback. Pascal emphasizes that it's critical to help Product Owners develop these capabilities so they can flourish in their role as the primary decision makers for their products. The Bad Product Owner: The Dominating Manager Pascal encountered a challenging Product Owner who exhibited several destructive anti-patterns. This PO dominated meetings by talking most of the time while the team remained silent, creating an environment where team members felt unsafe to contribute. The situation was complicated by the fact that this Product Owner also served as the line manager for the team members, blurring the boundaries between product decisions and personnel management. This dual role created a power dynamic that inhibited healthy team collaboration. The PO went so far as to stop retrospectives, even when Pascal explained how these sessions could benefit the entire team. Pascal identifies a critical anti-pattern: when a Product Owner has no channel of communication or coaching support, and they resist help, it becomes impossible to improve the situation. Self-reflection Question: What steps could you take to help Product Owners in your organization develop better communication skills and create safer environments for team collaboration? [The Scrum Master Toolbox Podcast Recommends]

Pascal Papathemelis: Selecting the Appropriate Agile Values for Organizational Impact 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. Pascal defines success for Scrum Masters through his recent mantra of "effectiveness over efficiency," "outcome over output," and "create value for the customer." Working with a client introducing a new digital platform, he focuses on understanding the value for both the organization and end customers while minimizing confusion in the process. Pascal emphasizes the importance of ensuring work sustainability over time by focusing on Agile values and principles and their deep understanding. He customizes the Agile Manifesto's values and principles for each organization, such as focusing on customer value, collaboration, and constant learning. Pascal strategically highlights the principles and values that address the biggest challenges facing the organization at any given time, making Agile concepts relevant and actionable for the specific context. Featured Retrospective Format for the Week: Sailboat Pascal recommends the sailboat retrospective as his preferred format, though he emphasizes that the choice depends on context and team focus. He values this metaphor-based retrospective because it helps teams discuss critical aspects of their work through different perspectives. The sailboat format allows teams to explore what propels them forward (wind), what holds them back (anchors), what they need to watch out for (rocks), and their destination (island). Pascal also uses timeline retrospectives and stresses the importance of varying retrospective formats to prevent teams from falling into routine patterns that might limit their ability to bring fresh insights to their work. He believes that good data and effective visualization are essential components of any successful retrospective format. Self-reflection Question: How effectively are you customizing Agile principles to address your organization's specific challenges and context? [The Scrum Master Toolbox Podcast Recommends]

Is Agile Disappearing? - Not Again...For the last two years, we've seen a fairly drastic change in the agile landscape. Large companies have laid off hundreds of thousands of agile and tech jobs (287k in 2023 and 152k in 2024). The job market for new jobs is also very different. You can't just search for Scrum Master or Agile Coach like you used to.Maybe it's because big firms have started treating agile like “a skill not a role”, as mentioned by the Business Agility Institute and scrum alliance in their “Skills in the New World of Work” research paper. You might need to be multiple things, a manager who knows agile or a technologist who knows Scrum. It's a trend that is sad but true, IMO.How to connect with AgileDad:- [website] https://www.agiledad.com/- [instagram] https://www.instagram.com/agile_coach/- [facebook] https://www.facebook.com/RealAgileDad/- [Linkedin] https://www.linkedin.com/in/leehenson/

Pascal Papathemelis: From Waterfall to Agile—A Multi-Level Change Strategy 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. Pascal describes a successful agile transformation where he collaborated with a fellow coach in the IT department of a large organization with a waterfall history and heavy documentation-driven processes. The two coaches worked together effectively, sharing information and scouting for opportunities to take action. They began with an assessment and discussions across IT, business, and management levels to understand the current state. Using the Cynefin framework to understand complexity, they conducted a two-day workshop to introduce Agile vocabulary, covering concepts like Push/Pull and process waste.  The coaches operated at multiple levels simultaneously - working strategically with leadership who typically pushed excessive work to the organization, while also helping teams visualize their processes and clarify priorities. At the team level, they acted as Scrum Masters to demonstrate the role while mentoring the actual Scrum Master through one-on-one sessions. They also supported the Product Owner in understanding their role and used story maps to help visualize and organize work effectively. Self-reflection Question: How might collaborating with another coach or change agent amplify your effectiveness in leading organizational transformation? [The Scrum Master Toolbox Podcast Recommends]

Pascal Papathemelis: The Hidden Cost of Removing Scrum Masters from High-Performing Teams 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. Pascal shares a cautionary experience with mature Scrum teams that appeared to function flawlessly. These teams demonstrated excellent Scrum practices with minimal impediments, leading management to conclude that Scrum Masters were unnecessary. When management removed all Scrum Masters from the department, the previously high-performing teams began to struggle significantly.  Team members had to absorb the responsibilities previously handled by their Scrum Masters, causing them to lose focus on their core value-creating work. Different teams adopted various approaches to fill the Scrum Master void, but none proved effective. Pascal reflects that the Scrum Masters could have made their value more visible by supporting Product Owners more actively and becoming more involved in team tasks. This experience taught him the importance of demonstrating the ongoing value that Scrum Masters provide, even when teams appear to be self-sufficient. Featured Book of the Week: Learning Out Loud—Community Learning and Networking Pascal draws his greatest inspiration not from a single book, but from active participation in the Agile community. He finds tremendous value in discussions within local communities, networking events, and sparring sessions with colleagues. Pascal particularly benefits from Agile Coaching circles in Helsinki, which provide practical knowledge and insights. He also gains inspiration from Agile conferences, but credits Agile Coaching Camps as having the biggest impact - these 2.5-day open space format events are intense and packed with valuable insights. Pascal recommends that Scrum Masters actively engage with their local Agile communities and attend coaching camps to accelerate their professional development and gain diverse perspectives. Self-reflection Question: How visible is the value you provide as a Scrum Master, and what steps could you take to make your contributions more apparent to your organization? [The Scrum Master Toolbox Podcast Recommends]

Pascal Papathemelis: From Mechanics to Human Factors—How Scrum Masters Grow 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. Pascal shares his evolution as a Scrum Master, moving from focusing purely on the mechanics of Scrum to understanding the critical importance of human factors. Early in his career, Pascal worked with teams that struggled to achieve sprint goals, with stories floating from one sprint to another. Through retrospectives and continuous improvement, he learned essential tips like not taking too much into sprints and making stories smaller.  However, Pascal's biggest transformation came when he shifted focus to human elements - involving everyone in the team, improving collaboration during refinement, and developing people's skills and attitudes. He emphasizes that every person is an individual with the intention to be their best, and a good Scrum Master must sense when something is wrong and create safe environments for open conversations. Pascal highlights the importance of corridor conversations and coffee machine breakthroughs, especially before COVID, and stresses the need to invest effort in how teams start, using models like Tuckman's team growth model and Diana Larsen's Team Liftoff approach. In this segment, we also refer to the episode with Arne Roock, about the importance of team design and setup in the success of teams. Self-reflection Question: How might shifting your focus from Scrum mechanics to human factors transform the way you support your team's growth and collaboration? [The Scrum Master Toolbox Podcast Recommends]

In this episode, Kate and Ryan unpack the real Scrum Master's toolkit—and it's not just post-it notes and Sharpies.  From mindset and agile knowledge to powerful facilitation techniques, they explore what it truly takes to lead effective teams.  You'll hear about the tools they carry (both physical and mental), how they keep retrospectives engaging, and why mindset matters more than mechanics.  Whether you're a new Scrum Master or a seasoned agile coach, this episode offers practical insights－and a few Elmo's－to help you serve your team with confidence, clarity, and a little creativity!

Every summer, the quiet charm of Saranac Lake and Lake Placid erupts in a joyful scrum of community pride, fierce competition, and unmatched camaraderie. That's right—it's time for the legendary Can-Am Rugby Tournament.In this episode of ADK Talks, hosts Jane and Steve delve into the heart of this beloved Adirondack tradition with Cameron Moody, the tournament director and lifelong rugby player, who joins us from his deployment with the National Guard in the Horn of Africa.Whether you're a seasoned rugby fan or just rugby curious, this episode is packed with stories, surprises, and reasons to attend the 51st Can-Am Rugby Tournament, happening July 25–27, 2025.In this episode, you'll learn:The grassroots origin story of Can-Am Rugby in the 1970s and how it grew into the largest amateur rugby tournament in the U.S.Why rugby is a “gentleman's game”—and what that really means on and off the pitchHow Can-Am supports local youth sports, scholarships, and community eventsWhat to expect at the Tournament: free matches, family activities, and the return of wheelchair rugbyWhy women's rugby is booming, and what new divisions are debuting this yearCameron's big dreams for expanding the tournament and building youth rugby across New York StatePlus, don't miss the Scrum & Done Lightning Round, where Cameron names his favorite post-match drink (hint: it's cold and comes in a can), the best rugby team names, and the advice he'd pass on to the next generation of players.If you're planning a summer trip to the Adirondacks, this is the tournament to build your weekend around—whether you're a player, spectator, or just looking for something unforgettable and totally free to do in the Tri-Lakes.Links & Resources:

We’re nearing Origin with Tony Squires, Nathan Hindmarsh, Wade Graham, and cardigan-less Queenslander Brent Read. The Scrum chat with Jarome Luai in NSW Origin Camp, talk about the big decider on Wednesday, and who will be their Wally Lewis Medal Winners. Dissecting the Broncos win over the Bulldogs, Ask Hindy is all about food, and what’s going on with the ARL and the Kangaroos coaching appointment?Tony’s Quiz, Ready’s Mail and Believe It Or Not? rounds out a great show.See omnystudio.com/listener for privacy information.

Bernard Agrest: Millions of Users, Multiple Stakeholders—The Art of Product Owner Navigation 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 Stakeholder Navigator Bernard describes an exceptional Product Owner who managed a product impacting millions of people while navigating constantly evolving requirements from multiple stakeholders. This Product Owner excelled at understanding each stakeholder's unique needs and communicating effectively with all of them. What made this person truly great was their ability to come to the development team with a clear understanding of both the business case and user needs, having done the hard work of stakeholder management upfront. This Product Owner understood that their role was to be the bridge between complex stakeholder requirements and clear team direction. The Bad Product Owner: The Collaborative Hoarder Bernard identifies a dangerous anti-pattern: the Product Owner who adds everything to the backlog under the guise of being "collaborative." While this behavior appears inclusive and team-friendly on the surface, it actually demonstrates that the Product Owner isn't following through on delivering real value. These Product Owners become almost exclusively focused on authority rather than outcomes, making them particularly difficult to coach since they resist guidance. Bernard recommends using Cost of Delay as both a prioritization technique and a tool to help Product Owners understand why certain items shouldn't be added to the backlog at all. Self-reflection Question: Is your Product Owner truly collaborating by providing clear direction, or are they avoiding difficult prioritization decisions by adding everything to the backlog? In this segment we refer to the Coach Your Product Owner e-course that we created for everyone who needs to help their Product Owners succeed! [The Scrum Master Toolbox Podcast Recommends]

Number 19 speaks as a Jet for the very first time.

Bernard Agrest: Creating Conditions for Healthy Conflict and Continuous Improvement in Agile Teams 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. Bernard believes successful Scrum Masters focus on creating conditions where tension and healthy conflict can emerge naturally, rather than maintaining artificial harmony. Too many organizations remain stuck in fear-based cultures where people avoid raising important issues. For Bernard, success means ensuring people regularly surface problems and engage meaningfully with each other—it's not enough to simply monitor green dashboards. He emphasizes that real leadership involves focusing on creating conditions for teams to discuss what truly matters, moving beyond surface-level metrics to foster genuine dialogue and continuous improvement. Self-reflection Question: Are the people on your teams regularly raising issues, or are you relying too heavily on dashboard metrics to gauge team health? Featured Retrospective Format for the Week: 4L's The 4L's retrospective format is simple yet powerful, examining what the team Liked, Learned, Lacked, and Longed for. Bernard particularly values the "Longed for" category because it asks people to connect the dots between how they felt and how they performed. In one memorable session, using 4L's helped his team understand what they were missing in their regular sync work, leading them to change how they conducted meetings to better support upcoming deliveries. This retrospective format had long-term organizational impact, helping teams realize gaps in their collaborative processes and make meaningful improvements to their working relationships. [The Scrum Master Toolbox Podcast Recommends]

Wade Graham, James Graham, Maroon are in as the NRLW season kicks off tonight! We unpack the Tigers in house beef, look at who will be the Kangaroos next coach & debate if the Panthers can still win the comp!See omnystudio.com/listener for privacy information.

Bernard Agrest: One-on-One Insights—Building Change Strategy Through Individual Conversations Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. When faced with a tool that needed complete rebuilding rather than more "duct-tape" features, Bernard knew that disruption was inevitable—but where to start? Through extensive one-on-one conversations with employees and stakeholders, he discovered that teams didn't understand their work was cyclical, and more importantly, that the onboarding team was central to the entire process. By starting the transformation with this pivotal team and focusing on training and user adoption, the new tool provided immediate organizational impact with data-driven decision making. Bernard's approach demonstrates that successful change management starts with understanding the true workflow and identifying the critical connection points that can drive the most significant positive impact. Self-reflection Question: In your current change initiatives, have you identified which team or process serves as the central hub that could accelerate transformation across the entire organization? [The Scrum Master Toolbox Podcast Recommends]

Most construction pros have heard of Lean — but far fewer truly understand it, and even fewer are putting it into practice. In this episode of The EBFC Show, we shine a light on why Lean is often misunderstood, overlooked, or completely invisible on job sites today. Join host Felipe Engineer-Manriquez and special guest Alan Boykiw as they unpack the roots of Lean, its relevance to construction, and what it really takes to make continuous improvement more than just a buzzword.   Why is Lean often misunderstood — or completely unseen — in today's construction industry?   In this eye-opening episode of The EBFC Show, host Felipe Engineer-Manriquez sits down with Alan Boykiw, Senior Experience Architect at Nialli, to explore why Lean Construction isn't as visible or widespread as it should be. Together, they unpack the history of Lean, bust some common myths, and share hard truths about where the industry stands on Lean adoption.   From the origins of the term “Lean” to the pressing need for change in how we plan, schedule, and collaborate — this episode gets real about what's holding teams back, and more importantly, how to move forward.  

07-02 Full Show- Kevyn Adams Press Scrum and Buffalo Bills news full 7528 Wed, 02 Jul 2025 22:30:00 +0000 Xd2EIWosKglJ6RkdH3COL0hdpXpFI5E3 sports Schopp and Bulldog sports 07-02 Full Show- Kevyn Adams Press Scrum and Buffalo Bills news Sports talk should be entertaining and informative, which is why Schopp and the Bulldog control the WGR 550 airwaves every weekday from 3-7 p.m. Chris "The Bulldog" Parker bleeds Buffalo and is as passionate about the Sabres and Bills as any listener to our radio station. Mike Schopp keeps the callers in line while dishing out his unique perspective and opinions, and creating on-air fantasy drafts of anything from favorite candy and meats, to actors, presidents and bands. Bills reporter Sal Capaccio appears daily on the show covering every move the team makes like nobody else!The top-notch weekly guests include:Mondays (DURING FOOTBALL SEASON) at 4 p.m. - Buffalo Bill, Eric WoodSabres general manager Kevyn Adams (DURING HOCKEY SEASON) - 5:30 p.m.Thursdays at 5:30 p.m. - Sports betting media specialist Evan Abrams from The Action NetworkTogether for 10 years, Schopp and the Bulldog are the No. 1 most listened to talk show in all of Western New York.On Demand Audio is presented by Northwest Bank. For What's Next. © 2025 Audacy, Inc. Sports False https://player.amperwavepodc

Hour One- Reacting to Kevyn Adams Scrum with the press full 2944 Wed, 02 Jul 2025 22:10:00 +0000 Ax9FHSnxWwwAZtCKeYroPtxQ9CK4rYtF sports Schopp and Bulldog sports Hour One- Reacting to Kevyn Adams Scrum with the press Sports talk should be entertaining and informative, which is why Schopp and the Bulldog control the WGR 550 airwaves every weekday from 3-7 p.m. Chris "The Bulldog" Parker bleeds Buffalo and is as passionate about the Sabres and Bills as any listener to our radio station. Mike Schopp keeps the callers in line while dishing out his unique perspective and opinions, and creating on-air fantasy drafts of anything from favorite candy and meats, to actors, presidents and bands. Bills reporter Sal Capaccio appears daily on the show covering every move the team makes like nobody else!The top-notch weekly guests include:Mondays (DURING FOOTBALL SEASON) at 4 p.m. - Buffalo Bill, Eric WoodSabres general manager Kevyn Adams (DURING HOCKEY SEASON) - 5:30 p.m.Thursdays at 5:30 p.m. - Sports betting media specialist Evan Abrams from The Action NetworkTogether for 10 years, Schopp and the Bulldog are the No. 1 most listened to talk show in all of Western New York.On Demand Audio is presented by Northwest Bank. For What's Next. © 2025 Audacy, Inc. Sports False https://player.amperwavepodcasting.com

We’re taking our own advice and hitting pause to recharge this July. While we’re off the mic, revisit past episodes packed with timeless insights and conversations you may have missed. Overview This week, we're pressing pause to model the sustainable pace we teach. Brian shares a quick update about our summer break, what’s ahead in August, and how you can make the most of the podcast archive while we’re away. Whether you’re poolside or simply stepping back from the daily sprint, we hope you’ll join us in creating a little breathing room and we can’t wait to be back with a fresh season soon. References and resources mentioned in the show: Subscribe & Listen to Previous Episodes of 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. Auto-generated Transcript: Brian Milner (00:00) Hey there Agile Mentors, this is Brian Milner and I'm just gonna take a moment of your time today because we're actually going to be practicing what we teach here at Agile Mentors and we're gonna be working at a sustainable pace. So for us that means we're gonna take a few weeks off. It's summer and I know many of you are going to be taking time off with your families and we're gonna be doing the same thing. So we won't be around for the next month. We're gonna be out of here for July, but already have some plans for when we come back in August. So stay tuned when we come back in August, we've got a new season of shows that will begin there in August that I think you'll really enjoy. While we're off, might I suggest you go back through our archive. Look at some of the previous podcast episodes we've done. There's quite a few now. And maybe you've missed some of the episodes from the past. Go back and find some of our great guests that we've had over the years when we've been doing this. I think you'll find some really great guests and some really interesting topics. So fill your diet of Agile Mentors with that while we're at taking a little bit of a break here at Agile Mentors. I hope you're having a great summer and we look forward to seeing all of you back here in August. Take care.

Bernard Agrest: Avoiding Hard Conversations—When High-Performing Agile Teams Self-Destruct 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. Bernard describes how a high-performing, fun-loving team began to unravel when a new member joined who wasn't delivering on their commitments. Instead of addressing the performance issue directly, team members started picking up the slack, avoiding the difficult conversation that needed to happen. As morale dropped and people checked out, Bernard realized the team was paralyzed by fear of confrontation and assumptions that raising the issue would be ignored. This experience taught him that individual performance problems quickly become whole-team problems when left unaddressed, and that strong relationships require the courage to have honest, supportive conversations. Self-reflection Question: What difficult conversation are you avoiding on your team, and what assumptions might be preventing you from addressing it? Featured Book of the Week: The 6 Types of Working Genius by Patrick Lencioni Bernard recommends The 6 Types of Working Genius by Patrick Lencioni because it helps leaders understand that everyone has specific "genius" areas in different phases of work. When people work outside their natural genius zones, they feel unfulfilled and frustrated. This framework has been invaluable for Bernard in understanding team dynamics—why some teams click naturally while others struggle. By recognizing each person's working genius, leaders can better position team members for success and create more effective, satisfied teams. [The Scrum Master Toolbox Podcast Recommends]

What's on your mind? Let CX Passport know...How do Agile principles, customer experience, and camper life all fit together? Lauren Feehrer connects those dots brilliantly in this *Greatest Hits* episode of CX Passport.Lauren is the founder of LoyaltyCraft, where she helps mid-market companies grow through smarter customer experience strategies. From her roots as a process analyst at Accenture to helping clients implement Agile CX frameworks today, Lauren brings a balance of structure and empathy to the CX world.This episode originally aired as E182 and stood out not just for Lauren's insights but for her authenticity — whether talking about CX in hospice care or running her family like a Scrum team (yes, really).Lauren blends CX discipline with curiosity and care — and it's no surprise this episode made the Greatest Hits list.CHAPTERS  00:00  Starting at Accenture...and blue screens  04:58  Listening deeply to customers  07:49  Agile CX explained  11:46  The business of grief and caregiving  15:34  Family road trips during the pandemic  18:41  First Class Lounge  23:41  Discipline, emotion, and process  26:54  Her grandfather's CX inspiration  29:11  Using Agile with your familyEpisode resources:  Connect with Lauren Feehrer on LinkedIn: https://www.linkedin.com/in/laurenfeehrer  Learn more about LoyaltyCraft: https://www.loyaltycraft.comIf you like CX Passport, I have 3 quick requests:✅ Subscribe to the CX Passport YouTube channel https://youtube.com/@cxpassport  ✅ Join other “CX travelers” with the weekly CX Passport newsletter https://cxpassport.kit.com/signup  ✅ Bring

Back in the early 2000s, software teams started embracing a new way of working that turned conventional project management on its head. Instead of trying to define everything up front and push massive projects toward a distant deadline, they asked a different question: what's the most valuable work we can deliver in the next two weeks? That question gave rise to Scrum—a system built on fixed time, cross-functional teams, and fast feedback. And while it started in software, the lessons apply just as powerfully to legal work. Tune in to hear how you can apply these principles to your practice—especially around prioritization, workflow design, and respecting your finite capacity—so that you're working smarter, not just harder.Get full show notes, transcript, and more information here: https://www.agileattorney.com/76

What does it truly take to deliver a great game consistently in an industry known for its challenges and complexities? Join us for a conversation with Steve Sargent, Head of Production at Blind Squirrel Games, a veteran with over 35 years of experience in the game industry, including work on iconic titles like BioShock: The Collection and Mass Effect Legendary Edition. Steve dives deep into the art and science of game production, sharing the things to do, and also what to avoid, from his extensive career. You'll learn: The core role of production Why reporting can actually add value - if it's done right! The five key behaviors that drive trust and success in game development Why pursuing "efficiency at all costs" can actually be detrimental to creating a great game The importance of understanding "the why" behind your processes, rather than just following rituals How to foster an environment where team members feel empowered to take ownership and solve problems Why planning is essential for alignment, even when the details change Whether you're an aspiring producer, an indie developer, or a seasoned leader, Steve's hard-earned wisdom offers actionable takeaways to help you build better games and stronger teams.  Learn more about Steven Sargent: LinkedIn: https://www.linkedin.com/in/steve-sargent-00ba59/ Blind Squirrel Entertainment: https://blindsquirrelentertainment.com/ MobyGames Profile: https://www.mobygames.com/person/26147/steven-b-sargent/ Resources: Agile Game Development with Scrum by Clinton Keith:  https://www.amazon.com/Agile-Game-Development-Scrum-Clint/dp/0321617415 Mike Cohn's Books on Amazon: https://www.amazon.com/stores/Mike-Cohn/author/B001JRX4F4 Connect with us:  LinkedIn: https://www.linkedin.com/company/building-better-games/  Twitter: https://x.com/BBG_Podcast  Instagram: https://www.instagram.com/buildingbettergames/#  Website: https://www.buildingbettergames.gg  YouTube: https://www.youtube.com/channel/UCZpMT-dUwQR-R4Mb4uub6Sw   #GameProduction #GameDev #AgileDevelopment #TeamLeadership #BlindSquirrelGames  

Bernard Agrest: When Stepping Back Becomes Stepping Away—A Leadership Failure 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. Bernard shares a powerful story about a critical research project where his instinct to step back and empower his team ultimately led to project failure and personal burnout. When Bernard realized his team wasn't ready for the work ahead, he made the mistake of taking everything on himself rather than building proper feedback loops and ensuring true understanding. Working overtime and feeling guilty about not supporting his team properly, Bernard learned that empowerment isn't about stepping back—it's about creating space to work together. His key insight reveals that it's through doing the work that we discover what work actually needs to be done, and that having people say they "get" the plan doesn't mean they truly understand it. Self-reflection Question: How do you distinguish between genuine team empowerment and abandonment when stepping back from direct involvement in projects? [The Scrum Master Toolbox Podcast Recommends]

Lilia Pulova: Business Case Ownership—The Product Owner's Core Duty 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: Always Present and Inspirational Lilia describes an exceptional Product Owner whose defining characteristic was consistent presence with the team. This presence went beyond just showing up - it was inspirational and made team members genuinely care about their delivery and the product they were building. The Product Owner served as the vital connection between the team and the organization's wider mission, helping everyone understand how their work contributed to the bigger picture. This constant engagement and visibility created a motivated team that took pride in their product development efforts. The Bad Product Owner: Unprepared and Responsibility-Shifting Lilia encountered a Product Owner who exemplified poor practices by consistently arriving at backlog refinement meetings without any preparation, expecting developers to provide business context instead. This approach was fundamentally wrong because developers aren't equipped to discuss business expectations or product direction - that's the Product Owner's responsibility. This individual habitually said "yes" to all tickets without consideration, shifted decision-making responsibility to the team, and relied on architects to manage the product and determine sprint priorities. Product Owners must own the business case rather than delegate it, and keep the business rationale constantly visible to the team. Self-reflection Question: How do you ensure your Product Owner maintains proper preparation and ownership of business decisions rather than shifting these responsibilities to the development team? [The Scrum Master Toolbox Podcast Recommends]

Lilia Pulova: Building Self-Sufficient Teams Through Emotional Intelligence 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. Lilia defines success for Scrum Masters by asking a simple but powerful question: "Do people feel supported?" Her approach focuses on training teams to take on her responsibilities and make their own decisions. Rather than dictating solutions, she presents options and allows teams to choose their path. Over time, teams learn these options and develop independence in decision-making.  She maintains awareness by monitoring delivery metrics, watching for tickets that take too long, and staying attentive during daily stand-ups. With her primarily remote team keeping cameras open, Lilia reads emotions and body language to identify potential issues early, preventing small conflicts from escalating into major problems. Self-reflection Question: How well do you read the emotional state of your team members, and what early warning signs might you be overlooking? Featured Retrospective Format for the Week: 1-on-1 Retrospective Lilia advocates for the 1-on-1 retrospective as her most effective format, explaining that people open up more in private conversations than in group settings. While group retrospectives can work well with smooth conversation flow, she finds that structured formats don't always suit every team - sometimes the "lack of format" creates better outcomes. The key to successful 1-on-1 retrospectives is building strong relationships and establishing trust, which she considers the most important foundation for effective retrospectives. [The Scrum Master Toolbox Podcast Recommends]

Lilia Pulova: Leading an Agile Transformation—The Power of Patience and Small Wins 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. Lilia shares her experience leading a genuine Agile transformation in an organization just beginning their journey. Faced with widespread skepticism and resistance, she encountered impatient stakeholders demanding immediate results during the challenging first 2-3 months. The breakthrough came after two months when stakeholders finally witnessed tangible improvements in the application and faster release cycles. Patience emerged as the critical skill that carried the transformation through its most difficult phase. Lilia emphasizes the importance of conducting numerous one-on-one conversations and consistently praising teams while celebrating small wins to maintain motivation throughout the change process. Self-reflection Question: How do you maintain team morale and stakeholder confidence during the uncertain early phases of organizational change? [The Scrum Master Toolbox Podcast Recommends]