Podcasts about Mob programming

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.

What if your team didn't need branches at all?

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.

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.

In dieser Episode des Podcasts geht es um die wesentlichen Kompetenzen, die moderne Softwareentwickler benötigen, um erfolgreich in agilen Umgebungen zu arbeiten. Ich spreche über die Bedeutung von Testautomatisierung, DevOps-Kenntnissen, agilem Arbeiten, Pair- und Mob Programming, Kommunikation, kontinuierlichem Lernen und Innovationskompetenz. Diese Fähigkeiten sind entscheidend, um in der heutigen Softwareentwicklung erfolgreich zu sein und agile Transformationen in Unternehmen voranzutreiben. Viel Spaß beim Reinhören

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.

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:

Is Agile still relevant in today’s fast-paced world? Brian and Joshua Kerievsky reveal the four game-changing principles of Modern Agile that prioritize safety, empowerment, and continuous value delivery. Overview In this episode, Brian Milner sits down with Joshua Kerievsky, a pioneer in the Agile community and the creator of Modern Agile. They discuss how Agile practices have evolved, the critical role of safety and empowerment, and how to deliver value continuously in today’s fast-paced world. Don’t miss these insights into creating better teams, products, and results through simplicity and experimentation. References and resources mentioned in the show: Joshua Kerievsky Industrial Logic Joy of Agility by Joshua Kerievsky Modern Agile #33 Mob Programming with Woody Zuill #51: The Secrets of Team Safety with Julie Chickering Badass: Making Users Awesome by Kathy Sierra The Power of Habit by Charles Duhigg The Lean Startup by Eric Ries Experimentation Matter: Unlocking the Potential of New Technologies for Innovation by Stefan H. Thomke Agile For Leaders Mike Cohn’s Better User Stories Course Accurate Agile Planning Course Join the Agile Mentors Community Subscribe to the Agile Mentors Podcast Want to get involved? This show is designed for you, and we’d love your input. Enjoyed what you heard today? Please leave a rating and a review. It really helps, and we read every single one. Got an Agile subject you’d like us to discuss or a question that needs an answer? Share your thoughts with us at podcast@mountaingoatsoftware.com This episode’s presenters are: Brian Milner is SVP of coaching and training at Mountain Goat Software. He's passionate about making a difference in people's day-to-day work, influenced by his own experience of transitioning to Scrum and seeing improvements in work/life balance, honesty, respect, and the quality of work. Joshua Kerievsky is the founder and CEO of Industrial Logic and author of Joy of Agility. An early pioneer of Extreme Programming, Lean Software Development, and Lean Startup, Joshua is passionate about helping people achieve genuine agility through principle-based approaches like Modern Agile. Auto-generated Transcript: Brian (00:00) Welcome in Agile Mentors. We're back. And this is another episode of the Agile Mentors podcast. I'm here as I always am. I am Brian Milner and today I am joined by Joshua Kerievsky and really excited to have Joshua here with us. Welcome in Joshua. Joshua Kerievsky (00:16) Thank you so much, Brian. Happy to be here. Brian (00:19) Very excited for Joshua to be here. Joshua's been around for a while. He's been doing this for a long time. He said, you know, when we were talking before, and he's been involved with Agile before, it was called Agile. And, you know, that probably tells you all you need to know there. But a couple other things here about him, just so that you kind of can place him a little bit. His company is Industrial Logic, Inc. and he's the CEO and founder of that company. He has a book called Joy of Agility that's out there that I highly recommend. It's a really great book. And he's also closely associated with something that maybe you've been aware of, maybe you've heard of, maybe you haven't, but something called Modern Agile. And that's what I thought we'd focus on here for our discussion is really to try to understand a little bit about it. especially for those of you, maybe you haven't heard of it, haven't been around it before. So... Why don't we start there, Joshua? Tell us a little bit about what was the need that was trying to be filled with something like modern Agile. Joshua Kerievsky (01:19) Well, it goes back to a conference I attended in Prague back in around 2015. And I was giving a speech, a keynote speech there, and that ended. And then I went and said, well, I'm going to go join the OpenSpace. And I was just looking at what people were talking about at the OpenSpace. And at that point in time, I had already been experimenting with a ton of stuff that just kind of different from what we had been doing 10 years earlier or even later than that. I mean, just this was new things that we were doing, whether it was continuous deployment or ideas from lean startup or ideas from the pop and dykes and lean concepts applied to agility or just a lot of things that were just different. And none of the sessions I was seeing in the open space seemed to be talking about any of that stuff, like giving up story points or moving away from sprints until continuous flow. just nothing was being talked about. So I just said, well, I'm going to host a session, and I'll call it, I don't know, a modern Agile. And so that's as far as I got in terms of thinking about the name. I just wanted to run a session where we could talk about, there's a lot of new things we're doing that kind of display some of the older ideas. And they're very useful, I found. So the session ended up getting a lot of attention. 60, 70 people showed up there. So we had a big group. And it was well received. People were fascinated by the stuff that they weren't aware of. And so I then repeated this open space event in Berkeley. Like a month later, was Agile Open Door Cal in Berkeley was running and did it again. And again, there was tremendous interest. in this, so much so that I decided to write a blog and wrote the blog and started getting more conversations happening. And that sort of began the movement of describing this thing called Modern Agile. And it took a few twists and turns in the beginning, but it wasn't sort of, I guess, if anything, I felt like Agile needed to be a little more simple. in terms of what we were explaining, because it was starting to get very complex with frameworks, enterprise frameworks coming along like safe and just too many moving parts. And so what ended up happening is I wrote some things and people started to notice, there's kind of like four things there that are really valuable. One of them was The names changed a little bit over time. But anyway, what ended up was four principles emerged. And that really became modern Agile. Brian (03:58) That's awesome. just for listeners here, I've pitched attending conferences in the past. If you've listened to this podcast, you've heard me say that, and I'll create things come out of that. And here's an example, right? This is something that was open space discussion. Open space, if you're not familiar with that, at conferences, can, if there's an open space day or a couple of days, then anyone can present any topic they want. And whoever shows up is who shows up. And this one got a lot of attention. And a movement grew from this open space topic, which is awesome. So let's talk. You mentioned there's four principles here. And I like the distinction here we're making also between the frameworks and the practices versus the cultural aspects or the philosophy behind it. And returning to those roots a little bit more from what Agile originally was. So you mentioned there's kind of four areas of this. Let's walk our way through those. I know the first one, or one of the first ones here is make people awesome. So help us understand, what do you mean by make people awesome? Joshua Kerievsky (04:59) Probably the most controversial of principles, because you'll get people coming along saying, wait a minute, people are already awesome. What are you talking about? And it comes from my, I'm a big fan of Kathy Sierra. And her blog was incredible. And her book, she wrote a book called Badass, Making Users Awesome. And in her book, she was really wonderfully clear about Brian (05:07) You Joshua Kerievsky (05:24) that teams that build products ought to focus on the user of the products more than the product itself. In other words, she would say, don't try to create the world's best camera. Try to create the world's best photographers. Big subtle difference there. Like that is focusing so much on empowering the users, making them awesome at their work or whatever they're doing, whether it's art or accounting or whatever, whatever your product does, how can you give them something that elevates their skills, that gets them to a point of awesomeness faster? And that's what she was talking about. So I thought, what a wonderful message. And initially, I used language like make users awesome. you know, having been an entrepreneur myself and created products and sold them and You learn a heck of a lot when you make your own product. And we've made several products over the years at Industrial Logic, probably the most successful of which was our e-learning software. And that has taught me so many, so many lessons. One of them is you have to serve an ecosystem of people. You can't just make your main user awesome. What about the person who's buying the software? How do you make them awesome in terms of helping them buy something that's going to get used? If they buy your e-learning and they never use it, they've wasted a lot of money. So we've got to make sure that their reputation is intact because they made an excellent investment and it got used and it got into valuable, it created value in the company. So how do I make the buyer awesome? How do I make the person that like rolls out the licenses to people awesome? How do I make their experience awesome? How do I make my colleagues awesome so that we love what we're doing and really enjoy working together? So it kind of morphed from make users awesome to make people awesome. And it's so expanded. If anything, we set the bar higher. And all of the principles of modern agile are like unachievable. They're all kind of high bars, right? But they're the goal that we go towards. So that really is it. It's about creating Brian (07:23) Ha Joshua Kerievsky (07:35) you know, wonderful, you know, the in Great Britain, they use awesome kind of sarcastically sometimes, right? They'll say, well, that's awesome. You know, and so for them, it would be brilliant. You know, I thought of making an English version. We have many translations of modern agile, and I thought of making an English version, which would be a proper British English version, make people brilliant. But it's meant to be to empower folks to give them something. And it's so it is. Brian (07:43) Ha You Joshua Kerievsky (08:04) It does have a product focus in the sense of we're typically building a system or a product that someone's going to use and it's going to give them skills they didn't have before or abilities they didn't have before that are going to be very valuable. Brian (08:18) Yeah, I love that. And there's a sort of a servant nature to that servant leaders, not servant leadership as much, but servant nature of I'm serving these people and how do I, how do I serve them in a way that really empowers them? Kind of reminds me of like, you know, the, the great principle with, with dev ops of just, know, if I can, if I can empower the developers to be able to do these things on their own. And so they don't need someone else to come and check the box and do everything for them. You're making them awesome. You're empowering them to be more than they were otherwise. Joshua Kerievsky (08:54) Yes, yes, absolutely. I I think we've seen a history in the software field of a lot of tools coming along and helping. It's not just tools, it's also methods as well. I mean, I'm entirely grateful to the Agile software development movement because it helped nudge everything towards a far better way of working and to make us more awesome at our craft. yeah, you have to have a North Star though. If you're going to build something, You have to know, what are we going for here? What are we shooting for? And with Cathy's influence, again, it's not so much make the greatest product in the world. It's, that focus on the users, the people who are going to be using the work, using the product. Brian (09:34) That's really good. Let's talk about the second one then on my list here, the make safety a prerequisite. What was the point here behind this principle? Joshua Kerievsky (09:40) Yes. So starting probably around 2011 or so, I could not stand going to the Agile Conference anymore. It had just become too commercial and too filled with just people hocking stuff. And it just was bothering me too much. I couldn't go. So I ended up going to South by Southwest, which is an Brian (09:54) You Joshua Kerievsky (10:09) Enormous conference tens of thousands of people show up So it'd be 20,000 30,000 40,000 people showing up for these for this event, which is musical film technology just it's just wild and I came across this book by Charles Duhigg called the power of habit. He was there that year and In that book. Well, first of all that particular year was 2012 that I went my first year there it poured The rain, it was every day, it was unusual for that time, but it was just like pouring rain. So what could you do? I bought some books and I was sitting there in my room reading them. And I'm reading this book, The Power of Habit, and I come across this chapter called The Ballad of Paul O'Neill. Now who the heck's Paul O'Neill? Well, it turns out Paul O'Neill is this incredible guy, a complete business maverick. He ended up becoming the treasury secretary under Bush and not. in 2000 for a short period of time, but that's another story. And he ran Alcoa for about 13 or 14 years. And so the Ballot of Paul O'Neill is very much about what he did at Alcoa to turn the company around. And in essence, you could say he made safety a prerequisite. That safety was his guiding light in turning that company around, which meant left people empowered to do all kinds of things. So it went way beyond safety, but started there. And it's an incredible story. I've written about it in Joy of Agility. I got so into Paul O'Neill that I ended up interviewing his main lieutenant. And then I got a chance to interview him a couple of times. the man's a genius. He passed away a few years back. Absolute genius. this concept of safety started to really pull at me in the sense that I felt, first of all, extreme programming, and I'm a big practitioner of extreme programming, brings a tremendous amount of safety to software development. It may not be as explicit in saying safety, safety, safety. When you look at extreme programming, doesn't really talk about safety, but it's implicit. And these days, Kent Beck's much more vocal about, you One of his missions is to make software development safer for geeks. But safety to me is almost like I found my home. Like safety was something that, what I learned through Paul O'Neill was that it's a doorway to excellence. And he transformed a hundred year old company with safety. I would complain about companies we were working with that were 25 years old and had an embedded culture. Like, how are we gonna change this company? But safety started to be this thing that I hadn't really thought enough about, and making it explicit opened up a lot of doors, right? And I became very interested in the work of Amy Edmondson, who's extremely famous today, but back then she was not so famous. And huge fan of hers. I, you know, I can email her and she'll email me back and she wrote a nice thing about my book. So. She has done some incredible work there. And so when we talk about safety in modern agile, it's psychological safety. It's financial safety. It's any of the safeties. There are many safeties that we could talk about. And it looks at all of them, right? It's brand safety, software safety in terms of security. you know, of the software and on and on and on. So make safety prerequisite is vast and big in terms of what we're trying to do there. Making it a prerequisite means it's not an afterthought and it's not a priority that shifts with the winds. It is permanent. It is something that we know we have to have in place. And it's very, very hard to achieve. Just like make people awesome is hard to achieve. Boy, is make safety a prerequisite difficult. Brian (13:43) Hmm. Yeah, I love Amy Edmondson's work as well. I'm just kind of curious. does the safety kind of inclusive of things like quality as well? Do you intend that to be part of what you mean by safety? Joshua Kerievsky (14:11) Well, mean, to the extent that it makes it safer to do good software development. So if bugs are happening all the time, you can't make people awesome, typically if you don't have quality. If you have really poor quality, nobody's being made awesome. They're experiencing all kinds of problems with your product. So make people awesome and make safety a prerequisite are very much tied together. That is, there is no real excellence without safety. You could think you're having an excellent experience, so that all of a sudden there's a major problem, and boy, are you unhappy. So they really go hand in hand. You could have the most incredible restaurant, and then one day you've got food poisoning happening. Great, no one's come to your restaurant. So you will not make anyone awesome if you don't make safety a prerequisite, and quality is part of that. Brian (14:57) Awesome. Well, let's move on to the next one then, because the next category is one that just resonates with me a lot. Experiment and learn rapidly. What was kind of the thought behind this one? Joshua Kerievsky (15:06) Yeah, and this is one where it that's shorthand, if you will, because you can only fit so many words on a wheel there. But it's important to know that that really means experiment rapidly and learn rapidly. And that comes a lot out of it in the influences of something like Lean Startup. I'm a huge fan of that book and of Eric's work, Eric Reese's work. Brian (15:13) Ha Joshua Kerievsky (15:29) And the fact that we can experiment rapidly and learn rapidly rather than just building everything and then learning slowly. Right? How can we do cheap experiments quickly to decide what's important to work on and what isn't? Let's not build stuff nobody wants. Let's find more time with our customers and understand their needs better so we can build the right things that make them awesome. In other words, and a lot of these are interconnected. In many respects, modern Agile is a Venn diagram. ideally want all four principles to be overlapping. And right there in that middle is where you really want to be. Not easy. But experimenting, learning rapidly, yeah. So challenge yourself to find ways to do quick, cheap, useful experiments. You can do lot of unuseful experiments. Amazon experienced that. There's a story in my book about how Amazon had to start just shepherding the experiments a little more and having some better criteria. Because you could do an endless array of experiments and not get anywhere. There's a wonderful book called Experimentation Matters by a Harvard business professor. Wonderful book as well. But I love experimentation and learning. And I see it as critical to building great products. So that's that principle there. Brian (16:46) Yeah, there's a real difference, I think, in organizations that put value on that learning process. if you see it as a valuable thing, that we invest time to gain knowledge, then that really can truly make an impact when you go forward. I know I've talked about this in classes sometimes where people will say, isn't it a little bit selfish from the organization to try to always just figure out what's going to sell the best? or what's going to work the best in advance of putting something out. My response is always, well, yes, there is a benefit to the business, but there's a benefit to the customer as well because they would rather you work on things that they care more about. Joshua Kerievsky (17:24) That's right. Yeah. I mean, we once put out an experimental product to a large automotive company. And we were really excited about it. We had a whole list of features we wanted to add to it. But we were like, you know what? Let's just get this primitive version kind of in their hands just to see what happens. it turned out that we learned very rapidly that they couldn't run the software at all. There was some proxy. that was preventing communication with our servers from their environment. So it was like, excellent. We learned really quickly that instead of those fancy new features we want to add to this thing, we're going to fix the proxy problem. And to me, that's the nature of evolutionary design is that we create something, get it out there quickly, and learn from it rapidly and evolve it. So it goes hand in hand with that as well. Brian (18:11) That's awesome. Well, there's one category left then, and that is deliver value continuously. So what was the genesis of that? Thinking about delivering value continuously. Joshua Kerievsky (18:19) So that was heavily influenced by my own journey into continuous delivery and continuous deployment and that whole world. We got into that very early. I was lucky enough to catch a video by Timothy Fritz, who he worked with Eric at IMBU. And he coined the term continuous deployment. And that video is actually no longer on the Brian (18:43) Ha Joshua Kerievsky (18:44) But this was something that I became enamored of was doing continuous deployment. And we started doing it at Industrial Logic with our own e-learning software back in about 2010. And by the time you get to like 2015, it's like, hey folks, there's this thing where you can do a little bit of work and ship it immediately to production in a very safe way, a safe deployment pipeline. It's friggin' awesome. But the principle doesn't just apply to that because this modern agile is not just about software development. It's how can I work in a way that gets value in front of people as fast as possible? So for example, if I'm working on a proposal, great, I'm not going to work for two weeks and then show you something. I'm going to put something together, a skeleton, I'm going to show it to you and say, what do you think? Does this add value? Where would we improve this? Blah, blah, Again, going hand in hand with evolutionary design. continuous delivery of value is something that is a way of working. With artists that I work with, they'll do a quick sketch or two or three sketches of something first before we start settling in on which one do we like the best and how do we want to craft and refine that. So there's a way of working in which you're delivering value much more finely grained and approaching continuously instead of in bigger batches. Brian (20:05) Yeah. I love the connection there between artists as well, because I've got a background in music, and I'm thinking about how when you go to write a song or create a new work like that, you start off with the roughest of demo tapes, and you move from there to increasingly more sophisticated versions of it until you finally have the finished product. But no one thinks that's strange or thinks that's weird in any way. But you're right. Sometimes there's this attitude or kind of I think in some organizations of, we can't let anyone see that until it's absolutely finished, until it's done. Joshua Kerievsky (20:39) Yeah, yeah, and that maybe that's that there's some fear there, you know, because they don't want to be thought of as, you know, being lesser because they put something rough in front of someone. Whereas I view it as a, you know, to me, it's a sign of weakness when you when you only send something polished because you haven't had the courage or the sense of safety to put something rough where we can make better decisions together early on. So. There's a lot of learning, I think, around that. But it's a challenging principle of its own, deliver value continuously. And people would say, well, what does value mean? Value is one of those words where it's unclear, because you could improve the internal design of a software system. Is that value? It probably is. But you've got to be able to quantify it or prove that it's going to help make things more graceful in terms of flowing features out. yeah, quantifying, communicating what the value is. is important. I'm also a big fan of maximizing the amount of work not done, as it says in the manifesto. So how can we do less and deliver more sooner? Our motto in industrial logic now is better software sooner. And a lot of these principles go straight into that. that drives it. Brian (21:38) Yeah. That's really great. Yeah, I love these four principles and I think that they really represent a lot. There's a lot that's baked into each one of these things. And I'm sure as you kind of put this together with the community and started to talk more about it, I'm sure there were some challenges. I'm sure people came up to you and said, well, what about and how about this? Is there anything now looking back on this that you'd say, gosh, we really... really didn't quite cover this or, know, this is maybe I could fudge it and squeeze it in this area, but you know, there's this other thing that I really think would be important to kind of mention here as well. Joshua Kerievsky (22:28) Well, you know, it's funny, because I thought I was going to write a book. I started collecting stories. I love telling stories, and I find stories to be a great way to help educate people. Not the only way, right? But as part of some of the workshops I give, you tell a story. Hopefully it's a story that's sticky, that sticks in the person's brain. And over the years, I collected stories like that, stories of agility. I thought I'd be writing a book about modern agile when I started writing Joy of Agility. Gradually, as I wrote more and more stories, they didn't quite fit into all those four principles. And I think the lesson I learned there was that I was starting to talk about what pure Agile means, the word Agile. What does it really mean to be Agile? Whereas modern Agile is really almost in the context of product development, of building services or products for people. Whereas Agile itself is even more pure. And so the... the book itself got into the difference between quickness and hurrying, which you can relate to this. You could say experiment and learn rapidly. Well, OK, maybe we shouldn't rush it. Don't rush. Be quick, but don't hurry is one of the mantras in Joy of Agility. So adapting, right? Adapting, we talk about adapting all the time. So to be agile, you need to be able to adapt quickly. These four principles in modern agile don't say anything about adapting. Brian (23:46) Ha Joshua Kerievsky (23:48) So that's kind of implied, but it's not there. So it's a different lens on agility. If anything, I'd say the make people awesome principles are not meant to. It created some dislike, I'd say, from some people. It could have been called empower people, potentially, although a lot of people really love make people awesome. I don't know so much what I'd change there. I'd say we have a .org. So it's a modernagile.org is a website. There's a pretty large Slack community, which, know, four or 5,000 people on that. We don't certify anyone in modern agile, so there's no certifications, but it's something that is neutral in the sense that whether you practice Scrum or Kanban or Safe or whatever, these principles can influence you. And, you know, but again, this all came out of like, when I went to that open space conference in Prague, I had no idea I was going to talk about modern agile. You know, it was not like a predetermined thing. It was just like, my God, they're not talking about the modern ways we're doing stuff. So, and I always encourage people to, you know, keep pushing the limits and keep modernizing. I said to my own company the other day, our wonderful ways of working that we've been doing now for years that have evolved, they're probably antiquated as of today. You know, with generative AI, what would we do differently? Let's have a perspective on our own work as it needs to be modernized constantly. So the term modern in modern agile means always be modernizing, always be looking. Okay, I've had people say, well, Josh, some things don't need to be modernized. There's things that are just evergreen. They're classic. I'm like, absolutely. I'm not changing evolutionary design anytime soon. I find it to be quite useful in so many contexts. So yes, there's the evergreen stuff. And then there's the stuff where you can, indeed, discover a better way. The manifesto itself says, we are discovering better ways of working. Great. Keep that going. Keep modernizing and looking for easier, simpler, quick, easy grace. as the dictionary definition of Agile says, how can we work with quick, easy grace? That's always going to be improving, hopefully. Brian (26:12) Love that, yeah. And you're right, I mean, think there's some, to some people I think that there's, I guess at times an attitude of, you this is all new stuff or this is a brand new concept and something they don't really see the connection backwards in time to how these things are all built on other ideas that have been progressive over the years. So the idea of, yeah, this is, you know, we're, we're not saying that certain ideas are bad because now we're trying to modernize them. We're just saying we're trying to apply that same principle forward into kind of the context of today, which I don't see anyone should have a problem with that. Joshua Kerievsky (26:48) That's right. That's right. Well, and if you are experimenting and learning rapidly with your own process, which I highly encourage, chances are the way you work today will be different than it was yesterday. You will be exploring, like we use discovery trees today. We didn't use them before. Years ago, no one knew what a story map was. There wasn't such a thing as a story map. Now we have story maps. There's constant improvement happening. And you've got to be open-minded and willing to try new things and drop old stuff. We thought sprints and iterations and extreme programming was absolutely fundamentally part of the way to work. Then we started experimenting with dropping them and turned out, wow, this is pretty cool. We like this. It works pretty darn well for our purposes. That came through experimentation. some of our experiments were terrible, just terrible. It's not an experiment if you already know the outcome. keep pushing the limits of what can make you happier and more joyful at work in terms of producing great stuff. Brian (27:46) Awesome. That's great stuff. Well, I can't thank you enough for coming on, Joshua. This is great stuff. just, you know, we'll put all the links to the books mentioned and everything else in our show notes for everybody. But as Joshua said, you can go to modernagile.org and find out more about this if you'd like to. You'll find information there about Joshua himself or his company again is Industrial Logic, Inc. And, you know, his book again, just to mention that, Joy of Agility. We were talking how some people get that title a little mixed up or whatever, but it's just the three words, joy of agility. So just look out for that book. I think you'll find it a rich resource for you. Joshua, thanks so much for coming on. Joshua Kerievsky (28:25) Thank you, Brian. Thanks to you. Thanks to Mountain Goat and the folks there. And I really appreciate chatting with you. It was really wonderful.

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

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.

