Podcasts about Agile

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]

Las metodologías ágiles no son solo para programadores. En este episodio destruimos mitos sobre Agile y mostramos cómo aplicarlo en cualquier área profesional. Aprenderás el modelo A.G.I.L. (Adaptabilidad, Generación rápida de valor, Iteración basada en feedback, Liderazgo distribuido), cuándo SÍ y cuándo NO ser ágil con la Matriz de Decisión, métricas reales vs. vanidad, y casos de empresas no-tech como ING Bank, The Guardian y Haier. Déjanos ⭐️⭐️⭐️⭐️⭐️ para ayudarnos a llegar a más personas con este contenido transformador: re:INVÉNTATE en Spotify y Apple Podcasts.¿Tienes preguntas o quieres compartir tus progresos en el desarrollo de este PowerSkill? Etiquétame en Instagram (@librosparaemprendedores) en una stories o deja tus comentarios y opiniones sobre este episodio.✨ ¡Hoy comienza tu re:Invención!

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]

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/

Shouldn't Agile rest on a spirit of rebellion? A better way? If so, we shouldn't be craving templates - instructions on how to do things in a set way. If we all follow the pattern, there's no room for original solutions. And there's no real value in sameness...

An international speaker, Microsoft MVP, ASPInsider, MCSD, PSM II, PSD, and PST, and a passionate member of the developer community, Phil has been working with .NET since the first betas, developing software for over 40 years, and has been heavily involved in the Agile community since 2005 as well as a Professional Scrum Trainer. Phil has taken over the best-selling Pro C# books (Apress Publishing), including Pro C# 10, is the President of the Cincinnati .NET Users Group (Cinnug.org), and the Cincinnati Software Architect Group, founded and runs the CincyDeliver conference (Cincydeliver.org), and volunteers for the National Ski Patrol. During the day, Phil works as the CTO & Chief Architect for Pintas & Mullins. Phil always enjoys learning new tech and is always striving to improve his craft.   Topics of Discussion: [2:53] Why Phil still loves writing software after 40-plus years.  [5:39] The difference between being a consultant and supporting code long-term. [8:27] Agile roles and user experience. [8:40] Embedding engineers in the business to avoid “telephone game” decisions. [11:30] “Move fast” vs. move efficiently — real-world cautionary tales. [13:40] Using Figma for business rule diagramming before writing a single line of code. [14:52] Releasing 4 x per week and getting rapid feedback. [16:49] NASCAR, motocross, and the connection of slow builds of how software teams avoid friction. [18:41] Measuring team efficiency, and how Phil eliminated emergency production fixes by mandating quality. [22:00] Feature flags, PBI coverage, and the team's shared ownership of the code. [26:09] AI in legal tech: where it works, where it doesn't. [34:56] The architectural shift created by LLMs, vector databases, and agents. [39:42] AI is not the goal — it's just a tool for solving the right problems. [44:03] How Phil uses GitHub Copilot's agent mode to streamline development. [46:03] Final thoughts: “It's not about the tech. It's about making someone's life better.”   Mentioned in this Episode: Clear Measure Way Architect Forum Software Engineer Forum Programming with Palermo — New Video Podcast! Email us at programming@palermo.net. “Clear Measure, Inc.” (Sponsor) “Philip Japikse: Professional C# in .NET - Episode 230” “Philip Japikse: Migrating from .NET Framework to .NET 8 - Episode 296”   Want to Learn More? Visit AzureDevOps.Show for show notes and additional episodes.

