The Mob Mentality Show

🎲 In this episode of the Mob Mentality Show, we dive into a unique and game-changing (literally) approach to learning Test-Driven Development (TDD) with Ted M. Young (JitterTed), John Wilson, and Janis Kampe. Discover the origin story of the TDD board game that started as a simple teaching aid and evolved into a powerful learning experience for developers, teams, and even product managers. Hear how this game went from casual pub nights to becoming a staple for some in team training sessions, meetups, and Agile coaching toolkits. We break down: ✅ How the TDD board game helps teams internalize the deeper steps of TDD beyond the basic "Red-Green-Refactor" mantra. ✅ Why the game’s focus on prediction, risk management, and working in small steps transforms the way people think about writing code. ✅ The surprising ways the game builds psychological safety, making it accessible even to people new to TDD or nervous about exposing gaps in their knowledge. ✅ How the game naturally leads to ensemble (mob) programming and seamless transitions into hands-on coding platforms like CyberDojo. ✅ Practical tips on using the game to onboard, coach, and improve team collaboration—whether you're remote, hybrid, or in-person. We also explore the importance of failing safely, incremental learning, and how the game allows players to experience both the thrill of success and the consequences of cutting corners—without the high stakes of real-world code. Whether you're a developer, Agile coach, product manager, or just curious about TDD, this episode will give you actionable insights on: 🛠 How to enable continuous learning in your teams. 🎯 Why predicting outcomes matters more than just getting green tests. 🎮 How gamification makes TDD fun, social, and sticky. Key Topics: TDD Board Game Mechanics & Variations Psychological Safety in Learning Risk vs. Reward in Software Development Ensemble Programming (Mob Programming) Transitioning from Game to CyberDojo Practical Coaching Tools for TDD and XP Building Stronger Developer-Product Manager Collaboration Video and Show Notes: https://youtu.be/GjcUdoS5K6I

👨‍💻 Legacy code isn’t just old untested code—it’s a symptom of deeper problems in your organization. In this no-fluff episode of the Mob Mentality Show, we’re joined by Agile and technical coach Wouter Lagerweij to break down why legacy issues persist and how shared responsibility between product and engineering is the key to meaningful change. 🎯 What we cover in this episode: - Why legacy systems are just as much about organizational baggage as they are about outdated code - How true Agile teaming—swarming, pairing, mobbing—can unlock speed, learning, and fun - Why your bug tracker is a graveyard, and how a zero bug policy can reset your team’s quality bar This is a grounded, experience-rich conversation packed with practical insights for developers, team leads, product managers, and anyone serious about improving delivery without adding more process theater. ✅ You’ll come away with: * A broader definition of legacy and how to confront it * Concrete examples of effective team collaboration models * A new perspective on software quality and defect tracking * Proven ways to foster stronger cross-functional ownership 👤 **About the guest:** Wouter Lagerweij is an independent Agile Coach based in The Netherlands and operating throughout Europe. He loves spending time with teams and organizations to figure out how to improve the way they make software, and make it more fun. To make that happen he uses the knowledge and skills gathered in over eighteen years of experience applying Agile processes and practices from XP, Scrum, Kanban, Continuous Delivery, DevOps, Lean and Systems Thinking. To turn those improvements into real business opportunities, he has added Lean Startup/Lean Enterprise approaches. Occasionally, he even uses common sense. 😅 Video and show notes to be posted here in the next day or so.

🎙️ What happens when software engineers and leaders don’t speak the same language? How do context-free Agile practices and technical dogma lead teams astray? And how do we create engineering cultures that deliver real business value without burning out? In this Mob Mentality Show episode, we sit down with Kyle Rowland—leadership and software consultant, 20-year software engineering veteran, and author of Powerful Profitable Software Products: The Executive Guidebook—to tackle the tough questions at the heart of sustainable, impactful software delivery. 💡 What We Cover in This Episode: 🔧 The Engineering-Leadership Impedance Mismatch Why do engineering leaders and business leaders often talk past each other? Kyle shares how focusing on both “how” we build and “what” we build—can prevent burnout, bottlenecks, and bad outcomes. We explore why real innovation depends on creating win-win systems, not siloed thinking. ⚠️ The Danger of Context-Free Agile Many teams argue about Agile, TDD, TBD, and pairing without understanding the systems that make those practices work. Kyle unpacks how context, principles, and shared goals determine whether these tools help or hurt—and how to avoid cargo cult Agile. 🔬 Empiricism vs. Philosophy in Tech Decisions Is the Agile Manifesto's call for empiricism enough? Or is there still a place for a priori reasoning (argument from principle) in engineering? Kyle argues for a balanced approach—using experiments where we can, and wisdom where we must. ⏱️ The 1:40 Rule and Escaping Tactical Overload Are you buried in endless 1-on-1s and tactical firefighting? Kyle introduces the “1:40 rule”—a lens for spotting when leaders are too involved in details and not investing in system-level growth. He explains how to avoid organizational entropy and shift your focus from maintenance to momentum. 📚 Plus: Behind the Book We go deep on Kyle’s new book Powerful Profitable Software Products, exploring practical ways leaders can move from reactive chaos to purpose-driven product delivery—while empowering teams and aligning with business goals. 🎧 Whether you're an engineering leader, product owner, or software dev, this episode is packed with insights on leadership, systems thinking, quality, speed, and how to build software that matters. FYI: Video and show notes to be posted here in the next day or so.