In this episode of the Mob Mentality Show, join us as we delve into "The Discovery of Ignorance in Product Development: Time for a Smarter Way to Deliver Customer Value" with our special guest, Gary Cohen. Drawing on his rich experience across diverse sectors—from government agencies to startups—Gary brings a wealth of insight into optimizing product discovery and delivery for true customer impact.  ### **Key Topics Explored: The Product Discovery and Delivery Intersection** Even if a team is familiar with the 80/20 rule (e.g., where 80% of features go unused), how does it determine the right 20% to deliver? Gary shares strategies to tackle this challenge, advocating for a shift from traditional roadmap fixation to embracing dynamic, continuous discovery that keeps customer value at the forefront. Together, we examine the effectiveness of "strict" roadmap discipline (the practice of adhering to set timelines and objectives) and if it becomes a barrier to true innovation and customer value. We also briefly touch on the FAST framework and its relevance to product discovery, emphasizing how collective discovery through mobbing allows teams to stay closer to evolving customer needs.  ### **The Role of GenAI in Modern Product Development** Is AI is reshaping product discovery? We explore how GenAI can be a collaborative asset for mobs, not only for code development but also for bringing value by uncovering insights into customer behavior and streamlining feature prioritization. We compare "introverted" AI and "extroverted" AI in mob environments and discusses how developing refined AI inquiry skills is key to leveraging AI's full potential. From training mobs in nuanced prompt engineering to using AI to help drive a more lean delivery, we share ways to maximize AI's impact while maintaining expert human oversight.  ### **Bootstrapping Pair and Mob Programming in Individualist Cultures** Transitioning to collaborative programming environments such as pair or mob programming can be challenging, especially in workplaces with a culture of individuality. We offer quick tips on how to bootstrap these methods, from creating a safe space for experimentation to aligning incentives via a peer promotion process. By using context sensitive analogies, how can we influence others in the org to consider jumping into the highly effective world of mob programming? ### **Unpacking Behavioral Expectations: A Smarter Approach to Product Decisions** Beyond the technical, we look at the behavioral side of product monitoring, asking, “What responses do we expect from our users?” Gary emphasizes the importance of behavioral prediction in discovery, cautioning against information bias and providing ways to gauge responses to feature experiments in real-time. We highlight the importance of monitoring usage data and what it reveals about customer engagement—whether a feature elicits a “wow” or a mere “meh.” ### **Takeaways for Product Managers, Engineers, and Innovators** From continuous discovery to leveraging the art of AI prompting, Gary Cohen's insights provide actionable advice for product managers, developers, and cross-functional teams who are ready to rethink their approach to product development and delivery. Whether you're looking to reduce waste, increase customer value, or integrate mob programming and GenAI into your workflow, this episode offers some experiments to try in your journey to achieve product success. Don't miss this engaging discussion filled with actionable strategies, insightful anecdotes, and forward-thinking approaches to innovation!  Video and Show Notes: https://youtu.be/od7E_M9B6gI  