Ever had to lead a project without being the official leader? Lots of people have. Today, unofficial project managers are like secret heroes. But how do they do it without the fancy title or training? Let's find out together. In today's episode of the Insight Out podcast, I am joined by Kory Kogon, Vice President and Content Development and Bestselling Author at FranklinCovey.  During our conversation, we talk about her book ⁠Project Management for the Unofficial Project Manager⁠ and insights on project management and leadership. Kogon emphasizes the importance of leading people, setting clear expectations, and effectively closing projects. She advocates for learning from retrospectives and choosing the right project management tools that align with project principles. Kogon also discusses the integration of waterfall and agile methodologies, stressing the significance of aligning projects with organizational values. She concludes by highlighting the mindset of value, people, and process as the key to success for project managers. In this episode, you will learn the following: Understanding the productivity paradox in the knowledge worker era The significance of leading with clarity and purpose, regardless of position The benefits of conducting retrospectives for continuous learning and improvement Key to success for unofficial project managers Advice on choosing project management tools that align with key principles The value plus people plus process mindset In This Episode: [03:14] - Introducing the productivity paradox [04:14] - Changes in society and productivity [06:25] - Tips for making high-value decisions  [06:36] - The five choices for project management [08:18] - Update on of the book [10:11] - Unofficial project managers and their challenges [11:55] - Pitfalls causing project failures [14:15] - Tips to improve engagement  [19:36] - Discoveries and surprises in research [23:50] - Self-awareness and Leadership [24:54] - Actionable insights from the book [27:33] - Postmortem and debrief [30:59] - Selecting project management tools [35:15] - Blending Waterfall and Agile [38:16] - Defining value in project management [41:46] - Leadership Mindset in Project Management Notable Quotes [04:37] "Now we're in the knowledge worker world where we're paid to think, innovate, create, and execute." -Kogon   [04:51] “It's no longer about time management. It's more about how do I make the best decisions” -Kogon [14:34] “The overarching mindset for a leader needs to be that it's the value of the project plus people plus process equals project success.”-Kogon [29:16] "Recognizing people and letting them know that they did a good job lights up their brain more than if you gave them cash."- Kogon  [[42:19] “If you want to change behavior or little, work on your behaviors, but if you want quantum leaps in behavior, work on your mindset.” -Kogon Resources and Links Kory Kogon ⁠https://www.linkedin.com/in/kory-kogon/⁠ ⁠https://www.franklincovey.com/⁠ Billy Samoa  https://www.instagram.com/billysamoa/ https://www.youtube.com/@BillySamoa https://www.linkedin.com/in/billysamoa/ Mentioned Book ⁠Project Management for the Unofficial Project Manager⁠ This is an encore episode and was originally published on March 2, 2024 Learn more about your ad choices. Visit megaphone.fm/adchoices

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]

Episode Summary:In this episode of WV Uncommonplace Interviews and Sessions, host JR Sparrow sits down with Helene Gidley, the mastermind behind The Art of Agile Living and founder of A2Agile Inc. With 40 years of experience in project management and coaching, Helene shares how she transformed IT industry methodologies into a powerful system for personal productivity and success.Whether you're an entrepreneur, professional, or just looking for better ways to manage your daily tasks, Helene's insights on Agile techniques will change the way you approach organization and efficiency.What You'll Learn in This Episode:✅ How Agile project management techniques can help organize your life✅ The Art of Agile Living and how it simplifies personal and professional tasks✅ Practical strategies for tackling overwhelming to-do lists✅ The connection between focus, order, and motivation✅ How to implement Agile principles into your daily routineConnect with Helene Gidley:

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

The rise of structure software fueled globalization by streamlining operations across borders. Now, Cloud and AI are accelerating this momentum, enabling faster innovation, smarter decision-making, and scalable growth. By modernizing ERP with intelligent technologies, organizations can stay agile, competitive, and ready for the next wave of global transformation.This week, Dave, Esmee and Rob talk to Timo Elliott, Innovation Evangelist at SAP, to explore how SAP is driving globalization—and how organizations can accelerate innovation through the power of Cloud and AI. TLDR00:55 Introduction of Timo Elliott02:40 Rob shares his confusion about misleading online ads08:06 In-depth conversation with Timo46:32 Rethinking control in enterprise systems1:00:00 Brunch at a Paris café or joining an event?GuestTimo Elliott: https://www.linkedin.com/in/timoelliott/HostsDave Chapman: https://www.linkedin.com/in/chapmandr/Esmee van de Giessen: https://www.linkedin.com/in/esmeevandegiessen/Rob Kernahan: https://www.linkedin.com/in/rob-kernahan/ProductionMarcel van der Burg: https://www.linkedin.com/in/marcel-vd-burg/Dave Chapman: https://www.linkedin.com/in/chapmandr/SoundBen Corbett: https://www.linkedin.com/in/ben-corbett-3b6a11135/Louis Corbett:  https://www.linkedin.com/in/louis-corbett-087250264/'Cloud Realities' is an original podcast from Capgemini

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]

