Podcasts about Agile

Anamaria Ungureanu: Building Self-Awareness in Overly-Technical Product Owners Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. The Great Product Owner: The Master Storyteller Anamaria highlights a Product Owner who excelled at storytelling and vision communication, making every team member feel aligned with project goals. This exceptional PO consistently explained the "why" behind requirements and painted compelling pictures of how the team's current work would create future value. Their storytelling ability kept the team engaged and motivated, demonstrating how great Product Owners apply agile mindset principles to create shared understanding and purpose. The Bad Product Owner: The Monologue Specialist Anamaria describes a technically-skilled Product Owner who transitioned from a tech lead role but fell into the anti-pattern of excessive monologuing during sprint planning sessions. This PO, despite good intentions, overwhelmed the team with lengthy technical details, causing developers to withdraw from interactions and leaving them confused about project purposes. Through one-on-one coaching focused on building self-awareness and establishing working agreements, Anamaria helped this PO learn to communicate more effectively and engage collaboratively with the team. Self-reflection Question: How do you help Product Owners transition from technical expertise to effective team communication, and what signs indicate when detailed explanations become counterproductive monologues? [The Scrum Master Toolbox Podcast Recommends]

Anamaria Ungureanu: Tracking Scrum Team Behavioral Evolution Over Time 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. Anamaria defines Scrum Master success by focusing on team behavioral trends and performance evolution over time. She monitors how teams increase trust with stakeholders, demonstrate commitment, and apply agile behaviors consistently. Her approach emphasizes seeking regular feedback from stakeholders and conducting honest self-assessments to ensure the Scrum Master role is truly maximizing team performance. Success isn't measured by a single moment but by sustained positive change in team dynamics and delivery capabilities. Featured Retrospective Format for the Week: Stop/Start/Continue with Enhanced Focus Anamaria recommends the classic Stop/Start/Continue format but emphasizes the importance of varying the questions and bringing both quantitative and qualitative data to drive meaningful conversations. She suggests picking specific themes for each retrospective (like testing) and ensuring that discussions lead to concrete, actionable outcomes rather than just surface-level feedback. Self-reflection Question: How do you currently measure your effectiveness as a Scrum Master, and what trends in your teams indicate genuine progress versus superficial compliance? [The Scrum Master Toolbox Podcast Recommends]

Can We Do 100% Scrum And SAFe Simultaneously? - NOPE...This question emerged during a recent Scrum.org Professional Scrum Master Advanced training in Germany

Join us as host Patty G sits down with Keith Primeaux from Agile Brewing. From software development to flavor profiles, Keith is a master of many trades. Hear the story of how he and his team have created one of the most unique breweries in town. Check out Agile here: http://www.agile.beer/Sponsors: PB&J Productions, Coretechs, Falaya, and Lake Men's Health CenterThe Patty-G Show website: ⁠https://thepattygshow.com/⁠#explorebatonrouge #batonrouge #batonrougepodcast #thepattygshow #onlylouisiana #visitbatonrrouge #louisianatravel #podcast #localpodcast #entrepreneur #entrepreneurship #vodcast #batonrougebusiness #batonrougeentrepreneur

Anamaria Ungureanu: Practical Strategies for Organizational Tool Rollouts 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. Anamaria shares her approach to successfully implementing JIRA across an organization by focusing on practical value rather than forcing adoption. Her strategy involved identifying early believers within teams, conducting open discussions to gather feedback, and demonstrating concrete benefits like improved dependency management. Rather than trying to convince resisters, she concentrated on working with willing teams to showcase the tool's value, providing real-time support during implementation, and ensuring team members felt supported throughout the transition. Her method emphasizes being present to answer questions immediately and building momentum through successful early adopters. Self-reflection Question: When leading organizational change, how do you balance addressing resistance with amplifying the voices of those ready to embrace new approaches? [The Scrum Master Toolbox Podcast Recommends]

Bentornati e bentornate su Azure Italia Podcast, il podcast in italiano su Microsoft Azure!Per non perderti nessun nuovo episodio clicca sul tasto FOLLOW del tuo player

