Podcasts about Agile

Shawn Dsouza: From AI Anxiety to AI Advantage: A Scrum Master's Experimental Approach 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. Shawn faces the massive AI transformation currently reshaping the tech industry, acknowledging both its benefits and the fear it creates among professionals questioning their relevance. In his organization, he witnesses AI delivering wonders for some teams while others struggle and lose projects. Rather than viewing AI as an overwhelming wave, Shawn advocates for experimentation. He shares practical examples, like helping a Product Owner streamline story creation from Excel to JIRA using AI tools, and leveraging MIRO AI for team collaboration. His approach focuses on identifying friction points where AI experiments could add value while keeping conversations centered on possibilities rather than fears. Self-reflection Question: Instead of fearing technological changes like AI, how can you create small experiments to explore new possibilities and reduce friction in your current work processes? [The Scrum Master Toolbox Podcast Recommends]

Shawn Dsouza: The Database Migration Disaster— Why Software Development Teams Need Psychological Safety 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. Shawn worked with a skilled team migrating a database from local to cloud-based systems, supported by a strong Product Owner. Despite surface-level success in ceremonies, he noticed the team avoided discussing difficult topics. After three months of seemingly smooth progress, they delivered to pre-production only to discover 140 critical issues. The root cause? Unspoken disagreements and tensions that festered beneath polite ceremony facades. The situation deteriorated to the point where a senior engineer quit, teaching Shawn that pausing to address underlying issues doesn't cost time—it builds sustainability. In this segment, we refer to the episodes with Mahesh Jade, a previous guest on the Scrum Master Toolbox podcast. Featured Book of the Week: The Advice Trap by Michael Bungay Stanier Shawn discovered this transformative book when he realized he was talking too much in team meetings despite wanting to add value. The Advice Trap revealed how his instinct to give advice, though well-intentioned, was actually self-defeating. The book taught him to stay curious longer and ask better questions rather than rushing to provide solutions. As Shawn puts it, "The minute you think you have the answer you stop listening"—a lesson that fundamentally changed his coaching approach and helped him become more effective with his teams. Self-reflection Question: When working with teams, do you find yourself jumping to advice-giving mode, or do you stay curious long enough to truly understand the underlying challenges? [The Scrum Master Toolbox Podcast Recommends]

The Agile Family Tree: Theme, Epic, Feature and User Story Explained“Let's group this into a theme, break it down into epics, then into features and finally user stories.”Sure. Cool. Great.Just one question: what does any of that actually mean?If you've ever nodded along in a backlog grooming session while secretly wondering whether an epic is bigger than a feature or the other way around — you're in good company.It's time we cut through the jargon and talk real Agile clarity.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 of Building Better Developers with AI, hosts Rob Broadhead and Michael Meloche revisit an earlier conversation—this time through the lens of AI—to explore how constructive communication in software development creates healthier teams and better code. By analyzing their original “Advocating vs. Arguing” discussion, they uncover new ways to transform conflict into collaboration. “The goal is never to win. The goal is to find the best solution.” – Rob Broadhead What Constructive Communication Really Means Rob draws a clear line between two mindsets: Constructive communication invites evidence, empathy, and openness. Defensive arguing focuses on winning, often shutting down valuable ideas. This subtle difference determines whether a team works together to solve problems or gets stuck in endless debates. Why Constructive Communication Improves Software Development Software projects depend on diverse skills and experiences. When team members communicate constructively: Blind spots shrink. Different perspectives uncover hidden issues. Technical debt decreases. Shared understanding prevents costly rework. Client trust grows. Positive dialogue strengthens long-term relationships. Rob highlights how even an outsider's insight—like a .NET developer's idea on a Python project—can spark innovative solutions. Practical Steps to Encourage Constructive Communication Michael offers proven techniques to keep discussions positive and productive: Ask clarifying questions. Instead of “That won't work,” try “How do you see that working in this context?” Restate what you heard. Confirm understanding before you respond. Stay curious. Open-ended questions invite deeper exploration. “No is a conversation killer. Replace it with ‘Let's consider that.'” – Michael Meloche Spotting When Communication Turns Unproductive Arguments often start subtly. Watch for these warning signs: Absolutes such as “always” or “never.” Interrupting or talking over teammates. Ego-driven choices that ignore user needs or project goals. Rob recommends slowing the pace when tempers rise—pause the meeting, schedule a follow-up, or ask everyone to write down their thoughts before reconvening. Agile Practices Support Constructive Communication Rob and Michael agree that Agile's built-in rituals—backlog refinement, iterative feedback, and sprint reviews—naturally encourage constructive communication in software development. If a team frequently argues, it may be skipping these essential steps. Michael also suggests a weekly “water-cooler” session where team members share new ideas or lessons learned. These informal gatherings nurture creativity and trust. Leadership Sets the Tone Managers and leads can reinforce constructive habits by: Checking in with teammates who seem defensive or frustrated. Offering mentoring or personal support when tension surfaces. Encouraging team traditions—from inside jokes to shared hobbies—that build rapport. Rob observes that the best teams always share a unique bond, whether it's dad jokes or a favorite game, which helps them weather stressful moments. Reader Challenge: Practice Constructive Communication This Week Your Mission: Over the next seven days, pick one team interaction—a stand-up, code review, or planning meeting—and intentionally practice constructive communication in software development. Steps to Try: Listen First. Before offering your idea, restate someone else's point to confirm understanding. Replace “No” with Curiosity. When you disagree, ask an open question like “How do you see that working with our current sprint goals?” Log the Outcome. After the meeting, jot down what changed: Did the discussion stay more positive? Did new solutions surface? Share your results with your team—or even comment on the blog post—to inspire others. Challenge yourself: Can you turn at least one potential argument into a moment of advocacy this week? Key Takeaway: Build a Culture of Constructive Communication This episode underscores that constructive communication in software development is more than a soft skill—it's a project-saver. By listening first, asking better questions, and validating every voice, teams can replace conflict with collaboration and move projects forward with confidence. “Choosing one approach together is better than arguing endlessly about the perfect one.” – Rob Broadhead Whether you're leading a sprint, conducting a code review, or gathering requirements, focusing on constructive communication ensures that every idea is heard—and the best solutions rise to the top. 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 Honest Communication Is Critical For Consultants When To Vent (never) as part of Consulting Communication Use Written Communication To Improve Your Standing And Career Communication Noise vs. Content The Developer Journey Videos – With Bonus Content Building Better Developers With AI Podcast Videos – With Bonus Content

This week, Liz and Rachel discuss the interview with Marnie Hamp and the importance of staying relevant post-launch. In their conversation, they focus on the need for training, marketing, and sales to all have ears in the field and strong collaboration among departments so that the needs of the reps and the customers can be met. In addition, they discuss the need to cross-train clinical reps and sales reps while maintaining clear roles and responsibilities.In 2025, we're embarking on a MedDevice Training Journey: From clinical trials to standard of care. Join us all year long as we explore training at each stage of the product life cycle.Need help developing your clinical trial training strategies? Contact us at training@cumbyconsulting.com.Related Resources:Marnie Hamp InterviewSubscribe to our newsletter to hear more about the journey from clinical trials to standard of care! Click here to subscribe! Connect with us on LinkedIn:   ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Cumby Consulting⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Rachel Medeiros⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Liz Cumby⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠About Cumby Consulting:   Cumby Consulting's team of professionals deliver innovative MedTech training services for physicians, sales representatives, teaching faculty, key opinion leaders and clinical development teams. Whether you need a complete training system developed to deliver revenue sooner or a discrete training program for a specific meeting, Cumby Consulting will deliver highly strategic, efficient programs with uncompromising standards of quality.

In this episode of Agile&Me, Ryan Buckley joins Richard Leaver to get real about the pressures and opportunities for outpatient physical therapy clinics in 2025 and 2026.There's real reason to be optimistic about the coming months and years as practices adopt new technology and look forward to rebounding demand for patients.To learn more about us, visit our website at https://www.allianceptp.com/

Shawn Dsouza: When Scrum Masters Forget to Listen - A Team Trust Crisis in Agile Implementation 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. Shawn shares a powerful lesson about the importance of listening before implementing. Working with a young, talented team drowning in firefighting, he rolled out Scrum in "full" without taking time to understand the team's context. Going through the motions of Scrum ceremonies without genuine team ownership led to dropping energy levels and lost trust. The turning point came when Shawn realized the team had lost faith in his approach, prompting him to rebuild the process collaboratively with team ownership at its core. This story highlights how good intentions can backfire when we prioritize frameworks over people. Self-reflection Question: Before implementing any new process or framework, how do you ensure you truly understand your team's current challenges and context rather than jumping straight to solutions? [The Scrum Master Toolbox Podcast Recommends]