Last episode, we talked about Instant Pot's failure via financial engineering that most product teams may never see coming.In this episode, we explore why financial literacy should be a core competency for product teams, not something left to the "adults in the room." We break down why reading basic financial statements, understanding customer lifetime value, and making data-driven decisions that actually consider the cost of building features are essential and how you can start moving toward a future where you have more transparency into financial matters.Key topics covered:• Why whoever controls the budget is the real product manager• How financial complexity hides exploitation and manipulation • The curriculum gap in product management education• Practical metrics every product team should track• How to bring finance people into your product discussionsThis isn't about becoming accountants - it's about understanding the financial impact of your product decisions and building something that lasts.#ProductManagement #FinancialLiteracy #AgileLeadershipREFERENCES----------------AA219 - How Private Equity Killed Instant Pot (And Why Your Product Could Be Next),AA217 - Extreme Ownership: Military Leadership Lessons for Professionals,AA201 - Mastering Stakeholder Communication & Management,KIRO 7 News Seattle: https://www.kiro7.com/news/trending/instant-pot-pyrex-parent-company-instant-brands-files-bankruptcy/VLWFB4OF75FHLERB7B5KCMXUFI/,LINKSYouTube: https://youtu.be/Xbub7ZKTMKoSpotify: https://open.spotify.com/show/362QvYORmtZRKAeTAE57v3Apple: https://podcasts.apple.com/us/podcast/agile-podcast/id1568557596Website: http://arguingagile.com= = = = = = = = = = = =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 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. 

In this conversation, Dave Prior and Reece Schmidt discuss the upcoming Agile 2025 conference, focusing on its structure, keynotes, and unique features like the Hackathon for Good. They emphasize the importance of preparation for attendees, including tips for maximizing the conference experience, networking, and engaging with speakers. The conversation also addresses resources for introverts and those who may feel overwhelmed, ensuring a supportive environment for all participants. Takeaways • Agile 2025 is a condensed three-day event with a focus on keynotes and hands-on learning. • The Hackathon for Good will allow participants to work on real-world problems for a nonprofit. • Attendees should prepare by reading the program and identifying key speakers and topics of interest. • Networking is crucial; attendees should engage with speakers and other participants. • Book signings will provide opportunities for attendees to connect with authors directly. • Self-care is important; attendees should prioritize sleep, hydration, and breaks. • Introverts can find quiet spaces and should not hesitate to take breaks when needed. • The conference will feature a variety of new voices and perspectives in the Agile community. • Participants should have backup session choices in case their first choice is full. • Visual cues will be provided to help attendees navigate social interactions. Links: Agile 2025: https://agilealliance.org/agile2025/ Interview with Jurgen Appelo on The Agile Network https://theagilenetwork.com/content/8f025d5e-e8d5-454b-97a3-18e47619b397 Contacting Reese: LinkedIn: https://www.linkedin.com/in/reeseschmit/ Agile 2025 https://agilealliance.org/agile2025/ Dave and Stuart's Talk at Agile 2025: Career Power-Ups: Surviving Through Uncertainty and Change https://tinyurl.com/2s4zhzts Dave and Stuart's Book: “No One Is Coming to Save You” https://www.stuartyoung.uk/copy-of-human-skills-1 AI Readiness for Professionals Course https://tinyurl.com/y79kassb Dave's Upcoming Scrum Certification Classes https://www.scrumalliance.org/courses-events/search?tr=14153&cnty=US Chapters 00:18 Introduction to Agile 2025 01:56 Conference Structure and Keynotes 04:13 Hackathon for Good 07:55 Hands-On Learning Opportunities 10:38 Book Signing and Author Engagement 12:54 Preparation Tips for Attendees 17:26 Survival Tips During the Conference 21:48 Resources for Introverts 25:56 Closing Thoughts and Contact Information