What if your beliefs—about work, people, or even yourself—are quietly holding you back? In this episode of The Mob Mentality Show, we sit down with visual thinker, author, and accidental Mob Programming anthropologist Dave Gray to unpack the power of belief, clarity, and collaboration in tech and beyond. Dave Gray is known for Liminal Thinking—a book about understanding the invisible beliefs that shape behavior and systems. But did he know he was writing a book about us? Turns out, our Mob Programming origin story and Dave’s journey are more connected than you’d expect. With roots as an artist, Dave brings a rare perspective to complex tech and business systems. From prior infographic posters that demystified RFID and Bluetooth when they first came out, to visual guides on inner transformation and his latest books, Dave's work simplifies the complicated and builds bridges for real understanding. With Dave we explore: What led Dave from agile software development to Liminal Thinking Why most Agile transformations fail How to navigate confusing resistance—are people really lost, or just saying “no”? The principles behind creating safe spaces and disrupting unhelpful routines Visual and liminal thinking for fostering organic authentic change, not just communication tricks Raw observation vs. narrative: how perception can distort reality Why having lunch with someone you think is "crazy" or "stupid" might be the wisest move The psychology behind tech resistance, organizational inertia, and true agility We also revisit how Woody Zuill and our original Mob Programming team with Chris Lucian smashed the belief that “real work” only happens in cubicles and outside of "meetings." The mob origin story had Liminal Thinking on full display as that team reflected, questioned, and ultimately act in defiance of broken norms. The result? A shift in how we define space, collaboration, and innovation as Dave captures in his book. If you work in tech, lead change, facilitate teams, or just feel stuck inside outdated ways of working, this episode is for you. FYI: Video and show notes to be posted here in the next day or so.

In this thought-provoking episode, we sit down with Tobias Mayer—author, coach, and longtime voice in the Agile world—to explore the journey from his early discovery of XP (Extreme Programming) in 1997 all the way to today’s debate around the death of Scrum. Tobias shares his personal transformation from developer to Scrum Master, his resistance to early XP, and how he learned great practices from developers he managed. We unpack his reflections on Agile’s semantic drift, the role of Scrum Masters as change agents vs. bean counters, and what happens when teams do Agile without even knowing the Agile Manifesto. 🔍 Topics we dive deep into: We also dig into mob programming (aka mobbing)—what it means, why the name matters, and whether or not new metaphors like “ensemble programming” or “teaming” (à la Amy Edmondson) better reflect how high-performing teams really work. 💡 Plus: Tobias brings rich context from classics, theology, and history—yes, even turning a conference t-shirt into fashion—to challenge how we think about building products, teams, and businesses. 🛠️ Whether you're into XP, Scrum, Mob Programming, Lean, or simply want to rethink your metaphors and language at work, this episode delivers grounded insight, sharp critique, and fresh perspectives. 👉 Subscribe for more conversations at the intersection of agile thinking, real teamwork, and modern product development. FYI: Video and show notes to be posted here in the next day or so.