BONUS: Mastering Remote Work in Agile Teams With Antony Marcano NOTE: We want to thank the folks at Tuple.app for being so generous with their stories, and supporting the podcast. Visit tuple.app/scrum and share them if you find the app useful! Remember, sharing is caring!   In this BONUS episode, Antony, co-founder of RiverGlide and Head of Engineering at Ford Digital, joins us to share his experiences and insights from 30 years in software development, including 25 years in Agile practices. As a technical practitioner, leader, and consultant, Antony reflects on navigating remote work, overcoming challenges, and setting up successful remote software teams, while exploring future trends in the industry. The Shift to Fully Remote Work Antony reflects on his first fully remote software project, which took place during the pandemic when everyone was forced to work from home. While his team had been working together for 12 months, they struggled with traditional video conferencing tools that lacked the ability to support pair programming or mob programming effectively. This is when Antony and his team discovered Tuple, a tool that allows for seamless control sharing and a co-located pairing experience. "Switching to Tuple was a game-changer for us in making remote pairing feel as interactive as in-person collaboration." Overcoming Challenges in Remote Collaboration The biggest challenge Antony identifies in remote work is the loss of serendipitous moments—those random watercooler conversations that often lead to innovation. To address this, Antony encourages teams to create opportunities for these moments by structuring time for informal interactions and fostering a safe and open communication culture. "You can't recreate the watercooler, but you can create opportunities for innovation by encouraging open-door policies and setting up shared virtual spaces." Building Effective Remote Teams For Antony, real collaboration is critical to the success of remote teams. He grew up on XP (Extreme Programming) and believes in the power of pairing and mob programming. Antony emphasizes the importance of maintaining good practices from in-person work, such as prioritizing mental well-being, while adapting to the unique needs of remote teams. "Collaboration is not just about tools—it's about mental well-being, trust, and giving the team what they need to succeed." Keeping Teams on Track with Clear Goals Antony shares his approach to ensuring that teams remain aligned with clear goals and progress tracking. His teams focus on delivering small, incremental slices of work and using techniques like limiting Work In Progress (WIP). Rather than viewing user stories as a list of tasks, Antony encourages teams to focus on the user benefit and desired outcomes. "It's about the ‘why,' not just the ‘what.' User stories should focus on the goal, not just be a list of tasks." The Future of Remote Work in Software Development Looking ahead, Antony predicts that tools will continue to evolve, with AI playing a more significant role in software development. He discusses the possibility of having AI participants in pairing sessions and shares his concerns about the convergence of tools that may lose focus over time. Antony encourages developers to experiment with new technologies and remain open to change. "AI is the next frontier in software development, and we need to embrace how it can enhance our remote work experiences." Recommended Resources for Mastering Remote Work Antony notes that while many resources on remote work are often too generic, there are valuable tools and practices software teams can adopt. He recommends regularly rotating hosts during remote pairing sessions and setting aside time for retrospectives and discussions about the bigger 'why' behind the work. "When pairing, rotate roles, reflect regularly, and always focus on the bigger ‘why' to keep your team aligned and motivated." About Antony Marcano Antony is the co-founder of RiverGlide and Head of Engineering at Ford Digital. With 30 years of software development experience, including 25 years in Agile practices, he is a respected leader, coach, and consultant. Antony has contributed to books and journals and is a keynote speaker at global conferences and universities such as Oxford and McGill. He is also the co-creator of 'PairWith.Us,' and remains a hands-on technical practitioner, specializing in Agile development and leading teams to excel in agility. You can link with Antony on LinkedIn visit RiverGlide.com, or check out RiverGlide TV on YouTube.

BONUS: What the UK COVID App Project Taught Us About Remote Agile Collaboration: A Conversation with Giovanni Asproni NOTE: We want to thank the folks at Tuple.app for being so generous with their stories, and supporting the podcast. Visit tuple.app/scrum and share them if you find the app useful! Remember, sharing is caring!   In this special BONUS episode, Giovanni Asproni, CTO and co-founder of Launch Ventures, takes us behind the scenes of his work on the UK government's COVID-19 app project. Giovanni shares insights into the rapid development process, the adoption of remote pairing and ensemble programming, and valuable lessons on leadership in large-scale, high-stakes projects. Giovanni also offers practical advice for teams embracing remote collaboration and agile methodologies. The Start of a Crucial Project "When we got the call from the UK government, we knew this was a mission to help stop the spread of the virus." Giovanni kicks off the episode by recounting how his team at Zühlke Engineering got involved in the development of the UK's COVID-19 app. Tasked with the challenge of building a solution that could help prevent the spread of the virus, they were under immense pressure to deliver quickly. Giovanni explains how they tackled technical hurdles, such as using Bluetooth technology to assess contagion risks, despite the lack of existing APIs on iOS and Android at the time. "Speed was essential, but we also needed a robust design—Bluetooth was key to evaluating contagion risks, even though we didn't have the APIs we needed." Overcoming Rapid Release Challenges "We had to move fast, but accessibility and coordination were non-negotiable." Giovanni discusses how the team, which consisted of around 60-70 members spread across the globe, used agile methodologies to stay organized and on schedule. By fostering open communication and using a clear team structure, they were able to streamline development. Agile planning and strong leadership, including cross-team coordination, were crucial to staying on track. "Agile was our backbone—every team knew their responsibility, and clear communication meant we could deploy with confidence." The Power of Remote Pairing and Ensemble Programming "Pairing allowed us to maintain quality under immense pressure." Giovanni dives deep into the practices of remote pairing and ensemble programming (or mobbing), which were introduced to enhance code quality and resilience during the project. With team members working remotely and under heavy scrutiny, mobbing provided a social outlet and improved problem-solving, while tools like Tuple made remote collaboration seamless. He reflects on the success of these practices, highlighting their impact on efficiency and team morale. "We embraced mobbing not just for resilience, but to stay connected in a time when social contact was scarce." Advice for Remote Pairing Beginners "Don't overthink it—just start and take breaks!" For teams new to remote pairing or ensemble programming, Giovanni offers simple but effective advice: give it a serious try, take breaks to avoid burnout, and don't overcomplicate the process. He emphasizes that these practices can dramatically improve productivity and team cohesion if executed well. "Take the plunge—remote pairing can feel awkward at first, but the benefits are worth it." Key Lessons on Remote Work and Collaboration "Don't try to recreate the office—remote work offers unique advantages." Reflecting on the lessons from the COVID-19 app project, Giovanni explains how remote work is not just a substitute for office work but an entirely different mode of collaboration. He warns against trying to replicate office dynamics remotely, and instead, encourages teams to embrace the benefits of remote settings, such as easier scheduling and fewer distractions from management oversight. "Remote work isn't about replicating the office—when done right, it's a whole new way to collaborate." Resources for Learning More "Explore the power of mob programming with these great resources." To wrap up, Giovanni shares a few key resources for listeners who want to dive deeper into remote pairing, ensemble programming, or leadership in software engineering. He recommends "Software Teaming" by Woody Zuill and the Remote Mob Programming website, which offers comprehensive guides and tools. You can also find out more about Giovanni's work at his company website: https://www.asprotunity.com. During the episode, Giovanni mentions a network of consultants, which you can access at: https://www.clockwork.ing. And the podcast Giovanni hosts is the Software Engineering Radio podcast. About Giovanni Asproni Giovanni Asproni is a consultant, CTO, and co-founder of Launch Ventures. He is an expert in agile development, software design, and modern software engineering practices. Giovanni is a host for the Software Engineering Radio podcast and a frequent speaker at international conferences. You can link with Giovanni Asproni on LinkedIn.