In this episode of the Share PLM Podcast, we are joined by Thomas Winden and Kerstin Roulet from T-Systems. Thomas Winden works as Tribe Lead Emerging Business & Innovation at T-Systems. He joined the company in 2012 after eight years in consulting and has since focused on PLM, Agile methodologies, and business development. Since 2022, he has led PLM strategy, partnerships, and portfolio management.Kerstin Roulet is a Change Consultant at T-Systems with a background in PLM and IT. Since joining in 2012, she has specialized in Agile transformation and cultural change, leading initiatives to enhance communication, collaboration, and team dynamics within PLM projects.The conversation explores how T-Systems integrates human-centric methodologies into its PLM projects, emphasizing collaboration, communication, and cultural change as essential elements of success. The company prioritizes helping clients take ownership of their transformation journeys by embedding change management practices into technical implementations. With a clear long-term vision, T-Systems is actively expanding its PLM services beyond traditional industries and regions, positioning itself as a trusted partner in digital product lifecycle transformation. Here are the main themes that emerged:⚉ Organizational Transformation: From Hierarchy to Tribes⚉ “Agile Doing” vs. “Agile Being”⚉ Cultural and Soft‑Skill Enablement⚉ PLM's New Identity at T‑Systems⚉ Insights for PLM Implementers⚉ Customer Ownership in PLM TransformationCONNECT WITH THOMAS AND KERSTIN:⚉ LinkedIn: https://www.linkedin.com/in/kerstin-roulet-376365147/ ⚉ LinkedIn: https://www.linkedin.com/in/thomas-winden/ CONNECT WITH SHARE PLM:⚉ Website: https://shareplm.com/ Join us every month to listen to fascinating interviews, where we cover a wide array of topics, from actionable tips, to personal experiences, to strategies that you can implement into your PLM strategy.If you have an interesting story to share and want to join the conversation, contact us and let's chat. We can't wait to hear from you!

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]

Emily Lint, senior technical Release Train Engineer at ICON Agility Services, is here to remind you not to be critical of yourself when dealing with the many changes that come with an Agile transformation. In fact, she says, “You're doing just fine.” Tune in to find out why. Like what you hear? Connect with Emily on LinkedIn. Learn more about Women in Agile. Explore SAFe courses here.

Watch on YouTube: https://youtu.be/MfImeEij4XY   In this episode of the Agile and Action Podcast, Bill chats with Bhavneet Chahal, Co-founder and CEO of GoSkills, about how AI is reshaping online learning and development. Bhavneet shares how GoSkills took the bite-sized learning approach seriously way back in 2013 and why it still holds strong today. Instead of hour-long snoozefests, they focus on 3 to 5 minute lessons that come with cheat sheets, quizzes, and exercises. Bhav also explains how their platform integrates AI to help trainers build courses, generate lesson plans, and even make course titles pop. But she's quick to add that AI should assist, not replace, human quality and insight. The conversation dives into how AI isn't a threat to structured learning but actually helps enhance it. While ChatGPT and YouTube are great for quick answers, structured platforms like GoSkills offer guided learning that actually sticks. They've rolled out tools like Genie and Ask AI to boost productivity and personalize the learning experience without losing quality. Bhav shares her thoughts on how AI can help not just with content creation but also strategy, marketing, and even spotting hidden opportunities from raw data. Her hot tip for trainers and instructional designers: learn how to use AI to polish and sell your course, not just build it. What You'll Learn Why micro-learning still wins in adult education How AI can help you build and market better courses The difference between using AI for quick answers vs structured learning How GoSkills uses AI to find trends and shape future content Tips for trainers to stay competitive using AI tools in course design and promotion

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]

Corporate Agile has caused true agility to become stagnant and undervalued in large organizations, losing its impact. What's with our loyalty to big companies these days anyway? We should look ahead to applying Agile in fresh settings, where we can discover new value, opportunity, and meaning in our craft.

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/