Is Your Team Heading For a Win? It's officially the end of summer here in the U.S. Part of me is sad. Cooler temps mean it's time for me to hang up my wakeboard and store my boat for the season.But part of me welcomes the move to falling leaves, long sleeves, and Major League Baseball playoffs. I'm a big Dodgers fan, and I'm hoping they make it to the post-season again this year.But even if my team doesn't go, I'll still watch the playoffs and World Series–both because I'm a fan and also to see if I can predict the winning team. And while I'm no Nostradamus, I do have a bit of a superpower. After just one or two innings, I can often tell who is going to win the game.Why? Because it's usually clear that one team is trying just a little bit harder. They're not pitching any better or getting more hits–they're just more engaged.They're running down every foul ball, even when it's already crossed into the stands. They're moving toward every hit, only backing off when a teammate yells, “Mine.” From the superstars to the backup right fielder, everyone on the field is looking for ways to contribute, even when it's outside their role.It's a thrill to watch teams like this: Teams who have put their individual egos aside to win the game. I've seen the same thing happen with successful agile teams, too.Agile teams thrive when team members let go of their egos and do what needs to be done. Agile teams struggle when people stay too rigidly in their most comfortable role–a programmer who refuses to do anything but code or an architect who won't come down from the ivory tower to dirty his or her hands with actual code.The Best Agile Teams Operate without Ego“Agile teams thrive when team members let go of their egos and do what needs to be done.”I'm not saying that everyone needs to be a generalist–that would be like having your pitcher also play first base! What I am saying is if that first baseman has to field the ball, I expect the pitcher to hustle over and cover first to make the out. And if the testers are behind or someone has run into a roadblock, I expect to see anyone who is able help out.On high-performing teams, each person plays their part as best as they can, and looks for opportunities to back up their teammates when they need help.On these teams, it seems as if everyone starts each day thinking: “How can I best help the team win today?”When team members have a winning attitude, I'm willing to bet they're on the move from good to great.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 Part 2 of their series on Stephen Covey's 7 Habits of Highly Effective People, Josh Anderson and Bob Galen dive into “Put First Things First” and “Think Win-Win.” Learn how modern leaders can prioritize with courage, create clarity, and build true win-win relationships. Stay Connected and Informed with Our NewslettersJosh Anderson's "Leadership Lighthouse"Dive deeper into the world of Agile leadership and management with Josh Anderson's "Leadership Lighthouse." This bi-weekly newsletter offers insights, tips, and personal stories to help you navigate the complexities of leadership in today's fast-paced tech environment. Whether you're a new manager or a seasoned leader, you'll find valuable guidance and practical advice to enhance your leadership skills. Subscribe to "Leadership Lighthouse" for the latest articles and exclusive content right to your inbox.Subscribe hereBob Galen's "Agile Moose"Bob Galen's "Agile Moose" is a must-read for anyone interested in Agile practices, team dynamics, and personal growth within the tech industry. The newsletter features in-depth analysis, case studies, and actionable tips to help you excel in your Agile journey. Bob brings his extensive experience and thoughtful perspectives directly to you, covering everything from foundational Agile concepts to advanced techniques. Join a community of Agile enthusiasts and practitioners by subscribing to "Agile Moose."Subscribe hereDo More Than Listen:We publish video versions of every episode and post them on our YouTube page.Help Us Spread The Word: Love our content? Help us out by sharing on social media, rating our podcast/episodes on iTunes, or by giving to our Patreon campaign. Every time you give, in any way, you empower our mission of helping as many agilists as possible. Thanks for sharing!

Are YOU Looking to Take the PMP Exam? Sign up: http://tinyurl.com/elitepmp Are YOU Looking to Take the CAPM Exam? Sign up: http://tinyurl.com/elitecapm From healthcare to aerospace, Charlene's inspiring PMPsuccess story is one for the books!

Bernie Maloney: Problems vs. Solutions: The Great Product Owner Distinction 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 Problem Solver Bernie describes an exemplary Product Owner from a stealth program sponsored by a CTO, where the company needed to create new intellectual property. This Great Product Owner understood that Agile operates in three dimensions: most organizations only focus on outputs and delivery (first dimension), some reach outcomes (second dimension), but the truly great ones operate in the third dimension of strategic or business agility - defining problems worth solving. This Product Owner knew that high-performing teams need to understand what problem is worth solving rather than just receiving solutions to build. They embraced the Mobius loop approach, focusing on discovering the right problems rather than jumping straight to solutions. In this segment, we refer to the Mobius Loop, and to Steve Blank's work on the job of a startup.  We also refer to the episode with Elliott Parker on the critical importance of the “startup mindset” to foster innovation in larger organizations.  The Bad Product Owner: The Backlog Jockey with Authority Issues Bernie identifies the anti-pattern of Product Owners being treated as mere "backlog jockeys" by their organizations, which forces them into solution-building mode rather than problem-solving mode. These Product Owners don't understand the importance of saying "no" and lack clarity about intent and goals. The worst case Bernie encountered was a team manager who also served as Product Owner, wielding positional authority that shut down team communication. This person would interrupt daily scrums, causing teams to revert to waiting for direction rather than self-organizing. The combination of unclear intent and positional authority creates a toxic environment that destroys team autonomy and psychological safety. Self-reflection Question: Is your Product Owner focused on defining problems worth solving, or are they primarily managing a backlog of predetermined solutions? [The Scrum Master Toolbox Podcast Recommends]

Threat modeling is often called the foundation of secure software design—anticipating attackers, uncovering flaws, and embedding resilience before a single line of code is written. But does it really work in practice?In this episode of AppSec Contradictions, Sean Martin explores why threat modeling so often fails to deliver:It's treated as a one-time exercise, not a continuous processResearch shows teams who put risk first discover 2x more high-priority threatsYet fewer than 4 in 10 organizations use systematic threat modeling at scaleDrawing on insights from SANS, Forrester, and Gartner, Sean breaks down the gap between theory and reality—and why evolving our processes, not just our models, is the only path forward.

Caleb Henry, Director of Research at Quilty Space, joins me to talk about EchoStar's spectrum sales and constellation cancellation, SpaceX's spectrum purchase, and the financials of Starlink.This episode of Main Engine Cut Off is brought to you by 34 executive producers—Bob, Heiko, Creative Taxi, Josh from Impulse, Russell, Donald, Will and Lars from Agile, Matt, Steve, Lee, Joel, Tim Dodd (the Everyday Astronaut!), Frank, Natasha Tsakos (pronounced Tszakos), The Astrogators at SEE, Better Every Day Studios, Ryan, Kris, Pat, Joakim (Jo-Kim), Stealth Julian, Warren, Theo and Violet, Jan, Joonas, Fred, David, and four anonymous—and hundreds of supporters.TopicsQuilty Space (@QuiltySpace) / XStarlink Financial & Strategic Analysis 2025 1H | Quilty SpaceSign Up Form | Quilty SpaceEchoStar sells spectrum to SpaceX, cancels MDA satellite contract - SpaceNewsEchoStar's $23 billion spectrum sale clears path for direct-to-device constellation - SpaceNewsEchoStar orders initial MDA satellites for $5 billion LEO constellation - SpaceNewsThe ShowLike the show? Support the show on Patreon or Substack!Email your thoughts, comments, and questions to anthony@mainenginecutoff.comFollow @WeHaveMECOFollow @meco@spacey.space on MastodonListen to MECO HeadlinesListen to Off-NominalJoin the Off-Nominal DiscordSubscribe on Apple Podcasts, Overcast, Pocket Casts, Spotify, Google Play, Stitcher, TuneIn or elsewhereSubscribe to the Main Engine Cut Off NewsletterArtwork photo by CMSEOWork with me and my design and development agency: Pine Works

Bernie Maloney: From Permission-Seeking to Forgiveness-Begging—Agile Team Evolution in Self-Management 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. Bernie defines success for Scrum Masters as creating teams that can thrive and do their best work independently. His ultimate goal is to make himself unnecessary - developing self-directing teams that step out of waiting for direction and instead seek permission or even beg forgiveness when needed. Using the "Circles and Soup" framework, Bernie helps teams stretch their circles of influence and control. He recognizes that every manager wants teams to succeed but may lack the necessary tools, making it crucial for Scrum Masters to coach managers as well. Bernie recommends building a backlog of organizational impediments and focusing on the top priority that will move the ball forward most effectively. Featured Retrospective Format for the Week: Sailboat Bernie champions the Sailboat retrospective format for its simplicity and adaptability. While the basic format is straightforward, he appreciates that you can add layers of complexity as needed. Bernie tends to keep retrospectives simple and also mentions the "What the Duck?" technique as another valuable retrospective tool. He suggests incorporating creative elements like having people build LEGO representations of what they're discussing, which helps teams visualize and engage with concepts more effectively. To know more about LEGO Serious Play, check out the Serious Play book.  In this segment, we also refer to Dissociation in Psychology, which helps with "third position" coaching/thinking, and Bernie's video on creative retrospective formats.  Self-reflection Question: How are you measuring whether your teams are becoming more self-directing, and what specific behaviors indicate they're ready to operate with less guidance? [The Scrum Master Toolbox Podcast Recommends]

In this power-packed episode, Jaryd Krause sits down with serial founder and dealmaker Anthony Franco, a man who knows exits inside and out. Having built and sold seven companies—six of them successfully, including two to publicly listed firms—Anthony brings rare, battle-tested wisdom to the table. Together, they dig into what it really takes to engineer a successful exit in the $5M–$50M range. From preparing your business to maximize valuation, to structuring deals that minimize risk for both buyers and sellers, Anthony shares the strategies he’s used to navigate countless transactions. He doesn’t sugarcoat it either—every deal has “hair” on it, and this conversation unpacks exactly how to handle those messy, unexpected challenges that can tank a deal if you’re not prepared. You’ll learn:✔️ How to structure an exit so you walk away with more security and better terms✔️ Why taking your foot off the gas before closing can destroy your valuation✔️ How buyers can avoid catastrophic mistakes by spotting risk early✔️ What makes a business truly attractive to both strategic and financial buyers✔️ The evolving role of AI in business growth, exits, and even the future of work Whether you’re eyeing a future sale, planning to acquire, or just want to build a business that’s more valuable and resilient, this episode is a masterclass in deal-making straight from someone who’s been through it all.