In this insightful episode of the Mob Mentality Show, we sit down with Michael K Sahota to dive deep into the transformative power of **Mob Programming** and **Pair Programming** in dissolving the ego and enhancing team dynamics. Michael shares his unique perspective on how mobbing/pairing can lead to profound psychological shifts, ultimately boosting team function, empathy, and humility. ### Key Highlights: **Pair/Mob to Dissolve the Ego and Increase Team Function** - Michael discusses the **primary goal** of a mob or pair session, revealing how it goes beyond just writing code or learning new techniques. It's about dissolving the individual ego and fostering a collective, empathic mindset that benefits the entire team. - We explore Michael's **personal journey** with his ego, offering a candid look at how pairing/mobbing have helped him grow both personally and professionally. - What is the most **significant outcome** of mobbing/pairing beyond the immediate code or learning? Michael explains how the real magic happens when team members listen to each other and take turns, creating a powerful forcing function for collaboration and psychological safety. - We dive into the **psychological processes** that occur during mobbing, including the death of "fear-based clinging" and how healing the ego leads to deeper empathy and humility. Michael offers anecdotes on how mobbing helps resolve internal conflicts and improve relationships—both at work and beyond. - How much time should be allocated for **production** versus focusing on **production capability**? Michael discusses how to strike the right balance between learning and output, avoiding over-indexing on either side. - A unique **"learning theft"** example highlights why juniors should be prioritized during experiments, while senior developers are encouraged to go last—except when it comes to admitting mistakes, where the inverse applies. **Pair/Mob for Production Capability and Beyond** - Michael shares his thoughts on balancing the **development of production capability** with immediate production needs. He explains how overinvesting in production at the expense of capability can destroy long-term results. - We explore how improving production capability with a solid **ROI** can often yield results within a quarter, but must be continually nurtured through retrospectives and lean thinking. - Breaking the cycle of **overinvesting in production** under intense pressure is a major challenge for many teams. Michael shares stories of how transparency in communication, both within and outside the team, can help break this cycle. - Michael introduces the concept of building **culture bubbles** and we share contrasting ideas on how much courage is needed for these bubbles.   - We also discuss the **HIPPO effect** and how mobbing can disrupt this dynamic by emphasizing experimentation and collective decision-making rather than deference to authority. - Finally, Michael ties it all together by emphasizing the role of **humility**. No one is a flawless expert, and through mobbing/pairing, teams can build a habit of asking for help and embracing the idea that everyone, regardless of experience, has something to learn and improve. ### Why You Should Watch: This episode is a must-watch for anyone involved in **software development**, team dynamics, or leadership. Whether you're interested in improving psychological safety, fostering team empathy, or enhancing production capability, Michael K Sahota's insights on mobbing and ego dissolution will help you rethink how teams work together. It's about more than code—it's about creating a culture of **trust, engagement**, and continuous improvement. Video and Show Notes: https://youtu.be/Wj2hYGMei8s 

Can you do mob programming remotely? Carl and Richard talk to Ulrika Malmgren about mob, or team programming - where three to five developers work together on the same problem, rotating keyboard control and collaborating to write the best possible code. Modern tools like Teams and Zoom make it easy to do the same programming style with everyone remotely! Ulrika talks about how team programming becomes the standard approach to development - as opposed to solo programming, where everyone works separately and then has to spend time sharing what they've done! Good team programming results in higher-quality code in less time - and more happiness!

Can you do mob programming remotely? Carl and Richard talk to Ulrika Malmgren about mob, or team programming - where three to five developers work together on the same problem, rotating keyboard control and collaborating to write the best possible code. Modern tools like Teams and Zoom make it easy to do the same programming style with everyone remotely! Ulrika talks about how team programming becomes the standard approach to development - as opposed to solo programming, where everyone works separately and then has to spend time sharing what they've done! Good team programming results in higher-quality code in less time - and more happiness!

Emily Bache, founder of the Samman Technical Coaching Society and author of several books about technical agile coaching, talks with SE Radio host Sam Taggart about katas and the importance of practice. They discuss how practicing in a safe environment helps developers to learn new skills and build new habits. They also talk about how Samman coaching combines this sort of deliberate practice with applying the lessons learned in practice to the production code base. They also touch briefly on the advantages of working in an ensemble fashion. Brought to you by IEEE Computer Society and IEEE Software magazine.

In this compelling episode of the Mob Mentality Show, we dive deep into the art of Sticky Mob Programming with Lennart Fridén, who brings a wealth of knowledge from his decade-long journey coaching mob programming in Sweden. Whether you're a seasoned mob programmer or new to the concept, this episode is packed with actionable insights and real-world examples that can help you make mobbing a lasting fixture in your team's workflow. ### Key Discussion Points: **Sticky Mob Programming:** - Lennart's insights on mob stickiness - Beyond just trying mobbing - Persistent mob habits even without the nudging of a coach  - Mob stickiness challenges and triumphs - Roles: outsider, insider, first follower (AKA eager first dance partner),  - Lessons from "Power of Habit" - Mob as keystone habit leading to a cascade of other beneficial practices - Community and belonging - Dealing with stagnation - Vulnerability and growth **Technical Coaching and Redundancy:** - Embedding coaching and making the coach's role redundant (times two) - Teaching for sustainability - Gradual coach transition examples - Handling eager vs. apathetic first follower (potential future coach) **P.S.** Reach out to Lennart Fridén ( https://www.linkedin.com/in/lennartfriden/ ) for guidance on introducing mobbing and ensuring it sticks in your organization. Tune in to discover how to make mob programming a sticky and sustainable practice in your organization! Video and Show Notes: https://youtu.be/FSFyifwXbWo  

Welcome to another episode of the Mob Mentality Show! In this episode, we dig into the essential 7th Habit of Highly Effective People: "Sharpen the Saw." Join us as we explore the concept's vital role in Mob Programming. **In This Episode, We Discuss:** - The significance of "Sharpen the Saw" in the Genesis of Mob Programming with Woody Zuill. - The repercussions of neglecting to "Sharpen the Saw" and its impact on team efficiency and personal growth. - Strategies for integrating "Sharpen the Saw" into your workday versus outside of work hours. - The importance of dedicated learning time for continuous improvement. - Comparing ad-hoc and scheduled approaches to sharpening the saw. - Using learning sessions to enhance team skill diversity and foster a culture of growth. - When to use kanban cards for "sharpen the saw" activities - Creating a well-ordered life with scheduled habits for consistent personal and professional development. - Insights from "The Power of Habit" and "Atomic Habits" on stacking habits for maximum impact. - Transforming real knowledge and belief into action through proper identity and motivations. Tune in to discover practical tips and strategies to keep your team sharp, focused, and continuously improving. Whether you're a seasoned mobber or new to the practice, this episode offers valuable takeaways to enhance your team's productivity and collaboration. **Don't miss this dive into the 7th Habit!** **Join the Conversation:** Share your thoughts and experiences with us in the comments! How do you incorporate "Sharpen the Saw" in your daily routine? Let's learn and grow together! Video and Show Notes: https://youtu.be/_Uu0EXhV8oY  

Embark on a journey into the world of collaborative learning with Yuki Tagawa and Christopher Martin as they unveil the "Mob Programming Tutor." In this episode, we explore the genesis of this cutting-edge tool, born from their university master's thesis work. Discover how it integrates a Mob Pomodoro Timer with an intelligent tutoring system driven by machine learning, to help improve the way students collaborate. Join us as we dissect the intricacies of the tool's development, its unique features like auto-shifting break times and feedback on mob roles, and its potential to transform both learning and teaching paradigms. Learn firsthand from the creators about the tool's impact on student collaboration and its future trajectory. But that's not all – we delve into the broader landscape of Mob Programming in education. Uncover the challenges of teaching collaboration, strategies to enhance educational philosophy, and the technical nuances that make this tool a transformative educational experience. Tune in for insights, actionable tips, and a glimpse into the future of collaborative learning. Whether you're a student, educator, or industry professional, this episode aims to leave you enlightened and inspired. Don't miss out – join the conversation today! Video and Show Notes: https://youtu.be/3Rhnj7jZWl0  

Dive deep into the realm of collaborative programming with a unique twist in this episode of Mob Mentality Show where in the spirit of "just sharing" Austin Chadwick unravels 20+ misconceptions and anti-patterns surrounding Mob Programming. From debunking the myth of Mobbing as merely 3+ individuals watching one person type to exploring the misconception of Mobbing being inherently slow and tedious, we dissect various preconceived notions about this innovative approach to coding. At this recorded Agile Lunch and Learn event, explore with us as we challenge the belief that Mobbing is monotonous and that every session involves wooden inflexible navigation and team composition. Moreover, we shed light on the diverse roles within a Mob, addressing the anti-patterns that can hinder effective collaboration. Meet the Anti-Driver, the Anti-Navigator, the Anti-Nose and other personas that disrupt the harmony of Mob Programming. Discover how collaboration can falter under the influence of Fight Club dynamics, lack of prioritization, and lack of pressure protection. At the end of this episode, we invite you to engage in a thought-provoking Q&A session, where we tackle burning questions about Mob Programming. Don't miss out on this opportunity to redefine your understanding of Mob Programming and revolutionize your approach to collaborative coding. Tune in now to Mob Mentality Show and embark on a journey towards a deeper comprehension of Mob Programming – what it truly is not. Video and Show Notes: https://youtu.be/Z5x5nYXBpis 

In this compelling episode of the Mob Mentality Show, prepare to be immersed into the dynamic world of Computer Science (CS) education with none other than Kieran Murphy, who is not only a seasoned tech consultant but also a university CS instructor. This episode offers an exclusive peek into Kieran's journey and the profound implications of mob programming in the undergraduate CS classroom. Throughout the episode, Kieran shares invaluable insights gleaned from his experiences, including the pros and cons of live coding sessions, the rationale behind integrating mob programming into the curriculum, and the tangible effects witnessed on students and on course structure and assignments. Delve into the nitty-gritty as we explore strategies for kick-starting code projects, navigating the dynamics of class sizes, and fostering effective communication and collaboration within the course. Moreover, gain firsthand knowledge on facilitating constructive feedback exchanges among students, managing remote participation, and anchoring engaging mob sessions in virtual environments. From mini-retrospectives to timer rotations, no stone is left unturned as Kieran elucidates many intricacies of mob programming implementation in a computer science class. But that's not all—tune in to discover the candid feedback received from students, as well as the invaluable lessons learned from this innovative approach to teaching. Whether it's embracing diverse learning styles, navigating IDE strategies, or instilling a growth mindset in budding coders, Kieran's expertise offers actionable insights for educators and learners alike. So, whether you're a seasoned educator, aspiring developer, or simply curious about the future of CS education, this episode promises to inform, inspire, and spark meaningful dialogue. Don't miss out on this illuminating exploration of mob programming's role in shaping the next generation of tech talent! Video and Show Notes: https://youtu.be/jtQ-Yeyowg4 

Welcome to a groundbreaking episode of the Mob Mentality Show, where worlds collide in a crossover event with Luca Ingianni & Jeff Gable from The Agile Embedded Podcast. Joining us as they delve deep into the intricacies of the embedded systems industry from a teaming/mobbing perspective. In the first part of the discussion, industry veterans Jeff and Luca share their insights into the "Pain Points and Practices of the Embedded Systems Industry." They explore the challenges of code coupled to hardware and discuss strategies for breaking down isolated silos. Can Electrical Engineers, Mechanical Engineers, and Firmware Engineers all work well together? How has the industry coped with post-COVID supply chain issues, and is the traditional yearly release cycle still viable? Key Highlights: Code decoupling strategies Adapting to post-COVID challenges Breaking down industry silos Cross-discipline team formation In the second part of the discussion, Chris and Austin provide an "Intro to Mob Programming from an Embedded Systems Perspective." Uncover the dynamics of collaboration with firmware engineers, the power of ad-hoc mobbing, and the benefits of problem-solving together in real-time. Learn about the growth of mobbing, from "destroying silos" to "just sharing" and "coalition of the willing." The hosts explore sizing mobs/teams for large cross-functional IOT teams, live code reviews, and the application of Conway's Law. Key Highlights: Collaborative problem-solving Mobbing for less coupling Sizing mobs for large teams Applying Conway's Law and Inverse Conway Maneuver Join us on this journey of exploration and transformation, covering topics from safety-critical processes to clean architecture. Unleash the potential of Mob Programming in the embedded systems domain and discover new avenues for collaboration, innovation, and continuous improvement. Tune in for a paradigm-shifting episode that will inspire, inform, and propel your understanding of teamwork and agility in the embedded systems industry. Don't miss out on this unique collaboration between Mob Mentality Show and The Agile Embedded Podcast! FYI: Video and show notes to be posted here in the next day or so. 