Agility isn't just for software teams—it's a way of thinking, leading, and living. In this heartfelt and insightful episode, we explore real-world lessons in agility from parenting to project management, from sticky notes to strategic pivots.Kate shares her personal journey transitioning from a project manager to a Scrum Master—and from a planning-every-minute parent to a supportive, servant leader. Along the way, she reveals six (and then some!) timeless lessons:Letting go of controlRetrospecting anything with anyoneKanban boards for the winEmbracing “done is better than perfect”Making failure safe and productiveListening without fixingWe also dive into bonus wisdom on the power of adaptability, embracing messiness, and remembering that true agility isn't about tools—it's about mindset. Whether you're leading a team or organizing a family holiday, these lessons apply.Tune in for an episode full of reflection, laughter, and takeaways that blend leadership, agility, and real life.

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]

Introduction to Emotional Agility Forget the outdated myth that stoicism equals strength. The strongest men don't bottle their emotions—they master them. In the boardroom, the weight room, or the storm of daily life, true mental toughness comes from the ability to feel deeply without being dominated by those feelings. That skill has a name: Emotional […]

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/

In this episode we discuss: Who knows what is going to happen with Toronado Palmetto in some deep water What is really going on The post Episode 594 – We Went Agile first appeared on The Craft Beercast.

GreenOps is a cultural transformation that empowers developers to turn emissions data into meaningful action, bridging the communication gap with ESG teams and exposing the critical truth that cloud cost and carbon cost are not the same, which fundamentally reshapes how we approach sustainable IT.This week, Dave, Esmee and Rob talk to James Hall, Head of GreenOps at Green Pixie, to unpack the real state of GreenOps today—and why we've only just scratched the surface.  TLDR 01:57 Rob is confused about AGI 06:11 Cloud conversation with James Hall 22:10 Esmee as media archeologist, found GreenOps is 50 years old 30:46 Having some drinks in the summer Guest James Hall: https://www.linkedin.com/in/james-f-hall/ Hosts Dave Chapman: https://www.linkedin.com/in/chapmandr/ Esmee van de Giessen: https://www.linkedin.com/in/esmeevandegiessen/ Rob Kernahan: https://www.linkedin.com/in/rob-kernahan/Production Marcel van der Burg: https://www.linkedin.com/in/marcel-vd-burg/ Dave Chapman: https://www.linkedin.com/in/chapmandr/ Sound Ben Corbett: https://www.linkedin.com/in/ben-corbett-3b6a11135/ Louis Corbett:  https://www.linkedin.com/in/louis-corbett-087250264/'Cloud Realities' is an original podcast from Capgemini

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]

In this episode of the Agilists: Aspire and Achieve podcast, host Renae Craven and guest Karyn Smith explore Karyn's journey from a high school graduate to her current role as a COO. Karyn shares her reflection on how far she has come and the things she has learnt about herself along the way. About the Featured Guest Karyn is a seasoned executive with over three decades of international and cross industry experience. Karyn has a proven ability to inspire, empower and motivate teams towards high performance and delivery of sustainable results, making her a dynamic leader.  Karyn is deeply committed to making a difference and ensuring meaningful engagement and outcomes for all. Follow Karyn on LinkedIn (https://www.linkedin.com/in/karyn-smith-14b4353/)   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 Renae Craven has been coaching individuals, teams and organizations for over 14 years and has spent a lot of time investing in and formalizing her professional coaching skills in recent years. Renae's passion is leading and coaching organizations and as a Certified Team Coach with Scrum Alliance, she helps teams to find their rhythm and pace that balances learning with delivery. Renae established her own company NaeCrave Pty Ltd (www.naecrave.com.au) in 2020 and keeps herself busy with coaching and training delivery. Renae is also a certified BASI Pilates instructor and runs her own pilates studio in Brisbane, Australia. She has a YouTube channel called ‘Pilates for the Office Worker' which features short 5 minute guided sessions that anyone can incorporate into their day, especially those of us who have been sitting down for extended periods. Subscribe to her channel Crave Pilates. Renae has been organizing the Women in Agile group in Brisbane since 2018. You can follow Renae on LinkedIn (https://www.linkedin.com/in/renaecraven/).