Gertrud Noone, Expertin für Change & Communications bei der Lufthansa Group, gibt Einblicke in eines der größten Transformationsprogramme der Konzern­geschichte. Sie zeigt, warum kontinuierliches, bedürfnisorientiertes Zuhören und modulare Sprint-Strukturen den Erfolg eines lang­fristigen Finance-Umbaus erst möglich machen – und wie Führungskräfte zu echten Change-Architekten werden.Highlights:

Anamaria Ungureanu: The Tech Lead Who Nearly Destroyed the Team Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. Anamaria describes a seven-member software team that initially seemed engaged but began self-destructing when a senior tech lead refused to embrace transparency and knowledge sharing principles.  The situation escalated when this key team member's four-day absence completely blocked the team's ability to deliver, creating a dangerous single point of failure. Through careful retrospective facilitation and strategic motivation techniques, including offering the specialist new learning opportunities while gradually transferring their legacy knowledge to teammates, Anamaria helped the team overcome knowledge silos and establish sustainable collaboration patterns. Featured Book of the Week: Never Split the Difference by Chris Voss Anamaria recommends “Never Split the Difference” by Chris Voss, a negotiation masterpiece because it taught her essential communication strategies for establishing trust and navigating tense situations. She emphasizes that negotiation is a critical Scrum Master skill, and Voss's techniques help build rapport with stakeholders while managing difficult conversations that arise during team transformations and organizational change initiatives. Self-reflection Question: What knowledge silos exist in your teams, and how might you motivate specialists to share their expertise while providing them with new growth opportunities? [The Scrum Master Toolbox Podcast Recommends]

Get featured on the show by leaving us a Voice Mail: https://bit.ly/MIPVM 

Bret is joined by Andrew Tunall, the President and Chief Product Officer at Embrace, to discuss his prediction that we'll all start shipping non-QA'd code (buggier code in production) and QA will need to be replaced with better observability.

In this episode of Product Confidential, join host Evie Brockwell and seasoned product management leader Beks Yelland as they explore the evolution of product management roles over the past two decades. From the early days of extensive documentation to the agile revolution and the rise of data-driven decision-making, Beks shares her insights on how the role has transformed. Discover how AI is reshaping the landscape and why embracing these changes is crucial for future success. Tune in for a deep dive into the challenges and opportunities facing today's product managers.Timestamp:Introduction to Product Management Evolution:Beks Yelland shares her experience over 25 years in product management, highlighting significant changes in the role.Transition from Documentation to Agile:Early 2000s: Extensive documentation was the norm.Shift to Agile methodologies introduced more collaboration and communication with development teams.Impact of Data Accessibility:The role evolved with the accessibility of data, allowing for more informed decision-making and customer insights.AI and Future of Product Management:Discussion on the role of AI in product management and the importance of adapting to technological advancements.Addressing Fear and Imposter Syndrome:Beks and Evie discuss the fear of AI replacing jobs and how product managers can overcome imposter syndrome.Job Market and Career Advice:Insights into the current job market challenges and strategies for navigating job searches.Ready to transform your product management career? Tune in to our latest episode with Beks Yelland and discover how to navigate the evolving landscape of product management. Don't miss out on expert insights and actionable advice. Listen now and subscribe for more episodes that keep you ahead of the curve!Follow Beks on LinkedIn: https://www.linkedin.com/in/beckyyelland/

Anamaria Ungureanu: Goal Clarity—The Missing Piece in Agile Team Performance 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. Anamaria shares her experience working with a platform implementation team that appeared engaged but was actually struggling in silence. Despite initial assumptions that everything was fine, the team's quiet demeanor masked their lack of understanding about project goals and deliverables.  Through strategic intervention including goal clarification with the Product Owner, confidence level assessments, and story mapping sessions, Anamaria helped transform a disengaged team into one capable of successful delivery. Her approach emphasized the importance of fostering constructive conflict, asking open questions during sprint planning about demo expectations, and facilitating better PO-team interactions to create transparency and shared understanding. In this episode, we refer to User Story Mapping and the concept of Gemba, or Gemba Walk Self-reflection Question: How might your teams be silently struggling, and what signs should you watch for to identify when apparent engagement actually masks confusion or disengagement? [The Scrum Master Toolbox Podcast Recommends]