🎙️ In this episode of The Mob Mentality Show, we’re joined by Professor Ben Kovitz—a former software developer with 15 years of industry experience who went on to earn a PhD and is now teaching Computer Science at Cal Poly Humboldt. Prof Ben flips the script and brings his own real-world mob programming questions—challenges he’s faced while mobbing live with college students in the classroom. This is not theory. These are hard-won questions from the trenches of mob programming in a learning environment, where curiosity meets complexity, and group dynamics get real. 🔍 We dive deep into 5 key challenges: 1. Deep Thought vs. Mob Timers: How do you carve out time to think deeply, explain thoroughly, or research ideas in a setting where timers tick every 3 minutes? Is it “wrong” to step away from the mob to figure something out? We discuss balancing solo exploration with group momentum, and how to build a culture that supports both. 2. Upfront Design or Just Start Mobbing? Do you need to pre-design work before mobbing, or can product discovery and agile planning happen in the mob itself? We explore Kanban, Continuous Delivery (CD), and even SPIDR story splitting as tools for flowing work in real time. 3. The Overrun Navigator: What happens when a mob gets too rowdy and drowns out the navigator—especially one who doesn’t yet know what to do? We unpack the difference between “good rowdy” energy and “bad rowdy” imbalance, and how facilitation, structured roles, or even a moment of silence can reset the team. 4. The Strong Opinion Navigator: Is it okay for someone with strong, often-correct opinions to mob effectively? How do we avoid stifling experimentation or learning? We tackle the value of letting experiments speak, coaching with humility, and using dominant voices to model vulnerability instead of control. 5. Mobbing with Documentation and AI: Should the mob read documentation together? What about using AI tools? We cover how teams can mob to teach effective doc reading, search strategies, and prompt engineering, while still adapting workflows to individual learning zones and WIP (Work in Progress) constraints. 💡 This episode is full of insights on: Group facilitation in real-time coding Balancing solo and group learning Creating psychological safety in a mob Adapting mob rules to context—not dogma Bringing agile, XP (Extreme Programming), and education together in the mobbing practice Video and Show Notes: https://youtu.be/nAAI5f7-vTs

🏈 Welcome to another episode of the Mob Mentality Show, where we explore the intersection of software development, leadership, and real-world lessons—from the unexpected to the game-changing. This time, we're talking Coaching Credits—as seen in the addictive mobile football game Retro Bowl—and how they map directly to trust, influence, and leadership in software teams. 🎙️ What are Coaching Credits? In Retro Bowl, Coaching Credits represent the respect and trust you’ve earned from players, staff, and fans. They let you upgrade your team, hire top-tier talent, and level up your environment. In software development, we argue Coaching Credits are just as real—earned through Extreme Programming (XP), Mob Programming, Test-Driven Development (TDD), Continuous Delivery (CD), and strong relationship-building. 👶 Austin kicks it off with a story about trying to stay awake helping his wife with their new baby—turning to Retro Bowl as a late-night lifeline. That sparks a deep dive into what the game teaches us about: Building trust and respect through small wins The balance between performance and relationships Using “credits” (influence) wisely inside and outside your team How to upgrade your environment and talent pool over time What happens when you try to “spend” influence you don’t actually have 👨‍💻 In Dev Culture Terms: Earn trust by delivering value. Spend it by coaching others, refactoring code, upgrading environments, or influencing org-wide decisions. Just like in Retro Bowl, you can overreach. Think: trying a big move when your trust bank is empty = a bounced check. 📘 We also tie Coaching Credits to Stephen Covey’s 7 Habits—specifically, the idea of an emotional bank account—and reflect on how these lessons align with the origin story of mob programming. 🚨 Key Questions We Explore: Can you go into Coaching Credit “debt”? Is quick wins and trust the only way forward when you're starting from zero? Are you too transactional in how you lead or code? Should someone build a Software Dev Sim game like Retro Bowl? 😅 💡 If you're a software engineer, tech lead, or engineering manager, this episode offers a fun but surprisingly deep framework for thinking about how trust, respect, and influence shape the way you build products and teams. FYI: Video and show notes to be posted here in the next day or so.