"MCP, c'est un peu le USB-C de l'IA." Le D.E.V. de la semaine est Zineb Bendhiba, principale software engineer chez Red Hat. Zineb vient nous parler du protocole MCP (Modèle, Contexte, Protocole) et son rôle dans le développement de l'intelligence artificielle. Zineb explique comment le MCP simplifie les interactions client-serveur grâce au découplage des systèmes et à l'utilisation du format JSON RPC. Elle explore également la différence entre un "assistant" et un "agent", la sécurité des données et la gestion des autorisations dans les serveurs MCP. La discussion va aux applications pratiques, y compris son expérience dans le développement de gateways et l'importance de tests rigoureux. La communauté est également reconnue comme vitale pour l'évolution du protocole.Chapitrages00:00:57 : Introduction au MCP00:03:05 : Définition du MCP00:06:36 : Le Protocole et ses Clients00:09:11 : Distinction entre Agents et Assistants00:13:59 : Exemples concrets d'utilisation00:22:55 : MCP comme Middleware00:24:23 : L'avenir du MCP00:38:22 : Limites et questions éthiques00:44:20 : Conseils pour débuter avec MCP00:51:13 : Améliorations souhaitées pour MCP00:54:32 : Questions finales et recommandations Liens évoqués pendant l'émission La spec officielle MCP https://modelcontextprotocol.io/Le blog de Guillaume Laforge (récemment sur AI et surtout Java AI) 🎙️ Soutenez le podcast If This Then Dev ! 🎙️ Chaque contribution aide à maintenir et améliorer nos épisodes. Cliquez ici pour nous soutenir sur Tipeee 🙏Archives | Site | Boutique | TikTok | Discord | Twitter | LinkedIn | Instagram | Youtube | Twitch | Job Board |Distribué par Audiomeans. Visitez audiomeans.fr/politique-de-confidentialite pour plus d'informations.

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]

This week we're joined by Alicja Spaulding, Founder of Status: Alpha, who helps marketing leaders operationalize AI, digital transformation, and creative agility.Alicja started her career in the music industry—cutting her teeth in the early days of digital disruption—and has since built brands in architecture, food, and now AI-enabled strategy. She's worked with startups and mid-market manufacturers alike, helping them become more nimble, less siloed, and more prepared for what's next.In this episode, we talk about:How to build marketing teams that are ready for rapid changeThe difference between automation and AI strategyWhy AI isn't your strategy—it's your foundationHow to think about large language models (and when not to)The power of working yourself out of a jobConnect with Alicja: https://www.linkedin.com/in/alicjaspaulding/Get the It'sRapid Creative Automation Playbook: https://itsrapid.ai/creative-workflow-automation-playbook/Take It'sRapid's Creative Workflow Automation with AI survey: https://www.proprofs.com/survey/t/?title=ffgvdEmail us at sales@itsrapid.io to find out how to get your free AI Image AuditTheme music: "Happy" by Mixaud - https://mixaund.bandcamp.comProducer: Jake Musiker

In this episode of the Women in Product podcast, Meghna Shah of PWC joins Cassie Campbell to discuss the intersection of consulting and coaching in product management. Shah explains the importance of teaching clients how to build product management disciplines, using the analogy of teaching them to fish rather than just delivering the fish. They explore the mindset shifts required to succeed with agile and product management approaches, emphasizing the importance of coaching in making these shifts. Shah shares insights on the 'two in a box' model, where a coach and a product manager work together to ensure skill transfer. The discussion also includes strategies for influencing cross-functional teams, storytelling in product management, and the importance of continuous learning and adapting to technology changes.00:00 Introduction and Guest Welcome00:37 Meghna Shah's Background and Role at PWC01:23 The Importance of Coaching in Consulting02:09 Mindset Shifts and Agile Practices03:37 Influence and Stakeholder Engagement04:09 Technology's Evolving Role in Business05:24 Coaching for Continuous Improvement13:42 Success Story: Financial Services Organization17:45 Roles in Agile and Product Management21:54 Understanding the Value Chain26:33 Characteristics of Effective Product Teams30:57 Conclusion and Final Thoughts✨Where to find Meghna:On LinkedIn