Bernie Maloney: Mastering Complexity Through Systems Thinking and NLP Coaching 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. Bernie addresses the constant challenge of mid-sprint changes by asking the crucial question: "what do you want to trade in for that new request?" His approach centers on recognizing that everyone is trying to do their best with what they have, using techniques from NLP and the three coaching positions to help people see the whole system. Bernie emphasizes rapport building as a key skill for Scrum Masters and warns against the anti-pattern of becoming judgmental when challenges arise. He advocates for moving from a plan-and-predict mentality to sense-and-respond thinking, highlighting the importance of conducting retrospectives once challenges are solved. Bernie's coaching philosophy revolves around helping people step into the "third position" - a dissociated perspective that enables better problem-solving and systems thinking. In this episode, we refer to Neuro-linguistic Programming (NLP), and to Instant Rapport by Michael Brooks, a primer on NLP. We also refer to the plan-and-predict vs sense-and-respond mentality. Self-reflection Question: How effectively are you helping your teams and stakeholders see the whole system when challenges arise, rather than just focusing on individual pain points? [The Scrum Master Toolbox Podcast Recommends]

In this episode of the Agilists: Aspire and Achieve podcast, host Renae Craven chats to Johanna Ferrer about her experiences of working with different cultures and across different timezones. Hear some of Johanna's tips for establishing connections with your team members.   About the Featured Guest With over 10 years of experience in the technology field, Johanna has collaborated with multidisciplinary teams in leading companies in the beauty, cosmetics, and retail sectors. In recent years, Johanna has focused on fostering agility and maximizing the talent of teams and areas within the organization through self-organization, empowerment, and generating value propositions with a systemic approach. Follow Johanna on LinkedIn (https://www.linkedin.com/in/johanna-ferrer-41183784/) 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 13 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/). 

On Mission Matters, Adam Torres interviews Natalie Buda Smith, Director of Digital Strategy at the Library of Congress. Natalie explains how to plan an agile, project-based career, build AI capabilities (like prompt engineering), and use technology to enhance human strengths—not replace them. This interview is part of our ⁠State of the Women Coverage Series⁠. Big thank you to ⁠Gail Letts!⁠ Follow Adam on Instagram at ⁠https://www.instagram.com/askadamtorres/⁠ for up to date information on book releases and tour schedule. Apply to be a guest on our podcast: ⁠https://missionmatters.lpages.co/podcastguest/⁠ Visit our website: ⁠https://missionmatters.com/⁠ More FREE content from Mission Matters here: ⁠https://linktr.ee/missionmattersmedia Learn more about your ad choices. Visit podcastchoices.com/adchoices

Bernie Maloney: The Triangulation Technique—Coaching Agile Teams Through Challenges 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. Bernie identifies critical patterns that cause teams to self-destruct, with lack of clarity about intention being the most common culprit. When teams are treated as mere "task workers" without clear vision, strategy, or goals, they become depressed and directionless. Some teams seek forgiveness after failed experiments, while others get stuck seeking permission without taking enough self-leadership. Bernie emphasizes that waiting for direction is fundamentally self-destructive behavior, and Scrum Masters must create safety for teams to reach high performance. He introduces the coaching technique of triangulation, where problems become a third point that coach and coachee examine together, side by side, rather than facing each other in opposition. In this segment, we talk about “What the Duck”, a Lego Serious Play workshop. Featured Book of the Week: Start with Why by Simon Sinek Bernie champions "Start with Why" by Simon Sinek as essential reading for Scrum Masters working to transform team culture. He explains that compelling stories are how leaders truly influence others, following the sequence of Attention-Emotion-Reason. This book helps Scrum Masters understand that their job fundamentally involves changing culture, and leaders must demonstrate the change they want to see. Bernie connects this to the broader leadership challenge of developing coaching and mentoring skills within organizational structures. During this segment, we also refer to the following books:  Drive, By Dan Pink Change the Culture, Change the Game, by Connors et al. The Secret Language of Leadership, by Denning Too Many Bosses, Too Few Leaders, by Peshawaria The Geek Way, by McAfee Right Kind of Wrong, by Edmondson   Self-reflection Question: What patterns of self-destructive behavior might your teams be exhibiting, and how could you help them move from seeking permission to taking ownership? [The Scrum Master Toolbox Podcast Recommends]

When Jeff De Francisco noticed his less tech-savvy colleagues billing more hours for the same estate planning work, he uncovered an injustice that would reshape his entire practice. The disparity wasn't about knowledge or skill. It was about efficiency, and the billable hour was punishing him for being good at his job.In this episode, I sit down with Jeff, a long-time client and now business partner, to explore his decade-long journey with Agile practices. You'll also hear lessons from Jeff's journey that you can apply to your own law practice - and get a peek at how tools like Greenline Legal can support your systems along the way.Get full show notes, transcript, and more information here: https://www.agileattorney.com/86Mentioned in this episode:Greenline.legal is Officially in BetaTo set up a demo of this software with me, talk through the workflow challenges and opportunities you have in your practice, and see how Greenline could help, click here: https://the-agile-attorney.captivate.fm/greenlinelegalGreenlineLegal Demo

Could 50% of the Fortune 500 vanish within eight years? In episode 169 of Manage Self, Lead Others video podcast, Dan Silberberg, master strategist for large enterprises, and with a storied CEO career, shares how Richard Koch's Star Principle 2.0 redefines market dominance and the shift from static enterprises to uncopyable ecosystems. Experience each episode in a whole new way and watch every video version on our YouTube channel HERE Subscribe now to be the first to catch our next release. Soundbites [02:29] Introduction to Richard Koch's The Star Principle and 80 / 20 Principle [02:52] Michael Porter's Five Forces model [06:24] How substitutes impact star businesses [06:59] Market shifts and changing consumer preferences [08:22] From company to ecosystem thinking [08:49] Predictions for Fortune 500 disruption and role of ecosystems [09:52] Service businesses enabling ecosystems [10:10] Adaptive intelligence and rapid market innovation [11:24] Cash cow stage and innovation timing [12:12] Agile innovation alongside existing cash cows [12:54] Static vs. exponential growth markets [15:26] Embedding innovation as standard operating practice [15:41] Shift from enterprise focus to customer-driven strategies [16:47] Key actions for using metrics effectively [17:07] Speed of reacting to data as competitive advantage [17:44] Building network platforms instead of static enterprises [19:27] Preview of “The Uncopyable Enterprise” eBook [20:14] Lessons from Buckminster Fuller [21:07] How to connect and work with Dan Silberberg CONTACT DAN SILBERBERG Website: https://entelechy.ai/ LinkedIn: https://www.linkedin.com/in/dansilberberg/ ABOUT PODCAST HOST, NINA SUNDAY Nina Sunday's latest book, ‘'Manage Self, Lead Others: Constructive Conversations, True Self-Leadership, and Culture You Can't Fake'' now on Amazon - paperback or kindle. Amazon USA ⁠⁠https://a.co/d/3WaplI9⁠⁠ Amazon Australia ⁠⁠https://amzn.asia/d/0KwghaM⁠⁠ You can read any Kindle eBook on your PC, laptop or phone; you don't need a Kindle device. Feel free to leave a review so others know it's a good read. === To learn more about face-to-face training programs with Nina Sunday or one of her experienced Facilitators from Brainpower Training Pty Ltd in Australia Pacific, visit: ⁠⁠⁠⁠⁠⁠⁠https://www.brainpowertraining.com.au/signature-programs/⁠⁠⁠⁠⁠⁠⁠ === To visit Nina Sunday's speaker site for conference speaking, Australia and globally, visit: ⁠⁠⁠⁠⁠⁠⁠https://www.ninasunday.com/⁠⁠⁠⁠⁠⁠⁠ === Connect with Nina Sunday on LinkedIn ⁠⁠⁠⁠HERE⁠⁠⁠⁠ === To subscribe to Nina Sunday's blog go to ⁠⁠⁠⁠⁠⁠⁠https://www.brainpowertraining.com.au/ ⁠⁠⁠⁠⁠⁠⁠and scroll to bottom of the page to register. Learn more about your ad choices. Visit megaphone.fm/adchoices

We are continuing our conversation with Nevine White, Senior VP of Finance at Greater Technology Together and a member of the Beyond Budgeting Round Table. Nevine has spent nearly two decades guiding organizations through the shift from rigid annual budgets to adaptive, rolling financial frameworks that enable true business agility.In this episode, Nevine explains how she executed the shift to rolling forecasting. She details the initial varied reactions, the creation of a robust training program, and the integration of finance teams into regional operations for real-time decision-making. Nevine also elaborates on gamification strategies, overcoming executive resistance, and the importance of continuous learning and communication. Highlighting her experience of guiding executive leadership through this transition, she emphasizes the role of proactive coaching and effective upward management.00:00 Introduction to Agile Tales01:57 Transitioning from Traditional Budgeting to Agile Financial Planning02:24 Implementing Rolling Forecasting: The First Steps03:14 Training and Engaging the Organization06:27 Challenges and Emotional Impact08:14 Burning Platform Conversations11:19 Embedding Finance in the Regions14:38 Building a Collaborative Learning Environment19:00 Executive Leadership Buy-In and Coaching26:13 Conclusion and Final ThoughtsNevine's insights highlight that there's no one-size-fits-all playbook for financial agility. Instead, transformation requires experimentation, iteration, and courage to question the sacred cows of yearly budgets. Her experiences demonstrate how finance - often seen as the last function to change - can become a catalyst for business agility, resilience, and innovation.About Nevine White:Beginning her 35-year career in telecom engineering, Nevine moved on to leading the FP&A function for TW Telecom for two decades. There she championed powerful changes in financial planning that enabled an agile and effective management structure by eliminating traditional budgets. After the sale of the company, Nevine continued this work with Live Future Ready, leveraging her experience to support organizations in their financial transformation efforts across various industries. In 2019, Nevine joined Hargray Communications Group as the VP Accounting, before taking on building the Finance and Administrative functions for a broadband start-up. She is currently the Senior Vice President of Finance at Greater Technology Together, a leading network and security as a service firm. Recognized for her experience in finance agility and building effective teams, she has been featured at conferences and on podcasts, and enjoys sharing her learnings and experiences with all who are seeking to meaningfully change and enable their teams. You can follow Nevine on LinkedIn at https://www.linkedin.com/in/nevinewhite/Podcast music courtesy of www.purple-planet.comVisit us at https://www.ouragiletales.com/about