🎙️ Ever faced a product vision so massive it felt impossible to start? In this Mob Mentality Show episode, we tackle the art and science of Story Splitting — breaking down huge dreams into small, deliverable slices without losing momentum or clarity. We explore real-world strategies, including: Asking the hard questions like Do we really need to release everything at once? Using SPIDR (Spike, Path, Interface, Data, Rules) to guide story splitting Implementing Feature Flags (tools to enable/disable features without deploying new code) for flexible delivery Creating color-coded diagrams to visualize release order and dependencies Practicing "Yes, and" techniques to manage big customer asks without abandoning Agile values Running post-mortem retrospectives focused on improving splitting practices Mapping ideas with Discovery Trees (visual structures for feature evolution) Handling the tension between Big Bang marketing launches and incremental delivery Influencing sales and marketing teams to only sell what's already done vs. selling the future Identifying the impact of poor story splitting on technical debt and customer trust Differentiating splitting technical work vs. splitting user-facing features Teaching business stakeholders the fundamentals of CD (Continuous Delivery) and good story practices implicitly vs. explicitly Working through known unknowns vs. unknown unknowns in product discovery Using the Cynefin Framework (a model for navigating complexity) to decide splitting approaches Prioritizing with cost of delay and story split diagrams to maximize value This episode is packed with hands-on advice for developers, product managers, Agile coaches, and leaders looking to move fast without breaking things. Whether you're struggling with overwhelming customer requests, complicated roadmaps, or internal misalignment, learning how to split the impossible is key to success in Agile, Continuous Delivery, and Lean Product Development. FYI: Video and show notes to be posted here in the next day or so.

🎙️ What’s really happening inside your engineering org? In this episode of the Mob Mentality Show, we sit down with Philip Borlin, Director of Engineering and advocate for lean thinking, mobbing, and team capability building, to uncover how Gemba Walks, smaller batch sizes, and healthy team nudges reveal the actual state of your tech organization—not just what reports say. We explore how leaders can stop flying blind and start leading based on facts from the field. 🔍 Topics Covered: ✅ Gemba Walks (Japanese term meaning “go to the real place”): Why your assumptions about how work gets done are probably wrong How spending even one hour a week in the mob or at the code level changes everything The myth of managing solely through middle managers Why high-fidelity information beats filtered reporting Remote-friendly adaptations: mobbing, Lean coffees, and async insight gathering ✅ Mobbing (also known as ensemble programming): How mobbing surfaces capability gaps and builds shared understanding Growing capabilities without enforcing rigid standards Real stories of capability fire drills, single points of failure, and org fragility “Low and slow” growth as the only sustainable path to true skill development? ✅ Fixing Batch Size and WIP (Work In Progress): How large batches lead to delivery waste, delays, and bugs The surprising power of reducing ticket size to unlock flow Socratic coaching at stand-ups to improve team work slicing Giving permission to drop non-priority work and focus only on what matters ✅ Building a Learning Culture: Why capability resilience > retaining every team member forever Using “nudges” and peer pressure the right way Investing in bright spots without ignoring skeptics Cultivating environments where psychological safety and growth feed off each other 💡 Whether you’re a Director of Engineering, Tech Lead, Agile Coach, or Software Engineer, this episode gives you practical ways to lead with clarity, scale team capability, and build resilience into your org’s DNA. 🎧 Subscribe now so you don’t miss the drop: 👉 https://www.mobmentalityshow.com/ FYI: Video and Show Notes to be posted here in the next day or so.