You Don't Need Agile... YES You Do Need Agile!When Agile was introduced many years ago, it gave software delivery an option to do things differently. From there, many offshoots have come from Agile that come from Agile that provide even more options for Software Delivery.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/

If you've ever wondered how to make test-driven development more than a coding technique, this episode is for you. Ashok Sivanand and producer Doug Branson answer listener and Reddit-sourced questions about building better product teams—covering everything from mindset shifts to hard truths about performance reviews and strategic alignment. Ashok connects TDD to the principles of Essentialism by Greg McKeown, revealing how teams can define success before they begin and cut through the noise of Slack and OKRs. Hear practical advice for first-time founders struggling to articulate value without a 20-minute demo, plus techniques to scale beyond early adopter customers using real-world interviews and Jobs to Be Done. Later, they explore how to recover from a tough performance review, especially in remote roles, and why communication—not effort—is often the missing ingredient. The episode wraps with a conversation about the dangers of leadership ambiguity when a company isn't sure whether it's selling a service or a product. ASK YOUR QUESTION: convergence.fm/contact Unlock the full potential of your product team with Integral's player coaches, experts in lean, human-centered design. Visit integral.io/convergence for a free Product Success Lab workshop to gain clarity and confidence in tackling any product design or engineering challenge. Episodes referenced in this episode... From Code to Culture: How Shopify Thrives Under Farhan Thawar's Thought Leadership - https://youtu.be/tKEKfjACv3k The POWER of Small Data With High Signal - A Jobs To Be Done masterclass with Andrew Glaser - https://youtu.be/0X1RKZWJgOU Building Customer-Centric Teams: Josh Seiden on OKRs and Agile - https://youtu.be/0dPoDNCQmyc Best of 2024 - Derisking and Evolving on your OKR (Objectives and Key Results) Implementation - https://youtu.be/6HcRd6qUq1A Inside the episode... TDD as a mindset beyond code, inspired by Essentialism How to recover from a tough performance review in a remote org Tips for first-time founders explaining product value without demos Jobs to Be Done and using customer language in sales Diagnosing product vs service strategy confusion in your org Mentioned in this episode... Essentialism by Greg McKeown The Mom Test by Rob Fitzpatrick Jobs to Be Done framework Calendly Integral Unlock the full potential of your product team with Integral's player coaches, experts in lean, human-centered design. Visit integral.io/convergence for a free Product Success Lab workshop to gain clarity and confidence in tackling any product design or engineering challenge. Subscribe to the Convergence podcast wherever you get podcasts including video episodes to get updated on the other crucial conversations that we'll post on YouTube at youtube.com/@convergencefmpodcast Learn something? Give us a 5 star review and like the podcast on YouTube. It's how we grow.   Follow the Pod Linkedin: https://www.linkedin.com/company/convergence-podcast/ X: https://twitter.com/podconvergence Instagram: @podconvergence

In this episode, Josh and Bob dive deep into Colin Powell's 18 Principles of Leadership, but with a Meta-Cast twist. They each bring their top five principles to the table and unpack them—not as motivational posters, but as real-world lessons earned in the trenches. The discussion spans hard truths about pissing people off as a leader, the danger of falling in love with the "expert" class, why perpetual optimism actually moves teams forward, and how fun and humility are underrated superpowers. As always, the conversation is grounded, unfiltered, and full of personal stories from decades of leadership experience. This is a masterclass in modern, practical leadership thinking.