Bernie Maloney: The Power of Psychological Safety 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. Bernie shares a powerful story about learning what psychological safety truly means through both success and failure. Working in a high-pressure division with tight timelines and margins, Bernie discovered the transformative power of the mantra "always make a new mistake." When he made a significant error and was met with understanding rather than punishment, he experienced firsthand how psychological safety enables teams to thrive.  Later, facing a different challenge where mistrust existed between management and teams, Bernie had to navigate the delicate balance of maintaining psychological safety while addressing management's desire for transparency. His solution was innovative: conduct retrospectives with the team first, then invite managers in at the end with anonymized contributions. Bernie's approach of framing changes as experiments helped people embrace newness, knowing it would be time-bound and reversible. In this episode we refer to Neuro-linguistic Programming (NLP).  Self-reflection Question: How might your current approach to mistakes and experimentation be either fostering or undermining psychological safety within your team? [The Scrum Master Toolbox Podcast Recommends]

We're kicking off a brand-new series revisiting Stephen Covey's 7 Habits of Highly Effective People — through the lens of modern leadership. In this episode, Josh and Bob unpack the first two habits:Be Proactive – Don't wait for permission. Great leaders anticipate, act, and build ahead of the curve. From hiring talent before you need it to proactively managing your own growth, proactivity isn't about flailing — it's about intentional, forward-looking leadership.Begin with the End in Mind – Leadership starts with clarity. Whether it's building a product, scaling a team, or shaping a career, vision matters. But so does flexibility. Josh and Bob share stories about startups, strategy shifts, and why leaders must balance end goals with the twists and turns of the real world.The conversation is unfiltered, practical, and rooted in decades of lived experience — showing how these timeless habits still hold power today.The 7 Habits of Highly Effective People: 30th Anniversary EditionStay Connected and Informed with Our NewslettersJosh Anderson's "Leadership Lighthouse"Dive deeper into the world of Agile leadership and management with Josh Anderson's "Leadership Lighthouse." This bi-weekly newsletter offers insights, tips, and personal stories to help you navigate the complexities of leadership in today's fast-paced tech environment. Whether you're a new manager or a seasoned leader, you'll find valuable guidance and practical advice to enhance your leadership skills. Subscribe to "Leadership Lighthouse" for the latest articles and exclusive content right to your inbox.Subscribe hereBob Galen's "Agile Moose"Bob Galen's "Agile Moose" is a must-read for anyone interested in Agile practices, team dynamics, and personal growth within the tech industry. The newsletter features in-depth analysis, case studies, and actionable tips to help you excel in your Agile journey. Bob brings his extensive experience and thoughtful perspectives directly to you, covering everything from foundational Agile concepts to advanced techniques. Join a community of Agile enthusiasts and practitioners by subscribing to "Agile Moose."Subscribe hereDo More Than Listen:We publish video versions of every episode and post them on our YouTube page.Help Us Spread The Word: Love our content? Help us out by sharing on social media, rating our podcast/episodes on iTunes, or by giving to our Patreon campaign. Every time you give, in any way, you empower our mission of helping as many agilists as possible. Thanks for sharing!

Ezinne and Oji Udezue have over 50 years of combined product leadership experience at Microsoft, Twitter, Atlassian, WP Engine, Typeform, and Calendly. They've witnessed every major shift in product management, and, despite their seniority, they're taking beginner AI courses and learning from engineers half their age, and Oji is coding more now than in the past decade—from Waterfall to Agile to AI. They are also the authors of Building Rocketships, a guide to building great products. In this conversation, the couple shares hard-won lessons they've learned from companies successfully adapting to AI, including their “shipyard” framework and their “sharp problem” methodology.What you'll learn:1. The “shipyard” framework: why the best AI teams embrace controlled chaos2. Why Oji writes more code now than in the past 10 years—despite being a PM for more than 25 years3. The three skills that matter most for PMs in 2025: curiosity, humility, and agency4. How to identify “sharp problems”5. AI at the core vs. AI at the edge: why companies that are building entirely new AI-centric codebases will beat those just “sprinkling AI” on existing products6. The counterintuitive truth: engineers are moving so fast with AI that PMs are now the bottleneck7. Their biggest product lesson from 50 combined years—Brought to you by:Mercury—The art of simplified financesVanta—Automate compliance. Simplify security.Coda—The all-in-one collaborative workspace—Where to find Oji and Ezinne:• ProductMind on Substack: https://substack.com/@ojiudezue• ProductMind on LinkedIn: https://www.linkedin.com/company/productmindco• ProductMind on YouTube: https://www.youtube.com/@ProductMindX/videos• ProductMind on Spotify: https://open.spotify.com/show/07OVh5pdSv0szHPwWktzQQ• ProductMind website: https://www.productmind.co/• Oji on LinkedIn: https://www.linkedin.com/in/ojiudezue/• Ezinne on LinkedIn: https://www.linkedin.com/in/ezinne/—Where to find Lenny:• Newsletter: https://www.lennysnewsletter.com• X: https://twitter.com/lennysan• LinkedIn: https://www.linkedin.com/in/lennyrachitsky/—In this episode, we cover:(00:00) Introduction to Oji and Ezinne(04:14) The evolving role of product managers(08:01) Challenges and opportunities in product management(10:34) Sharp problems(12:37) The shipyard model for product development(17:02) Hiring PMs in the AI era(24:55) The importance of staying humble(27:16) Hands-on learning and personal projects(39:10) Companies succeeding with AI adoption(46:25) Lessons from 50 years in product(49:22) Simplicity in design(51:24) The role of communication in strategy(55:17) Career intentions and personal growth(01:00:00) Ethics and responsibility in product management(01:03:09) Introducing Building Rocketships(01:06:42) Lightning round and final thoughts—Referenced:• How 80,000 companies build with AI: products as organisms, the death of org charts, and why agents will outnumber employees by 2026 | Asha Sharma (CVP of AI Platform at Microsoft): https://www.lennysnewsletter.com/p/how-80000-companies-build-with-ai-asha-sharma• Picking sharp problems, increasing virality, and unique product frameworks | Oji Udezue (Typeform, Twitter, Calendly, Atlassian): https://www.lennysnewsletter.com/p/picking-sharp-problems-increasing• Atlassian: https://www.atlassian.com/• Joff Redfern on LinkedIn: https://www.linkedin.com/in/mejoff/• Brownian motion: https://en.wikipedia.org/wiki/Brownian_motion• Calendly: https://calendly.com/• Women in Product: https://womenpm.org/• Brian Chesky's secret mentor who died 9 times, started the Burning Man board, and built the world's first midlife wisdom school | Chip Conley (founder of MEA): https://www.lennysnewsletter.com/p/chip-conley• Home Assistant: https://www.home-assistant.io/• What people are vibe coding (and actually using): https://www.lennysnewsletter.com/p/what-people-are-vibe-coding-and-actually• How many layers should I wear today?: https://layers.today/• Typeform: https://www.typeform.com/• David Okuniev on X: https://x.com/okuiux• Clay: https://www.clay.com/• Martin Eriksson on LinkedIn: https://www.linkedin.com/in/martineriksson/• Geoffrey Moore on finding your beachhead, crossing the chasm, and dominating a market: https://www.lennysnewsletter.com/p/geoffrey-moore-on-finding-your-beachhead• Dave Mendlen on LinkedIn: https://www.linkedin.com/in/davemendlen/• Deepfake: https://en.wikipedia.org/wiki/Deepfake• How to kickstart and scale a marketplace business: https://www.lennysnewsletter.com/p/how-to-kickstart-and-scale-a-marketplace• Forever on Netflix: https://www.netflix.com/title/81418639• Paradise on Hulu: https://www.hulu.com/series/paradise-2b4b8988-50c9-4097-bf93-bc34a99a5b4f• Sinners: https://www.imdb.com/title/tt31193180/• Claude: https://claude.ai/• Nespresso Vertuo: https://www.nespresso.com/us/en/vertuo-coffee-machines• Gamma: https://gamma.app/• Framer: https://www.framer.com/• Lovable: https://lovable.dev/• Building Lovable: $10M ARR in 60 days with 15 people | Anton Osika (CEO and co-founder): https://www.lennysnewsletter.com/p/building-lovable-anton-osika• Llama: https://www.llama.com/—Recommended books:• Building Rocketships: Product Management for High-Growth Companies: https://www.amazon.com/Building-Rocketships-Management-High-Growth-Companies/dp/1962339068• Coda version of Building Rocketships: https://www.productmind.co/brpro• Build: An Unorthodox Guide to Making Things Worth Making: https://www.amazon.com/Build-Unorthodox-Guide-Making-Things/dp/0063046067• The Let Them Theory: A Life-Changing Tool That Millions of People Can't Stop Talking About: https://www.amazon.com/Let-Them-Theory-Life-Changing-Millions/dp/1401971369/Production and marketing by https://penname.co/. For inquiries about sponsoring the podcast, email podcast@lennyrachitsky.com.—Lenny may be an investor in the companies discussed.My biggest takeaways from this conversation: To hear more, visit www.lennysnewsletter.com