From Prototype to Product: Navigating Hardware Manufacturing with Violet SuIn this episode of the Agile Embedded Podcast, Luca speaks with Violet Su, Business Development Manager at Seed Studio, about the challenges and opportunities in hardware manufacturing. The conversation explores the realities of hardware development, from initial prototyping to mass production. Violet emphasizes the importance of getting products into users' hands quickly to gather feedback, even if they're not perfect. She highlights common pitfalls for newcomers to hardware manufacturing, including underestimating costs, certification requirements, and supply chain complexities. The discussion also covers the growing influence of AI in hardware development and how emerging connectivity technologies are shaping the future of embedded systems.Key Topics[01:30] Introduction to Seed Studio and its focus on open source hardware and AI[03:15] Changes in hardware development landscape over the past decade[06:45] Common challenges for hardware startups and innovators[12:30] The importance of early feedback and iterative development[16:20] Success story: OpenUC2 microscopy project collaboration[23:40] Indicators of a successful hardware project[28:15] Insights from Embedded World 2024 conference[33:10] Future trends in hardware beyond AINotable Quotes"You might be able to design one and it really works when you have a sample or 10 samples, but when we talk about products, there are a lot of nuances that we really need to think about." — Violet Su"You can fail faster so that you can succeed faster. We couldn't make a perfect project and we shouldn't expect to make a perfect product." — Violet Su"When they give you the complaints early on, you will be very thankful, and they know you listened as well." — Violet Su"The projects that might take off either really solve the pain of some people, or get people excited because it's something new." — Violet Su"There's nothing better than getting customer complaints early on, so you don't get them later on." — Luca IngianniResources MentionedSeed Studio - Company providing open source hardware and AI solutionsOpenUC2 - Open source modular microscopy project mentioned as a success storyConnect With UsReach out to Violet Su at violet@seed.cc to discuss potential hardware collaborations with Seed StudioVisit seedstudio.com to explore their range of AI hardware and customization servicesConnect with Violet Su on LinkedIn for updates on hardware manufacturing trends You can find Jeff at https://jeffgable.com.You can find Luca at https://luca.engineer.Want to join the agile Embedded Slack? Click here

About Joacim "Jay" Mattisson Joacim "Jay" Mattisson is a solution finder, who brings fresh perspectives to the discussion. As a founder and investor, Jay shake things up - be it software solutions, SaaS, websites, workflows or data gathering. Jay has a sensitive ear to what the users actually need. He builds close-knit teams that translate customer requirements into solid services.  Experienced Scrum master and team leader using Agile methodology to bring projects in on time and on budget. Jay is President Swedish American Chamber of Commerce Arizona - promotes trade, investment and business opportunities between Sweden and Arizona. Board member SACC USA - the umbrella organization for 20 SACC chambers in the US. Adviser to the German American Chamber of Commerce Arizona. Board member and Treasurer Global Ties Arizona - grassroots diplomacy organization and International Visitors Leadership Program organization. Global Ties Arizona builds and strengthens relationships between community members, businesses and nations through international exchange and educational programs, one handshake at a time.   Episode Notes 03:34 Lesson 1: Dare to be Vulnerable 08:35 Lesson 2: Work on bigger problems earlier 12:28 Lesson 3: Focus on what is right 15:11 Lesson 4: Normalize Excellence 17:57 Lesson 5:   Be a Stradivarius among ordinary Violins. 21:48 Affiliate Break 22:33 Lesson 6: If you get upset over small stuff, you're not bigger than that 30:02 Lesson 7: Be aware of your shadow 32:07 Lesson 8: You can still lose 33:37 Lesson 9: Dual use 37:22   Lesson 10: It's never too late to have a fantastic childhood  

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]