EPISODE DESCRIPTION:In this Dev Life edition of the Angular Plus Show, we talk with Agile coach and author Woody Zuill all about Software Teaming or Mob Programming. We explore the unique aspects of this approach, the benefits, challenges, considerations, and then Woody addresses common barriers & concerns to adopting Software Teaming before sharing practical steps for how you can incorporate this collaborative approach into your workflow to really maximize productivity. Grab your coding crew, rally around the keyboard, and turn your development process into a coding flash mob! This is… The Dev Life!LINKS:https://woodyzuill.com/https://twitter.com/woodyzuillhttps://www.agilealliance.org/resources/experience-reports/mob-programming-agile2014/https://www.youtube.com/watch?v=SHOVVnRB4h0https://www.youtube.com/watch?v=s4Eg-mnx9zgCONNECT WITH US:Woody Zuill - @woodyzuillBrooke Avery - @jediBraveryPreston Lamb - @PrestonJLamb

Josh Lambert: T-Shaping Agile Teams, To Ensure Survival and Success When A Team Member Leaves Read the full Show Notes and search through the world's largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. In this episode with Josh, we explore a high-performing team facing challenges. Despite excellent collaboration and goal achievement, knowledge silos arose due to a distributed application ownership among different individuals. When a senior developer announced their departure, it became clear the team would not be able to take on the extra responsibility. With the lessons from this story, Josh advises sharing real-life stories with the team, to highlight potential problems with siloed-ownership of code, and advocates "T-Shape the team" for broader skill sets, and suggests swarming on stories to address resource gaps. He also suggests the use of a skills matrix for effective knowledge sharing, and visualizing the skill gaps.   [IMAGE HERE] Recovering from failure, or difficult moments is a critical skill for Scrum Masters. Not only because of us, but also because the teams, and stakeholders we work with will also face these moments! We need inspiring stories to help them, and ourselves! The Bungsu Story, is an inspiring story by Marcus Hammarberg which shows how a Coach can help organizations recover even from the most disastrous situations! Learn how Marcus helped The Bungsu, a hospital in Indonesia, recover from near-bankruptcy, twice! Using Lean and Agile methods to rebuild an organization and a team! An inspiring story you need to know about! Buy the book on Amazon: The Bungsu Story - How Lean and Kanban Saved a Small Hospital in Indonesia. Twice. and Can Help You Reshape Work in Your Company.   About Josh Lambert Josh is an Agile Coach at a financial institution. He has been through a few different Agile Transformations. And became a Scrum Master in one of the early transformations and loved the role where where he stayed for 6 years, after which he transitioned into an Agile Coach. You can link with Josh Lambert on LinkedIn.

Embark on a captivating journey through the Agile Mentors Podcast in 2023 with Brian Milner. Explore a spectrum of Agile topics, from Scrum Master challenges to leadership insights. Join Brian for insightful summaries, memorable moments, and a walk through the rich tapestry of Agile wisdom on the show. Overview In this episode of the Agile Mentors Podcast, Brian embarks on a retrospective journey through the standout moments of the podcast in 2023. Explore carefully curated episodes, offering solutions to the common challenges and then delving into the world of Agile beyond software development. Listen in as Brian shares insightful summaries featuring memorable moments and a diverse landscape of Agile wisdom shared by his esteemed guests. Categorized into topics like Scrum Masters, Product Owners, Developers, Agile’s use beyond software, general career advice, and leadership and coaching, this retrospective is a treasure trove of practical advice, actionable insights, and real-world experiences. Tune in for an inspiring tour through the rich tapestry of the Agile Mentors Podcast 2023 episodes. Listen Now to Discover: [01:16] - Brian introduces the episode and invites listeners to join him in a retrospective of the year's episodes, highlighting ones that may have been missed or are hidden gems worth revisiting, which he will group by listener preferences and areas of interest. [02:39] - For Scrum Masters: Brian begins discussing the first episodes tailored for Scrum Masters, kicking things off with #47, "Exploring Lean Thinking and Agile Development," featuring guest Bob Payne, who shares insights into lean thinking, a foundational principle in agile development. Brian recommends this episode for Scrum Masters aiming to enhance their understanding of Agile's fundamentals. [03:34] - Episode #52, "The Birth of Agile: How 17 Adventurous Techies Changed the World," features Agile icon Mr. Jim Highsmith, one of the authors of the Agile Manifesto. Jim provides a glimpse into the past and offers insights into the future of Agile. [04:06] - Episode #59, "Revising the Scrum Guide," features Don McGreal, who played a key role in the guide's revision, shedding light on the thinking behind the revisions. [05:31] - In Episode #62, "Effective Sprint Goals," Maarten Dalmijn delves into effective crafting techniques and the finer details of achieving success with Sprint Goals. [06:12] - In Episode #69, "Should Scrum Masters Be Technical with Allison Pollard," Allison and Brian explore the question of whether Scrum Masters should possess technical skills. If you grapple with how technical a Scrum Master should be, this episode provides valuable insights and perspectives. [06:51] - In Episode #39, Mike Cohn, an authority on user stories, shares valuable insights into the art of crafting effective user stories. [07:15] - In Episode #65 with Randy Hale titled "Unlocking Lean Portfolio Management," Brian and Randy explore the concept of moving beyond a single-team focus as a product owner, delving into the realm of lean portfolio management building upon insights shared by Bob in episode #47. [07:50] - For Product Owners: Must listen bonus from last year, Episode #22, with Roman Pichler, who shares his insights on "How to Create Helpful Product Roadmaps," addressing challenges commonly faced by product owners in dealing with the nuanced aspects of their role. The episode covers strategies to avoid pitfalls, especially the dangers of rigidly locking into scope and schedule timelines. [08:54] - For Developers: Episode #33, "Mob Programming with Woody Zuill," introduces developers to the transformative practice of mob programming. Woody Zuill, a pioneer in this way of working, shares insights and a practical and thoughtful approach that makes it worth exploring. [10:00] - In Episode #48, Brian hosts a unique episode featuring the renowned Lisa Crispin and Janet Gregory, experts in Agile testing, in a show called "Holistic Agile Testing." This episode is particularly recommended for developers specializing in testing or involved in testing within a Scrum team. [11:00] - In Episode #54, "Unlocking Agile's Power in the World of Data Science," Brian and Lance Dacy explore the intersection of Agile methodologies and data science. The popularity of this episode prompted a sequel, Episode #63, on the fusion of Agile and data science. [11:58] - In the final developer-focused episode, Carlos Nunez joins Brian to delve into the world of DevOps. Carlos, a speaker at Agile 2023, shares insights on the significance of DevOps in today's Agile landscape, emphasizing DevOps as a means of empowerment rather than gatekeeping. [12:38] - Agile Outside of Software: Episode #32 with Cort Sharp focuses on Scrum in High School Sports—specifically high school swimming. Cort shares his experience applying Scrum principles to create practice schedules and routines for the swim team he coaches, providing valuable insights for those interested in using Agile beyond the software realm. [13:24] - In #38: "Using Agile for Social and Societal Transformation with Kubair Shirazee," Kubair walks listeners through how his nonprofit employs Agile methodologies to empower micro-entrepreneurs in developing countries. The episode highlights success stories, such as a barber's journey from a rented spot to owning a professional store, demonstrating Agile's transformative impact beyond the tech industry. [14:40] - Episode #45 with Scott Dunn explores "Overcoming Agile Challenges in Regulatory Environments." This crucial topic addresses the unique challenges faced in tightly regulated sectors like government, legal, and medical professions, offering a compelling dialogue on navigating regulatory hurdles within an agile framework. [16:00] - Episode #64 features John Grant discussing "How Agile Methodologies Reshape Legal Practices." This episode reveals the transformative impact of Agile in the legal profession and offers a unique perspective on Agile as a philosophy rather than just a practice, illustrating its broader applicability beyond the software realm. [17:00] - Today's episode is brought to you by Mountain Goat Software's Certified Scrum Product Owner (CSPO) course. This is a two-day training course taught by one of our certified Scrum trainers that teaches you how to use the product backlog as a tool for project success and how to respond to changes in business conditions by restructuring the product backlog. For the schedule, visit the Mountain Goat Training Schedule. [17:27] - General Career Advice: #34: "I'm Trained, Now What? with Julie Chickering" addresses the post-training phase for Scrum Masters and Product Owners. Julie shares insights on taking the next steps, implementing knowledge, and finding opportunities to build a resume in Agile roles. [18:29] - In #40: "Is it Time to Go Out on Your Own? Tips and Insights with Chris Li" Brian and Chris Li discuss considerations for those at later stages of their careers contemplating the transition to independent consulting. If you're pondering whether it's time to establish your consultancy, this episode provides valuable insights and considerations to guide your decision-making process. [19:00] - In #42: "The Importance of Self-Mastery with Bob Galen," Bob emphasizes the value of constant learning, even after years of experience, highlighting the importance of staying open to new discoveries and others' experiences. This episode serves as a compelling guide for personal growth and continuous improvement. [20:28] - Episode #46 with Christina Ambers: In this episode, Christina shares insights on "How to Assess Company Culture Before Accepting a Job Offer." As the year closes and people consider new job opportunities, Christina guides listeners through the crucial step of evaluating company culture and the importance of understanding if a company truly embraces Agile values or merely pays lip service to them. [21:14] - Episode #50 celebrated the milestone of the 50th episode. Lance Dacy was on the show to discuss "Choosing Your Path: Exploring the Roles of Scrum Master and Product Owner." The episode offers guidance for individuals at crossroads, helping them decide between Scrum Master and Product Owner roles. It serves as a valuable resource for those navigating career decisions in the Agile landscape. [22:13] - Leadership and Coaching: In the Leadership and Coaching category, Episode #37 features Brad Swanson discussing "Servant Leadership, Not Spineless Leadership." Brad dispels misconceptions and offers valuable insights into the essence of servant leadership, making it a compelling resource for those interested in effective leadership approaches. [23:28] - In Episode 41, Karim Harbott explores "Cultural Transformations in Organizations." The episode delves into the challenges of changing organizational culture, emphasizing the time and effort required beyond implementing specific practices. [24:00] - In "#44: Transformations Take People with Anu Smalley", Anu highlights the often-overlooked aspect of involving people in organizational transformations, shedding light on the human dynamics that can either support or hinder the process. [24:35] - In Episode #53, "Debunking Myths in Agile Coaching with Lucy O'Keefe," we tackle the common myths surrounding Agile coaching and provide insights on unlocking excellence in Agile coaching practices. [25:01] - Episode #66 is a solo episode where Brian shares his insights into navigating team conflicts, laying the foundation for understanding and mastering the essential skill of conflict navigation. [26:00] - In Episode #68, Brian hosts Mike Hall for a discussion of "The Pros and Cons and Real-World Applications of SAFe." Whether you're new to SAFe or deeply involved, Mike's expertise provides valuable perspectives and tips for navigating this framework. [26:42] - In Episode #70, Mike Cohn joins Brian to explore "The Role of a Leader in Agile." Here, Mike shares valuable insights based on his extensive experience, offering sound advice and perspective on the crucial role of leaders in self-organizing teams. [28:10] - Brian encourages listeners, especially newcomers, to explore relevant episodes based on their roles, with the goal being to offer practical advice and solutions on specific issues rather than lengthy discussions. All episodes are available in the show notes for convenient access. [29:33] - Brian expresses gratitude to listeners for the past year, reflecting on the unique nature of podcasting and letting listeners know he cherishes the encouragement and connections made, especially at events like Agile 2023. [31:00] - What do you want to hear in 2024? What are some of the hot-button topics that haven’t been covered on the show or guests you want to hear from? Send Brian an email with your ideas. [32:28] - And don’t forget to share and subscribe to the Agile Mentors Podcast on Apple Podcasts so you never miss an episode. [33:00] - We also have our Agile Mentors Community, where we have discussions about every podcast [33:24] - Wishing you a Happy Holiday Season! We'll see you early again in 2024. References and resources mentioned in the show: #47: Exploring Lean Thinking in Agile Development with Bob Payne #52: The Birth of Agile: How 17 Adventurous Techies Changed the World with Jim Highsmith #59: Revising the Scrum Guide with Don McGreal #62: Effective Sprint Goals with Maarten Dalmijn #69: Should Scrum Masters Be Technical with Allison Pollard #39: The Art of Writing User Stories with Mike Cohn #65: Unlocking Lean Portfolio Management with Randy Hale #22: How to Create Helpful Product Roadmaps with Roman Pichler #33 Mob Programming with Woody Zuill #48: Holistic Agile Testing with Lisa Crispin and Janet Gregory #54 Unlocking Agile's Power in the World of Data Science #63: The Interplay Between Data Science and Agile with Lance Dacy #71: The World of DevOps with Carlos Nunez #32: Scrum in High School Sports with Cort Sharp #38: Using Agile for Social and Societal Transformation with Kubair Shirazee #45: Overcoming the Challenges of Agile in Regulatory Environments with Scott Dunn #64: How Agile Methodologies are Reshaping Legal Practices with John Grant #34: I'm Trained, Now What? with Julie Chickering #40: Is it Time to Go Out on Your Own? Tips and Insights with Chris Li #42: The Importance of Self-Mastery with Bob Galen #46: How to Assess Company Culture Before Accepting a Job Offer with Christina Ambers #50: Choosing Your Path: Exploring the Roles of Scrum Master and Product Owner with Lance Dacy #37: Servant Leadership, Not Spineless Leadership with Brad Swanson #41: Cultural Transformation in Organizations with Karim Harbott #53: Agile Coaching: Debunking Myths and Unlocking Excellence with Lucy O'Keefe #66: Successful Strategies for Navigating Team Conflicts #68: The Pros and Cons and Real World Applications of SAFe with Mike Hall #70: The Role of a Leader in Agile with Mike Cohn #49: Celebrating One Year: A Look Back at 50 Episodes of the Agile Mentor Podcast Certified Scrum Master Training and Scrum Certification Certified Scrum Product Owner Training Advanced Certified ScrumMaster® Advanced Certified Scrum Product Owner® Mountain Goat Software Certified Scrum and Agile Training Schedule Join the Agile Mentors Community Subscribe to the Agile Mentors Podcast on Apple Podcasts Want to get involved? This show is designed for you, and we’d love your input. Enjoyed what you heard today? Please leave a rating and a review. It really helps, and we read every single one. Got an Agile subject you’d like us to discuss or a question that needs an answer? Share your thoughts with us at podcast@mountaingoatsoftware.com This episode’s presenters are: Brian Milner is SVP of coaching and training at Mountain Goat Software. He's passionate about making a difference in people's day-to-day work, influenced by his own experience of transitioning to Scrum and seeing improvements in work/life balance, honesty, respect, and the quality of work.

