Folgen
-
šļø 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
-
Fehlende Folgen?
-
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
-
š„ 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 ChampionGarrick 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
The power of an XP coach early in a developerās journeyPublic speaking as a dev skill? (Toastmasters, teaching at community college)What happened when Garrick helped convert a college curriculum from Waterfall to XP/Scrum?Industry experts + academia: How can professional devs and educators collaborate better?The apprentice model: What it means and why learning stages (like the Dreyfus Model) matterAI & developer education: Does AI replace early learning stages, or is it just a slick salesman?Scaling Gilded Rose Kata to different skill levelsTest Coverage as a red herringāwhat should we focus on instead?š Debugging: The Missing Developer SuperpowerEver heard of The Debugging Book? Most developers havenātābut itās a game-changer. We explore:
Debugging as problem-solving, not just "stepping through" in an IDEThe 9 Debugging Rules: From reading the manual to never throwing away a good test toolHow to gamify debugging in a mob & introduce a "debugging auditor" roleThe anti-pattern of multiple experiments at onceāand how to avoid itWhy debugging is like navigating a labyrinth with a million wrong pathsš Reviving XP & Software Crafting After the Scrum Backlash
XP fills Scrumās missing middle: Building the right thing (Scrum) AND building it right (XP)How Scrum without XP leads to a āBall of Mudā in just 18 monthsWhy XP + Lean is the ultimate combinationBreaking free from sprints & pressure cookersājust focus on continuous iterationsCan XP stand without Scrum? Or does Scrum need XP?š” Donāt miss this high-energy, insight-packed conversation with Garrick West!
š¢ Comment below: Whatās YOUR experience with XP, Agile, or debugging challenges? Video and Show Notes: https://youtu.be/vxLDm-13Ny4
-
š 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
-
š 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!
Video and Show Notes: https://youtu.be/_kL_tXiNcl4
-
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 UsLet 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
-
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! ā¬ļøVideo and Show Notes: https://youtu.be/7__ghFw_Z3g
-
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/Video and Show Notes: https://youtu.be/0q3jaX6_bfw
-
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:
AI-generated Flutter app complete with unit tests.AI-driven identification of ZOMBIES.Automated Continuous Integration/Continuous Deployment (CI/CD) pipelines powered by AI.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:
Developers and teams exploring AI-powered tools.Agile practitioners and extreme programming enthusiasts.Anyone curious about the future of software development collaboration.Letās shape the future of collaboration and development together!
Video and Show Notes: https://youtu.be/BsFPbYX4WXQ
-
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:Autonomy vs. Consensus: Should mobs prioritize quick decision-making or seek input from external teams?Multi-Mob Context: Exploring the dynamics of multiple mobs interacting and how to handle shared ownership of repositories and projects.Inverse Conway Maneuver: Can designing your organizationās team structures to match the architecture you want your systems to have prevent this problem?Lean Thinking and Efficiency: How waiting for approvals from external owners can create lean wastes.Boundary Flexibility: Should code and team boundaries be rigid or adaptable to changing circumstances?The Monolith vs. Microservices Debate: Is the real issue a technical architecture debate or is the root problem found elsewhere?Scenarios and Examples:A hypothetical comparison of shared ownership in MS Word vs. MS Excel.The impact of Joe Justiceās Law on decision-making and team interactions.The challenge of managing too many communication nodes in multi-team environments.Key Questions Discussed:Is it more valuable to reduce the number of teams interacting with a repo?Should boundaries of ownership evolve with time?How can we balance flow efficiency with healthy collaboration across teams?How does "Nothing in Tech Matters Except XP" impact this discussion?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!
Video and Show Notes: https://youtu.be/rAT-EurLnrI
-
In this episode of the Mob Mentality Show, we dive into Sustainable Pace, a core principle of the Agile Manifesto ("Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely"). From software development to youth sports, we explore the massively destructive effects of an unsustainable pace and highlight the transformative benefits of a culture grounded in sustainable practices.
š„ Key Topics Covered1. The Massively Destructive Results of Unsustainable Pace
How the relentless work rate leads to burnout, dropouts, injuries, and errors.Insights from academic and medical studies showing the devastating effects of unsustainable workloads.Real-world connections to coding bug rates, over-specialization, and emotional exhaustion.Tim Urban's TED Talk ("Inside the Mind of a Master Procrastinator") and its ties to the procrastination monkey, panic monster, and unsustainable pace.Why misalignment between expectations and reality (e.g., unrealistic deadlines) breeds toxicity.Radical Candor's "obnoxious aggression" and it can join forces with unsustainable pace to form a diabolical duo.2. The Positive Results of a Sustainable Pace
Building high-quality, continuous delivery without chaos or burnout.The connection between psychological safety, inclusivity, and long-term success in both teams and individuals.Benefits of diverse experiences, low stress, and personal peace from a sustainable pace.Practical strategies to avoid contributing to toxic work or play environments.Stories from youth sports coaching and tech leadership that illustrate how sustainable pace leads to lasting excellence.3. Actionable Insights for a Better Future
How to shift from a culture of "run fast, burn out" to one of balance, productivity, and joy.The systemic changes needed to foster sustainable pace in tech teams and youth sports organizations.Why adopting sustainable practices isn't just about survivalāit's about thriving.šļø Why Listen?Whether you're a tech leader, Agile practitioner, parent, or coach, this episode is packed with actionable advice and thought-provoking discussions. Learn how sustainable pace can unlock continuous learning, higher quality results, and a more fulfilling life.
ā Subscribe to Stay UpdatedDon't miss other enlightening discussions! Subscribe to the Mob Mentality Show on your favorite podcast platform or YouTube channel: https://www.mobmentalityshow.com
š¢ Join the ConversationWhatās your experience with unsustainable pace? How have you built or experienced sustainable practices in your work, team, or community? Drop your thoughts in the comments below and letās talk!Video and Show Notes: https://youtu.be/bTvjoGosBnw
-
In this exciting episode of the Mob Mentality Show, we sit down with Martin Christensen, a product transformation coach, to explore the pivotal power of mobbing in product discovery.
What You'll Learn in This Episode:Mobbing Product DiscoveryWhat is Product Discovery? Understand the fundamentals user value, business value, and technical feasibility.Mob Style vs. Solo User Interviews: Learn how mobbing on user interviews enhances insights through diverse perspectives and how it contrasts with traditional solo interviews.The Benefits of Diversity: Discover why the mantra āMob Anythingā unlocks innovation, faster UI/UX iterations, and fewer lines of code while maintaining focus on user experience.Collaboration, Psychological Growth, and TransformationBarriers to New Methods: Dive into the psychological and organizational obstacles that can hinder teams from adopting mobbing or trying new approaches.Adult Development and Teaming: Martin shares insights on how stages of psychological development and life events can break down egocentrism and foster stronger collaboration.The "No Pain, No Gain" Paradox: Can growth happen without trauma? Discover the nuanced relationship between challenges, growth, and maturity in collaborative environments.Impact of Complexity on Happiness: Unpack how the complexity of problems and overall team happiness affect the ability to work effectively as a mob.Why Watch This Episode?If youāre passionate about product development, user experience, or team collaboration, this episode is packed with actionable insights and relatable stories. From understanding the power of mobbing in product discovery to overcoming barriers to psychological maturity in teams, this conversation will leave you inspired to experiment and grow.
šļø Donāt miss out!Subscribe to the Mob Mentality Show today to catch this episode and explore other topics at the intersection of innovation, collaboration, and personal growth.
š Watch here or on your favorite platform: https://www.mobmentalityshow.com/Video and show notes: https://youtu.be/IPYXElnuBns
-
Have you ever wondered who else is adopting mob programming? Or perhaps youāre curious about the diversity of organizations that practice ensemble programming? In this Mob Mentality Show episode, we take a deep dive into the Companies That Mob/Ensemble Program Board, a powerful tool for tracking and sharing insights about organizations, coaches, and educators engaging in mobbing practices worldwide.
Join us as we explore the story behind this invaluable resource and its broader implications for the mob programming community.
What Youāll Learn in This Episode:Why Track Mobbing? Discover why Chris Lucian started documenting companies and organizations that practice mob programming, beginning with a simple blog post.From Blog to Trello: Learn how this tracking effort evolved from a personal blog to a comprehensive Trello Board, making it easier to manage and share.Uses of the Board: Explore the boardās practical applications, including showcasing the diversity of mobbing practices across countries, industries, and contexts like IoT (Internet of Things), eCommerce, hardware, firmware, software, government, and private sectors.Related Resources: Uncover the connections between this board and other similar initiatives, such as the Software Professional Resources Board and the "We Do TDD (Test-Driven Development)" website.Anecdotal ROI: Hear how this board can serve as anecdotal evidence of the return on investment (ROI) for mob programming from a "just sharing" perspective ( https://justsharing.dev/ ), helping promote its adoption in the software development community.New Categories: Find out about Austinās updates, which include categories for coaches and professors who practice mobbing.Call to Action: Get inspired to contribute by adding new companies, organizations, or individuals to the board to help grow the global mobbing network.Why This Matters:The Companies That Mob/Ensemble Program Board isnāt just a listāitās a living resource that reflects the growing diversity and diffusion of mobbing practices worldwide. Itās a tool for saving time, building community, and promoting the Just Sharing mindset. Whether youāre a seasoned practitioner or a newcomer to mobbing, this board helps you connect with others and find inspiration for your own mob programming journey.
Get Involved:Want to see the board in action? Check it out here: Companies That Mob/Ensemble Program Board.
Subscribe for More Episodes:Donāt miss out on future episodes of the Mob Mentality Show! Subscribe on your favorite platform today: Mob Mentality Show Website.Tune in and discover who else is mobbingāand why itās transforming the way we work and learn!Video and Show Notes: https://youtu.be/yCB4n-0nxQk
-
Have you ever wondered why Extreme Programming (XP) isnāt commonly taught in schools? In this engaging episode of the Mob Mentality Show, we dive into this intriguing question brought to us by the mob programming community.
š What We Cover:1ļøā£ A Junior Developer's Dilemma: If schools donāt teach XP, does it mean itās not critical for your career?2ļøā£ Academiaās Pushback: What are professors saying about XP and unit testing? Is XP seen as incompatible with academic goals?3ļøā£ Systems Thinking in Action: Unpacking how a systems-thinking approach (holistic problem-solving) provides clarity on this issue.4ļøā£ The Runner Analogy: How comparing sprinters and cross-country runners sheds light on coding strategies.5ļøā£ Universities vs. Industry Needs: Are schools preparing students for industry or academic research? What should their goals be?6ļøā£ Degree Confusion: Why students struggle to navigate differences between computer science and software engineering programs.7ļøā£ Niche or Necessity? Why XP, a small sector of the software industry, may not get the spotlight it deserves in schools.8ļøā£ Unit Testing's Lone Survival: Is unit testing finding its way into classrooms, but XP is not?9ļøā£ The āUnknown Unknownsā Problem: What happens when students donāt even realize the value XP could bring to their careers.š Solutions That Work: Experiments and strategies weāve used to promote XP in university curricula.
š” Why This Episode Matters:
Maintainability in Code: Discover why maintainability is crucialānot just in industry, but even for academic projects.Handling Resistance: Learn how educators can introduce XP despite opposition from traditional academic mindsets.Spotlighting Success: Shout-outs to universities doing XP right and what others can learn from them.Academia-Industry Collaboration: Insights from years spent on professional committees advocating for XP.š Who Should Watch This Episode?
Students: Discover why your curriculum may overlook XP and how to build the skills yourself.Educators: Get inspired to bring XP into your classrooms and navigate institutional challenges.Industry Professionals: Understand the gap between academia and industry, and what it means for hiring new grads.Join us as we explore the challenges and opportunities of integrating XP into education. With actionable insights, engaging analogies, and practical advice, this episode is packed with ideas to spark change.Video and Show Notes: https://youtu.be/CidbB_SBGl0
-
In this thought-provoking episode of the Mob Mentality Show, we are joined by Ariel PĆ©rez to explore the fascinating intersection of Complex Adaptive Organizations, Organizational Topologies, and the FAST Agile Framework. Together, we dive into the challenges and opportunities of modern software development and organizational dynamics, offering actionable insights for leaders, teams, and anyone navigating complexity in their work.
Highlights from the Episode...Complex Adaptive Organizations and FAST Agile:Manufacturing vs. Software Development: Why building the same product repeatedly differs from creating custom software .Complexity Theory in Software Development: How unpredictable side effects shape outcomes and the pursuit of predictability in organizations.Fixed Scope and Fixed Date: Are they real business needs, or just external motivators? What are their long-term impacts on quality and delivery?Theory X vs. Theory Y (management theories): How a leaders' management principles and practices influence autonomy, trust, and collaboration.Dynamic Teams in FAST Agile: The pros and cons of adapting teams dynamically to match work needs versus forcing work into rigid team structures.Story of Transitioning to FAST: A tale of initial resistance to the FAST Agile approach and the eventual embrace of its benefits.Building a Culture of Experimentation and Learning:Experimentation as a Foundation for Innovation: How to test hypotheses in product development and team practices without compromising quality.From Fear to Trust: Encouraging experimentation in new teams or under new leadership while creating safety for bold ideas.Practical Experiments: Implementing small feature flags, A/B testing (comparing two versions in production), and time-limited trial runs to foster innovation.Respect and Radical Candor: Building trust through open communication, mutual respect, and the occasional dose of healthy banter š .Risks and Controls: A Never-Ending Game of Whack-a-Mole:Balancing Risk and Control: How risk-heavy environments lead to more controls (e.g., CABāChange Advisory Board, PRāPull Request) and the ripple effects of other risks these controls create.Holistic Thinking: Why addressing one risk often introduces others and how to manage risk without stifling agility.Mob Programming as a Solution: Handling emergency changes safely and collaboratively without falling into the trap of excessive gatekeeping.Key Takeaways:Embrace complexity and adapt dynamically to navigate unpredictable challenges.Optimize for learning through experimentation and apply these insights to real-world problems.Avoid control-heavy environments that stifle innovation and agility by thinking holistically about risks.Join us as we unpack these ideas and share strategies to foster a responsive, trust-based culture in your teams and organizations.
š§ Donāt miss this episode! Subscribe to the Mob Mentality Show on your favorite platform: https://www.mobmentalityshow.com/FYI: Video and more show notes: https://youtu.be/ghzOSV4waIo
-
Is some refactored code truly betterāor is it just a matter of taste? In this episode of the Mob Mentality Show, we explore the debate: Is some refactoring a subjective preference or an objective improvement?Join us as we dive into the fascinating world of refactoring, where code quality, team dynamics, and even artificial intelligence (AI) come into play. Hereās what we discussed:
The Ice Cream Debate: The story of a team/mob navigating a series of refactorings and asking, Are these changes about style, like preferring chocolate over vanilla? Or is there an objective improvement in the code?Cognitive Load, Cyclomatic Complexity, and More: How refactored code impacts key factors like cognitive load (mental effort required to understand code), cyclomatic complexity (a measure of the number of independent paths through a program), readability, and maintainability.Copilot AI's Take: Results of analyzing ābefore and afterā versions of refactored code using Copilot AI (a large language model or LLM trained for coding). Does the AI agree with human developers?Gray Areas vs. Black-and-White Decisions: How much of refactoring is clear-cut improvement versus a matter of debate?Coaching Through Disagreements: Strategies to coach a team through potentially heated refactoring disagreements. Should you stick to principles or let the team run experiments in production against the principles?Decision-Making Tactics: How to align on contentious refactoring decisions. Should you flip a coin, follow a guiding principle, or defer to team consensus?Principles and North Stars: Identifying which coding principles matter most to your team and using them as a decision-making anchor.Dealing with Apathy: How to engage team members who are indifferent to coding principles and quality debates.7 Habits of Highly Effective People: Applying Stephen Coveyās timeless principles to facilitate productive refactoring discussions and team collaboration.Diversity of Opinion as a Strength: Embracing different perspectives to make your team or mob/team stronger and more innovative.Radical Candor vs. Safe Experiments: Balancing direct feedback with the freedom to experimentāeven if it means running tests in production.āStop the Lineā Moments: Deciding when a refactoring disagreement is serious enough to halt progress versus letting safe experiments play out.Whether youāre a developer, team lead, or software architect, this episode is packed with insights to improve your approach to refactoring and team dynamics.š Donāt miss this thought-provoking discussion! Video and Show Notes: https://youtu.be/s2bl7dFAIV0
-
What happens when teams, codebases, or systems scale beyond their limits? In this thought-provoking episode of the Mob Mentality Show, we tackle this hyperbole: āIs scaling the root of all evil?ā We explore how the challenges of scaleāin team size, code complexity, and even societal structuresāmight be the culprit.
š” Key Discussion Points:
Defining Scale Across Contexts: How does scale impact teams, classrooms, codebases, and more?Innovation vs. Scale: Does scaling stifle the spread of good ideas, principles, and practices (e.g., in law, culture, or workplace norms)?Interpersonal Challenges: Why do interpersonal problems grow exponentially in larger groups?Code Quality and Scale: Does a larger codebase inherently lead to lower quality?Focus and Attention: How does scale dilute individual and team focus? What happens to attention in scaled systems?Second-Order Effects: Are rigid systems designed to handle scale unintentionally creating harmful side effectsāand even side effects of those side effects?Experimentation and Innovation: How do rigid systems inhibit experimentation, and why does this matter for growth and innovation?Descaling as a Solution: Are the best solutions to scaling problems simply about reducing scale?Inverse Conway Maneuver: Exploring this organizational design concept and its relevance to scaling.Lessons from Coaching: How scaling challenges in youth baseball practices compare to leading software development teams.šÆ Why You Should Watch/ListenThis episode touches on the consequences of uncontrolled growth, from technical issues in software engineering to cultural and organizational challenges. Learn why "descaling" could be the key to improving focus, quality, and innovation in your team or organization. Plus, discover how mobbing (collaborative software development) naturally counters the pitfalls of scaling.
š¢ Donāt miss out! Subscribe now on your favorite platform: https://www.mobmentalityshow.com/
Video and Show Notes: https://youtu.be/YLeyRHcI-eI
-
Join us in this exciting episode of the Mob Mentality Show as we dive deep into the fascinating intersection of mob programming, neuroscience, and team dynamics with the insightful Mike Bowler! Mike brings over a decade of experience facilitating mob programming sessions across hundreds of teams and countless experiments. Whether you're a software developer, team coach, or collaboration enthusiast, this conversation will leave you with actionable insights and inspiring takeaways.š What We Discuss:- A Different Approach to Facilitating Mob Programming Sessions- The Neuroscience of Psychological Safety and Mobbing- Team Flow States and Brainwave Activity- About Mike Bowlerš¢ Donāt Miss Out!Subscribe to the Mob Mentality Show on your favorite platform to learn more about innovative collaboration techniques and team success.
š Find us here: https://www.mobmentalityshow.com
Video and show notes: https://youtu.be/okeAxvRggVc
- Mehr anzeigen
