Agile Mentors Podcast

Brian Milner and Guests
Agile Mentors Podcast

The Agile Mentors podcast is for agilists of all levels. Whether you’re new to agile and Scrum or have years of experience, listen in to find answers to your questions and new ways to succeed with agile.

  1. 4 DAYS AGO

    #133: Trending Agile: Scrum Masters, AI, and the Future of Agile

    The Agile Alliance partners with PMI—what does it mean for Agile’s future? Plus, how AI is reshaping Scrum Master roles and why honesty (even when it stings) is the key to career growth. Brian Milner and Cort Sharp tackle these hot topics in a no-holds-barred discussion. Overview In this episode of the Agile Mentors Podcast, Brian Milner and Cort Sharp dive into the recent Agile Alliance-PMI partnership and its potential impact on the Agile community. They also explore AI’s growing influence on Scrum Master roles—will it replace them or elevate their value? Finally, they tackle a tricky but crucial topic: when to speak up in the workplace, balancing honesty with career preservation. If you want to stay ahead in Agile’s evolving landscape, this is a must-listen! References and resources mentioned in the show: #32: Scrum in High School Sports with Cort Sharp #82: The Intersection of AI and Agile with Emilia Breton #129: 2025: The Year Agile Meets AI and Hyper-Personalization with Lance Dacy #132: Can Nice Guys Finish First? with Scott Dunn Mike Cohn’s Better User Stories 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. Cort Sharp is the Scrum Master of the producing team and the Agile Mentors Community Manager. In addition to his love for Agile, Cort is also a serious swimmer and has been coaching swimmers for five years. Auto-generated Transcript: Brian Milner (00:00) Welcome in. Welcome back, everybody. This is the Agile Mentors Podcast. I'm with you as always, Brian Milner. And today, we're going to do something a little different. We're in this mode right now. We've kind of been open to some suggestions recently about maybe we should try some experiments and try some different things. And so today's going to be one of those little experiments. We have someone that's going to be with us, Mr. Cort Sharp. So welcome in, Cort. Cort (00:23) Hey Brian, thanks for having me on. Brian Milner (00:26) Absolutely. Cort is our community manager for the Agile Mentors community. And Cort and I do classes together a lot. He is often the producer in the classes. So we see each other a lot. We talk a lot. Cort's also a certified Scrum professional. So he's been doing this and has encountered Scrum in some kind of unusual circumstances as well. He's a high school swim coach. There's an episode that we talked about that. way back so that anyone wants to dig that out, they can go back and find that and learn a little bit more about it. But we just thought it would be good to have maybe periodically a little check in about maybe some stories that have come up in the news about Agile or things that have been flashing through social media feeds or anything like that. know, Cort and I are a little bit different age groups, a little bit, more than a little bit. And I'm sure the of things that cross court's radar may be a little bit different than the things that cross mine. And we just thought maybe it would be an interesting kind of thing to have a little discussion, the two of us, about some of these major burning issues and things that people are talking about on LinkedIn and Twitter and, I'm sorry, X, anywhere else. I'm going to kind of... Give the reins over to court here a little bit, because I know he's pulled some things that he wants to talk about, and we'll just kind of see where we go. Cort (01:40) Awesome, yeah, thanks Brian. Not just X and LinkedIn, we're also looking through Instagram, YouTube Shorts, where the cool kids hang out, I guess is. That's at least what my swimmers tell me. Brian Milner (01:50) Okay, okay I Got it I got a yeah, I you know, I had to learn a lot about an Instagram with my daughters and I still don't get it. just I mean I have fun flipping through stuff but I don't I could never like get a following there because I just don't understand how to Do all the but that's old guy talking. So Cort (02:11) It's a weird place, Brian. I don't blame you. It's totally good. But I've seen a few things come across my feed, and we've kind of had lighter versions of this conversation, whether it's in classes or just kind of on the side or something like that. So we just kind of thought, hey, let's sit down and actually go into depth about this, because I'm curious what your thoughts are on some of these things. And I don't know. Brian Milner (02:14) Yeah Cort (02:35) Hopefully I'm able to add into the conversation a little bit more than just here's a young guy yelling at a cloud instead of an old guy yelling at a cloud, right? No, I hope not. But let's come out and I'm gonna come out swinging at you. So the biggest news bite that I have found over the last couple of months or the last month-ish is that the Agile Alliance and PMI Brian Milner (02:37) Ha ha. young guy and old guy yelling at each other. That's not what anyone wants to hear. Yeah. Yeah. Cort (03:02) have entered, have announced that they're entering a partnership. We don't really know a ton about what that partnership looks like, but it is presumed that the Agile Alliance will be hosting some kind of content through PMI or PMI will be hosting some kind of content that the Agile Alliance has created. So I'm just curious, like, what are your thoughts on that? Do you think it's a good move, bad move, any kind of potential impacts that you see? It's a big one. Brian Milner (03:30) Yeah, way to start with a softball that we just, yeah, mean, it's obviously a hot button topic right now. I've heard lots, I've read lots of opinions of people on different kind of forums and discussion boards and things where people are talking about kind of, what does this mean? That kind of thing. And so here's kind of, Cort (03:34) Hahaha Brian Milner (03:57) Here's kind of what I've heard from both sides, right? The people who are kind of anti feel like this is maybe a little bit of a betrayal. And I think that the reasoning behind that kind of feels like maybe historically or somewhere maybe further into the past, the PMI may have been a little bit of an antagonist towards the Agile movement, or some people feel that way. I'm not saying this is my opinion, but this is what I've heard. Some people might feel that way. And so they feel like, would you attach your name to something like that? But I've also heard from people who are pro and have said, look, the basics of the deal are that it's not going to change anything for the Agile Alliance other than the name. It's officially the PMI Agile Alliance. But other than that, what I've heard from people who are board members that have posted Cort (04:43) Sure, yeah. Brian Milner (04:50) from the Agile Alliance have said, it's just nothing more than our name is now different. We're autonomous. We can still do the things we've always done. And we feel like the connection to this larger organization will enable us and help us. And I know the Agile Alliance has gone through some tough times, as a lot of us in the industry have, with the conferences. At least I know the conferences last year was kind of not what people have hoped, and not just the Agile Alliance conference, but other conferences have had down attendance and other things. Maybe just a sign of the times, I don't know. But personally, I kind of look at it and I got to preface this. got to, before we talk about anything else, right? Because now we're going to get into opinion. But I would just say, let me preface by saying the opinions you are about to hear. are not the official opinions of Mountain Goat Software. They are just the opinions of the individuals that you will be listening to. So this is just one guy's opinion, right? I think I would just say I get it from both sides. I understand. I see kind of the concern. From the people who are pro and they say, look, it's just the name, I don't know why anyone would freak out about that. It's just a, we're just putting letters PMI in front of our name. hear that, but I've also heard other people counter that to be like, yeah, but it would be like Greenpeace saying, you know, we're now Exxon Greenpeace, you know? And I don't think, I think that's quite, you know, a huge overstatement. I don't think that's the same thing at all. And I, you know, I recognize that the PMI has, you know, they've adapted. anyone who thinks that they're the same way that they've always been, I think is wrong. I think that they have incorporated over time more and more agile ideas into their certifications and other things. they certainly, I feel like they've recognized the agile sort of the future and they've tried to invest more heavily. I think this is a sign of that as well. They're trying to invest a little bit more into agile because they see it as, you this is the future of project management. You know. But they also see it as one of the paths. It's one way of doing project work. And it's not the only way. There are other ways that are good as well. I don't know that I disagree with that. Depends on the project. It depends on what it is you're trying to do. But we talk about this in class. If I know what it is that we're going to make, I know exactly how to make it, the customer knows what they want, and we're not changing anything along the way, then Cort (07

    37 min
  2. 29 JAN

    #132: Can Nice Guys Finish First? with Scott Dunn

    Can being "nice" at work actually hold you back? Join Brian and Scott Dunn as they unravel the myths around workplace "niceness," explore the balance between kindness and assertiveness, and reveal how honest communication can earn you respect—and maybe even that long-overdue promotion. Overview In this episode of the Agile Mentors Podcast, Brian and Scott dig deep into the question: Do nice guys (or gals) really finish last at work? They discuss the critical balance between being accommodating and assertive, why conflict can be a tool for growth, and how emotional intelligence plays into team dynamics. With stories, tips, and the psychological truths behind professional success, this episode is a must-listen for anyone looking to navigate workplace interactions while staying true to themselves. References and resources mentioned in the show: Scott Dunn Bill of Assertive Rights Elements of Agile Radical Candor Advanced Certified ScrumMaster® 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. Scott Dunn is a Certified Enterprise Coach and Scrum Trainer with over 20 years of experience coaching and training companies like NASA, EMC/Dell Technologies, Yahoo!, Technicolor, and eBay to transition to an agile approach using Scrum. Auto-generated Transcript: Brian (00:00) Welcome in Agile Mentors. We're back and we're here for another episode of the Agile Mentors podcast. I'm with you as always, Brian Milner. And today we have friend of the show, buddy of the show, Scott Dunn is back with us. Welcome in Scott. Scott (00:13) Hey Brian, great to be back as always. Love it. Brian (00:17) Love to have Scott on as always and if you've listened to some of the past episodes with him then you know why. If not, I encourage you to check it out after this episode. We wanted to have Scott on earlier this year just to talk about some things that might be percolating in a few people's heads with the turn of the year and kind of as you start to prepare and look forward and maybe even look back a little bit in things. And particularly deal with an issue around how people show up at work and Scott was saying to me earlier, kind of this phrase about, nice guys finish last? Do they finish first? Do they finish last? Can you be nice? Can you be nice at work and be promoted? Can you be nice at work and move upwards? Or do you have to not be nice? Scott (01:03) you Brian (01:11) in order to do that. So tell me a little bit about kind of the genesis of the idea from you, Scott. What have you been hearing or what's been crossing your path? Scott (01:17) Yeah, and I'm so glad we had a chance to talk about this because it's recent. So the first thing that sparked my thought on this, so granted in the leadership class, we talk about being a balance of accommodative and assertive, and I'll usually refer to a... a document called the Bill of Assertive Rights. And I was reading another book this week and actually it referenced the same thing. I thought, switching fast forward a few days and I'm doing an assessment with a company that's asked for help because they're not, they're struggling with quality, they're struggling with predictability. And I know what the leaders goals are for the efforts. And so now I'm meeting with all the team members to do an actual formal assessment for baseline. Now, and this assessment, you're going to go through, I don't know, 30, 40 questions. So it's not lightweight. It's trying to be tactical, like, Is the team well formed? Is the backlog in good shape? Do you have a roadmap? Are the leaders supporting the change? I mean, whether company level, product level, team level, and we even added some advanced questions. And the fascinating thing is over a course of all these questions, the answer was essentially, we're okay at that, right? If you ask them, are they doing this practice or not, they'd say, somewhat. And it didn't matter if it was the most basic thing at the team level or the most advanced thing at the corporate level, everything was okay. So when you look at the dashboard at the end, in our normal red, yellow, the whole thing was yellow. And so I just paused and said, you know, I've never seen this before. I said, yeah, I joke with them a little bit about that, but I said, you know, my friends kind of think about it. It actually doesn't make sense that you would be okay at the fundamental beginning things and also okay at advanced high level things. So it's usually progressive, right? You get the basics down like the satiric change curve. That's kind of what we're following. So now... And then what came out later in the conversations is that someone said basically, we're afraid to say things that are hard to hear. He used the word judgment. Like we don't want to kind of stand in judgment of others, but essentially saying something that someone's not going to hear, whether it's true or not, because they had nothing green, nothing red. So not doing well. And then the last thing that really got me triggered, you know, really start diving into this is this new year and people are getting this promotions and things going on at some of the companies. And there was a story of this one guy, like, I've worked here eight years and never been promoted. And yet everyone loves this person. Everyone likes this person. And I'm hopping on social media and someone asked that question, literally, like, give me an example of when nice guys finish last. And the guy said the same thing. He said, I am the one everyone goes to for help. I'm always ready to help. I'll do anything anyone needs. Everyone likes me. They all praise me. And I haven't been promoted in like 13 years. So partly for our own careers, partly for, you know, being a change agent, et cetera, I thought it'd be worth, you know, just having to... It's a great conversation topic, Brian (03:51) Yeah, well, I'll confirm part of that, or at least a couple of crossovers there with what you said, because there's an assessment kind of thing that we do at Mountain Good as well called Elements of Agile. And one of the things we learned early on in doing that was you would pull the data from the survey, from actually asking them. But then before we present it back, we always have a coach who kind of does interviews as well, and then manually can shift and adjust things. And one of the things I've learned as being one of those coaches who does that is if there's something that's negative that's said, if there's, you know, we give like a five point scale, you know, five is really great, one is terrible, and you know, what number is it? If it's a little bit over into the negative side, you never get anything that's like all the way over at one, right? Nobody ever comes back to you and says, that's terrible. Scott (04:44) you Brian (04:46) but they will say, that's a three or that's a two. If it's a two, that's severe. That's kind of what I've learned is two is severe, three is bad. And you kind of have to shift those things over one notch to say, people are, their niceness are entering into this and they don't want it to be, they don't want it to look too bad. They don't know how it's gonna reflect on them. They don't know how it's gonna reflect on others. And so they don't want it to look Scott (04:50) Yeah. Okay. Yes. Brian (05:15) too bad, so they tend to like skew it a little bit towards the positive. Yeah. Scott (05:20) Yes, and the thing I think is good from that so one I keep coming back to you know self preservation this world kind of wired for this and someone was mentioning recently It's you know, shouldn't say people are selfish. We should say they have self in the center So if I'm gonna I'm just with you like if I'm gonna give feedback I'm honestly just pass facts or for those listening. I think it's totally fine say well Is it really worth it for me to say something that I'm going to have to end up explaining if a manager figures out that was me that said it because I'm the only one working on that project or whatever, right? In some ways, you're like, no, it's not worth it. I'll just kind of gently say it's not going great. Like you said, it's almost like that bell curve you got shifted over because, the professor's like, there's only, I'll only give out two A's each semester because that's truly exceptional. And so it moves it. It's a little like that. But then when you and I were talking earlier, you mentioned that conflict quadrants. And I thought that was really great because I think that's a clear structure that people could refer to as well. It's kind think about how they have interactions not just at work, but seriously in our other relationships. thought I was looking at like, man, this is so fitting. So I just thought that was a good tool to share as well. Brian (06:18) Yeah, it's interesting to see how that kind of affects people and how that affects their answers and how it affects how they're reporting. And there's a crossover here as well, because I know if you've listened to this podcast for a while, last year I did a talk on conflict management and kind of how to navigate that a little bit from a team lead or a Scrum Master kind of perspective. And it's a very sticky area that I think there's not enough training and there's not en

    33 min
  3. 22 JAN

    #131: Lessons from Modern Agile with Joshua Kerievsky

    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 Poppendiecks 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, wel

    32 min
  4. 15 JAN

    #130: Be the Change: How to Drive Impact Without Authority with April K. Mills

    Ready to spark real change in your organization? In this episode, Brian Milner sits down with April K. Mills, founder of Engine for Change, to reveal how anyone can become a powerful change agent—without waiting for permission. Learn how to drive meaningful change, navigate resistance, and reignite Agile practices with strategies that actually work. Overview In this inspiring episode of the Agile Mentors Podcast, Brian Milner talks with April K. Mills, CEO of Engine for Change and author of Everyone is a Change Agent, about what it truly means to lead change. April explains how effective change agents focus on clearing obstacles rather than forcing compliance, and why fostering curiosity, empowerment, and collaboration is key to sustainable change. From navigating corporate roadblocks to revitalizing Agile practices, April shares actionable insights and tactics to help you take control and make a lasting impact—whether you're in a small startup or a global enterprise. References and resources mentioned in the show: April K. Mills Everyone is a Change Agent: A Guide to the Change Agent Essentials by April K. Mills Change Tactics: 50 Ways Change Agents Boldly Escape the Status Quo by April K. Mills Certified ScrumMaster® Training and Scrum Certification Mountain Goat Software Certified Scrum and Agile Training Schedule 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. April K. Mills is an engineer-turned-change-evangelist and author of Everyone is a Change Agent and Change Tactics, empowers individuals and organizations to thrive through change using her proven Change Agent Essentials. With a passion for turning ideas into action, April helps people drive meaningful change with the time, title, and budget they already have. Auto-generated Transcript: Brian (00:00) Welcome in Agile Mentors. We're back for another episode of the Agile Mentors Podcast. I'm with you as always, Brian Milner. And today I have April K. Mills with us. Welcome in April. April K. Mills (00:11) Thanks for having me. Brian (00:13) Very happy to have April with us. April is the founder and CEO of an organization called Engine for Change. That's engine-for-change.com. That's her website. She's also an author. There's a book that she put out called, Everyone is a Change Agent, a Guide to the Change Agent Essentials. And that's what we wanted to have her on to talk about today with a little bit about being a change agent. Now I shouldn't say from the outset, April is a request. We had a listener request for April to come on. And I always love that. I always try to push those people to the top of our list and get them on as soon as possible. And it was such an interesting topic. I thought this would be just a really great way to have a great topic to have early in 2025. So April, let's start with just trying to understand when we say change agent, how do you define that? What do you mean by change agent? April K. Mills (01:09) Yeah, a change agent is someone who takes action to bring about the change they want to see in the world. So rather than waiting for a boss or a corporate program or somebody from HR to come in and say, hey, let's improve this process, the change agent sees the need for a change and takes action. And the big thing I talk about in my books and my work is the difference between what typically happens when somebody sees a need for a change in an organization where they decide, I'm gonna go get a boss to go make everybody do my idea. I call that driving people. And I draw the contrast with that and driving change where you choose the change for yourself and you clear the obstacles for others to choose it too. And I love talking about that with Agile audiences especially because Agile is a change agent movement. of folks who want to drive change. I see a better way to create this product and I want to be part of it. And that's always what's drawn me into the agile space. Brian (02:13) Yeah, that's awesome. Yeah. And it is a big change, right? To think about the dynamics of someone kind of sitting back and saying, yeah, I see something that needs to be done. I see something that should be a different way, but you know, who am I to say anything about this? Who am I to do anything about versus the person who actually takes action and does things. So that kind of leads to a question about change agents. What kind of skills or traits do you think are really helpful or beneficial to someone to be a better change agent. April K. Mills (02:46) Well, the key is that difference between driving people and driving change. It's not what degree do you have, it's not how long have you been in the industry, it's not are you a people person, are you more focused on the data or some of those factors that we usually like to talk about. It really is, are you willing to take the step yourself first and clear those obstacles and encourage and invite people to join you? Or do you want somebody to make them obey you? And that choice is really the key for anybody to be a change agent. Because so many times we've seen people who might be able to convince the boss, hey, our team should be agile. And what happens, right? It goes on for about three months. The team gets frustrated. The boss gets angry. And then everybody starts to have a reaction when you bring it up, right? I'm sure plenty of the listeners have gone into an organization. If you're passionate about agile and you go, hey, have you guys heard about agile? And they go, ooh. And they make like a face. That's because they've encountered somebody who is driving people. And so that's the big focus I always try and talk with people about is can you show up with that willingness to let people join you and understand what their obstacles are to doing it. Brian (03:57) What are some kind of warning signs or signals you'd look for to kind of recognize whether I'm actually approaching this from a driving people perspective versus driving the change? April K. Mills (04:08) So a lot of times the key is how are you thinking about or talking about in your own head about the people around you or even yourself? We have a tendency to drive ourselves as well. So you can hear it in the language, right? I'm frustrated because so-and-so won't listen. I wish I could get more attention. It's all this sort of vague or... putting the action onto someone else and then complain the action isn't happening fast enough. You can hear it in the language. And so when someone's driving change, you don't hear that. hear, you know, I'm working on, I'm doing, the next thing is my action is I'm going to go talk with this person. I want to understand. I'm going to be curious. And you get this agency, this power coming back into your body almost, and then taking taking the next step from there. And so it's almost easy. You can almost say, well, how far outside your body would you put the power to make this change happen is a useful question to ask people. And if they say, well, it's in the CEO of the company, it's in the industry, it's in my tech lead, but it's certainly not me, well, then you're not a change agent. Brian (05:20) So that brings up a good point because I think I can try to channel what the listeners might be thinking here. I know that in times I've been in organizations where, yeah, you have the ideal, you have the thing that you think is the best thing to do. But because the power dynamics in the organization, you don't really have the power to make that change and you depend a little bit on others that have the power to to help affect it. And so there is a sort of an aspect of, I don't really have the capability or the power to cause this change to happen. How can I still stay with that mindset of driving change versus driving people when I know I need someone else's help? April K. Mills (06:03) Right. So that's a great conversation. And I've started to call it phase one Agile versus phase two Agile. I'm old enough in this space where when I first joined, a lot of Agile was team-based. Somebody on the team or several people on the team said, yeah, I want better. And these are the things that we can do as a team to deliver better. And let's do them together. And then the problem was the teams could do it, but they couldn't scale it. And they were like, if only we could get the senior leaders to pay attention to us, that would solve all our problems. And then you get phase two agile, which was executives buying agile implementations and forcing it down on people. There is one right way and we will do exactly this and you must conform and no other versions are allowed. And then we got the fractures and all of the fights about all of the different aspects. And so we tried it both ways, right? We tried it with the team effort and then we tried it with this thou shalt effort. And I think the key to actually making Agile work across organizations and deeper into organizations is to keep that energy from the team-based Agile to say, we're choosing something better, but it's that piece of driving change. What are the obstacles for others to choose it to? We didn't do that step. We went from my team does it, now the boss should make everybody else do what my team does. And I think that's where we got off track. in

    30 min
  5. 8 JAN

    #129: 2025: The Year Agile Meets AI and Hyper-Personalization with Lance Dacy

    Curious about the future of Agile in 2025? Join Brian and Lance Dacy as they dive into the rise of AI, hyper-personalization, and how teams can balance innovation with customer focus. Plus, discover actionable insights to navigate a rapidly evolving landscape—don’t miss this forward-looking discussion! Overview In this episode of the Agile Mentors Podcast, Brian and Lance set their sights on 2025, exploring how AI is transforming Agile practices and reshaping customer engagement. They discuss the shift from output to outcome metrics, the expansion of Agile beyond IT, and the critical role of leadership agility. With practical takeaways on fostering continuous learning and delivering real value, this episode equips teams and leaders to stay ahead in a fast-changing world. References and resources mentioned in the show: Lance Dacy Accurate Agile Planning Subscribe to the Agile Mentors Podcast 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. Lance Dacy is a Certified Scrum Trainer®, Certified Scrum Professional®, Certified ScrumMaster®, and Certified Scrum Product Owner®. Lance brings a great personality and servant's heart to his workshops. He loves seeing people walk away with tangible and practical things they can do with their teams straight away. Auto-generated Transcript: Brian (00:00) Happy New Year's Agile Mentors. We are back and a very happy New Year's to everyone who's listening. Welcome back for another episode and another new year of the Agile Mentors podcast. I'm with you as always, Brian Milner, and we have our friend of the show for our annual kind of tradition now. We have Mr. Lance Dacey back with us. Welcome in, Lance. Lance Dacy (00:23) Thank you, Brian. Happy New Year to all of y'all. Happy to be setting this tradition. think it's two times now, so we'll just call it a tradition, but I love it. Thank you for having me. Brian (00:32) Very glad to have you here. The tradition we're referring to is that we like to take the first episode of the new year and just take a pause and kind of look ahead a little bit. What do we see coming up? What do we think this new year is going to be like? Obviously, it's a year of change. Here in the US, we'll have a new president that comes in. I'm not going to get into whether you like that or not, but it's new. It's going to be a change. There's going to be differences that take place. And I know there's a lot of differences and changes going on just in the way businesses operate and how things are run and lots of new technologies, lots of new trends. So we just thought we'd take a pause and kind of scan the horizon and maybe give you our take at least on what we're hearing and what we're seeing. And you can see if you agree with these or not. We'd love to hear from you in our discussion forum on the Agile Mentors Community afterwards if you have other thoughts or opinions on this. let's get into it. Let's start to talk about this. So Lance, I guess I'll start. I'll just turn it over to you and ask you that generalized question. Give me one point or one thing that you've been reading or seeing recently that you think is going to be a really important thing for us to kind of be prepared for or look out for here in 2025. Lance Dacy (01:44) Great question, Brian. There's so many things out there, and I thought we could start by looking back a little bit. if we're okay with that, just let's summarize, you what did we see happen in 2024? You mentioned, you know, 2025 is a year of change, absolutely, but 2024 was definitely a different kind of year as far as my experience is concerned and seeing a lot of industry trends that are just popping up out of nowhere. Now we are fans of agility, which means we embrace quick, efficient changes, but there's things going on in 2024 I never predicted Brian (01:52) Yeah, yeah. Lance Dacy (02:19) fast. And so I think we've got to reshape the way that we're thinking about these things. I think the topic of mind, one of the biggest shifts that I saw in 2024 that I think will continue in 2025 is AI. So that artificial intelligence is a big word that we keep lumping into a lot of things. And I just wanted to take a pause a little bit and say, I know everybody's got a little bit different experience about AI, but in particular, as it relates to product development and agile delivery, which is what this show is basically focused on, I thought we could look at some insights of what happened in 2024 with that. And so I think I call us babies at it right now. And I know that may be a bad term, but I have a lot of experience with AI and machine learning and things like that. But as far as the use of it, I feel like we're all a little bit more of babies on how to use it in the day-to-day work that we're trying to accomplish. And I think that comes with learning something. I embrace that. I don't mean that as a downplay, by the way, but that we're all babies. I'm just saying we're less mature about it. We're experimenting with a lot of things. And I don't think that some of the AI is all good. I I embrace it as a thing that's going to help us later on, but... I thought we could just share our experiences of how we've seen this thing manifest itself. I think tools like AI driven, I'm going to use the bad word JIRA, but in place of that, just use any product backlog management tool that you see. And I've seen a lot of organizations not just talk the game of, we use AI for our backlog management, but I'm talking about backlog prioritization, sprint planning capacity. And I believe what's happening is it frees teams up to do more of the... value driven work that we're going to see a lot more of in 2025. So what I mean by that is when we got automated testing and development, if you remember those days, it freed the developers up or the testers, should say, from doing less of the does this thing work to more of how does it feel using it as a human being, you know, automating that. So I've seen things like JIRA, with AI with JIRA and GitHub co-pilots, you know, reshaping the value creation in the teams and eliminating the need of having to do very low level tasks. So what is your thoughts on that and do you have any experiences of that as well? Brian (04:36) Yeah, for sure. There's a couple of things I've found that just kind of some stats I found from some different places. you know, listeners know I'm kind of like a data geek here. want to know where the data comes from and want to make sure it's a, yeah. Yeah. You want to make sure it's a solid source and it's not some questionable, you know, sketchy kind of, well, I asked 10 of my friends and here's the answer, you Right, right. Exactly. Lance Dacy (04:48) Good hand. I love that. or a FBI. Brian (05:02) But so there's a couple of things that came back. One was, I think Forrester is probably a pretty good source of information. They have some pretty good rigor to their process. And they have a thing that they put out every year. This one's just called the Developer Survey. And this is the one that they put out for 2024 that I'm quoting here. But a couple of stats from that that I found interesting. One was, 49 % of developers are expecting to use or are already using general AI assistance in their coding phase of software development, which, you know, maybe higher than most people might think. But it doesn't surprise me too much. I think that's probably kind of what I'm used to it. Understand saying, you know, an assistant co-pilot, that kind of thing. They're not saying 49 % have been replaced. They're saying 49 % are being assisted. by that and that seems about right. Maybe again, maybe a little higher than some might expect, but that seems like not too big of a shocker. Lance Dacy (06:04) Well, the animation too. So when you talk about assistance versus letting it run it, I saw a gentleman on LinkedIn, which is also a good. I wish we could interact more with our users on this call, because I'd love to hear their perspective. But I heard somebody say, let AI write my code. No, thank you. Code is like poetry. It has to be refined over time. It has humanistic qualities. And I was like, man, that's a really good point. But when I try to show my kids how to create a Ruby on Rails app to do an e-commerce site and I type it into chat GPT or whatever tool you use, I was amazed at how quickly it was able to put together. mean, you got to still know the file structures and things like that. But I don't know that developers are just going to say, I was going to write the whole thing. think they're, I think it's saving us keystrokes. I think we talked about that last time as well, but that's an interesting, interesting take. Brian (06:50) Yeah. Yeah. So I thought, I thought that was interesting. There was another, you know, I'm kind of, I'll move around between these two sources basically, but there's another source that I saw where there was a Harvard Business Review article. posted this on LinkedIn a while back, but it was a kind of the source of it was about a survey that they did to try to determine the impact on the job market. And one of the things t

    43 min
  6. 18/12/2024

    #128: Top Lessons from 2024’s Most Inspiring Episodes with Brian Miner

    Missed some episodes this year? Don’t worry—Brian’s got you covered with a highlight reel of 2024’s most memorable moments, featuring game-changing insights from Agile thought leaders and innovators. Tune in to catch up, reflect, and set your sights on a stellar 2025! Overview In this special year-end episode of the Agile Mentors Podcast, Brian takes us on a trip down memory lane, sharing highlights from some of the most impactful conversations of the year. Featuring insights from Agile legends like Mike Cohn, Clinton Keith, Heather McGowan, and more, this curated selection is packed with golden nuggets that you can revisit or discover for the first time. Whether you missed an episode or want to relive the best moments, this recap is a perfect way to close out 2024 and prepare for what’s ahead. References and resources mentioned in the show: #79 Navigating Agile Trends and Challenges in 2024 with Lance Dacy #86 Revisiting User Stories with Mike Cohn #90 Mastering Agile Coaching with Cherie Silas #93 The Rise of Human Skills and Agile Acumen with Evan Leybourn #100 Navigating the Future of Agile and Scrum with Lance Dacy & Scott Dunn #111 Adapting to the Future of Work with Heather McGowan #120 Agile in Gaming with Clinton Keith #123 Unlocking Team Intelligence with Linda Rising 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. Auto-generated Transcript: Brian Milner (00:00.622) I'm Brian Milner and this is the Agile Mentors Podcast, a show about both the personal and organizational journey towards agility. My friends and I will be sharing with you what we've collectively learned from seeing thousands of companies Agile implementations, apparels and pitfalls, as well as the secrets to success. We'll share our personal in the trenches experiences so that you can apply what we've learned in a practical way in your careers. We also hope to hear and learn from you as well. If you're like us and are always in search of better ways of working together, you're in the right place. Join us, mentor, and be mentored. Let's get started. Brian Milner (00:53.288) Welcome in Agile Mentors. We are back for the final episode of 2024. Believe it or not, we have reached all the way to the end. You might be thinking, wait, there's a few more weeks left. Yeah, there's a few more weeks left, but the next release date would have been on Christmas Day itself and the one following would have been on New Year's Day. So we're gonna take two weeks off to be with our families after this episode. And we encourage you to enjoy that time, take the time with your family as well and friends, and truly wish you the best over that time period. But before we get there, we do have one more episode for you. We thought what we'd do for today's episode might be tiny bit different than normal. In fact, I don't think we've done anything like this before. What I wanted to do is, since it is the last episode of the year, is to look back over the past year and play you some portions of some of the really fantastic discussions that we had over this past year. Just pull out a handful of these to talk to you about. If they sound interesting to you, maybe you can go back and take a listen to those episodes. So let's get right into it, because I don't want to waste time setting it up any more than that. For starters, I want to go back to something that's now kind of a tradition for us, and the next one you'll hear from us after this episode will be the continuation of that. The beginning of this year in 2024, we started things off and we kicked it off with friend of the show, Lance Dacey. And that episode was really about looking forward into 2024. And for us to talk about what we maybe thought was coming and what we saw in the future, and then trying to somehow make some predictions or give some advice about how we might be better prepared for it. And one of the areas that came out in that discussion was really talking about how leadership affected an Agile transformation and Agile with the culture of an organization. So I'll play you a little clip here from Lance's discussion. One of the thoughts that he had in that episode, really talking more about how we need to go to the next level with our organizations and with the leadership in our organization. Take a listen. We've been trying to scale Scrum and Agile for a long time and we've written the practices on how to do it. Brian Milner (03:13.23) but we're not allowing the people to practice that. You know, just got through coaching. My youngest son is in fifth grade and we coach his football team. It's like, we're going to sit down and tell you during this play, here's the stance that you take to block. You're basically a robot. Do everything that we say, even if you don't understand it, because the whole scheme for that play is built on everybody doing their job exactly as prescribed. But as you evolve into professional football or high school football, they've learned so much about those mechanics. that's really fun now because they've got the IQ to respond to what's in front of them. That's agile. And that to me is what we have to start learning in organizations, is we know how to run the play at the team level, but how do we build up the people to run the play correctly in challenges when there's adaptations that need to be made? And a lot of times management and leadership is the suffocating part of that where they don't allow for that. It's always interesting to go back and look at those conversations that we have at beginning of the year. and see kind of how it played out. Were we right? Were we wrong? So if you're interested in that, check out that. That was just episode 79 was the first one that we did in 2024. Next up, I'm gonna jump to episode 86. This was one with our very own Mike Cohn. Mike had come back on because quite frankly, we've had for many years a set of user stories that were sample user stories that you could come to our website and download just as a resource for people if they wanted to see what... samples of user stories look like, try to imagine what that would look like in their particular context. So that's why we had this collection of user stories. Well, Mike went back to re-edit those recently, and then he took kind of another look at it and had forced him to kind of reconsider some things, wanted to share some thoughts about those new ideas and thoughts he had about user stories, just in re-examining ones that he had put together previously. So in this next clip, what you'll hear Mike talk about is really kind of a controversy maybe just his own controversy internally, but kind of a shift that he had over the years and really the template itself for a user story. So take a listen to this. I had a bunch of slides. I looked at them a few years ago to confirm this. I looked at them and they all said, I want to blank, right? And it was what the user wants. And sometimes it's not what the user wants. So if you look at slide decks that I create today, they all say, I. Brian Milner (05:36.866) They don't say I can, they don't say I want to, they just say I, and then you fill in the verb. For example, as user, I am required to enter a strong password. I don't want to enter a strong password. I want to type in my dog's name and let the system know it's me, right? So I am required to enter a strong password that doesn't fit with I want to or I can. I can enter a strong password? Well, that doesn't really help. I don't want to. I can enter a strong password. I can enter a weak password. Is that possible? So I do think there's problems with I can, but I leave all of that out of the template and I let the situation determine what that verb should be. Always an interesting conversation there with Mike Cohn. Very, very lucky and fortunate to have him come on usually multiple times per year. And that was just one of the times that Mike came on our show this last year, but really, really interesting stuff there about user stories. If that's something you're interested in, I encourage you to check out that. That was episode 86 with Mike Cohn on user stories. Now we're gonna jump ahead to episode 90. Episode 90, we had a friend of mine, Sheree Silas, come on. Sheree is a very authoritative, knowledgeable person on Agile coaching. In fact, she is the person that I most likely am going to point you to if you come to me and want to find out more about Agile coaching. She has some really great classes and other things that she teaches. And we had her on to talk about Agile coaching, obviously. And one of the things that came up is something that I hear sometimes in classes that Some of this coaching stuff you talk about sounds a little bit like counseling a little bit. Is there a crossover there with counseling? Is this a counseling job? So take a listen to what Shree had to say in response to that question. As an adult coach, you are not an organizational psychologist. You are not a counselor. You are not an organizational therapist or any of those things. That is not the job. The job is consulting, mentoring, training. and some coaching, helping people how to learn how to negotiate, learn how to collaborate, learn how to have good, healthy conflict. And there's helping them to get the business re

    24 min
  7. 11/12/2024

    #127: Agile Strategies for Job Market Uncertainty with Mark Kilby

    How do you navigate a bumpy job market with an agile mindset? Join Brian and leadership coach Mark Kilby as they explore practical strategies for staying prepared, leveraging your network, and taking ownership of your career during uncertain times. Overview In this episode of the Agile Mentors podcast, Brian Milner and Mark Kilby explore how to approach the challenges of today’s unpredictable job market with an agile mindset. Drawing on insights from Mark’s extensive career as a leadership and career coach, they discuss how preparation, adaptability, and proactive networking are essential to staying ahead. Mark emphasizes the importance of treating your career like a product, continuously iterating and inspecting trends to navigate change effectively. The conversation also delves into the power of maintaining strong professional relationships, keeping your resume and LinkedIn profile up to date, and using experimentation to explore new career paths. Whether you're facing a career transition, considering your next step, or simply looking to stay prepared, this episode offers actionable advice to help you take ownership of your professional journey. References and resources mentioned in the show: Mark Kilby From Chaos to Successful Distributed Agile Teams: Collaborate to Deliver by Johanna Rothman & Mark Kilby Advanced Certified Scrum Product Owner® Advanced Certified ScrumMaster® Mountain Goat Software Certified Scrum and Agile Training Schedule 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. Mark Kilby is a leadership and career coach specializing in helping leaders and teams thrive in complexity. Passionate about building more inclusive and effective organizations, he draws on years of experience guiding professionals through organizational change, remote work transitions, and sustainable growth, all with a focus on fostering trust, collaboration, and long-term success. 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 with you as always Brian Milner and today I've got a friend that I have seen talk several times at conferences, we were talking, I don't think I've actually crossed paths with him personally yet, but Mr. Mark Kilby is here. Welcome in Mark. Mark Kilby (00:21) Thank you, Brian, and glad that we finally had a chance to meet virtually face to face at least. Brian (00:26) Right? Right? Yeah. And today's world, you know, that's actually saying a lot. You know, that's kind of the default. Mark is a leadership and career coach and has been, you know, a speaker at multiple Agile conferences over the years. He has a book that he co-authored called From Chaos to Successful Distributed Agile Teams. And he has spoken on lots of different topics. Mark Kilby (00:31) Yes it is. Brian (00:51) But when we talked about having him on, we talked about a topic that I know is very topical here. For some of you, maybe, know, kind of right in the meat of where you are at the moment, but really starting to think about this bumpy job market a little bit and how to navigate that with an agile mindset. You know, this agile stuff is not just stuff we talk about in working with a team, but it actually is a way of thinking about you know, doing anything. give me kind of your description there, Mark. When you think about, you know, navigating a bumpy job market with an agile mindset, how does that look different from others? Mark Kilby (01:27) So, well, it. The best way to think about this is whether you get this out of college at career placement or you're working with a career coach later on, it's always plan out your route and just follow the steps. Well, it's kind of hard over the last couple of years to say what the right steps are because so much has happened. And you and I were talking just before we hit the record button about one of the things that gets a little bumpy here in Florida, and we call those hurricanes. And I've learned over the many years living in Florida that you can prepare for hurricanes, but you can't prepare for exactly what happens. And so it's kind of the same way these days with our careers. You can maybe get certain certifications, you may get the right resume, the right LinkedIn profile, but if... If you're not paying attention to how the market shifts, and I think many people have been caught off guard with the latest market shifts, you can be in a world of hurt. how do do the prep to weather that storm? So that's kind what I'm focusing on these days. Brian (02:42) That's awesome. That's awesome way to look at it. Cause I think you're right. know, like I know I personally have gone through a couple of, you know, layoff periods in my career and, you know, it's never something when it hits, well, at least I shouldn't say this in my experience, I absolutely were completely prepared for, they were a little bit of a shock when they happened and Mark Kilby (02:51) yeah. Brian (03:05) first one much more so than the second one. I think you learn something from each time something like that happens. But you mentioned kind of the way the market is shifting and the way things are changing a little bit and trying to be prepared. So I wanna follow that for a little. So when you talk about navigating kind of a bumpy job market and the shifts and being prepared, how do you prepare for the unknown? For things that you don't really know what's coming or you don't really know how things are shifting. How do we do that? Mark Kilby (03:38) Yeah. Well, it's paying attention to some of the longer term trends. mean, 100 years ago, know, kind of fall into the hurricane example. We had no way to predict these. And now we've got a little better way. have models to kind of guess and it's still guessing. So, but at least we have a sense of, OK, how big is it going to be? You know, how big is the change that's going to happen? How do we prepare for it? Do we stay in place? Where we're at? Is it time to move and do something else? So it's kind of the same way with our careers these days. I'm gonna guess, not everyone's gonna have the visual, but with the amount of gray on the podcast right now, you could probably relate to this. Our parents probably stuck in the same job. most of their life. I learned early on, especially in tech, the changes that happen rapidly. Matter of fact, the place where I went as a summer intern shut down the next year. The whole plant went poof. But my parents were like, how can you? It's such a great place. This company's been around for decades. But I could tell that the winds were changing. Something was shifting there. So I learned to look at, right, how is the business doing? How is the market doing for the business? And what does that mean for me? So it really helps that we kind of build up our own little model to predict, you know, how is my job going to be here in the next year or so? Even five years ago, I saw early indicators that Azure coaches, scrum masters, we're going to be at risk. But the job market was going to turn. think several people could tell that. But I mean, we had so many that were going into that, that the set of roles and we were also, you we we were seeing some failures as well as successes with transformation. And I remember, so I actually had Ken Schwaber in my, as my my Scrum instructor, I remember him saying, know, Scrum will not solve your problems. It'll make them highly visible. But guess who gets blamed? The person who made it visible. you know, as, as agile coaches and Scrum masters, you know, were the, those folks in particular are always navigating a tightrope. You know, what, what do you, you know, what do you make visible, both the good and the bad? And if, if you're dealing, Brian (05:55) Yeah. Right. Mark Kilby (06:17) with cultures that are more focused on short-term kind of improvements and not looking at the longer term. How are people staying engaged? How are the steam aligned so they can do to deliver business value? You know, if that's not a focus of the organization, then it's that job, that role is going to be probably misunderstood and was. And so when things start going bad, fingers start getting pointed. It's like, okay, maybe we don't need these folks. And we've seen that for the last couple of years in particular, but we were getting early indicators well before that, well before the pandemic hit. So that shift was gonna happen. So we can model some of this is my point. Brian (07:01) Yeah. I like that. Go ahead. Well, I was going to go straight to that. I I like the comparison there with the hurricane. And I was thinking as you were talking about that, why are we better at it now? I would kind of presuppose it's because of the amount of data. But the more data we have, over the years, the better we are. And that if we've suddenly, magically, for whatever reason, lost all our historical data of hurricanes and what they do, then I would imagine we'd be back to square one of not really being able to predict very well about where they go. So translating that over into our careers, I love that comparison. And I love what you're pointing to to say, you can see indicators, can look at the trends, you can

    31 min
  8. 04/12/2024

    #126: Mastering the Scrum Master Role with Gary K. Evans

    What does it take to be an effective Scrum Master? In this episode, Brian Milner and Gary K. Evans, author of The Effective Scrum Master, explore the nuanced role of Scrum Masters, the importance of people skills, and the shift from efficiency to effectiveness. Overview Join Brian Milner as he chats with Agile coach and author Gary K. Evans about the essential qualities of an effective Scrum Master. From fostering self-organizing teams to balancing proactive leadership with people-centered strategies, this conversation unpacks the skills and mindsets needed to thrive in the role. Whether you’re new to Scrum or a seasoned pro, this episode offers fresh perspectives and practical advice for taking your Agile expertise to the next level. References and resources mentioned in the show: Gary K. Evans The Effective Scrum Master: Advancing Your Craft by Gary K Evans   Join the Agile Mentors Community Mountain Goat Software Certified Scrum and Agile Training Schedule Certified ScrumMaster® Training and Scrum Certification Advanced Certified ScrumMaster® 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. Gary K. Evans is a seasoned Agile Coach and author of The Effective Scrum Master, with over 30 years of experience transforming Fortune 100 and 500 companies through Lean-Agile practices. Known for his expertise in building high-performing teams and training over 15,000 professionals, Gary brings a unique focus on people-centered solutions to complex organizational challenges. Auto-generated Transcript: Brian (00:00) Welcome in Agile Mentors. We are back and it's another episode of the Agile Mentors podcast. We're getting towards the end of the year. I am here with you, as always, Brian Milner. And today I have a very special guest with me, Mr. Gary K. Evans is with us. Welcome in, Gary. Gary (00:17) Thank you, Brian. It's great to be here. Brian (00:19) Very glad to have Gary with us. Gary is an agile coach. He's a lean consultant. He owns his own company called Evanetics, but he is also the author of a newly published book that came out this summer. It's called The Effective Scrum Master. And it really is a comprehensive guide. It's a really interesting read. So I thought we'd have him on to talk to us about. what that means, an effective scrum master. So scrum master is this episode, I think it's gonna be really a special one for you. So Gary, let's start with that question. When you say an effective scrum master, what is an effective scrum master? Gary (00:56) In my experience, I've worked with a lot of Scrum Masters who go through the motions, they understand the events, they focus on how to run these Scrum events. But the teams flounder and they struggle with what should I do next? How do I anticipate things? And the Scrum Masters themselves often get very frustrated. One of the complaints that I hear, especially from early to mid-career Scrum Masters is I have this anxiety. How do I know that my team is operating as efficient, as efficiently and effectively as they can because they focus so much on efficiency. So this idea of effectiveness really is much more important. In fact, John Kern, one of the co-authors of the Agile Manifesto, who wrote the foreword for my book, he focused in on that word effective because we spend so much of our energies trying to be efficient. that we aren't accomplishing what we need to do, which is to build self-organizing, mature teams. And that's really the focus of my book. Brian (02:01) That's an awesome distinction, I think, because I like that a lot. There's a conversation that I will have sometimes in class about how that drive or search for trying to be not effective, sorry, what was the other word that you used? Efficient, sorry, sorry, just slipped my mind, ADHD. But the efficient kind of quotient there I think is... Gary (02:18) Efficient. Brian (02:27) something that in business in the business world today is a highly visible term. It's something that everyone seems to think is needed. But, you know, that really dates back to sort of the assembly line and efficiency experts that would stand behind you with a stop clock and try to get you to do something, you know, point two seconds faster so that it would total up to, you know, more productivity over the course of the day. But that's not the kind of work we do. Gary (02:56) I love the fact that you've mentioned that that was really the Frederick Winslow Taylor scientific management approach. And it was very much based on this idea of efficiency. But I have seen so many teams and as an agile coach, I've had multiple experiences of teams that are very, very efficient at going in the wrong direction entirely. They've lost their focus on true north. They don't understand what it is they're actually supposed to do. They think that the Scrum Guide, 14 pages in the Scrum Guide, is their Bible. And that's all that they need to know. And nothing could be further from the truth. Brian (03:37) Yeah. Yeah. And to me that, you're talking about efficiency versus effectiveness. You know, if we were a company that was trying to create a new drug to cure some disease, you know, I want effective. I don't want efficient. I don't want someone, I don't want to produce a million pills that don't work. I want to produce, you I'd rather produce one that works, you know. Gary (03:59) Exactly. Brian (04:05) And that seems to be kind of something that I think a lot of teams are missing today. Gary (04:09) It does indeed. Brian (04:10) Well, good. I like that distinction. I think that's a good distinction and that's a good place for us to start to think about this role as being kind of more effective. I think that they're sort of, I don't know, I'm kind of curious what your take is on this. Is it a marketing problem? Is it an education problem? Why is there so much confusion, I think, about what a scrum master, what a good scrum master is? Gary (04:41) That's a really deep and broad question. Part of it is that in the beginning, when Scrum was introduced into the community and was just beginning to become known, there were two attributes of Scrum Masters that were repeated again and again and again. That was you became a servant leader for the team and you removed impediments. Brian (04:44) Just a light casual one here. Gary (05:09) Unfortunately, most people stopped at that point. And they didn't realize that this, the Scrum Master role, and I'll admit, I take a very expansive view of the Scrum Master role because I've been doing this since 1993, basically, 1994. And I've learned through making lots and lots of mistakes. And the idea that All we have to do is be a servant. Well, what does that mean to be a servant leader? Nobody ever really defined it. I actually wrote an essay a number of years ago on what it meant to not be a servant leader so that I could understand by contradiction what it was that I should be doing. I called it the top 10 scrum master crimes. And really, a lot of them really had to do with crimes because it's very easy for a scrum master to start to merge into making decisions for the team that the scrum master should not be making. Now, there are times when a scrum master should direct the team, should make decisions for the team if the team is not qualified to make certain decisions because they're just too new. But this idea of being a certain leader There's so much more to that. In my expansive view of the Scrum Master role, it is not a process role first. It's a people role. And to be an effective Scrum Master, you have to be an effective people person. I've worked with so many teams and coached Scrum Masters. Scrum Masters just did not like people. They weren't people persons. And the teams responded accordingly. So. A lot of the coaching that I do with my Scrum Masters is you've got to reach deep. You've got to be able to get into people's lives rather than hold them off, you know. And so a lot of it has to do with that. Brian (07:10) I love that. I wholeheartedly concur with that. I've talked on this podcast a little bit about how it seems like we've lost the focus of that first line of the Agile Manifesto, individuals and interactions over process and tools. And I mentioned when I go to Agile conferences sometimes, I feel like the majority of the talks that I see and hear are process and tools talks rather than know, individuals and interactions talks. And I can't agree more. I think that's really a focus for us as Scrum Masters is the individuals and interactions portion, the people portion. You know, our teams are made up of people and if we're not good with helping understand how people work together, we're kind of really missing the value of what it is we deliver to the teams, I think. Gary (08:04) And Brian, the people are all different. And to have a one size fits all because the scrum guy says do X, and Z. Well, that'll work for some people, but it will not work for others. And it may even build resentment within the team because they feel that they're being treated unfairly. The focus, the theme of my book and the reason I wrote the book. Brian (08:06) Right, exactly. Gary (08:30) is that I had seen so many teams that were floundering under Scrum Masters who really didn't

    35 min

Ratings & Reviews

4.7
out of 5
11 Ratings

About

The Agile Mentors podcast is for agilists of all levels. Whether you’re new to agile and Scrum or have years of experience, listen in to find answers to your questions and new ways to succeed with agile.

You Might Also Like

To listen to explicit episodes, sign in.

Stay up to date with this show

Sign in or sign up to follow shows, save episodes and get the latest updates.

Select a country or region

Africa, Middle East, and India

Asia Pacific

Europe

Latin America and the Caribbean

The United States and Canada