The Mob Mentality Show

🎙️ 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. Video and Show Notes: https://youtu.be/MjwIkiM25xM 

🎙️ 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/ Video and Show Notes: https://youtu.be/bFMD0AsVDUA  

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/ Video and Show Notes: https://youtu.be/4PZN1yO8l2c  

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 leave 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! Video and Show Notes: https://youtu.be/Rajvp2nrg1A  

Garrick West, a seasoned XP practitioner and Agile coach, shares insights from his rich history in software development, starting with coding at age 10. He discusses effective strategies for building great developers through mentorship and an apprenticeship model. The conversation dives into mastering debugging with key techniques and the significance of communication. Additionally, Garrick emphasizes the revival of Extreme Programming, making it crucial for Agile teams today, while advocating for stronger collaborations between industry experts and academia.

🚀 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/ Video and Show Notes: https://youtu.be/AZEH_FmBBKs 

Join Jason Swett, an author and Rails testing expert, as he dives into the world of automated testing. He sheds light on common misconceptions about Test-Driven Development (TDD) and discusses why many developers struggle with testing. Jason emphasizes the importance of understanding the essence of a test versus mere verification. He also explores how to improve software testing practices and the role of automation in development, sharing insights on transforming testing into a more effective process. Prepare to rethink your testing strategies!

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 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? Video and Show Notes: https://youtu.be/ikmWgj44g28 

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 

Discover whether having a full-time domain expert in a Mob truly embodies the DDD dream. Explore the trade-offs of quick access versus full immersion and hear real-world stories of product owners that illustrate the impact on team effectiveness. Delve into the advantages of faster decisions and deeper collaboration paired with potential downsides, such as staying current in their field. The discussion also highlights the synergy of domain expertise with agile mob programming and the critical role effective naming plays in enhancing software development clarity.