Dive into the intricacies of remote mob programming from the perspective of an introvert on this episode of the Mob Mentality Show with our guest, Chris Stone. Join us for a fascinating exploration of the benefits and challenges, seasoned with 2.5 years of Chris's mobbing experience.

Set out on a journey across continents in this episode of the Mob Mentality Show, where we explore the dynamic realm of remote cross-continent mob programming. Join our guests Jeff Langr, Nick Goede, and Merlijn Tishauser as they share stories and insights from their year-long collaboration on a front-end project.

Embark on an immersive exploration of Mob Programming in the Summer of Nix 2023 in this episode of the Mob Mentality Show. Joining us are participants Lorenz, Dawn, Valentin, Albert, and Auguste as they unravel the intricacies of this unique collaborative experience.

In this episode, Dave and Jamison answer these questions: There aren't a lot of engineering management growth resources in my company. It's a relatively small company with about 50 engineers. My manager doesn't have time to properly mentor me. And I'm not sure I would want him to because I feel like his advice isn't always the best. Where can I go for management mentorship or other learning resources? Is it worth exploring non-engineering managers on other teams? Or leaning more on my peers? Or should I be looking for outside advice? A recent episode mentioned awkward Zoom silences. My experience is the exact opposite. I recently switched teams at the same company. This new team has a Zoom room open for the entire work day. The first person to start their day begins the Zoom and the last to leave ends the meeting. They do “mob programming” using a command line tool that switches users every few minutes along with all the strict rules of Extreme Programming - a driver, navigator, etc. But they also do everything in groups: story refinement, diagrams, documentation, everything. Live collab, all day, every day. I'm one month into this transfer but worried that this isn't a good fit and that I made a horrible mistake. ALL the other engineers here rave about how this is the greatest thing ever. Am I the weirdo for not liking it? I feel like I am of split-mind to only either speak or type (but not both) and have not yet rediscovered my coding flow. Mostly I just wanted to roll a perception check with you: Am I the weirdo for not liking all this collaboration and 100% Zooming, or would this workflow drive most other engineers mad as well? Any pep talk about sticking it out would be appreciated.

Discover the mindset and courage it takes to be truly agile. Listen in as Ryan Gottfredson sits down with Brian to explore the four common fears that hinder agility. In this episode of the Agile Mentors Podcast, Ryan Gottfredson, an expert on the psychology of agility and author of the bestselling book "Success Mindsets," sits down with Brian to explore the four common fears that hinder agility. Listen in as Brian and Ryan walk listeners through examples of how these fears manifest in the workplace, sharing valuable insights on how recognizing and reshaping your mindset can lead to more effective agile, and more personal and professional growth. Listen Now to Discover: [01:18] - Brian introduces his guest, Ryan Gottfredson, a leadership and management professor at the College of Business and Economics at California State University, Fullerton to walk us through his talk from Agile 2023 in Orlando called The Four Fears that Undermine Agility. [06:07] - Brian reflects on the evolving understanding of agility as one progresses in their Agile journey, emphasizing the importance of interpersonal dynamics and human psychology in Agile work. [07:47] - The mindset and courage it takes to be truly agile. [09:23] - Ryan offers up some indicators of agility. [10:11] - Ryan introduces the four fears that undermine agility. [12:02] - How fear of failure and reluctance to try new things can lead to resistance to change, ultimately undermining agility. [12:16] -The importance of leadership in fostering agility with an example of Satya Nadella at Microsoft. [15:03] - Ryan discusses the first fear inhibiting agility, the fear of failure, and how it can significantly impede agility. [15:27] - The conversation then delves into the second fear, the fear of being wrong, and how this fear can obstruct agility by hindering the acceptance of diverse perspectives. [17:03] - The Agile Mentors Podcast is brought to you by Mountain Goat Software and their Certified Scrum Training Classes. These classes were designed and developed by the Co-founder of the Scrum Alliance, Mike Cohn. Mike taught his first Scrum class in 1997, and since then, more than 24,000 people have chosen to train with Mountain Goat Software. To join them, click on the Mountain Goat Software Certified Scrum and Agile Training Schedule. [18:13] - Is your expert mindset holding you back? Brian and Ryan explore the importance of shifting from an expert mindset to a truth-seeking mindset to foster agility by being open to the possibility of being wrong. [20:04] - Brian shares a personal experience related to the "no estimates" movement.v [21:28] - The value of conversations that focus on embracing the complexities of a topic. [22:09] - Ryan introduces the third fear inhibiting agility, the fear of having problems. Ryan shares an analogy of reacting to a mouse like it's a bear to illustrate his point. [24:29] - The "window of tolerance" for handling problems effectively. [25:43] - Ryan explains the fourth fear that hinders agility, the fear of getting passed up or not being recognized. [26:22] - The difference between a limited mindset, and a more open mindset that acknowledges the value of giving and sharing. [27:10] - Ryan shares a real-life example of an executive who initially shut down his employees' ideas to keep from being viewed as dispensable. [28:23] - Ryan reflects on the prevalence of these fears in organizations, and how they can collectively hinder agility. [30:03] - Ryan shares the four mindsets related to the four fears: fixed vs. growth, closed vs. open, prevention vs. promotion, and inward vs. outward. [31:33] - Brian thanks Ryan for sharing his insights on the show. You can find Ryan’s mindset assessment on his website, Ryan Gottfredson. You can also find his book, "Success Mindsets," or take his FREE Personal Mindset Assessment on his website or connect with him via LinkedIn. [36:45] - We invite you to subscribe to the Agile Mentors Podcast on Apple Podcasts. Do you have feedback or a great idea for an episode of the show? Great! Just send us an email. And if you’d like to continue this discussion, join the Agile Mentors Community. References and resources mentioned in the show: Ryan Gottfredson Success Mindsets by Ryan Gottfredson Ryan Gottfredson on LinkedIn Ryan's talk from Agile 2023 Ryan Gottfredson's FREE Personal Mindset Assessment #33 Mob Programming with Woody Zuill Subscribe to the Agile Mentors Podcast on Apple Podcasts Certified Scrum Master Training and Scrum Certification Certified Scrum Product Owner Training Advanced Certified Scrum Product Owner® Advanced Certified ScrumMaster® Mountain Goat Software Certified Scrum and Agile Training Schedule Join the Agile Mentors Community Want to get involved? This show is designed for you, and we’d love your input. ● Enjoyed what you heard today? Please leave a rating and a review. It really helps, and we read every single one. ● Got an Agile subject you’d like us to discuss or a question that needs an answer? Share your thoughts with us at podcast@mountaingoatsoftware.com This episode’s presenters are: Brian Milner is SVP of coaching and training at Mountain Goat Software. He's passionate about making a difference in people's day-to-day work, influenced by his own experience of transitioning to Scrum and seeing improvements in work/life balance, honesty, respect, and the quality of work. Ryan Gottfredson, Ph.D., is a renowned mindset expert, author, and consultant. Through his work at California State University-Fullerton, his talk called, The Four Fears that Undermine Agility, and his bestselling book "Success Mindsets," Ryan helps organizations and leaders thrive through mindset improvement.