Mariano Gontchar: The Micromanagement Trap—When PO's Good Intentions Harm 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. The Great Product Owner: The Visionary Leader During an agile transformation project modernizing a build system with multiple stakeholders, Mariano worked with an exceptional Product Owner who demonstrated the power of clear vision and well-defined roadmaps. This visionary Product Owner successfully navigated complex stakeholder relationships by maintaining focus on the product vision while providing clear direction through structured roadmap planning, enabling the team to deliver meaningful results in a challenging environment. The Bad Product Owner: The Task-Manager Micromanager Mariano encountered a well-intentioned Product Owner who fell into the task-manager anti-pattern, becoming overly detail-oriented and controlling. This Product Owner provided extremely detailed story descriptions and even specified who should do what tasks instead of explaining why work was needed. This approach turned the team into mere task-handlers with no space to contribute their expertise, ultimately reducing both engagement and effectiveness despite the Product Owner's good intentions. Self-reflection Question: Are you empowering your team to contribute their expertise, or are you inadvertently turning them into task-handlers through over-specification? [The Scrum Master Toolbox Podcast Recommends]

Mariano Gontchar: Fear-Free Teams—Creating Psychological Safety for High 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. Mariano's definition of Scrum Master success has evolved dramatically from his early days of focusing on "deliver on time and budget" to a more sophisticated understanding centered on team independence and psychological safety. Today, he measures success by whether teams can self-manage, communicate effectively with stakeholders, and operate without fear of criticism. This shift represents a fundamental change from output-focused metrics to outcome-focused team health indicators that create sustainable high performance. Self-reflection Question: How has your definition of success evolved in your current role, and what would change if you focused on team independence rather than traditional delivery metrics? Featured Retrospective Format for the Week: Frustration-Based Retrospective Mariano's retrospective approach focuses on asking team members about their biggest frustrations from the last sprint. This format helps team members realize their frustrations aren't unique and creates psychological safety for sharing challenges. The key is always asking the team to propose solutions themselves rather than imposing fixes, making retrospectives about genuine continuous improvement rather than just complaining sessions. [The Scrum Master Toolbox Podcast Recommends]

Nigel Thurlow previously served as the first-ever Chief of Agile at Toyota, where he created the World Agility Forum award-winning “Scrum the Toyota Way” and co-created The Flow System™, a holistic FLOW-based approach to delivering customer-first value built on a foundation of The Toyota Production System.Throughout his career, Thurlow has gained an enviable recognition as a leading expert in Lean and Agile methods, tools, techniques, and approaches. He specializes in developing effective organizational designs and operating models for organizations to embrace both Lean and Agile concepts. By leveraging knowledge from various sources, Thurlow helps optimize organizations to enact successful, long-lasting transformational strategies in applying Lean thinking, Agile techniques, and Scrum – while combining complexity thinking, distributive leadership, and team science, represented by a triple helix structure known as the DNA of Organizations™.As of 2024, he has trained over 8,500 people worldwide in Scrum, Agile, Lean, Flow, Complexity, and organizational design. Thurlow is a Professional Scrum Trainer (PST).An instinctive problem solver, Nigel Thurlow takes a method-agnostic, cross-industry approach in helping organizations find the right tools, methods, and approaches to overcome challenges within their contextual situation. He advocates for the fact that there is not a one-size-fits-all prescriptive approach to agility; all tools have utility, but they also have contextual limitations. From this vantage point, Thurlow equips an organization's people to become an army of problem solvers, expanding their perception of what they do so they can better understand and prepare for potential challenges along the way.Thurlow is currently the Chief Executive Officer at The Flow Consortium, a collection of highly regarded companies in the Lean and Agile world — as well as the scientific and academic communities at large. The Flow Consortium strives to expand the boundaries of current Lean and Agile thinking through the understanding of complexity thinking, distributed leadership, and team science by tapping into the minds of top thought leaders from these concentrations.While at Toyota, Thurlow worked to frame Scrum as more than just a standardized behavioral process by applying and advancing fundamental methodologies to spur innovative, forward-thinking solutions to Toyota's most complex challenges. He also founded the Toyota Agile Academy in 2018. These efforts signaled a transformative phase for Toyota, leading the company towards organizational agility and helping its team members better understand this concept in an automotive production context.Additionally, Thurlow has been a board presence at the University of North Texas since 2019, serving as an advisor to the Department of Information Science Board and a member of the College of Information Leadership Board. He has also served as the President of CDQ LLC since 2012. Prior to that, Thurlow held executive coaching and training roles for companies including Vodafone, Lumen Technologies, Scrum, Inc., GE Power & Water, 3M Healthcare Information Systems, Bose Corporation, The TJX Companies, Inc. – as well as the Commonwealth of Massachusetts. He has also taught Scrum at the Massachusetts Institute of Technology (MIT).As an author, Thurlow was named a Forbes top 10 author for co-authoring the book “The Flow System™” in 2020. He has recently co-authored “The Flow System Playbook” published in 2023 which presents a practical study guide and reference book to all the concepts covered in the first book.His other notable publications include “Introducing the Flow System (2019)” and “TPS and the Age of Destruction (2019).” He is also the co-author of The Flow Guide and The Flow System Principles and Key Attributes Guidebook. Recently, Thurlow co-authored “The...

Today on The Federal Drive with Terry Gerton DOE's latest cohort of innovators is turning science into startups Agile started with tech, but now it's driving smarter, faster, more resilient government What do fading unions, and a funding fight mean for the federal workforce?See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Agile government is a blueprint for reform. By shifting focus to end-users, empowering small teams, and embracing rapid iteration, agencies can better meet public needs in a fast-changing world. That's the foundation of the National Academy of Public Administration's new Agile Learning Program. Here with insight into how the course equips leaders with practical tools for navigating complexity and driving change are Dr. Joe Mitchell and Amanda Mullan. Dr. Mitchell serves as the Cooley-Fanning Director of Strategic Initiatives & International Programs at the National Academy of Public Administration (NAPA). Ms. Mullan serves as the Academy's Project Director for Strategic Initiatives.See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Procurement is often the missing piece in Agile transformations. In this Scrum.org Community Podcast, Dave West is joined by  Mirko Kleiner, President, Lean Agile Procurement Alliance and Simon Reindl, Professional Scrum Trainer to explore how procurement's traditional predictive approach can clash with Agile's iterative nature—and how to fix it. They share how early involvement, transparency, and cross-functional collaboration between procurement, legal, and product teams can unlock greater agility. Learn how to apply Lean Agile Procurement principles, shift toward goal-oriented contracts, and align third-party relationships to deliver better outcomes faster.Watch related webcast

Mariano Gontchar: From Evangelist to Facilitator—How To Lead A Successful Company Merger 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. During a complex merger between two telecom companies, Mariano faced the challenge of uniting team members with different cultures, practices, and tools. His initial approach of selling Agile theory instead of focusing on benefits failed because he forgot about the "why" of change. The breakthrough came when he shifted from being an Agile evangelist to becoming a facilitator who listened to managers' real challenges. By connecting people and letting the team present their own solutions to leadership, Mariano successfully created unity between the formerly divided groups. Self-reflection Question: Are you trying to sell your methodology or solve real problems, and what would happen if you focused on understanding challenges before proposing solutions? [The Scrum Master Toolbox Podcast Recommends]

Daniel Deogun and Dan Bergh Johnsson -- two of the co-authors of the book, Secure by Design -- discuss the intersection of good software design and security with host Sam Taggart. They describe how following certain software design principles can help developers create secure software without needing to become security experts. They talked about how this is the continuation of developers taking on more responsibilities: Agile asked developers to become responsible for testing their code. DevOps asked developers to work together with operations in deploying their code. Secure by Design asks developers to incorporate security into their designs. Brought to you by IEEE Computer Society and IEEE Software magazine.

Consider The Downstream Effects - Mike CohnHave you ever looked at the pipes under a bathroom or kitchen sink?If you do, you'll notice that the pipe doesn't run straight from the sink to the wall. Instead the pipe from the drain goes down farther than necessary, curves right back up and then heads into the wall.This little extra bit of pipe that goes down farther than necessary and u-turns back up is called a P-trap. That's because it looks like a P turned on this side.Why do plumbers install P-traps? They must cost more to manufacture, so it increases their costs, which they may or may not be able to pass on to customers. They're a little harder to install, so they cost the plumber time, too.So, why? Plumbers install P-traps because they prevent downstream problems. A P-trap under your sink traps gases that would otherwise rise back into the house. They also catch small items that fall down the drain.And good plumbers care about this even though they know they may not be the plumber to return to fix the problem.Good plumbers care because they're good plumbers. Installing a P-trap under your sink is simply the right thing to do because it prevents downstream problems. We want agile team members who behave the same way. Good agile team members care–not just about their own work but also about the work of everyone downstream of them. OK. Back to the example. A while back, I helped a team incorporate more automated testing into their work. Some programmers, who viewed their job as nothing more than writing what they considered good code, balked at the idea of altering their code to make future testing easier. Code testability, they argued, was not their problem; it was the testers' problem.The situation came to a head during a sprint planning meeting, when the testers were giving some really large estimates for testing code that was going to take only a fraction of that amount of time to program.The programmers were asked if they could do anything to make the code easier to test. And it turned out there were some things they could do, but some of the programmers didn't want to do them because they felt it would make their code less elegant.They had defined their jobs as merely writing good code. Who cared if that code was hard to test?Why Do Something If It's Harder?Act Like a Good PlumberI'm going to give you an example of why this matters, but first, I need a favor. Would you take this short AI survey?We want to learn more about how Agile teams are using (or thinking about using) AI in their work. Your input will help us better understand current practices, opportunities, and challenges—and we'll be sharing the results with the community.Take the survey here: https://www.surveymonkey.com/r/ZJY2SXY“They had defined their jobs as merely writing good code. Who cared if that code was hard to test?”If my plumber had done that, I would have had a fully functional sink, perhaps for years. But eventually enough debris would have made it past where a P-trap should have been installed and deep into my plumbing. This would have led to an expensive--and easily avoidable--repair.When team members accept responsibility for issues caused downstream of their work, that team can begin to grow from good to great.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/