EP145 — The Scrum Guide Expansion Pack¿Hay algo nuevo bajo el sol? ¿Es más de lo mismo? ¿Es en realidad una “expansión” en los confines del universo?. En este episodio de Hormigas Agilistas Podcast discutimos sobre el “Scrum Guide Expansion Pack”, analizando en detalle este documento de aproximadamente 50 páginas que expande el marco de trabajo Scrum.¿Qué te puedes llevar de este episodio?:El propósito y motivación detrás de esta expansión de Scrum (¿necesidad de los equipos? ¿cambios en la decisiones de negocio del “producto Scrum”? ¿necesidad de reimpulsar certificaciones?)Teorías complementarias como sistemas complejos, empirismo y mentalidad de producto.Nuevas definiciones de roles incluyendo Stakeholders y Supporters.El papel de la inteligencia artificial como posible “socio poderoso pero supervisado” (vs “una herramienta”) en equipos Scrum.La separación entre “output” (incremento) y “outcome” (valor)Refinamiento como actividad importante aunque no sea evento oficial.Profesionalismo y excelencia técnica en el desarrollo.Liderazgo en todos los niveles (¿Conocen esto de otro lado?)En el artículo de este episodio (lo que ahora estás leyendo) incluimos la traducción de una de las páginas de esta nueva guía, la cual resume esta nueva mirada.En este episodio participan las hormigas Antonio Gallardo Burgos, Arturo Robles Maloof, Rodrigo Burgos NocetiSi deseas conocer más sobre este episodio y todos los demás, visita el sitio: HormigasAgilistas.CL o en https://medium.com/hormigas-agilistas/¡Gracias por ser parte del Universo de Hormigas Agilistas!IMPORTANTE: Siempre es bueno recordar que en Hormigas Agilistas Podcasts no somos buscadores de la verdad, el objetivo acá no es indicar los que se debe hacer; más bien, abrimos el micrófono para que las personas puedan contar sus experiencias, sus ‘heridas de guerra', y así los oyentes puedan tomar lo que más le haga sentido en sus organizaciones y avanzar en la mejora continua.#Scrum #ExpansionPack #ScrumExpansionPack #TheExpanse #HormigasAgilistas #IA

Anh Vu: The Hidden Cost of Decision-Making Delays in Product Development 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 Strategic Connector Anh describes an exceptional Product Owner who went far beyond managing the backlog to become a strategic connector between customer needs, business requirements, technical constraints, and overall strategy. What made this PO remarkable was their background - they came from a developer background rather than business, yet quickly mastered the Product Owner role through dedicated learning. Despite being new to the PO role, they rapidly developed the ability to connect backlog items directly to customer pain points, often using techniques like user story mapping. This PO brought both clarity and purpose to the team, significantly boosting team motivation by helping developers understand how their work directly impacted customers and business outcomes. The Bad Product Owner: The Proxy Problem The worst Product Owner situation Anh encountered involved a Proxy PO who lacked the authority to make decisions independently. This created significant challenges for both the team and the PO, as every new problem or decision required seeking permission from external stakeholders. This pattern lengthened feedback cycles and demotivated both the PO and the development team, who couldn't move forward efficiently when blocked by decisions. Anh's approach to addressing this involved coaching the PO on engaging with external stakeholders, setting up regular touchpoints (2-3 times per week) to shorten feedback cycles, and focusing on improving the decision-making process to unblock the team. He also emphasized creating a strong network of connections for the PO to navigate the organization effectively and always having a Plan B when certain decisions couldn't be made quickly. Self-reflection Question: Does your Product Owner have true decision-making authority, or are they frequently forced to seek permission from others, and how is this affecting your team's velocity and motivation? [The Scrum Master Toolbox Podcast Recommends]

Anh Vu: Situational Leadership for Scrum Masters - Knowing When to Step Back 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 defines success for Scrum Masters through a simple but powerful test: when you take vacation and return to find the team working exceptionally well without you. This ultimate measure of success focuses on building self-organization and enabling true team autonomy. He emphasizes that Scrum adoption should serve as a metaphor for autonomy and self-organization, with the Scrum Master's stance evolving alongside the team's growth. Drawing from Situational Leadership principles, Anh points out that a team can only become as autonomous as the Scrum Master can envision and facilitate. The key is recognizing when to step back and allow the team to demonstrate their independence while ensuring they have the foundation and confidence to succeed. Featured Retrospective Format for the Week: Free Form Retrospective Anh advocates for the free form retrospective format, which requires only a whiteboard, table, and people gathering for open reflection based on the previous sprint's goals. Rather than following structured formats, he invites team members to share their insights freely, considering the retrospective successful as long as the team leaves with 1-3 actionable insights. This approach works particularly well with teams he knows well, where trust and communication patterns have been established. He builds on this by incorporating silent thinking time to start conversations, a habit developed over time that makes teams more comfortable sharing in the free form format. Anh also recommends conducting retrospectives during in-office days when the team can eat together, investing heavily in these face-to-face interactions to strengthen team bonds. Self-reflection Question: What would happen if you took a week off from your current role - would your team continue to thrive, or would they struggle without your direct involvement? [The Scrum Master Toolbox Podcast Recommends]