Welcome to an adrenaline-pumping episode of The Mob Mentality Show! In this captivating installment, titled "Mastering the High Stakes Arena: A Story of Mobbing Under Pressure with Giovanni Asproni," we dive into the thrilling world of Mob Programming in high-pressure environments. Join us as we embark on an exploration of high stakes work, dissecting the very definition of what "high stakes" truly means. Giovanni Asproni takes us on a roller-coaster ride through his enthralling story of Mob Programming under the intense pressure of a high-stakes scenario.  Discover the challenges and triumphs faced during those critical first moments with a new team amidst a high-stakes project. Giovanni provides insights into the diverse skill sets and experience levels within and outside the mob, shedding light on whether the decision to mob was driven by the high stakes or not. Uncover the significance of bugs in high-stakes products, and the accessibility and security constraints in this specific situation. In the midst of high-stakes work, Giovanni emphasizes the unwavering commitment to quality, exemplified by full Test-Driven Development (TDD) and the art of story slicing. Delve into the world of unorthodox design for observability and the dynamics of decision-making in high-pressure mob settings. Explore the rapid shift to radical candor while the pressure mounts and learn strategies for managing stress within the ensemble. Giovanni shares his experiences of mobbing under pressure with unfamiliar team members, touching upon the role of a team/mob firewall/gatekeeper and the value of pairing during meetings. Gain insights into overcoming major challenges when mobbing versus working solo and the critical importance of the bus factor and resilience in high-stakes endeavors. Unearth the secrets behind maintaining high automation levels and Giovanni's epic 16-hour mobbing marathon learning Terraform. Discover the nuanced approach to TDD within the mob while having manual testing support outside of it. And yes, we even explore the surreal scenario of having a prime minister as a major stakeholder - you won't want to miss that story! Join us as we discuss their race against time to deliver and authentically demonstrate lean principles within the mob. Uncover the concept of "Productive Paranoia," and understand the impact of real vs. artificial crisis modes on work dynamics. Is it possible to channel the benefits of crisis-mode work into non-crisis projects without causing destruction? Giovanni shares his thoughts not only on this but also on coaching in a crisis and whether non-XP ways of working naturally lead to crises. Don't miss this high-energy, high-insight episode as we unravel the secrets of how a team mastered a high-stakes arena through Mob Programming. Tune in and immerse yourself in the world of ensemble teaming like never before!  Video and show notes: https://youtu.be/-tgjrd8sL2U 

Join us in this episode of the Mob Mentality Show where we venture into the realm of fostering deep listening and understanding within mob programming. In this discussion, we unveil the profound 5th Habit of a Highly Effective Mobber: Empathetic Listening, drawing inspiration from Stephen R. Covey's timeless "7 Habits" book. 

In the second part of the podcast episode, Gayatri Kalyanaraman is in conversation with Woody Zuill, Expert Coach and co-author of Mob Programming, shares his career journeyBalancing the speeches and consulting with consulting engagementsWoody shares tips and tricks of being in the speaking networksWoody talks about joy of creating his own businesses - Almost 16 of them is creating Woody shares early experiments on signs and making new thingsHe shares his passion of making his day productive by avoiding repeated steps and automateWoody shares his deep inflection points in his career that has positioned him today Woody also shares his ideal places to work and attracting like minded people to work Instead of Doing what others are expecting of us and always uplifting to oneself alsoWoody also shares deep views on how one needs to contribute for a better tomorrowWoody has been programming computers for almost 40 years, and have 20+ years of experience as an Extreme Programmer, and 15+ years as an Agile Guide of some sort. He truly believes that code must be simple, clean, and maintainable so that we can realize the Agile promise of Responding to Change, and that we must constantly "Inspect and Adapt".Woody is a co-author with Kevin Meadows of the book "Mob Programming, A Whole Team Approach". He's a prolific speaker on this topic at conferences, user groups, and meet-ups all over the world.More generally, I've delivered workshops, trainings, and coaching sessions on Agile Software Development, Mob Programming, and Software Development Practices for a number of firms including Ericsson, Schneider Electric, Qualcomm, Intel, H & M, King Games, Capital One, Twitter, and Spotify.Woody can be connected at https://www.linkedin.com/in/woodyzuill/ 

In this exciting episode with Parker Barrett and Aaron Griffith, we dive into the world of Mob Programming with AI on Test Automation. After a quick intro on Mob Programming, we explore the benefits of testing with both human friends and robot friends. We'll share our fascinating origin story of Mobbing with a Robot and explore how AI can drive test development in an ensemble. Discover how testing with robots can help us uncover ZOMBIES and learn about the limitations and warnings of this approach. Watch an AI Mobbing Demo where ChatGPT generates a Flutter app with unit tests, and witness the power of AI-generated test ZOMBIES using Copilot. Don't miss this opportunity to explore the intersection of AI, Mob Programming, and Test Automation! Video and Show Notes: https://youtu.be/EGySAVY2atE 

Join us as we explore the transformative benefits of mob programming in a software dev internship program, taking you on a journey from interviews to potential full-time hires. Discover how we interview 10-20 intern candidates at once using mob programming, revolutionizing the way we assess their skills and potential. Explore the pros and cons of interns joining existing mobs versus having an independent intern-only mob, and learn the key steps to prepare for the intern mob experience. We deep-dive into the essential aspects of intern mob onboarding, project selection, and the crucial roles of intern mob coaches. We share how we witnessed the incredible growth as interns present their end-of-project demonstrations and gain valuable "agile" training at the culmination of their internship. But the journey doesn't end there – we delve into the exciting possibilities that follow the internship.  Don't miss this episode that combines the power of mob programming, internships, and agile practices.  Video and Show Notes: https://youtu.be/5B7xaAEV3GI 

Join Brian as he rediscovers and relives the most captivating topics, memorable guests, and impactful topics from the first year of the “Agile Mentors” podcast. Overview From deep dives into Agile methodologies and practical tips for using your knowledge to benefit others and foster change, the first 50 episodes of the “Agile Mentor” podcast have been filled with fascinating topics and memorable guests. In this episode, Brian Milner embarks on a retrospective journey through the inaugural year of the show. Listen in as he shares the real stars of the podcast, the moments that surprised him, those that took him out of his comfort zone, and the ones that inspired him to push to be better every day! Plus, what’s next for the show. Listen Now to Discover: [00:45] - Brian introduces the retrospective episode to celebrate one year and 50 episodes of the "Agile Mentors" podcast and share what's next. [01:54] - A thank you for YOUR role in the show. [02:17] - The role of marrying the right topic to the right guest. [02:56] - The format that allows listeners to choose the episodes that interest them the most. [04:03] - Pointing you toward the best of the best. Our first several episodes were focused on the Agile Framework and some core topics, including having Mike Cohn on to talk about the different roles and generally accepted practices. [05:13] - Sending out thanks to a few of our guests, including the trainers at Mountain Goat Software, including Lance Dacy. [05:45] - Kert Peterson joined us to share his knowledge, and Scott Dunn shared his insight from the product owner's perspective. [06:05] - On episode 16, Mitch Lacey joined us to discuss The Hidden Secret Ingredient And Julie Chickering brought a great perspective from a project management background and applying that to some of the stuff we've discussed here on the show. [06:39] - The time when one of my mentors joined us on the show to discuss transformation. [07:08] - Learning about coaching and marketing from the best! [07:27] - Roman Pitchler joined us to discuss product roadmaps and planning things from a product owner perspective. And John Miller shared about using Scrum in the education environment. [07:46] - On EP25, Henrik Nieberg came on and talked to us about scaling, and on EP27, Tricia Broderick walked us through leadership without blame. [08:18] - How Scrum can be applied outside of software development and mob programming. [08:42] - The key to working with humans. [09:03] - The episode that surprised Brian a little bit. [09:34] - Three episodes all about change: The first one was about how one organization uses Scrum to help impoverished micro-entrepreneurs succeed (and change their lives). The second featured Chris Li sharing his insight on how to know when it’s time to strike out on your own, and Karim Harbott walked us through the difficulty of transforming an organization's culture. [10:25] - The episode that inspired Brian to try to push in different ways to get better. And how to cultivate an Agile culture in a virtual world. [10:53] - Why transformations take people, how to assess a company’s culture before you accept their job offer, and lean thinking in Agile with Bob Payne. [11:49] - The real stars of the podcast. [12:30] - What’s ahead for the podcast? [13:02] - Stepping off the gas a bit. [13:45] - Virtual dial—targeted tips. [14:32] - The lifeblood of the “Agile Mentors” podcast. [15:06] - Mike Cohn and Brian are both presenting at Agile2023 in Orlando, July 24 through 28th. [15:39] - The most significant benefit of BIG conferences. [16:41] - Thank you for getting us to a year and 50 episodes! Join the Agile Mentors Community to continue the discussion. If you have topics for future episodes, email us by clicking here. And don’t forget to subscribe to the “Agile Mentors” Podcast on Apple Podcasts so you never miss an episode. References and resources mentioned in the show: Agile2023 | Orlando, Florida | Agile Alliance #1: Scrum vs Agile & Keys to Success with Mike Cohn #3: What Makes a Great Product Owner? With Lance Dacy #9: Scrum Artifacts with Kert Peterson #10: Why User Stories are the Best Way to Capture Requirements with Mike Cohn #17: Getting There From Here: Agile Transformations with David Hawks #18 Coaching in an Agile World with Lyssa Adkins #21: Agile Marketing Teams with Stacey Ackerman #22: How to Create Helpful Product Roadmaps with Roman Pichler #23 How Agile Works in Education with John Miller #25: Scaling with Henrik Kniberg #27: Leading Without Blame with Tricia Broderick #29: Influencing Up with Scott Dunn #32: Scrum in High School Sports with Cort Sharp #33 Mob Programming with Woody Zuill #34: I'm Trained, Now What? with Julie Chickering #37: Servant Leadership, Not Spineless Leadership with Brad Swanson #38: Using Agile for Social and Societal Transformation with Kubair Shirazee #40: Is it Time to Go Out on Your Own? Tips and Insights with Chris Li #41: Cultural Transformation in Organizations with Karim Harbott #42: The Importance of Self-Mastery with Bob Galen #43: Cultivating Agile Team Culture in a Virtual World with Richard Cheng #44: Transformations Take People with Anu Smalley #46: How to Assess Company Culture Before Accepting a Job Offer with Christina Ambers #47: Exploring Lean Thinking in Agile Development with Bob Payne Mountain Good Software's Certified Product Owner course Mountain Goat Software Certified Scrum and Agile Training Schedule Join the Agile Mentors Community Subscribe to the Agile Mentors Podcast on Apple Podcasts Want to get involved? This show is designed for you, and we’d love your input. Enjoyed what you heard today? Please leave a rating and a review. It really helps, and we read every single one. Got an Agile subject you’d like us to discuss or a question that needs an answer? Share your thoughts with us at podcast@mountaingoatsoftware.com This episode’s presenters are: Brian Milner is SVP of coaching and training at Mountain Goat Software. He's passionate about making a difference in people's day-to-day work, influenced by his own experience of transitioning to Scrum and seeing improvements in work/life balance, honesty, respect, and the quality of work.

Marjorie placed the start of her journey during her work as an agronomist when she wrote her first R lines of code. She explained how her childhood in southern France brought her to study plants, create a hydroponic startup, work on risk and project management, and slowly become interested in web development. We spoke of her Bootcamp and how she found her first job. We discussed eXtreme-Programming and Mob-Programming, and what it's like to be a newbie in a teaching environment.Here are the links from the showhttps://www.linkedin.com/in/marjorie-aubert-full-stack-developer/CreditsCover Legends by HoliznaCC0 is licensed CC0 1.0 Universal License.Your host is Timothée (Tim) Bourguignon; more about him at timbourguignon.fr.Gift the podcast a rating on one of the significant platforms https://devjourney.info/subscribeSupport the show

Some programming tasks are hard to start. Either because there are a lot of unknowns, because the team hardly knows each other, or because there are knowledge gaps in the team. Read more › The post Mob Programming appeared first on Complete Developer Podcast.