Mariano Gontchar: Breaking Down The Clan Mentality 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. Mariano encountered a competent team that was sabotaging itself through internal divisions and lack of trust. The team had formed clans that didn't trust each other, creating blind spots even during retrospectives. Rather than simply telling the team what was wrong, Mariano created an anonymous fear-based retrospective that revealed the root cause: a Product Owner who behaved like a boss and evaluated team members, creating a culture of fear. His approach demonstrates the power of empowering teams to discover and solve their own problems rather than imposing solutions from above. Self-reflection Question: What fears might be hiding beneath the surface of your team's dynamics, and how could you create a safe space for them to emerge? Featured Book of the Week: Turn the Ship Around! by David Marquet Mariano recommends "Turn the Ship Around!" by David Marquet (we have an episode with David Marquet talking about this book, check it here). Mariano highlights the fascinating story and introduction to the leader-leader model, which differs significantly from the traditional leader-follower approach. This book resonates with Mariano's journey from directive leadership to facilitative leadership, showing how empowering others rather than commanding them creates more effective and engaged teams. [The Scrum Master Toolbox Podcast Recommends]

The Birth of the Agile Delivery Manager = No More ScrumMastersIn 2025, we formally changed the title of Scrum Master to Agile Delivery Manager (ADM) in our technology division. This renaming wasn't a rebrand for the sake of optics. It reflected a deeper evolution already happening, rooted in the expanding scope of delivery leadership, the adoption of Flow Metrics and Value Stream Management, and our real-world shift from strict Scrum toward a more customized Kanban-based model.It was this year that the name finally clicked. After assigning Value Stream Architect responsibilities to our Scrum Masters and giving them ownership of delivery metrics, team-level delivery health, and collaboration across roles within their Agile team, I realized the title “Scrum Master” no longer fit their role. I even considered Agile Value Stream Manager, but it felt too narrow and platform-specific.That's when Agile Delivery Manager stood out, not only as a better label but also as a more accurate reflection of the mindset and mission.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 season of Building Better Developers with AI, hosts Rob Broadhead and Michael Meloche revisit a past topic: 'Transform Your Projects: The Ultimate Guide to Effective User Stories.' This episode offers a fresh perspective on how teams can achieve greater success by writing better user stories. The hosts initially tackled this subject in an earlier season, but they return to it because the challenge remains timeless: poorly written user stories continue to derail software projects. This time, they dive deeper into lessons learned, customer-centric approaches, and frameworks that make user stories truly work. Why Writing Better User Stories Still Matters Rob opens with a familiar frustration: sitting in sprint planning and realizing the user stories don't make sense. Vague requirements create confusion, rework, and wasted effort. A user story is not a specification—it's a promise for a conversation that builds shared understanding. By writing better user stories, teams maintain focus on outcomes, rather than implementation. They deliver features that users actually need, instead of technical solutions that fall short. The Philosophy of Writing Better User Stories User stories should always: Stay customer-centric by focusing on what the user wants, not the technical details. Break down work into small, manageable chunks that improve agility and estimation. Emphasize outcomes over implementation, avoiding the trap of data tables and CSS classes too early. Rob illustrates this with the ATM example: “As a customer, I want to withdraw cash so that I can access money in my account.” This keeps the story grounded in the user's experience. The Anatomy of Writing Better User Stories At the core of writing better user stories is a simple formula that makes requirements clear and human: As a [user role] I want [goal] So that [reason] This framework ensures that every story is tied directly to a user's perspective, their needs, and the value they'll receive. However, strong stories extend beyond this sentence structure. Rob and Michael highlight two key frameworks that add depth and clarity: The Three C's – Card, Conversation, and Confirmation, which explain how stories spark dialogue and define “done.” The INVEST Model – Independent, Negotiable, Valuable, Estimable, Small, and Testable- is a checklist that helps teams evaluate whether a story is ready to move forward. Finally, one important reminder: each story should only have one meaning. If a story can be interpreted in multiple ways—or contains “if/then” scenarios—it should be split into smaller, more focused stories. This keeps the backlog clean and avoids confusion later in development. The Three C's of Writing Better User Stories 1. Card The card represents the user story itself. Traditionally, teams would write stories on index cards. Today, tools like Jira, Trello, or Asana take their place. The key is that the card is just a placeholder for a conversation, not the entire requirement. It captures the essence of the story but leaves room for discussion. 2. Conversation The conversation is where the real value happens. Developers, product owners, and stakeholders discuss the story, ask clarifying questions, and uncover details that weren't written down. These discussions ensure that the team shares a common understanding of the user's needs. Without this step, the story risks being too vague or misinterpreted. 3. Confirmation The confirmation defines how the team knows the story is complete. This typically takes the form of acceptance criteria or test cases. Confirmation transforms a story from an idea into a verifiable piece of functionality. It answers the critical question: What does “done” look like? Card captures the idea. Conversation builds the understanding. Confirmation proves the work is complete. The INVEST Model for Writing Better User Stories The INVEST model is a simple but powerful checklist that helps ensure user stories are clear, practical, and actionable. Each letter represents a quality that a strong user story should have. Independent A good user story should stand on its own. That means it can be developed, tested, and delivered without being blocked by another story. Independence reduces dependencies and keeps projects moving smoothly. Negotiable User stories are not contracts carved in stone—they're open to discussion. Teams should be able to negotiate details, scope, and implementation during conversations. This flexibility encourages collaboration and prevents rigid requirements that may not fit real-world needs. Valuable If a story doesn't provide business or user value, it doesn't belong in the backlog. Every story should clearly tie back to outcomes that matter for the end-user or the organization. This keeps the team focused on delivering impact, not just features. Estimable A story should be clear enough that the team can estimate the effort to complete it. If it's too vague or too large, it can't be accurately sized. Estimable stories make sprint planning realistic and help track progress more effectively. Small Stories should be small enough to complete within a single iteration. Large stories, sometimes called “epics,” should be broken down into smaller, more manageable pieces. Small stories are easier to understand, estimate, and test. Testable Finally, a user story must be testable. The team needs to know how to verify it's “done.” This often takes the form of acceptance criteria or test cases, ensuring the functionality can be validated from the user's perspective. The INVEST model keeps stories clear, focused, and actionable. If a story fails any of these tests, refine it before moving forward. Lessons From the Trenches: Writing Better User Stories in Practice Michael highlights a recurring issue: customers often don't fully understand their “why.” They may use outdated paper trails, redundant processes, or even misuse tools they already own. Sometimes developers must reverse-engineer requirements by observing workflows, asking why at each step, and uncovering hidden pain points. Rob adds that trust plays a huge role—stakeholders may initially follow the “official” process, but only reveal their real practices after rapport is established. Avoiding Common Pitfalls Even with good intentions, stories can fall short when they are: Too vague or incomplete. Disconnected from actual business processes. Written without acceptance criteria. Michael stresses that implied requirements are dangerous. Developers should always strive for clearly defined acceptance criteria that leave no room for ambiguity or uncertainty. Practical Tips for Writing Better User Stories The hosts wrap up with actionable guidance for developers: Speak up – Don't code vague tickets without asking questions. Push for the “so that” – The business value matters most. Write acceptance criteria – Define what “done” means. Break down big stories – Smaller, testable stories are easier to validate. Stay user-focused – Keep technical details in subtasks, not in the story. Example: Bad: Add a contact form. Good: As a potential customer, I want to fill out a contact form with my name, email, and message, so that I can get in touch with the company about their services. This richer story sparks the right questions: Which fields are required? Should multiple contact methods be supported? These clarifications lead to solutions that match real needs. Final Thoughts By revisiting this subject, Rob and Michael remind us that user stories are more than backlog items—they are bridges between developers and customers. Writing better user stories keeps teams aligned, prevents rework, and ensures projects deliver meaningful results. Implied requirements are not good requirements. Defined requirements are good requirements. 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 Updating Developer Tools: Keeping Your Tools Sharp and Efficient Building Your Personal Code Repository Your Code Repository and Ownership of Source – Consulting Tips Using a Document Repository To Become a Better Developer The Developer Journey Videos – With Bonus Content Building Better Developers With AI Podcast Videos – With Bonus Content

Mariano Gontchar: From Boss to Facilitator—The Critical Role of Empathy in Scrum Mastery 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. Mariano shares his transformation from viewing himself as a boss in his project manager role to embracing the facilitator mindset essential for Scrum Masters. His journey reveals a crucial insight: you cannot implement Scrum with a "big bang" approach.  Instead, success comes through empathy and understanding your team's needs. Mariano emphasizes that working with Agile requires constant practice and learning, but the key lesson that changed everything for him was learning to empathize with his team members rather than directing them from above. Self-reflection Question: How might your current leadership style be limiting your team's potential, and what would change if you shifted from directing to facilitating? [The Scrum Master Toolbox Podcast Recommends]