Far too many software projects crash not because of poor coding, but because of poor planning. In this episode of Building Better Developers with AI, Rob Broadhead and Michael Meloche explore why requirements matter more than ever. They dive deep into the foundational role that clearly defined, testable, and outcome-focused requirements play in delivering successful software projects. With insights drawn from hands-on experience and AI-generated discussion points, the episode uncovers how misaligned expectations and incomplete planning can derail even the most promising initiatives. Whether you're a developer, product manager, or founder, this conversation reminds us that getting it right starts well before a line of code is written. Why Requirements Matter in Software Development Rob and Michael begin by revisiting a powerful truth: software requirements are the blueprint for everything that follows. Vague requests and incomplete specifications are the root cause of missed deadlines, blown budgets, and frustrated clients. Callout CEO: 70% of software project failures are tied to poor requirements, not bad developers. When everyone understands what's being built—and more importantly, why—teams align better, and projects succeed more often. Requirements Matter More Than Perfect Code Even flawless code can't rescue a project built on the wrong foundation. Rob highlights three common causes of failure: Misunderstood business goals Disconnects between stakeholders and developers Expanding scope from unclear requirements If the team can't agree on what success looks like, no amount of elegant code will save the effort. For more on aligning teams and expectations, check out our episode on Bridging Methodologies. Requirements Matter: Start with the Why Michael emphasizes starting with the business objective. Before diving into specs or wireframes, ask: Why does this solution need to exist? What problem is it solving? Many clients envision modern systems based on outdated workflows. Developers must educate while extracting needs—balancing modernization with functionality that still matters. Requirements Matter When Writing User Stories Rob and Michael advocate for user stories—clear, testable statements of what the system must do. A well-written story includes: A specific actor (e.g., user, admin) A goal (e.g., schedule an appointment) An expected result (e.g., receive confirmation) Michael puts it plainly: If a developer doesn't know when a requirement is “done,” it's not a requirement—it's a guess. Learn more about effective story writing with this Agile user story guide. Requirements Matter in Managing Scope and Budget Requirements aren't just lists—they're guardrails. Michael warns that unchecked feature creep can quietly drain resources and sink projects. A disciplined list of must-haves versus nice-to-haves keeps everything on track. Start with the core. A “calendar app” doesn't need AI-scheduling in version one. Build the basics first, validate them, and then iterate with purpose. Requirements Matter in Prototypes and Demos Rob is a strong advocate for visual requirements. Tools like Figma, PowerPoint, and internal “kitchen sink” demos help bring vague ideas into sharp focus. Stakeholders often struggle to articulate what they want—until they see it. Clickable mockups bridge the communication gap and reduce costly rework. As Rob puts it, “the more real it feels, the better the feedback you'll get.” Balancing Detail: When Requirements Matter and When They Don't Finding the balance between too little and too much detail is key. Rob favors lightweight specs for creative flexibility, while Michael leans on testable, bulletproof requirements. Their advice? Define what the system must do, but avoid locking in how it must be done—especially too early. The goal is clarity of intent, not rigidity in implementation. Make Requirements Matter on Your Team Before wrapping up, Rob and Michael pose a practical challenge to all teams: Can every requirement in your backlog be tested and tied to a business goal? If not, it may be time to revise or remove it. Unclear requirements aren't just annoying—they're expensive. By committing to clarity, your team reduces ambiguity, limits rework, and speeds up delivery. Every stakeholder benefits when expectations are grounded in reality. Final Thoughts From stakeholder interviews to wireframes and test-driven development, requirements matter at every stage of the software development lifecycle. Each assumption should be questioned. Each “nice to have” should be weighed carefully. Every essential feature must be validated. So the next time you're tempted to “just start coding,” take a step back and ask: Do we really understand what we're building—and why? Because when requirements matter, your software delivers. 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 Software Development Requirements: Staying True to Specifications The Importance of Properly Defining Requirements Changing Requirements – Welcome Them For Competitive Advantage Creating Use Cases and Gathering Requirements The Developer Journey Videos – With Bonus Content Building Better Developers With AI Podcast Videos – With Bonus Content