This week's podcast is about how Alibaba.com restructured its business and re-ignited growth in 2017-2018.You can listen to this podcast here, which has the slides and graphics mentioned. Also available at iTunes and Google Podcasts.Here is the link to the TechMoat Consulting.Here is the link to our Tech Tours.My summary of the Alibaba Management Playbook:Diagnose the problem:What is the chief complaint?Stagnant growth? Low NPS?What is the differential diagnosis?1-Re-clarify and re-focus customer value. This includes:Customer segmentation. Who are you targeting? What are you after (revenue)? Traffic? Data?What do they most care about? Map out the process.Is what customers want changing? Tech change? PC to mobile changed what maps could do.What is the competitor offering and how you are going to take their customers?2-Launch 2-3 key strategic initiatives to increase refocused customer value.3-Improve production. Fix the big pain points of customers, staff, suppliers, etc. Requires data-driven decision making and iteration.4-Change the org structure, talent and culture. Improve production relations.Increased communication and coordination.5-Have early wins (small phased victories). Important to test the strategy and get data. And to re-enforce culture and org changes.6-Agile tactics and speed are key.You win chess with 2x the moves.Tactical brilliance and guerrilla execution.7-Build a powerful biz model or operating flywheel. Maybe access multi-growth curves.Measure OutcomesFinancial and operationalStrategic——-- I write, speak and consult about how to win (and not lose) in digital strategy and transformation.I am the founder of TechMoat Consulting, a boutique consulting firm that helps retailers, brands, and technology companies exploit digital change to grow faster, innovate better and build digital moats. Get in touch here.My book series Moats and Marathons is one-of-a-kind framework for building and measuring competitive advantages in digital businesses.This content (articles, podcasts, website info) is not investment, legal or tax advice. The information and opinions from me and any guests may be incorrect. The numbers and information may be wrong. The views expressed may no longer be relevant or accurate. This is not investment advice. Investing is risky. Do your own research.Support the show

Robert C. Martin, more often known as Uncle Bob, has been programming since 1970 and has served as a mentor to generations of software engineers. He's one of the original authors of the Agile Manifesto and played a foundational role in forming the Agile Alliance, where he served as its first chairman. But beyond titles and organizations, Bob's lasting impact comes through his writing, his lectures, and his philosophy of software craftsmanship. He has spoken at conferences around the world — QCon, Agile 20XX, IT Days, and countless other industry gatherings — always advocating for clarity, discipline, and ethical responsibility in code. And if you've ever read Clean Code, The Clean Coder, or Clean Architecture, you know that he doesn't just teach how to build systems — he challenges us to become better professionals in the process. His most recent work, Functional Design, continues this legacy, distilling decades of experience into patterns and principles that are just as relevant today as they were when he first put finger to keyboard.   Topics of Discussion: [2:22] Uncle Bob's advice for young programmers entering the field: Be cautious with AI tools, learn fundamental programming skills, and understand that AI won't replace programmers. [4:42] Get to the basics first, and then you can move on: Master core programming skills and fundamentals before relying too heavily on AI or advanced tools. [8:19] The impact of AI on experienced developers. [15:44] Highlighting the role of programmers in managing low-level details that managers and customers don't want to think about. [18:43] Programmers as language learners. [27:19] The state of Agile methodologies. [29:33] The original Agile goal of making small teams work efficiently together, which remains a crucial challenge. [35:37] Discussing the limitations of university computer science programs and the potential of trade school or apprenticeship models. [36:07] What's next for Uncle Bob?   Mentioned in this Episode: Clear Measure Way Architect Forum Software Engineer Forum Programming with Palermo — New Video Podcast! Email us at programming@palermo.net. Clear Measure, Inc. (Sponsor) Clean Agile: Back to Basics  Clean Code: A Handbook of Agile Software Craftsmanship We, Programmers: A Chronicle of Coders from Ada to AI “Uncle Bob Martin: Clean Code and How to Do Software Well - Episode 283” Functional Design: Principles, Patterns, and Practices UncleBob on GitHub The Clean Code Blog Agile Principles, Patterns, Practices Clean Coders   Want to Learn More? Visit AzureDevOps.Show for show notes and additional episodes.

Master the art of risk management and unlock your full potential with this transformative journey into project management!

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]

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]

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]

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]

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]