Josh and Bob get real about what happens when leadership lands in your lap—whether you asked for it or not. From “org charts on chairs” to the harsh reality of being the single ringable neck, they break down the mistakes, lessons, and turning points that define the journey from individual contributor to leader.They share personal stories of micromanaging gone wrong, learning the hard way about delegation, discovering that the true job of a leader is helping others succeed, and the uncomfortable truth that stepping into leadership often means bucking the system around you.This is an honest, unfiltered roadmap for anyone thrust into leadership, complete with hard-earned wisdom on humility, self-care, finding mentors, and building the leadership style you aspire to—before it's too late. Stay Connected and Informed with Our NewslettersJosh Anderson's "Leadership Lighthouse"Dive deeper into the world of Agile leadership and management with Josh Anderson's "Leadership Lighthouse." This bi-weekly newsletter offers insights, tips, and personal stories to help you navigate the complexities of leadership in today's fast-paced tech environment. Whether you're a new manager or a seasoned leader, you'll find valuable guidance and practical advice to enhance your leadership skills. Subscribe to "Leadership Lighthouse" for the latest articles and exclusive content right to your inbox.Subscribe hereBob Galen's "Agile Moose"Bob Galen's "Agile Moose" is a must-read for anyone interested in Agile practices, team dynamics, and personal growth within the tech industry. The newsletter features in-depth analysis, case studies, and actionable tips to help you excel in your Agile journey. Bob brings his extensive experience and thoughtful perspectives directly to you, covering everything from foundational Agile concepts to advanced techniques. Join a community of Agile enthusiasts and practitioners by subscribing to "Agile Moose."Subscribe hereDo More Than Listen:We publish video versions of every episode and post them on our YouTube page.Help Us Spread The Word: Love our content? Help us out by sharing on social media, rating our podcast/episodes on iTunes, or by giving to our Patreon campaign. Every time you give, in any way, you empower our mission of helping as many agilists as possible. Thanks for sharing!

BONUS: Agile Tour Vienna 2025—Building Community-Driven Agile Excellence In this BONUS episode, we explore the upcoming Agile Tour Vienna 2025 (get your ticket now!) with three passionate organizers who are bringing together the Austrian agile community for a day of learning, networking, and innovation. Join us as we dive into what makes this community-driven event special, the challenges facing today's agile practitioners, and why local connections matter more than ever in our evolving professional landscape. The Heart of Community-Driven Events "For me, it's really about creating an event from the community for the community. So at the Agile Tour Vienna we really pay a lot of attention that the contributions are made by community members." - Sabina Lammert The foundation of Agile Tour Vienna lies in its commitment to authentic community engagement. Unlike corporate-led conferences focused on sales and marketing, this event prioritizes genuine knowledge sharing and peer-to-peer learning. The organizers emphasize creating space for meaningful conversations, where participants don't just consume content but actively contribute to discussions and support one another with real-world challenges. This approach fosters an intimate atmosphere where attendees leave with valuable professional connections and practical insights they can immediately apply. Balancing Local Expertise with Global Perspectives "This local aspect is very important, but then it needs to be enhanced by bringing in ideas from people from the outside world." - Robert Ruzitschka Agile Tour Vienna strikes a unique balance between showcasing local Austrian talent and bringing in internationally renowned speakers. The event features a carefully curated mix of practical experiences from Vienna-based practitioners working directly with teams and companies, combined with keynotes from global thought leaders. This blend creates opportunities for attendees to understand both the local context of agile implementation and broader industry trends, making the learning experience both immediately relevant and strategically valuable. A Thoughtfully Designed Experience "We make sure we have a good diversity within the speakers. We also take care that we have a good mix, because for me, agile started with the engineering practices." - Richard Brenner The 2025 program demonstrates attention to creating a comprehensive learning experience. The organizers ensure language accessibility by maintaining at least one English track throughout the day while also offering German sessions. The content spans from technical engineering practices to team coaching and business strategy, reflecting agile's evolution across organizational levels. The event takes place in a stunning castle location (Auersperg Palace) that enhances the intimate, family-like atmosphere the organizers work hard to cultivate. World-Class Content in an Intimate Setting "Agile Tour Vienna is never aiming to go big, but to stay small and familiar. By the end of the day, you know new people." - Sabina Lammert This year's highlights include keynotes from Dave Farley on engineering excellence and Mirella Muse on product operations, plus an innovative Comic Agile storytelling workshop. The organizers deliberately limit attendance to maintain the conference's intimate character, ensuring meaningful networking opportunities rather than overwhelming crowds. Additional touches like a professional barista bar and ample space for informal conversations between sessions create an environment where genuine professional relationships can develop. From Concept-Based to Context-Based Agility "The biggest challenge is that we go from concept-based agility to context-based agility. Companies realize the world is complex. There is no one framework to rule them all." - Richard Brenner The agile community faces a significant evolution as the methodology matures from underground movement to established practice. Organizations are moving away from rigid framework implementations toward contextual problem-solving approaches. This shift requires practitioners to focus on solving real business issues rather than introducing agile for its own sake. The challenge lies in maintaining agile's core values while adapting to diverse organizational contexts and avoiding the trap of seeking simple solutions for complex problems. Maintaining Values-Based Working "It's not about winning over something. It's about using common sense, getting into interaction and trying to find sometimes complex solutions for complex problems." - Sabina Lammert Rather than declaring agile "dead," the community must refocus on value-based working and continuous adaptation. The real challenge involves empowering people to constantly reevaluate situations and embrace the reality that today's solutions may not work in three weeks or three years. This requires normalizing the inspect-and-adapt mindset as standard practice rather than exception, moving beyond method-focused thinking toward principle-driven decision making. Sustaining Community Spirit Through Challenging Times "In times of crisis, people tend to fall back to old patterns of behavior. We need to keep the ideas that made us work in a specific way alive." - Robert Ruzitschka Economic and political uncertainties create pressure to abandon agile practices in favor of traditional command-and-control approaches. Community events like Agile Tour Vienna play a crucial role in maintaining momentum for collaborative, adaptive working methods. The discipline required for agile practices - continuous integration, experimental approaches, market-driven feedback collection - represents a more sophisticated and ultimately more sustainable way of working than traditional project management approaches. The Discipline of Adaptability The discussion revealed an important distinction about discipline in agile environments. Agile teams demonstrate remarkable discipline through practices like continuous integration, experimental product development, and systematic feedback collection. This represents a more humane form of discipline that acknowledges complexity and enables adaptation, contrasting sharply with the rigid discipline of following predetermined plans regardless of changing circumstances. About Robert Ruzitschka, Sabina Lammert, and Richard Brenner Robert Ruzitschka is a Senior Principal Engineer at Raiffeisen Bank International and leads a team of Engineering Coaches. You can connect with Robert Ruzitschka on LinkedIn. Sabina Lammert is Founder and Agile Coach of Leadventure and supports Teams and organizations to improve their way of collaboration. You can connect with Sabina Lammert on LinkedIn. Richard Brenner is a previous guest, he started as Software Engineer and is now working as Agile Coach helping clients to adopt agile ways of working. You can connect with Richard Brenner on LinkedIn.

Salum Abdul-Rahman: Learning to Communicate Value in Public and Non-Profit Sectors' 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 Systematic Value Communicator Salum describes working with a Product Owner who had a PhD in data science on a public sector visualization project. This exceptional PO was extremely systematic in working with stakeholders and possessed a unique ability to bridge abstract concepts with concrete implementations. In the public sector, where monetary feedback is absent, this PO excelled at thinking about value achievement and communicating it effectively to the team. They had the magical capability to involve stakeholders while demystifying complex requirements, helping the team understand not just engagement metrics but how their work would change society and the world. The Bad Product Owner: The Absentee Specialist The most common anti-pattern Salum encounters is the absentee Product Owner - typically a specialist assigned to the PO role while maintaining their full-time job as a domain expert. With only 10-20% time allocation, these POs lack the capacity to fulfill their responsibilities effectively. They often don't have the time or knowledge to develop essential PO skills, requiring extensive hand-holding to understand even basic concepts like user stories. Salum's approach involves booking time directly in their calendar for backlog refinement sessions and providing comprehensive guidance to help them understand the role, though this intensive support is necessary due to their limited availability for skill development. In this segment, we refer to the concept of ‘enshitification' by Cory Doctorow, and refer to Tom Gilb's bonus episode on the Scrum Master Toolbox Podcast.  Self-reflection Question: How do you ensure your Product Owner has both the time allocation and skill development needed to truly serve the team and stakeholders effectively? [The Scrum Master Toolbox Podcast Recommends]

Salum Abdul-Rahman: The SECI Model of Knowledge Management Applied to Team Retrospectives 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. Salum explains how the key role for Scrum Masters is to help teams develop themselves to the point where they can learn and grow without constant guidance. Success means building team resilience and operational capability while knowing when to step back. He emphasizes the importance of recalibration workshops to maintain shared understanding and the balance between supporting teams and challenging them to become self-sufficient. When teams reach this level of maturity, Scrum Masters can focus their efforts elsewhere, knowing the team has developed the capability to continue evolving independently. Featured Retrospective Format for the Week: The 5-Stage Retro Format From the book "Agile Retrospectives," this format captures the complete learning process and aligns beautifully with knowledge management principles. Salum connects the three central phases of this format to the SECI model of knowledge management, particularly referencing Nonaka and Takeuchi's work in "The Knowledge Creating Company." This retrospective structure helps teams create new knowledge and behavioral change by following a systematic approach that transforms individual insights into collective team learning and action. In this segment, we also refer to the seminal article by Takeuchi and Nonaka: “The New New Product Development Game”, which originated the work on Scrum as a framework.  Self-reflection Question: How do you recognize when your team has developed enough self-sufficiency that your role as facilitator can evolve or step back? [The Scrum Master Toolbox Podcast Recommends]