Dave, Esmee, and Rob take a moment to look back on the wild ride that was Season 4—revisiting the themes that sparked the biggest conversations and the guests who left a lasting impression. They also reveal what's on their summer to-do lists and drop a few juicy hints about what's coming in Season 5. Get ready—it's going to be even bigger and bolder.Thank you to all our listeners and guests for joining us in Season 4 - have a great summer and we will see you in September!TLDR:00:40 Season 4 by the numbers – and a fun mix-up with round figures03:20 Reflecting on standout topics and memorable guests03:42 Scaling AI: Hyperscaler narratives, tech momentum, and the adoption gap13:18 Ethics in the AI era – how organizations can and must stay grounded18:12 The human factor: Why “human-in-the-loop” matters more than ever27:29 Sovereignty in tech – geopolitics, shifting narratives, and the rise of Sovereign AI37:16 A deep dive into Telco – highlights from our dedicated mini-series53:48 2025 tech trends with Gene Kim55:33 Listener Q&A: Daniel Delicate on Cynefin vs. IT operating models1:01:44 Andrea Kis on keeping humanity in fast-paced tech1:06:09 Ezhil Suresh on how we prep and record our podcast with top-tier guests1:11:38 John Eaton-Griffin on how guests have shaped our thinking1:17:19 A word from our co-host1:19:57 Looking ahead to Season 5: AAA episodes, new industry mini-series, and Hyperscaler events1:22:09 Meet our new AI companions: Substack and the Cloud Realities chatbot1:23:40 What's next for us this summerHostsDave 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

Building Resiliance with Agile2025 Keynote Speaker Tricia Broderick Dave Prior interviews Tricia Broderick for the Agile 2025 pre-conference, focusing on her keynote on building resilience. Tricia discusses the challenges of the current job market, including high unemployment and overworked employees. She emphasizes the importance of resilience and community support. Tricia also highlights the upcoming AI Readiness for Professionals course, starting August 6, which aims to help professionals stay competitive in an AI-driven world. The conversation touches on the emotional toll of supporting others and the need for empathy and practical support. Tricia looks forward to the Agile 2025 conference, particularly the opportunity to honor past community members. Key Takeaways - Resilience is essential in our current world of work due to a challenging job market and overwhelming workloads. - Empathetic people struggle with the emotional toll of trying to support numerous friends and colleagues who are out of work or struggling. - Community and in-person connections, like at the Agile conference, provide a vital source of restoration and support. - Building personal resilience can be achieved by focusing on what you can control, such as limiting news consumption and performing small acts of kindness. - Tricia will use her keynote to honor four mentors who are no longer with us but had a significant generational impact on her career. To register for Agile 2025 https://agilealliance.org/agile2025/pricing/ Tricia's Links Details on Tricia's Keynote at Agile 2025 https://tinyurl.com/nuwyk629 Lead Without Blame by Tricia Broderick and Diana Larsen https://tinyurl.com/bddcxhhd Tricia's Website https://igniteii.com/ Tricia on LinkedIn https://www.linkedin.com/in/tricia-broderick Links from the Intro The Agile Network - Live from Agile2025 Lineup https://tinyurl.com/bdf4n92m Dave and Stuart's Talk at Agile 2025: Career Power-Ups: Surviving Through Uncertainty and Change tinyurl.com/2s4zhzts Dave and Stuart's Book: “No One Is Coming to Save You” www.stuartyoung.uk/copy-of-human-skills-1 AI Readiness for Professionals Course tinyurl.com/y79kassb Dave's Upcoming Scrum Certification Classes www.scrumalliance.org/courses-events…=14153&cnty=US