Johannes Lindman: Introducing Mob Programming, and how to overcome resistance to new ways of working in Agile teams Read the full Show Notes and search through the world's largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.   In this episode, Johannes talks about how he introduced mob programming to his teams as a new way of working and sharing competencies. One of the teams team tried it for a few minutes and gave up. Surprisingly, another team started at 9am and continued throughout the day, and eventually noted it was too draining. Johannes suggests limiting the time for mob programming and being adaptable in trying different tools. He also warns against falling in love with one tool and introduces the concepts of Shu-Ha-Ri and NoEstimates. Johannes emphasizes the importance of measuring progress and visualizing metrics to ensure that teams are driving towards their goals. Ultimately, Johannes achieved his goals with this new way of working, even with some resistant individuals who initially said "no" to the idea.   [IMAGE HERE] As Scrum Master we work with change continuously! Do you have your own change framework that provides the guidance, and queues you need when working with change? The Lean Change Management framework is a fully defined, lean-startup inspired change framework that can be used as the backbone of any change process! You can buy Lean Change Management the book at Amazon. Also available in French, Spanish, German and Portuguese. About Johannes Lindman Despite many years of experience Johannes still learns new things every day in order to stay relevant. This aligns with his curiosity on life and people.  You can link with Johannes Lindman on LinkedIn

The Mob Mentality Show is back with another informative episode titled "Certifiably Extreme with Paul Moore." In this episode, Chris Lucian and Austin Chadwick sit down with Paul Moore to talk about certifications and Mob Programming in the Certified Scrum Developer Course. They cover a range of topics, including the potential benefits and drawbacks of certifications, mob makeup in the CSD course, story splitting value and techniques, and the hole in the Scrum framework. Join the conversation as they explore the world of agile development and learn how to become "Certifiably Extreme." Don't miss out on this insightful episode! Subscribe to the Mob Mentality Show and stay tuned for more. Video and Show Notes: https://youtu.be/96llOG03z08  

Imagine you get to design a college class that teaches mob programming, craftsmanship, and agility.  What would it look like? How would you do it? Imagine no more and join Chris and Austin as they discuss with professor Paul Gestwicki his agility focused college courses and how he adapted the Mob RPG for the classroom. Paul talks about how he heard about Mob Programming via a Joe Justice video and shares about his first experiments with using Willem Larsen's Mob RPG Game in the college classroom. Come hear what Paul learned from those experiments and what changes he made to the game to tailor it for his students' levels and context. They all discuss scaffolding for learning navigation skills and Paul tells a TDD and clean code game design success story. Come celebrate awesome educators like Paul Gestwicki in this episode of the Mob Mentality Show! Video and Show Notes: https://youtu.be/nqVUe7ezHhQ  

Join Woody Zuill and Brian Milner as they discuss the benefits of teams working together through Mob Programming. Overview In this episode of the Agile Mentors podcast, Woody Zuill, a 40-year veteran software developer specializing in team interaction, joins Brian to explore the concept of Mob Programming. Woody shares the benefits of working together rather than separating tasks in software development and how removing things like queuing, multitasking, and context switching can actually make teams more effective. Listen in as he walks us through the collaborative software development approach's perks. Listen now to discover: [02:22] - Brian introduces Woody Zuill, a 40-year veteran software developer specializing in team interaction. [02:51] - Woody explains how he discovered the term Mob Programming. [04:56] - Where the idea of Teaming came from. [06:20] - Woody explains why he's changing the name from mob programming to teaming. [07:23] - Teaming = collaboration brought to software development, where more than one brain connects to do the work that needs to be done. [11:11] - Painting the Mob Programming picture: it's when "all the brilliant minds work together on the same thing ‌in the same space, at the same computer." [13:40] - To work efficiently in software development, one team member acts as the driver at the keyboard while everyone else acts as the navigator. [16:41] - The drawbacks and disconnect of breaking software development down into smaller pieces. [18:34] - Isn't six people in one room working on one computer a waste of resources? [21:07] - Do you want to be productive or effective? Examining the Lean concept of flow. [24:57] - Enhancing the effectiveness of software development by removing the negative impact of waiting, queuing, multitasking, and context switching. [25:22] - The benefits of working together vs. separating tasks in software development. [26:53] - Team Flow: how collaboration adds to our ability to work in the zone. [28:38] - Working together is often more effective, so why have we gotten better at it? [31:25] - The strength of experimentation. [33:09] - Woody explains that since the software development process is a discovery process, innovations such as mob programming can benefit the process. [35:25] - Woody shares resources where you can find more information on Mob Programming (see the resources section below for more) and how you can contact him to schedule a workshop. References and resources mentioned in the show: Software Teaming: A Mob Programming, Whole-Team Approach by Woody Zuill Teaming by Amy C. Edmondson Code with the Wisdom of the Crowd: Get Better Together with Mob Programming by Mark Pearl The Mob Mentality Show on Apple Podcasts Diffusion of Innovations by Everett M. Rogers Online And In-Person Training To Help You Succeed With Agile Through Mountain Goat Software The Agile Mentors Community Want to get involved? This show is designed for you, and we’d love your input. Enjoyed what you heard today? It would be great if you left a rating and a review. It really helps, and we read every single one. Got an agile subject you’d like us to discuss or a question that needs an answer? Share your thoughts with us at podcast@mountaingoatsoftware.com This episode’s presenters are: Brian Milner is SVP of coaching and training at Mountain Goat Software. He’s passionate about making a difference in people’s day-to-day work, influenced by his own experience of transitioning to Scrum and seeing improvements in work/life balance, honesty, respect, and the quality of work. Woody Zuill has been a software developer for over forty years. Woody is one of the pioneers of Mob Programming, a method of teamwork in software development that involves the entire team working together. Woody gives remote and in-person workshops on the topic. You can find out more about him on Twitter @WoodyZuill or on LinkedIn.

Join Woody Zuill and Brian Milner as they discuss the benefits of teams working together through Mob Programming. Overview In this episode of the Agile Mentors podcast, Woody Zuill, a 40-year veteran software developer specializing in team interaction, joins Brian to explore the concept of Mob Programming. Woody shares the benefits of working together rather than separating tasks in software development and how removing things like queuing, multitasking, and context switching can actually make teams more effective. Listen in as he walks us through the collaborative software development approach's perks. Listen now to discover: [02:22] - Brian introduces Woody Zuill, a 40-year veteran software developer specializing in team interaction. [02:51] - Woody explains how he discovered the term Mob Programming. [04:56] - Where the idea of Teaming came from. [06:20] - Woody explains why he's changing the name from mob programming to teaming. [07:23] - Teaming = collaboration brought to software development, where more than one brain connects to do the work that needs to be done. [11:11] - Painting the Mob Programming picture: it's when "all the brilliant minds work together on the same thing ‌in the same space, at the same computer." [13:40] - To work efficiently in software development, one team member acts as the driver at the keyboard while everyone else acts as the navigator. [16:41] - The drawbacks and disconnect of breaking software development down into smaller pieces. [18:34] - Isn't six people in one room working on one computer a waste of resources? [21:07] - Do you want to be productive or effective? Examining the Lean concept of flow. [24:57] - Enhancing the effectiveness of software development by removing the negative impact of waiting, queuing, multitasking, and context switching. [25:22] - The benefits of working together vs. separating tasks in software development. [26:53] - Team Flow: how collaboration adds to our ability to work in the zone. [28:38] - Working together is often more effective, so why have we gotten better at it? [31:25] - The strength of experimentation. [33:09] - Woody explains that since the software development process is a discovery process, innovations such as mob programming can benefit the process. [35:25] - Woody shares resources where you can find more information on Mob Programming (see the resources section below for more) and how you can contact him to schedule a workshop. References and resources mentioned in the show: Software Teaming: A Mob Programming, Whole-Team Approach by Woody Zuill Teaming by Amy C. Edmondson Code with the Wisdom of the Crowd: Get Better Together with Mob Programming by Mark Pearl The Mob Mentality Show on Apple Podcasts Diffusion of Innovations by Everett M. Rogers Online And In-Person Training To Help You Succeed With Agile Through Mountain Goat Software The Agile Mentors Community Want to get involved? This show is designed for you, and we’d love your input. Enjoyed what you heard today? It would be great if you left a rating and a review. It really helps, and we read every single one. Got an agile subject you’d like us to discuss or a question that needs an answer? Share your thoughts with us at podcast@mountaingoatsoftware.com This episode’s presenters are: Brian Milner is SVP of coaching and training at Mountain Goat Software. He’s passionate about making a difference in people’s day-to-day work, influenced by his own experience of transitioning to Scrum and seeing improvements in work/life balance, honesty, respect, and the quality of work. Woody Zuill has been a software developer for over forty years. Woody is one of the pioneers of Mob Programming, a method of teamwork in software development that involves the entire team working together. Woody gives remote and in-person workshops on the topic. You can find out more about him on Twitter @WoodyZuill or on LinkedIn.

Squirrel and Jeffrey continue discussing why you and your team might need a coach—for techniques and skills that they are already good at. This week they concentrate on practical steps for finding internal and external sources of instruction and inspiration. SHOW LINKS: - Pair Programming: https://en.wikipedia.org/wiki/Pair_programming - Mob Programming: https://en.wikipedia.org/wiki/Mob_programming --- Our book, Agile Conversations, is out now! See https://agileconversations.com where you can order your copy and get a free video when you join our mailing list! We'd love to hear any thoughts, ideas, or feedback you have about the show. Email us at info@agileconversations.com

Read the full Show Notes and search through the world's largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. Yousef was working with a team that others call “trouble team”. But, as he observed the team, it looked like they were trying hard to do a good job. So he started working through 1-on-1's to try to get a better, more detailed picture of what was going on. In that process, he realized that something critical was missing for that team to work well. Featured Book of the Week: The Five Dysfunctions of a Team: A Leadership Fable by Lencioni In The Five Dysfunctions of a Team: A Leadership Fable by Lencioni, Yousef learned how to diagnose a team by looking at their dynamics. He also learned a model that helps him work with teams and grow the people in it.  In this segment, we also refer to Team of Teams: New Rules of Engagement for a Complex World by General McChrystal, and MobProgramming, a topic we've covered before here on the podcast. How can Angela (the Agile Coach) quickly build healthy relationships with the teams she's supposed to help? What were the steps she followed to help the Breeze App team fight off the competition? Find out how Angela helped Naomi and the team go from “behind” to being ahead of Intuition Bank, by focusing on the people! Download the first 4 chapters of the BOOK for FREE while it is in Beta! About Yousef T. Fahoum When starting out as a ScrumMaster and BA years ago Yousef passionately followed the ScrumMaster Podcast. Yousef is a SAFe Enterprise Coach at Elabor8 with experience implementing Agile and SAFe at some of the largest and most recognized brand leaders across industry domains in the U.S. and Australia. You can link with Yousef T. Fahoum on LinkedIn and connect with Yousef T. Fahoum on Twitter.

Read the full Show Notes and search through the world's largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.   About Woody Zuill and Yves Hanoulle Woody is the man behind Mob Programming, and he often talks and presents on agile topics, and coaches people interested in creating a wonderful workplace where people can excel in their work, and in their life. You can link with Woody Zuill on LinkedIn and connect with Woody Zuill on Twitter.    Yves is all about collaboration. His goal is to inspire people to create more collaborators.  Creating self-sustaining communities from home allows him to spend more time with his kids.  And to get a better work-life fusion. For him agile and communities share a common element called trust. With trust anything is possible, without trust, some things might be possible, yet very hard and expensive... You can link with Yves Hanoulle on LinkedIn and connect with Yves Hanoulle on Twitter. 

We're talking with Woody Zuill today about all things Mob Programming. Woody leads Mob Programming workshops, he's a speaker on agile related topics, and coaches and guides orgs interested in creating an environment where people can do their best work. We talk through it all and we even get some amazing advice from Woody's dad. We define what Mob Programming is and why it's so effective. Is it a rigid process or can teams flex to make it work for them? How to introduce mob programming to a team. What kind of groundwork is necessary? And of course, are mob programming's virtues diminished by remote teams in virtual-only settings?