Nigel Thurlow previously served as the first-ever Chief of Agile at Toyota, where he created the World Agility Forum award-winning “Scrum the Toyota Way” and co-created The Flow System™, a holistic FLOW-based approach to delivering customer-first value built on a foundation of The Toyota Production System.Throughout his career, Thurlow has gained an enviable recognition as a leading expert in Lean and Agile methods, tools, techniques, and approaches. He specializes in developing effective organizational designs and operating models for organizations to embrace both Lean and Agile concepts. By leveraging knowledge from various sources, Thurlow helps optimize organizations to enact successful, long-lasting transformational strategies in applying Lean thinking, Agile techniques, and Scrum – while combining complexity thinking, distributive leadership, and team science, represented by a triple helix structure known as the DNA of Organizations™.As of 2024, he has trained over 8,500 people worldwide in Scrum, Agile, Lean, Flow, Complexity, and organizational design. Thurlow is a Professional Scrum Trainer (PST).An instinctive problem solver, Nigel Thurlow takes a method-agnostic, cross-industry approach in helping organizations find the right tools, methods, and approaches to overcome challenges within their contextual situation. He advocates for the fact that there is not a one-size-fits-all prescriptive approach to agility; all tools have utility, but they also have contextual limitations. From this vantage point, Thurlow equips an organization's people to become an army of problem solvers, expanding their perception of what they do so they can better understand and prepare for potential challenges along the way.Thurlow is currently the Chief Executive Officer at The Flow Consortium, a collection of highly regarded companies in the Lean and Agile world — as well as the scientific and academic communities at large. The Flow Consortium strives to expand the boundaries of current Lean and Agile thinking through the understanding of complexity thinking, distributed leadership, and team science by tapping into the minds of top thought leaders from these concentrations.While at Toyota, Thurlow worked to frame Scrum as more than just a standardized behavioral process by applying and advancing fundamental methodologies to spur innovative, forward-thinking solutions to Toyota's most complex challenges. He also founded the Toyota Agile Academy in 2018. These efforts signaled a transformative phase for Toyota, leading the company towards organizational agility and helping its team members better understand this concept in an automotive production context.Additionally, Thurlow has been a board presence at the University of North Texas since 2019, serving as an advisor to the Department of Information Science Board and a member of the College of Information Leadership Board. He has also served as the President of CDQ LLC since 2012. Prior to that, Thurlow held executive coaching and training roles for companies including Vodafone, Lumen Technologies, Scrum, Inc., GE Power & Water, 3M Healthcare Information Systems, Bose Corporation, The TJX Companies, Inc. – as well as the Commonwealth of Massachusetts. He has also taught Scrum at the Massachusetts Institute of Technology (MIT).As an author, Thurlow was named a Forbes top 10 author for co-authoring the book “The Flow System™” in 2020. He has recently co-authored “The Flow System Playbook” published in 2023 which presents a practical study guide and reference book to all the concepts covered in the first book.His other notable publications include “Introducing the Flow System (2019)” and “TPS and the Age of Destruction (2019).” He is also the co-author of The Flow Guide and The Flow System Principles and Key Attributes Guidebook. Recently, Thurlow co-authored “The...

When operations break down, growth stalls — and for most companies, the warning signs creep in long before anyone notices. Tammara Carr, founder of Audacity Management, has seen it all: from Fortune 50 boardrooms to fast-moving SaaS startups. With a Master's in Project Management, top-tier Agile and Six Sigma certifications, and experience leading multimillion-dollar initiatives, she's the go-to expert for turning operational chaos into a well-oiled growth engine. In this episode, she shares: The early red flags that your operations are holding you back The most common scaling mistakes mid-sized companies make — and how to avoid them How to prioritize business shifts without grinding everything to a halt One system or mindset shift that works just as well for scrappy teams as it does for corporate giants If you're a founder, COO, or team leader feeling buried under moving parts, this conversation will show you how to build systems that not only sustain your business, but help it scale with clarity and confidence. Connect with Tammara: www.audacitymgmt.com www.carrandcompass.com/ IG: @carrandcompass www.pinterest.com/carrandcompass/ www.linkedin.com/company/audacity-management/ Audacity Management Initiative Strategizer | Prioritize what will drive the most value and change for your business: https://audacitymgmt.com/value_disruption Audacity Management Operational Health Check | Pinpoint your biggest areas for operational improvement: https://audacitymgmt.com/operational_check Audacity Management Composite Case Study | See proven approaches for tackling business challenges: https://audacitymgmt.com/case_study-293872 Iconic business leaders all have their own unique genius. Take this quick 10 question quiz to uncover your specific CEO style advantage: ⁠⁠⁠⁠⁠⁠⁠⁠⁠https://cubicletoceo.co/quiz⁠⁠⁠⁠⁠⁠⁠⁠⁠ If you enjoyed today's episode, please: Post a screenshot & key takeaway on your IG story and tag me ⁠⁠⁠⁠⁠⁠⁠⁠⁠@missellenyin⁠⁠⁠⁠⁠⁠⁠⁠⁠ & ⁠⁠⁠⁠⁠⁠⁠⁠⁠@cubicletoceo⁠⁠⁠⁠⁠⁠⁠⁠⁠ so we can repost you. Leave a positive review or rating at ⁠⁠⁠⁠⁠⁠⁠⁠⁠www.ratethispodcast.com/cubicletoceo⁠⁠⁠⁠⁠⁠ ⁠⁠⁠Subscribe for new episodes every Monday. Learn more about your ad choices. Visit megaphone.fm/adchoices

Casey Handmer, Founder of Terraform Industries, joins me to talk about the state of NASA in 2025, talent acquisition and retention, productivity, and so much more.This episode of Main Engine Cut Off is brought to you by 34 executive producers—Kris, Joakim (Jo-Kim), Creative Taxi, Heiko, Joel, Frank, Josh from Impulse, The Astrogators at SEE, David, Jan, Tim Dodd (the Everyday Astronaut!), Theo and Violet, Joonas, Stealth Julian, Donald, Warren, Matt, Pat, Steve, Fred, Bob, Lee, Natasha Tsakos (pronounced Tszakos), Will and Lars from Agile, Russell, Better Every Day Studios, Ryan, and four anonymous—and hundreds of supporters.TopicsCasey Handmer (@CJHandmer) / XCasey HandmerTerraform IndustriesNASA Is Worth Saving – Casey Handmer's blogEpisode 170 - Luckily, We Did All the Math (with Casey Handmer) - Off-NominalThe science behind clean hydrocarbons | The Freethink Interview - YouTubeThe ShowLike the show? Support the show on Patreon or Substack!Email your thoughts, comments, and questions to anthony@mainenginecutoff.comFollow @WeHaveMECOFollow @meco@spacey.space on MastodonListen to MECO HeadlinesListen to Off-NominalJoin the Off-Nominal DiscordSubscribe on Apple Podcasts, Overcast, Pocket Casts, Spotify, Google Play, Stitcher, TuneIn or elsewhereSubscribe to the Main Engine Cut Off NewsletterArtwork photo by NASAWork with me and my design and development agency: Pine Works

Salum Abdul-Rahman: From Lunch Conversations to Company-Wide Change—The Power of Creating Communities of Practice Within Organizations 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. Salum shares how he organically built an Agile community within his company by recognizing a shared need for discussion and learning. Starting as a software developer who took on Scrum Master tasks, he felt isolated in his Agile journey. Rather than waiting for formal training or external events, he sent out a simple invite on the company Slack for a lunch discussion during a work day. People showed up, and what began as informal conversations about different approaches to Scrum and Kanban evolved into monthly gatherings. Over time, this grassroots community grew to organize company-wide events and even found new leadership when Salum moved on, demonstrating the power of identifying shared needs and taking initiative to address them. Self-reflection Question: What shared learning needs exist in your organization that you could address by simply reaching out and organizing informal discussions? [The Scrum Master Toolbox Podcast Recommends]

In this episode of the Agilists: Aspire and Achieve podcast, host Renae Craven chats to Vinnie Gill about her experience of living in different countries and how her agile career has grown because of that.    About the Featured Guest Vinnie Gill puts people and culture first. She enjoys connecting with people and companies to find their purpose, walking alongside them in their organisational growth journey. Her passion is influencing change at the Enterprise level.   She is deeply involved in the Agile community, speaks at international conferences and has a special interest in educating and education being the tool that empowers people. Follow Vinnie on LinkedIn (https://www.linkedin.com/in/vinniegill/) Her website: https://outcomeoveroutput.com   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 13 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/).

Salum Abdul-Rahman: From Isolation to Integration—Rebuilding Agile Team Connection For Remote 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. Salum describes working with a grocery ecommerce team during COVID that fell into the trap of prioritizing individual convenience over team collaboration. Remote work led team members to design their work around personal preferences, with the lead developer becoming increasingly isolated and unresponsive to team communication. This anti-pattern of "what works for me" over "what works for the whole team" created significant dysfunction. Despite management intervention, the situation required creative solutions like organizing face-to-face sessions and shared working sessions with digital whiteboards to rebuild team cohesion. Featured Book of the Week: Agile Retrospectives One of the most important roles of Scrum Masters is to help teams develop themselves. Salum emphasizes that you can't tell the team what to do - you have to help them discover it themselves. "Agile Retrospectives" provides the foundation for running meaningful retrospectives that become the key tool for team self-development. The book's emphasis on variation and building retrospectives to match your team's needs and maturity level makes it essential for empowering teams to grow and evolve continuously. Self-reflection Question: How might your team's current work arrangements prioritize individual convenience over collective effectiveness, and what steps could you take to shift this balance? [The Scrum Master Toolbox Podcast Recommends]

Salum Abdul-Rahman: The Expert Who Couldn't Connect: An Agile Team Integration Challenge 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. Salum shares a challenging situation where a software architect with deep expertise struggled to integrate with the team. Despite the architect's technical knowledge, his expert-based communication style and inability to justify reasoning created friction with other developers. The conflict escalated when the architect disengaged from teamwork and ultimately left the company. This experience highlights the importance of understanding organizational dynamics in large corporations and recognizing when separation might be the best solution for everyone involved. In this episode, we refer to Nonviolent Communication, a topic we've discussed often here on the podcast.  Self-reflection Question: How do you balance respecting expertise while ensuring all team members communicate in ways that foster collaboration rather than create hierarchies? [The Scrum Master Toolbox Podcast Recommends]