Join Melissa Perri as she sits down with Nan Yu, Head of Product at Linear, to explore how Linear is reshaping project management tools for software development. This episode delves into creating seamless user experiences, the evolving role of AI in product management, and the importance of aligning product strategy with company goals.In this engaging conversation, Nan shares insights on how Linear is designed to enhance software development, the strategies for balancing feature requests with strategic development, and the role of AI in reducing administrative burdens for product managers. If you're looking to understand how to align product strategy with real-world customer needs while leveraging cutting-edge technology, this episode is a must-listen.Don't miss out on this insightful discussion! Tune in to learn how to elevate your product management skills and strategies.You'll hear us talk about:08:00 - Restoring the Joy in Software DevelopmentNan Yu explains how Linear aims to bring back the fun in software development by minimizing friction and enhancing user experience, allowing developers to focus on creating.21:00 - Rethinking Estimation and CapacityDiscussing the challenges of scope and estimation in Agile environments, Nan provides insights on how Linear encourages milestone-based development rather than fixed scopes.40:00 - AI's Role in Streamlining WorkflowsNan talks about the impact of AI on product management, highlighting how AI can take over routine tasks, allowing PMs to focus on strategic and customer-focused activities.Episode resources:Nan on X: https://x.com/thenanyuLinear: https://linear.app/Check our new course: https://productinstitute.com/p/mastering-product-strategy-overviewTimestamps:00:00 Coming Up02:38 Dear Melissa06:57 Getting into Linear14:54 Making Linear engaging for developers and PMs22:58 Capacity, estimation, and internal collaboration29:58 AI's role in streamlining PM workflows36:07 Linking strategy to execution and future trends40:45 Advice to younger self

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]

In this episode of the Agilists: Aspire and Achieve podcast, host Renae Craven and guest Nidhya Palaniappan explore Nidhya's journey from South Asia to Canada, including how she found her agile role in her new location. About the Featured Guest Nidhya Palaniappan is a seasoned professional with over 15 years of experience in the IT industry, specializing in Agile practices. With a strong background in software engineering, Nidhya has dedicated over 9 years in various agile roles across geographies. Currently as an RTE at TD Bank Canada, Nidhya is at the forefront of driving Agile transformations and delivering successful products. Follow Nidhya on LinkedIn (https://www.linkedin.com/in/nidhyapalaniappan/) Reference(s) The Culture Map by Erin Meyer 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/).

What can Whatsapp's origin story teach us about adding business value - even when it doesn't seem “fun”? Reflecting on two weeks' backpacking, Jeffrey introduces the concept of Type 1 and Type 2 fun and Squirrel ponders how you can apply the two methods of fun to different types of work in Agile teams. SHOW LINKS: - Types of Fun: https://www.rei.com/blog/climb/fun-scale - WhatsApp baked into "dumb" phones: https://www.wired.com/story/nokia-asha-500-502-and-503-hands-on/?utm_source=chatgpt.com -------------------------------------------------- You'll find free videos and practice material, plus our book Agile Conversations, at agileconversations.com And we'd love to hear any thoughts, ideas, or feedback you have about the show: email us at info@agileconversations.com -------------------------------------------------- About Your Hosts Douglas Squirrel and Jeffrey Fredrick joined forces at TIM Group in 2013, where they studied and practised the art of management through difficult conversations. Over a decade later, they remain united in their passion for growing profitable organisations through better communication. Squirrel is an advisor, author, keynote speaker, coach, and consultant, and he's helped over 300 companies of all sizes make huge, profitable improvements in their culture, skills, and processes. You can find out more about his work here: douglassquirrel.com/index.html Jeffrey is Vice President of Engineering at ION Analytics, Organiser at CITCON, the Continuous Integration and Testing Conference, and is an accomplished author and speaker. You can connect with him here: www.linkedin.com/in/jfredrick/

"How do I learn ServiceNow" is an ever more complicated question with how rapidly AI is changing the ecosystem.CJ & The Duke make the case to still learn platform fundamentals alongside AI.They also give tips on how AI might help accelerate your learning.MENTIONED IN THIS EPISODE:The Duke's questions to ChatGPTABOUT USCory and Robert are vendor agnostic freelance ServiceNow architects.Cory is the founder of TekVoyant.Robert is just some guy.Sponsor Us!

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]

If you're a change agent, such as a SAFe Practice Consultant (SPC), your job is to bring about change—even if the organization doesn't want to change. Eduardo Alvim, SAFe Fellow and principal business agility consultant at Gladwell Academy shares his advice for leading change in challenging situations. Like what you hear? Connect with Eduardo on LinkedIn. Explore SAFe courses here.

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

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. 

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.

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]

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]