What if your team didn’t need branches at all? 💥 In this episode of The Mob Mentality Show, we sit down with Ron Cohen, CTO and co-founder of Bucket, to unpack the real story behind Trunk Based Development (TBD) and the practical use of Feature Flags. Ron stirred the pot online by challenging common assumptions around TBD — and now he’s here to clear the air. We talk about: What Trunk Based Development really means (Hint: It’s not just “no branches”) Why TBD isn’t just a Git strategy, but a safety mindset often backed by solid practices like Pair Programming, Mob Programming, and TDD (Test-Driven Development) Gitflow vs. TBD — which one sets your team up to move faster and safer? The myth that TBD = chaos, and why short-lived branches might still play a role How mobbing and pairing can make TBD not just possible, but powerful We also dive deep into Feature Flags (a.k.a. Feature Toggles): Why Ron became obsessed with them — and how they changed how his teams ship code How to use toggles for faster releases, safer experiments, and smoother collaboration between devs, Product Owners (POs), and marketing The difference between feature flags that require a deployment and those that don’t The value of “dogfooding” your features in production before a full rollout Why not all toggles are created equal — from simple UI switches to ops-level controls How to avoid the mess of long-lived toggles and clean up after experiments (Austin, we're looking at you 😅) Plus: How flags can power A/B testing and internal beta programs Fowler’s definition of Feature Flags — and how it is in action Using toggles to build internal and external trust Ron’s framework for different kinds of flags in different contexts Whether you're deep into CI/CD (Continuous Integration/Continuous Delivery), trying to tame your branching strategy, or just want to ship smarter — this episode’s packed with insights you can use immediately. 🎧 Subscribe and listen on your favorite platform: 👉 https://www.mobmentalityshow.com/ FYI: Video and show notes to be posted here in the next day or so.

What happens when a college software design course ditches traditional lectures and embraces Mob Programming? In this episode of the Mob Mentality Show, we sit down with Ben Kovitz, a former software developer turned professor at Cal Poly Humboldt, to explore his innovative approach to teaching software design through mobbing. Topics Covered: ✅ From Industry to Academia: Why Ben left software development to become a professor and how he discovered mob programming. ✅ Redefining Software Education: Instead of 30 traditional lectures on software design, Ben’s students learn by doing—designing software while coding. ✅ The Power of Mobbing in the Classroom: How students collaborate in the mob of 8, rapidly sharing knowledge and tackling challenges together. ✅ Fast Learning vs. Lectures: Why mobbing enables faster knowledge transfer compared to passive lectures. ✅ Strong-Style Navigation: How rotations and fast timers helped to stimulate a highly effective learning environment. ✅ The Role of the Navigator: How students help each other navigate, learn C++ and the QT framework, and document key lessons from each mob session. ✅ Real-World Software Challenges: Simulating legacy code maintenance, evolutionary design, and design patterns like MVC (Model-View-Controller). ✅ Overcoming Student Struggles: What happens when students don’t know how to navigate? How asking for help and learning together fosters growth. ✅ Teaching Through Experience: Letting students experiment with flawed solutions before introducing better design principles. ✅ Assessment & Engagement: How Ben measures student participation, engagement, and learning outcomes in a mobbing environment. Why This Matters: Traditional software design education can leaves students unprepared for the realities of refactoring real code and collaborative development. By integrating Mob Programming, refactoring techniques, and hands-on problem-solving, Ben Kovitz is equipping the next generation of developers with practical, real-world skills and deeper design insights. 📢 Subscribe to the Mob Mentality Show to stay updated on the latest insights in Mob Programming, Extreme Programming (XP), Agile, and collaborative software development! 🎧 Listen on your favorite podcast platform: https://www.mobmentalityshow.com 🔔 Don’t forget to LIKE, COMMENT, and SUBSCRIBE for more episodes on software development, coding education, and team collaboration! FYI: Video and show notes to be posted here in the next day or so.

🔥 How do you actually build great software developers? How do you debug like a pro? And what happens when XP (Extreme Programming) makes a comeback after the Scrum backlash? Join us as Garrick West—a seasoned XP practitioner, Agile coach, and software craftsmanship advocate—dives into: ✅ Building Agile Software Developers: From XP mentorship to industry-academia collaboration ✅ The Best Debugging Strategies: Unpacking The Debugging Book and applying its rules in a mob ✅ Reviving XP & Software Crafting: Why XP is more crucial than ever in Agile teams 🚀 Garrick's Story: From Early Coding to XP Champion Garrick started coding at 10 years old (at day camps in the 80s! 😅), earned a Computer Science degree, and had his development worldview shaped by reading the first edition of Extreme Programming Explained. He has worked at XP-centric organizations, trained teams in TDD (Test-Driven Development), Ensemble Programming, and CI/CD (Continuous Integration/Continuous Deployment), and even revamped a college curriculum from Waterfall to XP/Scrum. 🎯 "Building" Agile Software Developers 🐞 Debugging: The Missing Developer Superpower Ever heard of The Debugging Book? Most developers haven’t—but it’s a game-changer. We explore: 🔄 Reviving XP & Software Crafting After the Scrum Backlash 💡 Don’t miss this high-energy, insight-packed conversation with Garrick West! 📢 Comment below: What’s YOUR experience with XP, Agile, or debugging challenges?

🚀 How do Game Jams accelerate learning? Can mobbing make game development more effective? In this episode of the Mob Mentality Show, we dive deep into Game Jams, Mobbing, and Game Dev Collaboration with James Herr—a full-stack developer, game dev enthusiast, and published game creator on Steam. 🎮 What You'll Learn in This Episode: 🔹 What Are Game Jams and why they’re a must-try for devs? 🔹 The tech stacks and tools commonly used in Game Jams 🔹 How themes shape a Game Jam’s creativity and constraints 🔹 How James is bringing mobbing into Game Jams 🔹 The difference between solo development, swarming, and full mobbing? 🔹 Pros & Cons of Mobbing Game Jams—Does it boost creativity or slow things down? 🔹 How Discord & Twitch fuel real-time game dev collaboration 🔹 Can Twitch chat act as a “navigator” in game development? Does the live audience guide decisions? 🔹 How Game Jams reveal code smells faster and teach refactoring & design patterns 🔹 Why public game dev can be a game-changer for learning speed 🔹 How Game Jams can simulate real-world software challenges and improve teamwork 🔹 Mob timer tools & Git handover techniques for smoother collaboration 🤝 Why This Episode Matters: Mobbing isn’t just for software teams—it’s transforming game development, learning, and onboarding. James shares his firsthand experience mobbing with kids, running Game Jams with cross-discipline teams, and teaching mobbing roles in game dev. Whether you’re a seasoned developer, indie game creator, or just curious about Game Jams, this episode is packed with actionable insights! 📢 Want to Join the Game Dev Community? James discusses how Discord and Twitch connect developers worldwide, making it easy to collaborate, get feedback, and learn from others. Checkout James' communities here: https://jamcraft.io/ 🎧 Subscribe & Listen Now! Don’t miss out! Subscribe to the Mob Mentality Show and get notified when this episode drops: 🔗 https://www.mobmentalityshow.com/ FYI: Video and show notes to be posted here in the next day or so.

🚀 Why is there so much confusion around Test-Driven Development (TDD) and Automated Testing? Why do many developers struggle with testing, and what are they getting wrong? In this episode of the Mob Mentality Show, we sit down with Jason Swett—author, speaker, and a go-to expert on Rails testing—to unpack the most common misconceptions, challenges, and best practices in modern software testing. 🔍 Topics We Cover: ✅ Why Jason Swett is passionate about Automated Testing and why he wants to help the development community ✅ Misconceptions about TDD (Test-Driven Development)—not liking TDD itself vs. not liking something called "TDD" ✅ The reality of software testing—why most developers aren't doing it well and how to improve ✅ Testing vs. verification vs. specification—what is a test really? What is code? ✅ Red, Green, Refactor vs. Specify, Encode, Fulfill—what do these different ways of thinking about TDD highlight? ✅ Why software changeability matters and how to reduce the cost of ownership ✅ What are you actually testing? The difference between testing the product (e.g., squirt gun) vs. testing the system that builds it ✅ The role of automation in development—is code like factory machinery? ✅ How testing connects to broader software and team dynamics—beyond just writing tests ✅ Common pitfalls in testing and how to ensure your tests actually add value ✅ Logical debates vs. ego-driven arguments—how to have productive discussions about TDD 💡 Key Takeaways: 🔹 TDD is often misunderstood—before rejecting it, understand what it really is 🔹 Many developers struggle with writing the right kind of tests—knowing what to test is critical 🔹 Automated tests don’t just verify code; they help manage change and reduce long-term costs 🔹 Good testing and TDD are about more than just code—they’re about communication, clarity, and better software development 📌 Who should watch/listen? If you’re a developer, tester, software engineer, or tech lead who wants to improve your testing skills, understand TDD better, and learn from a Rails testing expert, this episode is for you! 🎧 Subscribe & Listen: Don’t miss an episode! Subscribe to the Mob Mentality Show on your favorite platform: 👉 https://www.mobmentalityshow.com/ 🔥 Join the Conversation! Have thoughts on TDD and Automated Testing? Share them in the comments! FYI: Video and show notes to be posted here in the next day or so.

How often should Agile teams reflect and adjust? Is your team on a road with switchbacks but they are not turning the wheel? In this episode of The Mob Mentality Show, we take a deep dive into Agile Principle #12, which states: "At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly." From a Mob Programming perspective, we explore what "tuning and adjusting" really looks like in high-uncertainty, high-interdependence work. Is it like steering a car, constantly making small adjustments, or is it something that requires far less steering? How do different Agile approaches—Waterfall, 2 Week Scrum, and Mob Programming—each handle batch size and feedback loops with continuous improvement? In This Episode, We Discuss: ✅ Agile Principle #12—How it drives continuous improvement in teams ✅ "Regular Intervals"—Comparing Waterfall, 2-week Scrum sprints, and healthy mobbing ✅ Batch Size & Effectiveness—How small adjustments impact team agility ✅ Single vs. Double Loop Learning—Which leads to deeper team growth? ✅ Diversity & Focus—Does learning together accelerate improvement more than learning separately? ✅ The Cynefin Model—Navigating uncertainty and complexity in Agile work ✅ Liminal Thinking—How belief structures and assumptions impact team reflection Many teams go through the motions of retrospectives, but are they truly adjusting their behavior effectively? Join us for this insightful discussion where we challenge assumptions, explore deeper learning, and uncover the best ways to reflect, adapt, and improve as a team. 🎧 Subscribe & Listen: Don't miss this episode! Subscribe on your favorite platform here: 🔗 https://www.mobmentalityshow.com/ 📩 Connect with Us Let us know your thoughts in the comments! How does your team reflect and adjust? FYI: Video and show notes to be posted here in the next day or so.

How do you balance small, iterative progress with the vast unknowns of research and development (R&D)? Can test-driven development (TDD) literally or "in spirit" still provide value when you're navigating uncharted territory? In this episode of the Mob Mentality Show, we dive deep into the intersection of R&D Mobbing and software development, exploring real-world scenarios, strategies, and challenges teams face when innovating under uncertainty. What You’ll Learn in This Episode: 🔬 Chris's Journey with Mob Randori & R&D: From "we don’t know what we’re doing" to "we know what we’re doing"—how mob programming helped transform uncertainty into effective delivery. 🛠️ R&D vs. CD? Can teams practice continuous delivery (CD) even when tackling complex, unknown problem spaces? If so, is there a change in what is "delivered"? 📌 Keeping Small Steps & Feedback Loops in R&D: TDD is known for its rapid feedback and endorphin kicks—but how do you retain those benefits when exploring an unfamiliar landscape? 🔄 Adjusting Your Mobbing for the Task at Hand: When should you modify your mob programming approach to fit the nature of research-driven work versus production-level development? 🧗‍♂️ Clean Code Spelunking & Navigating the Unknown: Techniques for digging deep into existing codebases while ensuring safety and maintaining forward momentum. 🚩 Feature Flags & Safety in R&D: How to experiment with new ideas and do Trunk Based Development (TBD) without introducing instability to production. 📊 Transparency, Visualization & Business Buy-in: Addressing stakeholder fear of an "infinite problem space." 🧠 The Inverse of ZOMBIES in R&D Mode: How do you maintain focus, momentum, and value delivery when dealing with high levels of uncertainty? ⚡ Real-Life R&D Success Stories & Lessons Learned: Practical examples of mob programming driving R&D innovation in high-unknown environments. If you’ve ever wondered how to keep experimentation structured, learning fast, and delivery continuous—even when dealing with complex unknowns—this episode is for you! 📌 Watch More Episodes & Subscribe on Your Favorite Platform: https://www.mobmentalityshow.com/ 🔔 Don’t miss future episodes—hit the subscribe button! Video and Show Notes: https://youtu.be/nipbhFopqMM

Is the ultimate Domain-Driven Design (DDD) dream having a domain expert fully embedded in a Mob? Or does it come with hidden trade-offs? In this thought-provoking episode of the Mob Mentality Show, we explore the benefits, challenges, and real-world experiences of having a domain expert (or product owner) participate full-time in a Mob—not just as a consultant but as an active driver and navigator. 🔹 What We Discuss in This Episode: ✅ Quick Access vs. Full-Time Participation – Is it better to have a domain expert available when needed or fully immersed in the Mob? ✅ Real-World Stories – Chris shares insights from four product owners with different availability levels and how that impacted effectiveness. Austin reveals what happened when a domain expert became a full-time Mobber. ✅ The Pros of a Full-Time Domain Expert in a Mob – Faster decisions, deeper collaboration, improved knowledge transfer, and more! ✅ Natural Synergy with DDD – How DDD experts seamlessly jump into code naming, improving model alignment. ✅ Testers & Domain Experts: A Similar Integration? – The parallels between merging testers into a Mob and embedding domain experts. ✅ Potential Downsides – Does being in the Mob full-time reduce a domain expert’s ability to stay ahead in their field? ✅ Autonomy & Learning Diversity – How does this setup impact team growth and decision-making? ✅ Is This the DDD Dream? – With fewer moving parts (like event storming), does a domain expert in the Mob make DDD even more effective? ✅ The Power of Different Perspectives – Why having a built-in devil’s advocate can enhance team decision-making. ✅ The Truth About Cryptic Code – Can a domain expert help clarify unclear code in real time? 🎧 Don’t Miss This Insightful Discussion! Hit Subscribe and turn on notifications so you don’t miss future episodes! Find us on your favorite platform here 👉 https://www.mobmentalityshow.com/ What do you think? Would you want a domain expert full-time in your Mob? Drop a comment below! ⬇️ FYI: Video and show notes to be posted here in the next day or so.

Can a combo of Large Language Models (LLMs) and Domain-Specific Languages (DSLs) streamline development by automating repetitive patterns across teams? In this Mob Mentality Show episode, we dive deep into the intersection of AI-driven automation, code generation, and lean software development. Join us as we explore: ✅ The "Generator for the Generator" Concept – How AI-powered tools and Mob Programming can create DSLs that automate code generation at scale. ✅ Handling Cross-Domain Development with DSLs – How DSL arguments can be leveraged to generate applications across multiple domains while maintaining usability. ✅ Serverless Infrastructure as Code (IaC) & Auto-Generated Apps – How to use DSLs to automate cloud deployment with Angular or Streamlit apps. ✅ The Challenge of UI/UX in Generated Code – When UI is too generic, does it hurt usability? Can a DSL strike the right balance between automation and user experience? ✅ Regeneration vs. Continuous Development – Should teams work exclusively in the DSL, or also refine the code it generates? How to handle sync issues when regenerating applications. ✅ Turning Docs into Code with a DSL Converter – Automating workflows by transforming team documentation into executable code. ✅ Mob Automationist Role Inception – Is the next evolution of Mob Programming automating the automation? ✅ ZOMBIE Test Generation & Nested Python Dictionaries – How automated testing fits into the DSL-driven workflow and whether a DSL can be as simple as a structured Python dictionary. 🎯 Whether you’re a software engineer, an agile practitioner, or just fascinated by AI-driven development, this episode is packed with real-world insights into DSLs, LLMs, and the future of lean automation. 🔔 Don't miss out! Subscribe to the Mob Mentality Show on your favorite platform: 👉 https://www.mobmentalityshow.com/ FYI: Video and show notes to be posted here in the next day or so.

Explore the exciting intersection of human collaboration and artificial intelligence (AI) in software development with this insightful episode of the Mob Mentality Show. Recorded for the 2024 UACon Winter: The Future of Product Development Summit on December 10, 2024, Aaron Griffith and Parker Barrett joins Austin to dive deep into how Mob Programming and AI are reshaping the way we build and test software. This episode is packed with practical insights, real-world examples, and actionable strategies for leveraging AI with a mob programming style. Whether you’re an AI enthusiast, a software developer, or just curious about the future of collaboration, this session has something for you. What You'll Learn in This Episode: 🔹 What is Mob Programming? 🔹 The Origin Story of Mobbing with AI – Discover how our human teams began mobbing with AI tools like ChatGPT and GitHub Copilot to enhance software development processes. 🔹 AI-Driven Test Development in a Mob – See how AI can streamline test-driven development (TDD) workflows, making testing faster and more effective. 🔹 Testing with AI to Find ZOMBIES Test Cases (Zero, One, Many, Boundaries, Interface, Exceptional, Simplicity) – Learn how AI tools help identify missing test scenarios and code improvements. 🔹 AI Limitations and Warnings – Understand the ethical, technical, and operational challenges when incorporating AI into your workflows. 🔹 AI Mobbing Demo Highlights: Why This Episode Matters: As AI tools continue to evolve, understanding how they integrate with collaborative programming methods like Mob Programming and Extreme Programming (XP) is critical for staying innovative in the fast-paced world of software development. In this session, we not only discuss the benefits of AI but also provide a realistic view of its limitations and how to navigate them. Perfect For: Let’s shape the future of collaboration and development together! FYI: Video and show notes to be posted here in the next day or so.

In this thought-provoking episode of the Mob Mentality Show, we dive into the world of extreme ownership within a multi-mobbing environment. What happens when a mob/team wants to make a decision, like extracting a method, refactoring to a new pattern, or reorganizing code boundaries? Should that decision wait for approval from outside teams? Or does extreme ownership mean trusting the mob to act autonomously for maximum flow efficiency? Topics Discussed: Scenarios and Examples: Key Questions Discussed: Subscribe and Stay Connected: Don’t miss this insightful episode as we unravel these questions and more! Discover how the principles of extreme ownership and mob programming can transform team dynamics and decision-making processes in software development. 📢 Subscribe to the Mob Mentality Show on your favorite platform: https://www.mobmentalityshow.com. 🔔 Like, comment, and share to join the discussion and stay updated on upcoming episodes! FYI: Video and show notes to be posted here in the next day or so.