Podcasts about agile coaches

Agilität in Deutschland? Klingt erstmal gut.Fühlt sich aber oft an wie: „Neues Korsett – alte Probleme.“In dieser Folge spreche ich mit Dr. Stephanie Puckett, Organisationspsychologin und Autorin von gleich mehreren Büchern zur agilen Transformation. Gemeinsam sezieren wir, warum viele Unternehmen auf Agilität setzen – und trotzdem keine PS auf die Straße bringen.Du erfährst:✅ Warum psychologische Sicherheit wichtiger ist als das perfekte Framework✅ Weshalb Agilität kein Prozess-, sondern ein Transparenzproblem ist✅ Wie Du die echten Kosten von Transformation erkennst – monetär UND mental✅ Und warum viele „agile Change-Prozesse“ eher Dressur als Empowerment sindReal Talk. Ohne Buzzword-Gelaber. Ohne Dogma.Dafür mit Klartext, Haltung – und einer klaren Vision:Was Agilität in Deutschland WIRKLICH braucht.

Is the Party Over For Scrum Masters and Agile Coaches? Over the past decade, agile adoption in organizations has seen an upswing. Large enterprises—banks, insurance companies, automakers, and many others—have all been at the forefront of launching agile transformations to achieve business agility—the elusive elixir. The promise of increased flexibility, faster delivery, and enhanced collaboration across teams is almost impossible to resist in today's competitive world, where markets change rapidly, bringing risks and opportunities.How to connect with AgileDad:- [website] https://www.agiledad.com/- [instagram] https://www.instagram.com/agile_coach/- [facebook] https://www.facebook.com/RealAgileDad/- [Linkedin] https://www.linkedin.com/in/leehenson/

BONUS: Maria Chec Explores the Divide Between Agile Leaders and Practitioners In this BONUS episode, we explore Agile leadership with Maria Chec, author and host of Agile State of Mind. Maria shares insights from her analysis of Miro's Agile Survey, revealing a concerning disconnect between how Agile leaders and practitioners experience agile methodologies. We explore the roots of this divide, discuss practical approaches to bridging the gap, and consider the implications of recent industry developments like the PMI-Agile Alliance merger. Maria offers valuable perspectives on creating truly collaborative environments where frameworks serve the teams, not the other way around. The Disconnect Between Leaders and Practitioners "Practitioners feel pressured to comply with agile practices when they don't seem to add value." Maria highlights a stark divide revealed in Miro's survey of 1,200 agile practitioners and leaders. When asked if agile is living up to its original values, leaders and practitioners gave drastically different responses. For example, 69% of practitioners felt processes and tools overshadow individuals in their organizations, while only 43% of leaders shared this view. Similarly, 58% of practitioners believed documentation was prioritized over delivering final products, compared to just 39% of leaders. These disparities point to a fundamental disconnect in how agile is experienced at different organizational levels, with practitioners often feeling frameworks are imposed rather than collaboratively implemented. When Frameworks Become the Problem "The framework is too rigid... The framework is too complex... We have to change too much to use the framework." The issue isn't with agile frameworks themselves but how they're applied, Maria argues. Leaders often implement frameworks like SAFe without sufficient practitioner input or adaptation to organizational context. This creates an anti-pattern of "magical thinking" where companies believe they can install off-the-shelf solutions that worked elsewhere without considering their unique circumstances. The practitioners, who must live with these frameworks daily, experience frustration when rigid implementations fail to address their actual needs. Conway's Law comes into play here – the structure imposed by leadership often doesn't align with how teams naturally need to collaborate based on the systems they're building. The Role of Psychological Safety "Can I really admit that something the leadership made me do is not working for me? Will I be the only one admitting it?" This disconnect reveals deeper issues around psychological safety and trust within organizations. Many practitioners fear speaking up about framework problems, especially when they've just endured yet another organizational transformation. Maria emphasizes that without psychological safety, feedback loops break down, preventing the continuous improvement that's central to agile philosophy. Leaders must create environments where teams feel safe to provide honest feedback about what's working and what isn't, without fear of being singled out or dismissed. Without this safety, frameworks become rigid implementations rather than adaptable approaches that evolve with team needs. Reconnecting Through Gemba Walks "Be there where the value is created and know what's going on." To bridge the gap between leadership vision and practitioner reality, Maria strongly recommends Gemba walks – a concept from Lean and Toyota where leaders go to where value is created. This practice helps leaders understand the actual work being done and build relationships with team members. Maria references Project Aristotle at Google, which found that trust and psychological safety are fundamental to team success. She also notes the importance of leaders articulating a meaningful mission to inspire teams, sharing her experience at a taxi-hailing app where the CEO's vision of reducing urban parking needs made her feel she was "building something for the future." Leaders should regularly spend time where the actual work happens Teams need to understand how their work contributes to a larger purpose Open communication channels must be genuine, not just symbolic In this segment, we refer to Management 3.0 and Managing For Happiness by Jurgen Appelo.  The PMI-Agile Alliance Merger and the Future of Agile "Have we really found better ways? Why are Agile Alliance and PMI merging?" The recent merger between the Project Management Institute and Agile Alliance represents a surprising development in the industry. Maria takes an optimistic view, wondering if this indicates PMI recognizing that agile is truly the way forward. She acknowledges the perception that "Agile is dead" discussions highlight a crisis in the movement, but suggests the merger might be an opportunity to influence project management with agile values. She emphasizes how AI is creating massive changes that require experimentation and adaptation – precisely what agile approaches enable. This industry shift offers agile practitioners the chance to shape how traditional and agile methodologies might complement each other in the future. The merger could be seen as closing a circle or as an opportunity for cross-pollination "Agile is dead" discussions reflect growing pains rather than true failure Rapid technological changes with AI require more experimentation, not less Breaking Down Silos with "Glue Roles" "What are the 'glue roles' that you need in your organization?" Maria introduces her concept of "glue roles" – positions that help break down silos and foster collaboration regardless of what they're called. Whether they're RTEs (Release Train Engineers), Agile Coaches, or Technical Project Managers, these roles can transform organizational effectiveness when focused on enabling teams rather than enforcing processes. She observes that nature constantly changes, yet we expect our companies to remain static. This mindset prevents the adaptation necessary for true agility. Instead, organizations need individuals who can facilitate communication, remove barriers, and help teams collaborate effectively across boundaries. Focus on the function of collaboration rather than rigid role definitions Adapt roles to organizational needs rather than forcing organizational change to fit frameworks Use these roles to foster psychological safety and open communication Learning Through Experimentation "We need to experiment." Looking toward the future, Maria emphasizes the importance of experimentation in the face of rapid technological change, particularly with AI. She notes that while tech professionals are often thought to be early adopters, AI tools like ChatGPT are being embraced across all industries. The accelerating pace of change means we can no longer plan years ahead with certainty – what we use today may be obsolete in two years. This reality makes agile approaches even more relevant, as they embrace change rather than fight it. She encourages agile practitioners to openly discuss how they use these new tools, adapting their practices rather than clinging to outdated methods. The accelerating pace of change makes long-term planning increasingly difficult AI is already transforming work across all industries, not just tech Agile principles of adaptation and experimentation are more relevant than ever About Maria Chec Maria Chec is a seasoned Agile leader, ProKanban Trainer, and creator of Agile State of Mind. With over a decade of experience, she specializes in transforming teams through SAFe, OKRs, and process optimization, achieving remarkable productivity gains. Maria's mission is empowering teams to thrive through collaboration and adaptability. You can link with Maria Chec on LinkedIn and subscribe to Maria Chec's Substack.

In dieser Folge der Agile Transformation Toolbox dreht sich alles um eine Rolle, die in der agilen Welt immer wichtiger wird: den Agile Transformation Manager. Doch was genau macht ein Transformation Manager eigentlich? Wofür ist er verantwortlich – und warum reicht es nicht aus, ein paar Scrum Master und Agile Coaches ins Unternehmen zu holen?

What’s next for Agile coaching? Brian Milner and Andreas Schliep dive into the shifting landscape of Agile coaching, the differences between Scrum Masters and Agile Coaches, and how to carve out a sustainable career in a changing industry. Overview In this episode of the Agile Mentors Podcast, Brian Milner and Andreas Schliep explore the evolving role of Agile coaching, the challenges coaches face in today’s market, and the skills needed to thrive in a shifting industry. They break down the differences between Scrum Masters and Agile Coaches, discuss how to develop a personal coaching style, and emphasize the importance of integrity and resilience. From navigating layoffs to redefining what it means to be an Agile leader, this conversation offers valuable insights for anyone looking to grow in their Agile career. References and resources mentioned in the show: Andreas Schliep Certified ScrumMaster® Training and Scrum Certification Certified Scrum Product Owner® Training 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. Andreas Schliep is a Certified Scrum Trainer and executive partner at DasScrumTeam AG, helping organizations navigate complex projects with agile methodologies. A thought leader and co-author on Enterprise Scrum, he empowers teams—from startups to Fortune 500 companies—through high-impact coaching, training, and a passion for continuous learning. Auto-generated Transcript: Brian Milner (00:00) Welcome in Agile Mentors. We are back here for another episode of the Agile Mentors Podcast. I'm here as always, Brian Milner, and today I have someone we've been trying to get on here for a little bit, and I'm excited to have him here. Mr. Andreas Schliepp is with us. Andreas, thank you for being on. Andreas Schliep (00:17) Thank you for inviting me. Brian Milner (00:19) Yeah, very excited to have Andreas on here. Andreas has been in the community here for a long, time. He's been just really generous with his time and he's mentored a lot of people. He's a CST, a Scrum trainer. He's also a certified enterprise coach. So he has kind of those dual high level certifications with the Scrum Alliance. But he mentioned to me earlier, he's kind of always considered himself a Scrum trainer. But he's also a coach in this group called the Leadership Gift, or there's also another name here that they've used recently, Responsibility Immersion. So that might come to play in our conversation here because we wanted to talk about sort of the future of agile coaching and agile coaches in general. There's a lot of turmoil, there's a lot of upheaval and things that are shifting and changing every day in our profession. So I guess, you know, let's just dive into the topic here. Andreas, how do you see things currently? And, you know, in a broad sense, where do you see them going? Andreas Schliep (01:18) Yeah, so first of all, why am I concerned? So typically I say that I kind of, train coaches and I coach trainers. So most of my work is centered around the path of scrum masters and how they can kind of acquire the necessarily skills and insights to become actual coaches themselves. Or scrum coaches as I would prefer to say it. And that includes a lot of stuff like we want to equip them with facilitation, with training skills, with coaching skills, with systemic observations and other methods. And we've been doing that for a couple of years. And so of course we came across lots of good people, good coaches and good trainers, good consultants out there. And we kind of kept our community open. So it's not like people attend our classes and then we forget them or we only have closer relationships to our corporate customers. It's like we kind of managed to build some kind of little community. People keep coming back and we keep chatting about what's going on, what's happening in their environment. And as a mainly training focused company, one of the first effects that we notice is that our classes are getting emptier and emptier. So what's going on, especially advanced classes are not that well. So we still have some, well, yeah. basic attendance, but it's not as it used to be. well, a couple of years ago, we had like full classes and everything, and then COVID hit and we could say, okay, so COVID kind of reduced the demand for edutraining. And then the next crisis came and the next catastrophe and the next disaster. But there have also been some structural changes. I think that we are currently experiencing two effects that happen at the same time. So the one thing is that, well, Diana Larsen put it that way, Agile has won. So there's no doubt that organizations employ Agile methods and want to use Agile practices, some of them with, some of them without any clue about what that even means or what Agile thinking or Agile attitude behind it is, but still, there's no shortage on like the use of Agile or the, but there's also no shortage of the Agile basic training or educational videos, content or whatever. So people get lots of more resources than we used to get back then when we had like this one scrum book by Ken Schwabe. So read this and then you went out and said, how do I do that? So. And then came the second book by Mike Cohen and the third book and so on. had to, had all these puzzle pieces coming together where we needed to find our own way and build our proficiency. And now you get a flood of books and stuff going on, which is fine. So the one thing is that of course our profession is developing and it's kind of natural that you will notice some kind of within that. But there's another effect and this is one thing where we scrum trainers can kind of take responsibility for our own contribution. It's the fact that organizations can hire an unlimited number of low-level agile coaches nowadays. There's been no quality control. Anyone who went through a two-day CSM class could call themselves agile coaches and they got hired for lots of money and eventually produced nothing. some of them, some agile coaches or people who call themselves agile coaches even caused chaos. So, and the systems. that they were affecting started to kind of fix themselves and heal themselves from the Agile coaches by expelling those. So, and of course, maybe you have a third effect, which is sometimes it just doesn't work and you blame the Agile coaches. So if you just lay on your couch and you do nothing and your doctor tells you, you have to get moving, you have to get up and get moving and say, yeah, it's a bad doctor because... I still lie on my couch and my health is deteriorating and this doctor doesn't help me. He doesn't give me what I want. What do you want? Yeah, I want just, I would just want a pill that I can swallow that I'm healthy. It doesn't work that way. And then we had those people who were selling those pills, yeah, who were telling people, here we got a, we got a safe way that you can do this. All you need to do is implement this process, hire our consultants. Brian Milner (05:26) Yeah. Andreas Schliep (05:43) We kind of made all the thoughts and the heavy thinking ourselves beforehand and you just need to install it. Here's the roadmap, here's the process manual, here's the 300 page guide. Just do it this way. And this is also detrimental. now we have, I've been talking to many people, many great people, you've been laid off, who are looking for a new orientation. Brian Milner (06:05) Yeah, yeah, I agree. I mean, I think you laid that out really, really well because there's I think you're right. It's kind of a multi effect scenario. There's a lot of things affecting it. And I know I've had conversations with with friends and colleagues about this. And, you know, we've talked a lot about the I think more kind of the second thing that you're talking about, just that and It's sort of a chicken and egg thing because the industry has built up and spread agile concepts through offerings of usually two day classes. You and I both do those quite regularly. And I think we probably both would say that's a very valuable thing. to go through sort of that immersion kind of a couple of days to learn it and get a foundation in it. But there may have been sort of a misconception or it may have been sold incorrectly to say, now you're ready to lead an organization and transforming from zero to 60 in Agile. when you're not, right? I mean, you've got a good grounding. You're ready to begin learning with a team, but it's the first step. There's gotta be some sort of ongoing support system that when you come up against something that you don't really know how to handle, that you have someone to ask. You have somewhere to go to get help and get answers. Even the, you I work with Mike Cohn, I think he's a great trainer. But even a two day class with Mike Cohn, I don't think is gonna make anyone an expert that now you're ready to, you know, take on the huge challenge of cultural change within the organization, you know? Andreas Schliep (07:53) Yeah, yeah, it's like with anything agile, these classes are a starting point or a waypoint and not a designation. It's not the goal. So when I made my driving license, my driving instructor told me, and in Germany you have to spend lots of hours with your driving instructor. And my driving instructor told me gladly, now you can get to practice on your own. He was happy that he didn't have to co-practice with me any longer because I wasn't the best driver. So I actually aced the theory test, but the practical driving was a little more difficult and kind of probably was bad for the blood pressure of my driving instructor. yeah. And that way, but I never thought about this. So the idea was I get the permission or I get the next level to the next step. And the next step will be, I want to learn proper driving. And that's something that you need to do on your own. And with this understanding, we try to kind of provide a path for people to become better scrum masters and agile coaches by kind of revamping the CSP path, the scrum aligns and other things. A glorious project that also failed gloriously. I'm still not entirely sure why, but probably because the Scrum Alliance and many other people failed to understand the similarities between Agile Coach as a profession and the Scrum Master as a role. So they claimed that there were two different things. And I think that's also a structural issue in organizations. Brian Milner (09:16) Yeah. Andreas Schliep (09:25) that they see Scrum Masters and Edge of Coaches as different things. So the Scrum Masters work on the team level and they just know their Scrum and they facilitate the meetings and then they come up with nice cookies for the retrospective so that everybody on the team is happy. And occasionally they take one of the team members aside when they have some issues and help them go through that. That's totally fine, but the Edge of Coaches do the real stuff. release train engineers and the others, do the organizational thing and they don't bother with what's happening on the team level because they need to do the important things on the higher level. And with this attitude somehow fueled by some decisions by Scrum Alliance and other organizations like, yeah, in order to become a certified team coach or certified enterprise coach, you have to kind of prove that you're... had coached like 2000 hours or 2500 hours. But by the way, the scrum master worked. It doesn't count towards this coaching, which is totally ridiculous. So that means the misunderstanding of the role is a structural problem. Another structural problem is that the organizations that would need the most experienced scrum masters, they attract all the rookies. Brian Milner (10:16) you Andreas Schliep (10:34) because they don't even know what a good scrum master would cost like. They have those two day or even less day. I heard about a transformation at a large automobile builder in Germany. They had something like a half day class for scrum master training within the safe environment. And they wonder why they fail. They wonder why they're failing. Brian Milner (10:53) Ha Andreas Schliep (10:54) On the other hand, we have organizations, even here in Germany, they have great leadership and coaching concepts. So they develop the Scrum Masters. They have the finest Scrum Masters ever on such a high level that the teams actually don't need them because the teams also evolved by taking care and taking responsibility for themselves and paying attention to the work. So they're kind of over-coached. So like, I think it was at Rally 10 or 15 years ago. There was a period when the external rally coaches didn't get so many contracts. And so they went inside and coach all the software teams and rallies at Rally. And after three or four months, the software team said, please, please give us a timeout, give us a break. We over coach. It's just too much. We just want to do some work and maybe not get better for like a month or two before we, because it's Brian Milner (11:42) Yeah. Andreas Schliep (11:47) It's hard always to get better and even better and you're so excellent coaches, cut us some slack. So that's so, but this is the structure. So on the individual level, it's just the same as with any major shift in any kind of industry. If your current profession or your current job title doesn't fit any longer, focus on what you're good at and see that you Brian Milner (11:54) Yeah, yeah, yeah, right. Andreas Schliep (12:13) become excellent at that. So that's, it's an old formula. It's an old formula and it can be different things. So I know about some scrum trainers who go and went into software development again, because they said, actually, I'm passionate about software development. I can understand that. I have a developer background as well. So sometimes I'm not that unhappy about taking care of a website and other stuff. It's a nice distraction. But some are really great facilitators. But if they only go out with a label, agile coach, and do not let the facilitation skills and experience shine, then they might get a mis-hired. So we have great personal coaches in there. So people with various skill sets. And if you take a look at the agile coaching growth, we have Biomark, some of them others. Brian Milner (12:37) Right. Andreas Schliep (13:00) You see that it's a vast field. So you cannot expect anyone, maybe the two of us, but you cannot expect anyone to be, not even me, so anyone to be excellent in all these knowledge areas and to be such a light and catalyst in everything. So the idea is to find your own way how you can contribute best. and then collaborate with others in their fields. So for me, the most interesting areas in that field are training and facilitation. Because I think that's the main thing that agile coaches or scrum masters can shine in. Brian Milner (13:41) Yeah, I've always loved, know, Lisa Atkins has that kind of different aspects of a coaching stance. And one of the ones that she had there that I've always loved is the idea of having a signature presence. And I remember when I first kind of encountered that, was, when it kind of sunk in, it was a very freeing idea for me. Andreas Schliep (13:49) See you. Brian Milner (14:01) to, you know, kind of like you're describing there, there's so many different aspects that you could, you know, try to do and you could do well, but it's too much for any one person to do all of it. So that signature presence to me, one of the things that I really kind of took away from that was know what you're good at, right? I mean, there's something about you that you bring from your own personality and your history and and everything that's made you who you are that is unique. And when you can find what that is, then it's almost like prior to that recognition to me, I was almost even a little ashamed that that was where my strength was. And I felt like I had to make up on these other areas that I struggle with or I didn't do as well. But that concept to me, Andreas Schliep (14:47) Mm-hmm. Brian Milner (14:52) kind of help me see, no, there's something that's really unique about how you approach things. And if you recognize that, lean into it because nobody else can offer that, right? Nobody else brings that to the table because that's uniquely you. Andreas Schliep (15:06) Yeah. Yeah. I have to admit, well, we're both with Scrum Alliance and I've been with Scrum Alliance for more than 20 years now. But some of the biggest insights about Scrum and the role of Scrum Master were some things that I actually learned by looking through the Scrum.org certification parts. So just out of curiosity, I started digging into the... Professional Scrum Master Series by Scrum.psm1. Okay, PSM1 is a walking part, so that's no big deal. 50 minutes without preparation, A's are done. Okay, next thing, PSM2, was a little more chilling. Okay, there are some different concepts in the way they address Scrum. And I completely faded PSM3. So that's interesting. So I should have known that. And the point is that... Brian Milner (15:52) Huh. Yeah. Andreas Schliep (15:58) There are differences in the message and the Scrum Master and the Scrum.org framing of Scrum is far more of a leader. So they take far more responsibilities. They are much closer to a sports team coach actually, even taking care of the crew and even throwing people out of the team if necessary. Then the fluffy Scrum Master social worker thing. with no real responsibility always in the background that we appear to propagate sometimes that I even have propagated lots of times. And I see this in my own style as well. So I'm rather strong at the facilitation part and working from the side of the background of people. But sometimes I see, and I think that's a big challenge for many agile coaching scrummers out there. Brian Milner (16:32) Yeah. Andreas Schliep (16:48) When it comes to the situation where I should take the lead, I'm still reluctant when I say, okay, yeah, somehow I don't want to step under the feet of others. I want to give them room. I want to be in my facilitator stance because I love that stance and that's my personal brand or whatever. The calm way and listening to people and integrating all voices. But all of a sudden, I encounter situations where say, my voice first. So, yeah. So let's do it that way. this week, I kind of stopped the client workshop in the middle. I said, so yeah, what is that? here you booked me for the entire day, but I noticed that you're very upset about important stakeholders missing. Brian Milner (17:19) Yeah. Andreas Schliep (17:39) I also noticed that you don't see the point in reiterating some other concepts that I prepared. you could use these methods and then talk to your stakeholders, but you rather want me in this room with your stakeholders and have this discussion together. So let's just stop this now. And I offer you a gift. I will come back for another half of days. So we stop this half day. You can use your time for something else. I can use my time for something else. And then I come back, but only if you have your manager in here. So if you bring your boss, I will come for another half day and then we finish this and deal with these questions. And they were kind of impressed that I was offering them. But where's the point? I needed to change the mode. I couldn't stay and I think this is something Brian Milner (18:20) you Yeah. Andreas Schliep (18:29) which is another great opportunity for Scrum Masters or agricultural coaches to say, what if I stepped into this leadership role? Brian Milner (18:37) Yeah. Yeah, that's a great kind of approach to it. And I know we've had some similar things at Mountain Goat as well, where we've worked with some clients and you kind of show up and you start to get into the things. Or even sometimes in the kind of just pre-work calls where you're trying to arrange things and talk through what is it you want to get out of this. And you sort of get that feedback and understanding that this is really just checking a box, right? They wanna check the box that they did this, but really making the change. No, they really don't wanna make the change. They really don't wanna have to change what they do on a day-to-day basis. you kind of are, as a coach or a trainer, you kind of get to that decision point where you have to say, at what point do I call this out? At what point do I say, you know what? You're gonna waste your money. Right? mean, I can come and do this. I can take your check. I can go away, but it's not going to make any difference. And you're not ready for it yet. and, that's, that's always a really hard decision. When you get to that point, when you realize, you know what? It's not serving your needs for me to, move forward here. You know, it's, it's, you're not going to be happy with me. Andreas Schliep (19:48) Yeah. I think it's important to maintain the personal integrity. the whole point about resilience is that you kind of are able to change while you maintain your own identity. So the path that you are trying to. And this change can mean a lot of things. So if someone would tell me, you've got to stop with Scrum now because Scrum is now forbidden everywhere. I would kind of dig into the facilitation. So I joined the IAF, the International Association for Facilitators. I don't have a credential there yet, but this is something if I would go into more facilitation gigs, this would be very interesting for me. I also became a coach in the responsibility program with Christopher Avery. First of all, I think that was a nice addition to my training or to my work with leaders. But then I also discovered that this is kind of navigation aid for myself. So whenever I do something, I start with what do I want? So what do I want? How do I want the situation to evolve? What is the outcome that I want to achieve? And how am I blocking myself from that? So what is kind of my inner blocker that prevents me from getting what I want? Brian Milner (21:03) Yeah. Andreas Schliep (21:04) So I could also talk about external blockers, but these external blockers are sometimes just things on my path that I choose to say, okay, I can't go there because there's this blocker. And when I found these two things, so what do I really want and what is blocking me? I can go and make a decision. I can confront myself. And with this ability, I'm pretty sure that I'm able to respond to any kind of situation. So, and... whether I pursue the facilitator part further or whether I go into the coaching way. I love to work with groups so that just the one-on-one coaching is not so interesting for me. But these are kind of independent from what I'm doing now, but also based on what I'm doing now. So I can derive lots of good skills and insights and approaches from what I did as a scrum trainer so far, what I have done as a scrum trainer. Brian Milner (21:58) Yeah. Well, I think when I'm hearing and tell me if I'm misquoting this or saying it or misunderstanding, but it feels like there's sort of an element here that, you know, I think a lot of us sometimes, have some kind of a title that we've earned. and we, we sort of inherit from that, set of, activities or things that we feel empowered to do. based on that title. And what it sounds like I'm hearing from you is it should kind of be the reverse. You should think about what you do well and the titles may come and go. They may change the descriptors that people use to describe what you do, it might change, but what you love to do with the activity, what you're good at, that can shift and change a little bit and don't be so concerned with the title. Andreas Schliep (22:45) Yeah, so edge-hired coaches still can keep this kind of title for the tribe to identify a peer group. And I've also joined edge-hired coach camps even as a scrum trainer. because this identification is important to say, okay, I know a couple of people who have different skills or different things who are some more similar to me, but I don't think we should stick to Agile Coach as a job title and only look for Agile Coach offers. But rather go out and see what's out there, what opportunities do we see. Apply for weird stuff. So at the beginning of this year, I applied as a facilitator for United Nations volunteer program and even made an extra language proficiency exam before that because I had to kind of prove that I'm at least at level C1. for this job. I just did it because it was there because this opportunity came through the International Association for Facilitators. I just said, okay, I don't know. They didn't even throw me back. I don't have anything, but I just, I want to apply for this. I want to get this material together. I want to show that I'm potentially able to do this. I will be far too expensive with my current rate, but yeah. And I think anyone currently in the situation as an edge on coach being laid off or looking for another job should kind of step back and go through these steps. So what do I want? What are the activities that I'm really passionate about? Brian Milner (24:13) Yeah. Andreas Schliep (24:13) And the answer might be surprising. So sometimes, it's actually coding. Maybe we'll get back to the basics. Brian Milner (24:19) Yeah, yeah, you're right. I've known a lot of people or I've known several people, I guess I should say, that have kind of maybe migrated backwards. If you think of it in that way, I don't know that's backwards, but migrated to their roots a little bit more, you know, and maybe left training, but went back to doing, you know, managing software teams or even coding just because they enjoy it. And I think that's a great thing if that's... Andreas Schliep (24:41) Yeah. Brian Milner (24:45) brings them happiness, you know? Andreas Schliep (24:47) Yeah, you know, when the whole agile thing started, they came up with a little website and the website says something like, we're discovering better ways to sort fire customers or so. I don't have a probably and helping others to do it. And if even if you go back or if you go to actually start working as a developer again. You still bring the edge of spirit and you still bring the ideas and methods of collaboration. It's going to be so helpful in your environment. Especially with new technologies, AI stuff and remote work and all these things kicking in. Everything looks like it's making your work more difficult. Massive layers like even media firing developers now, not only edge of coaches. So we have... so many disruptions to deal with. And I think that, well, kind of resilient HR coaching tribe stance is helpful in whatever role you fulfill afterwards. Brian Milner (25:43) That's really good. Yeah. Well, this has been great. I really enjoyed the conversation. Sometimes you're not really quite sure where we're going to end up and where we're going to travel, but I've really enjoyed all the directions we've taken here, Andreas. So I can't thank you enough. Thank you for making time and coming on and sharing your experience and wisdom with everyone. Andreas Schliep (26:00) Mm-hmm. Yeah, was great fun and thanks for the opportunity and I hope that this will help some people find little more guidance, least a little more confidence if they don't find guidance yet. Brian Milner (26:13) Yeah, I agree. Thank you very much. Andreas Schliep (26:15) Thank you.

AI is changing the game for Agile Coaches, Scrum Masters, and Project Managers—but do AI micro-certifications from Scrum Alliance and PMI really bring value? In this episode 66, I break down their pros, cons, and real-world impact. A Deep Dive for Scrum Masters & Project Managers You'll learn:
✔️ How AI is reshaping Scrum, Agile Coaching, […] The post AI & Agile: Are Micro-Certifications Worth It? appeared first on Agile Lounge.

Im Impuls der Woche schauen wir auf die Arbeit von Organisationsentwicklern, Scrum Mastern oder Agile Coaches, für die es essenziell ist, Experimente nicht nur zu planen und zu begleiten, sondern auch Schutzräume dafür zu schaffen – und vor allem sicherzustellen, dass sie bestehen bleiben. Denn Schutzräume sind keine stabilen Konstrukte. Sie werden durch die Organisation selbst immer wieder infrage gestellt, insbesondere durch die bestehende Kultur, die oft vergangenheitsstabilisierend wirkt. Du erreichst uns mit deinen Fragen auf den unten angegebenen Social Media Kanälen, auf unserer Webseite https://www.wir-muessen-reden.net oder direkt an podcast@wir-mussen-reden.net Abonnieren, teilen, Algorithmus glücklich machen! Über positive Bewertungen auf den gängigen Plattformen freuen wir uns natürlich auch. Viel Spaß beim Hören! Dein David & Martin Martin Aigner: LinkedIn: https://www.linkedin.com/in/martin-aigner-865064193 David Symhoven: LinkedIn: https://www.linkedin.com/in/david-symhoven-2a04021a5/

“I was really nervous and scared starting my first [Agile Release] Train. It would have been awesome if I had a mentor or coach initially to help me with that. You have to have mentors in your life. Those areas that I struggled with as I was growing my career, I reflected on ‘how can I make it better for others?' and that's what I strived to do.” In this mentor-focused episode, Adam talks to Sarah Blaesing, an SPCT at TEKsystems who found her passion in tech and determination while balancing her roles as a working mom and military spouse. The conversation covers topics including finding career success by building connections and being willing to take risks; developing and empowering others, especially women, in tech and Agile careers; and how she created a unique academy program that provides newly certified Agile coaches and practitioners with hands-on experience and mentorship. Like what you hear? Connect with Sarah on LinkedIn to learn more about the SAFe Academy at TEKsystems and check out their Agile Transformation Services. Explore SAFe courses here.

In dieser Episode des Agile Transformation Toolbox Podcasts diskutiere ich mit Marc Bleß über die aktuellen Entwicklungen und Herausforderungen im Bereich Künstliche Intelligenz (KI) und deren Integration in agile Arbeitsmethoden. Wir beleuchten die Bedeutung von KI in der heutigen Zeit, die verschiedenen Tools, die zur Verfügung stehen, und die Notwendigkeit, Daten effektiv zu nutzen, um die Vorteile von KI voll auszuschöpfen. Ausserdem diskutieren wir die vielfältigen Anwendungsmöglichkeiten von Künstlicher Intelligenz (KI) im Scrum-Umfeld. Marc Bleß teilt seine Erfahrungen und Einsichten darüber, wie KI die Effizienz in Meetings steigern, das Backlogmanagement unterstützen und sogar bei der Konfliktlösung helfen kann. Zudem wird erörtert, wie KI in Marketingstrategien integriert werden kann und welche Tools zur Automatisierung von Prozessen zur Verfügung stehen. Abschließend wird auf die Bedeutung von Trainings für Scrum Master und Agile Coaches eingegangen, um die Nutzung von KI in der Praxis zu optimieren. Du findest die KI Trainings von Marc Bleß hier: https://agilecoach.de/trainings/ki-fuer-scrum-master-und-agile-coaches/ Liste der erwähnten KI-Tools im Podcast ChatGPT – Allround-Tool für zahlreiche Anwendungsfälle wie Ideenfindung, Textgenerierung, Meeting-Notizen, und vieles mehr. Perplexity – KI-gestützte Suchmaschine, die Quellenangaben liefert und Antworten nachvollziehbar macht. Gemini (Google) – KI-Tool von Google für Textgenerierung und Analysen, derzeit mit Stärken im englischsprachigen Bereich. Claude (Anthropic) – KI-Tool mit starkem Fokus auf Prototyping und als Alternative zu ChatGPT. Notion AI – Integrierte KI für Wissensmanagement und Team-Organisation. Atlassian AI (Jira/Confluence) – Unterstützt Teams bei der Verwaltung und Analyse von Daten. Guru – Plattform, die Daten aus verschiedenen Quellen (z. B. Dropbox) integriert, um personalisierte Informationen bereitzustellen. Cursor – Entwicklertools, die helfen, Code zu schreiben, zu debuggen und automatisierte Tests durchzuführen. Gamma – Präsentationssoftware, die mit KI schnell professionelle Foliensätze erstellt. Eleven Labs – Tool zur Stimmklonung und Audiogenerierung in hoher Qualität. Hey Gen – KI-Tool für die Erstellung von Avataren und Videos. Zoom AI Companion – Integrierte KI für Meeting-Zusammenfassungen und Aufgabenmanagement. Zapier/Make.com/N8n – Tools zur Automatisierung von Arbeitsprozessen mithilfe von KI. Notebook LM (Google) – Tool zur Analyse und Erstellung von Inhalten aus vorhandenen Dokumenten.

Robert Finan: Throwing Features Over the Fence, The Disconnected PO 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. The Great Product Owner: Fostering Quick Feedback Loops With Story Mapping Robert describes a great Product Owner as someone who immerses themselves in the team, fostering collaboration and ensuring quick market feedback.  By using tools like Story Mapping, these POs help teams focus on value while staying engaged and open to learning. The Bad Product Owner: Throwing Features Over the Fence, The Disconnected PO Bad Product Owners remain distant, throwing requirements “over the fence” without participating in the team's efforts. This disconnect often leads to misalignment and poor outcomes.  For Scrum Masters and Agile Coaches, Robert suggests investigating the root cause of this distance and addressing it collaboratively. [The Scrum Master Toolbox Podcast Recommends]

BONUS: A Coaching Masterclass - How Our Language Affects Our Leadership Style, And The Culture We Create, With Michelle Pauk and Victor Pena In this BONUS episode, Victor Pena and Michelle Pauk dive deep into the power of language in shaping our work as leaders, Agile Coaches, and Scrum Masters. Together, we explore how the words we use influence relationships, decisions, and the success of Agile practices. From navigating the ambiguity of language to fostering effective communication, this episode provides actionable insights to help you thrive in a constantly changing workplace. Language as a Culture Carrier “Language is how we carry culture, but without clarity, it can lead to misalignment and conflict.” Victor and Michelle discuss how language reflects and shapes workplace culture. Misaligned terminology—like “servant leader”—can create tension between teams and executives. They highlight the importance of achieving shared understanding and the role of language in fostering trust and collaboration. “Start by asking what others mean by key words—it's the first step toward alignment.” Feedforward vs. Feedback “Feedback gets us stuck in the past, while feedforward builds a path to a better future.” Drawing inspiration from Marshall Goldsmith, we discuss how focusing on future-oriented improvement (feedforward) avoids the blame game and builds positive momentum. As Agile practitioners, shifting from root cause analysis to solution-focused coaching allows teams to move forward effectively. “Ask yourself, what can we do better tomorrow instead of dwelling on what went wrong yesterday?” The Ambiguity of Language in Collaboration “Words mean different things to different people—be curious about how others see the world.” Victor and Michelle unpack how language ambiguity impacts communication and decision-making. They emphasize the need to explore the assumptions behind others' words and how Agile principles like #NoEstimates challenge traditional views on planning and work management. “When you encounter a term that seems obvious, ask: What does this mean to you?” Semiotics and the Language of Work “Symbols are the silent drivers of collaboration.” Semiotics, the study of symbols, plays a vital role in Agile practices like visual management. From story cards to team boards, symbols help teams communicate and navigate their work. The duo discusses how the language of Agile evolves through symbols and how to introduce these effectively in organizations. “Create visual symbols that align with your team's values—they'll anchor your collaboration.” Beyond the “Agile is Dead” Debate, Raising The Bar Of Our Shared Conversation “What's trying to come forward in the evolution of Agile?” While some criticize Agile as outdated, Victor and Michelle argue that its core principles—delivering value faster and improving quality—remain timeless. They explore how Agile can evolve to meet current challenges while retaining its essence. “Instead of asking if Agile is dead, ask what the next evolution looks like.” About Victor Pena and Michelle Pauk Victor Pena is an Agile Coach dedicated to helping organizations achieve business agility. With a focus on innovation, collaboration, and delivering great customer value, Victor transforms practices to ensure long-term success in a dynamic environment. You can link with Victor Pena on LinkedIn and connect with him via email at victor@vpena.com. Michelle Pauk is the founder of Streamside Coaching, helping leaders and organizations thrive through change. With over 15 years of experience in Agile environments and certifications from the International Coaching Federation, Michelle specializes in leadership development and organizational growth. You can link with Michelle Pauk on LinkedIn and connect with her at StreamsideCoaching.com.

Karthiga Seturaj: The Isolated Product Owner, Lacking Collaboration and Engagement 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. The Great Product Owner: Dealing With Uncertainty and Growing Team Trust Karthiga shares the characteristics of an exemplary Product Owner, emphasizing their ability to navigate ambiguity and support their teams during challenging moments. Great Product Owners demonstrate strong leadership, foster team relationships, and celebrate successes, contributing to a positive and collaborative environment. The Bad Product Owner: The Isolated PO, Lacking Collaboration and Engagement Karthiga discusses anti-patterns in Product Ownership, including the absence of strong relationships with developers and testers. A “bad” PO often fails to collaborate effectively within the “three amigos” framework or acts solely as a task scribe. These behaviors hinder refinement and the overall development process, emphasizing the need for active, communicative Product Owners. Self-reflection Question: How does your Product Owner foster collaboration with developers and testers? [The Scrum Master Toolbox Podcast Recommends]

Karthiga Seturaj: Building Habits for Continuous Improvement With The Help Of Agile Retrospectives 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. Karthiga's success definition is similar to what we've heard before:  helping teams achieve independence and self-sufficiency. To illustrate that point, she describes an experience where a team's decision to run retrospectives independently was both surprising and fulfilling, marking a key moment of maturity. This shift allowed her to focus on more strategic initiatives and support the team's continued growth. Self-reflection Question: Does your team take proactive steps to improve their work processes without prompting? Featured Retrospective Format for the Week: DAKI (Drop, Add, Keep, Iterate) Karthiga highlights the DAKI retrospective format as a simple yet effective way to foster team reflection. By encouraging teams to categorize feedback into what to drop, add, keep, and iterate, this approach helps Scrum Masters facilitate actionable discussions. She suggests using tools like a retro postbox on a shared whiteboard to make capturing daily ideas a habit. [The Scrum Master Toolbox Podcast Recommends]

Karthiga Seturaj: Leading Agile Transformations with the Flow Framework 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. Karthiga discusses an agile transformation involving the adoption of the Flow Framework and Spotify model. With leadership support and tools like Lean Change Canvas, the transition fostered psychological safety, adaptability, and feedback-driven improvement. Key lessons include measuring the current state, establishing clear success criteria, and embracing agility in agile adoption. Self-reflection Question: How can you ensure psychological safety during major changes in your organization? [The Scrum Master Toolbox Podcast Recommends]

Karthiga Seturaj: The Right And The Wrong Metrics For 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. Karthiga shares a team story where metrics like Flow Efficiency were implemented to improve understanding of work processes. Despite leadership support and training, the team became overly focused on “making metrics look good,” reflecting Goodhart's Law. This led to discussions on aligning the purpose of metrics with improving workflows, not chasing numbers. Self-reflection Question: Are your team's metrics driving the right behaviors and outcomes? Featured Book of the Week: Project to Product by Mik Kersten Karthiga recommends Project to Product: How to Survive and Thrive in the Age of Digital Disruption with the Flow Framework for its introduction to the Flow Framework and its impact on understanding value stream management. This book transformed her approach to metrics, highlighting bottlenecks and improving flow efficiency. She particularly appreciated its simplicity and practical application in bridging business and technical team gaps. [The Scrum Master Toolbox Podcast Recommends]

Karthiga Seturaj: The Importance of Addressing Conflicts Early 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. As a Scrum Master, Karthiga shares a failure story involving unresolved conflicts between a Product Owner and an engineering lead that escalated into organizational changes and team departures. Reflecting on this experience, Karthiga emphasizes the importance of confronting issues early and effectively. Key tips include involving the right people, leveraging feedback from retrospectives, and using data to address conflicts constructively. Self-reflection Question: How comfortable are you with addressing conflict in your team, and what steps can you take to improve? [The Scrum Master Toolbox Podcast Recommends]

Martin war auf der Manage Agile Konferenz in Potsdam. Wir sprechen über inspirierende Keynotes, brillante Check-ins und darüber wie die Systemtheorie langsam breiteren Einzug in der Wirtschaft findet. Du erreichst uns mit deinen Fragen auf den unten angegebenen Social Media Kanälen, auf unserer Webseite https://www.wir-muessen-reden.net oder direkt an podcast@wir-muessen-reden.net Abonnieren, teilen, Algorithmus glücklich machen! Über positive Bewertungen auf den gängigen Plattformen freuen wir uns natürlich auch. Viel Spaß beim Hören! Dein David & Martin Martin Aigner: Twitter: @aigner_martin LinkedIn: https://www.linkedin.com/in/martin-aigner-865064193 David Symhoven: LinkedIn: https://www.linkedin.com/in/david-symhoven-2a04021a5/ Buch: http://www.amazon.de/dp/398267431X Links: Manage Agile 2025 Programm https://events.summit-community.de/event/361c2a1c-9857-4a0b-aa89-a1c14e91ad82/agenda Prof. Stefan Kühl – Agilität – Täglich grüßt das Murmeltier.... – Manage Agile 2023 https://youtu.be/vLhNT6-8D6k?si=-CQtCswL-twIxLDw Folge 126 - Interview mit Mark Poppenborg https://podcasts.apple.com/de/podcast/wir-m%C3%BCssen-reden-dein-podcast-f%C3%BCr-agile-organisationsentwicklung/id1498061005?i=1000606691950 https://open.spotify.com/episode/5kV90VeCt5xgdX6ekM8mzS?si=iTrVeYFETRqyGfS6zZh7YA Agile Spiele – kurz & gut: Für Agile Coaches und Scrum Master https://amzn.eu/d/68kOcBd

Aliona Zapanovici: How To Help Agile Teams Own Their Work, And Be Independent 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. When it comes to successful approaches for great Scrum Masters and Agile Coaches, Aliona strives for teams to be proactive, care deeply about the product, and value the impact they create. This approach, though sometimes daunting, fosters independence and strong ownership among team members. Self-reflection Question: What steps can you take to empower your team to be more independent? Featured Retrospective Format for the Week: Well / Not So Well / Improve / Actions Aliona prefers simplicity in retrospective formats to maintain focus. The “Well / Not So Well / Improve / Actions” structure allows teams to zero in on what truly matters without getting lost in complex frameworks. She also supports the use of anonymous boards for candid feedback, while cautioning their use if team trust is low. About Aliona Zapanovici  Aliona is an Agile Coach and Scrum Master with a background in architecture who transitioned to IT to pursue her passion. She values impactful contributions over years of experience. Balancing her roles as a coach, mentor, and mother, she focuses on empowering teams and guiding individuals to achieve their best. You can link with Aliona Zapanovici on LinkedIn.

BONUS: The Power of TWI in Transforming Supervisory Skills and Software Leadership With Hugh Alley In this BONUS episode, we delve into how Training Within Industry (TWI) principles can revolutionize leadership and supervision, and those principles can be adapted to the software industry. Hugh Alley, industrial engineer, author of The TWI Memory Jogger, and seasoned consultant, brings invaluable insights on how adapting these timeless methods can enhance team cohesion, productivity, and job satisfaction. From Toxic Workplaces to Transformative Solutions "When I first saw supervisors shouting in the workplace, I knew there had to be a better way." Hugh's journey began in the high-stress world of manufacturing where ineffective leadership was the norm. His turning point came when he discovered TWI, which shifted a company from zero employee suggestions to implementing 2-3 improvements per week. He shares the importance of recognizing poor patterns and seeking practical solutions that lead to lasting change. "A key insight? The power of TWI isn't just in theory; it creates immediate, real-world results." The Historic Power of TWI: Lessons from World-War II "We learned that repetition is essential for true skill mastery." Hugh recounts the origins of TWI during WWII when the U.S. War Manpower Commission had to quickly upskill the workforce and develop leaders. He highlights the drastic improvement in training time for complex tasks, such as lens grinding, reduced from five years to just five days. This approach emphasized breaking tasks into micro-skills and practicing them repeatedly. "The secret to learning is practice—not just once, but deliberately and consistently." Core Managerial Responsibilities: Mission and People "If you don't look after your people, they'll leave." Hugh elaborates on two often-overlooked managerial duties: achieving the mission and caring for the team. In software projects, where meeting deadlines becomes paramount, leaders may overlook their teams' well-being. He shares a case where training in TWI's Job Relations (JR) module reduced turnover from 60% to 10%, proving that attention to people directly impacts results. "Feedback isn't optional—it's the backbone of a motivated team." The Five Essential Supervisory Skills "Getting people up to speed isn't luck; it's skill." Hugh discusses the five essential skills for supervisors outlined in TWI: giving instructions, fostering performance, improving methods, setting priorities, and listening. These skills ensure that new team members integrate smoothly and that ongoing work aligns with team goals. For software teams, he emphasizes that structured training can prevent future issues and enhance productivity. "Supervisory success is built on clear guidance and active listening." Why TWI Gets Overlooked and How to Revitalize It "We don't need heroes; we need high-functioning teams." Post-WWII, TWI lost momentum as it was seen as outdated, and the culture shifted toward individual heroics in the workplace. Hugh argues that today's teams thrive not on isolated brilliance but on collective efficiency and shared learning. "Our challenge today is to reclaim TWI's structured approach for consistent team performance." Addressing Performance Issues with TWI "Inspection isn't just watching; it's understanding and acting." Hugh explains how the Job Relations module of TWI can be adapted for software teams to address performance issues. He shares practical steps for leaders to approach these conversations constructively, improving team trust and transparency. "Proactive feedback, rooted in observation, fuels team growth." Application for Scrum Masters and Agile Leaders "Basic certifications don't cover these leadership essentials." Hugh talks about how Scrum Masters can leverage the insights from his book, The TWI Memory Jogger, to build vital supervisory skills that foster better team dynamics and output. He emphasizes the importance of continuous learning beyond basic training to handle real-world challenges effectively. "To be truly effective, Scrum Masters must master supervisory fundamentals." The Art of Listening in Leadership "Respect starts with truly hearing your team." Hugh shares a story about a colleague named Angie, illustrating how active listening can uncover underlying issues affecting performance. He discusses how TWI encourages leaders to move beyond surface-level interactions and engage meaningfully with their teams. "Listening is the gateway to trust and respect in leadership." Improving Methods: A Supervisor's Guide "Ask better questions, get better answers." For supervisors and Agile Coaches, Hugh introduces six reflective questions that improve work methods. He explains how applying these questions can enhance retrospective meetings and process improvements in software teams, reinforcing TWI's impact on continuous improvement. "Improvement begins when you challenge every assumption and ask the right questions." TWI's Influence on Team Cohesion and Values Hugh shares a success story from his book where TWI principles transformed team unity. He shows how applying these principles nurtures an environment of mutual respect and shared responsibility. "True cohesion comes from shared learning and collective effort." Hugh encourages listeners to explore TWI resources and start with practical application in their teams. For those eager to dive deeper, his books Becoming the Supervisor and The TWI Memory Jogger offer accessible entry points to mastering these crucial skills. About Hugh Alley Hugh Alley is an industrial engineer, author, and consultant specializing in continuous improvement and supervisory skills. He has led multiple manufacturing firms and trained over 1,000 front-line leaders, authoring two books on effective supervision. Based near Vancouver, Canada, Hugh supports clients across North America with practical strategies for leadership development. You can link with Hugh Alley on LinkedIn.

Dominika Bula: Building Stronger Agile Teams Through Working Agreements And Deliberate Collaboration 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. Dominika shares a story about a growing team in a scaling agile environment where new members were joining frequently. This team lacked a proper working agreement, which resulted in disengaged team members who didn't participate fully in daily discussions. Dominika's approach was to help the team start a buddy system for new joiners and ensure that everyone, especially new members, felt heard. She emphasizes the importance of developing a deliberate decision-making model and the need to differentiate between the Definition of Done (DoD) and a team working agreement. Self-reflection Question: Is your team's working agreement fostering participation and inclusion from every member, especially new joiners? Leave your answer in the comments, let's get this conversation started!  Featured Book of the Week: Kanban Pocket Guide by Dan Vacanti Dominika recommends Kanban Pocket Guide by Dan Vacanti as a must-read for anyone interested in improving team flow. It's a concise and practical guide that helps integrate Kanban into Scrum teams by focusing on value and transparency. Dominika appreciates its clarity, specific examples, and how it helps Scrum Masters and Agile Coaches refine their understanding of Kanban to enhance team performance. The guide is also a great resource to revisit regularly. About Dominika Bula Dominika is an Agile Coach at SAP Signavio with a strong background in agile practices from her experiences at Oracle and Red Hat. She is passionate about Kanban and firmly believes that Agile and DevOps are the perfect combination. As a facilitator for the Women in Agile mentorship program, Dominika is dedicated to supporting and nurturing the next generation of agile leaders. You can link with Dominika Bula on LinkedIn.

Agile Coaches Make the Best Venture Capitalists

Discover how recognizing and accommodating different collaboration styles can transform your Agile team dynamics. Join Brian Milner and Jessica Guistolise as they delve into the key to effective and inclusive collaboration. Overview In this episode of the Agile Mentors Podcast, Brian interviews Jessica Guistolise about the diverse collaboration styles that impact team dynamics. They explore the importance of recognizing and accommodating different collaboration styles—relational, expressive, and introspective—to create effective and inclusive collaborative environments. Jessica provides practical tips for Scrum Masters and facilitators to cater to these styles during meetings and retrospectives. The discussion emphasizes the value of diversity in collaboration styles, which brings different perspectives and ideas to the table, fostering creativity and innovation. References and resources mentioned in the show: Jessica Guistolise Lucid The Collaboration Style Quiz & Report The Global Scrum Gathering Advanced Certified ScrumMaster® Certified ScrumMaster® Training and Scrum Certification Advanced Certified Scrum Product Owner® Certified Scrum Product Owner® Training Join the Agile Mentors Community 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. Jessica Guistolise is an Agile Evangelist and coach at Lucid who excels in helping organizations deliver continuous value to their customers. With a passion for people over process, she specializes in change adoption, gaining critical buy-in, and establishing trust in Agile methodologies across various industries. Auto-generated Transcript: Brian (00:00) Welcome in Agile Mentors. We are back for another episode of the Agile Mentors podcast. I'm with you as always, Brian Milner. And today I have a special guest with us. have Jessica Gastolis with us. Did I say that correctly? Jessica Guistolise (00:14) You did. Thank you so much. It's a mouthful. I am so happy to be here. Thank you so much for inviting Brian (00:21) Absolutely, incredibly excited to have you here. For those who aren't familiar with Jessica, she is an evangelist at Lucid. So I'm sure we'll hear a little bit about that as we talk. She is an agile coach and she has the credentials to back that up. She has from the Coaches Training Institute, a professional coach certification and also she's an ORSC coach, if you are familiar with that. I'm familiar with that. I know there's a lot that goes into getting those. So it's not just, you know, filling out a, sending in some box stops and, you know, getting it back in the mail. and, so the reason I wanted to have Jessica on is because she was speaking at, or she did speak at the scrum gathering that just took place, back in May. And, she had a couple of talks actually that she did with, Brian Stallings there. but one of them really caught my And I thought it would be interesting here to the audience. And that's about collaboration styles. So let's dive into that topic. When we talk about collaboration styles, Jessica, don't we all collaborate the same? Jessica Guistolise (01:33) You know, it's funny, we don't actually. Though, although there is a kind of a misconception that we do because we collaborate in the way that we collaborate, but not everybody collaborates in the same way. And so for us to create really amazing collaborative environments, it's helpful to have an awareness of those different styles. And if we facilitate in such a way that cares to each one of those styles, you're gonna get so much more in the room than you would if you only stick with, well, here's how I collaborate. So obviously this is the way to do it. Brian (02:09) Right. Yeah, I think this is such an important topic because I know one of the questions I'll get a lot in classes or just even in Q &A sessions when we talk about retrospectives is, I'm having a hard time facilitating my retrospective and my team doesn't want to talk or my team's quiet and shy. And to me, this is all kind of indicative of this concept of you're probably not recognizing that they have different collaboration styles than you do. Jessica Guistolise (02:41) Yeah, absolutely. And it's so amazing because I think as Scrum Masters, as Agile Coaches, this is a really important piece to recognize because as the facilitator, you're really building the container. think of these events as like the containers and the folks who are doing the work, they're all the content. But if you build a container that's going to allow for that content to emerge in a healthy way, you just, I mean, Anything's possible. Brian (03:10) Right, right. And you know, one of the things I love to say in classes is just that, you know, that facilitation, that's the root goes back to this phrase, it means to make easy. And you know, that's our job is to make whatever that thing is easy. And if we are, if we're not aware of our own personal preference and style and how we collaborate, then it's harder for us to even be empathetic or recognize that other people have different styles and much less how to accommodate them and be inclusive of them in those environments. So I just think it's a really important Jessica Guistolise (03:51) Well, and the interesting thing too, besides easy, there's also an element of safety. Because if you're asking me to collaborate in a way that makes me really uncomfortable, then I'm spending all of that time in my discomfort and trying to put forth ideas. Those two things are so, they clash. And so there's also an element of just creating an environment of not just easy because this is the way that I collaborate, but I feel safe in collaborating in a that make sense to me. In fact, there's some, there are a couple of styles that are almost opposites. So if you're asking me to collaborate in that way, ooh, I am not sharing anything with you. Brian (04:31) Right, right, you have that amygdala hijack going on. You're kind of, you're in that fight or flight mode of just, my gosh, I'm panicked. I don't want to do this. I feel highly uncomfortable. you know, it's, can, you know, literally it's blocking those neural pathways of actually being able to collaborate and access, you know, the parts of your brain that would allow you to, to contribute in that kind of environment. Jessica Guistolise (04:59) Yeah, it's fascinating actually, right before the study that was done came out, I was in a collaboration with a group of people who were collaborating in a way that was wildly uncomfortable. And I came out of that meeting feeling dumb. Like I really was like, wow, I didn't, I just gave nothing. But then, you know, a little while later I was like, well, but I have this idea and this idea and this, wait a minute. I was just stuck because this isn't a way that's very comfortable for me. Brian (05:28) Yeah. Well, you know, I know you probably know this, but for anyone else listening out there as well, I have definitely felt that way as well in sessions that were kind of contrary to, you know, opposite of what I prefer. And, you know, the way I always describe it is I don't, I'm not a person who thinks out loud. I think internally, I think quietly and then express it later. I need time to process and work through things. But I recognize there are others who are verbal processors who need to speak out loud and and You know if you're in a meeting with a bunch of those Types of people who have that collaboration style and and yours is a quiet one Then you know I've walked out of those rooms before feeling like gosh I'm the dumb one in this meeting because I didn't have anything to contribute Jessica Guistolise (06:12) Yeah, I didn't provide any value in that, but there is, there's so important to recognize that. And I think there's, there's, there are ways to create these containers and to create these collaboration sales that really help to make it so that everyone can feel comfortable collaborating in the way that is going to be comfortable for them. And it just, it's, you know, it's the facilitator work of being prepared. Brian (06:16) Right, right. Jessica Guistolise (06:38) preparing for the meeting or the event, creating the container in a way that's going to be safe, comfortable, and easy for everyone. Brian (06:45) Yeah, absolutely. All right, well, let's get to the meat of that then, because I know there are a few, you kind of delineated these in the presentation that you had. So walk us through, what are the differences in these different kinds of collaboration styles? Jessica Guistolise (06:59) Yeah, so the study was done, Lucid did a really interesting study. I was so excited by this. And what they found was over half of knowledge workers identify with one of three collaboration styles. And the other part of that is you may not land fully in one of the three and you may have kind of a blend of them, but these are the ones that we see most often. And one of the things that I always like to point out too is that none of these are Like it's just the way that you feel comfortable. They're all really helpful and healthy and really great ways of coming together. So I'll start with the one that I most identify with because it makes the most sense to me. That's we normally create collaboration is we see how do I collaborate and I'll collaborate with you. So the first is relational. And so relational collaborators really want that human connection. Like they want to be, they want to spend some time. How was your weekend? Or just if it's a brand new person, let's get to know each other a little bit before we dive into trying to solve problems. there's it's, it's almost like, for me, I just feel like I need to be in relation with, in relationship with someone before I'm comfortable collaborating. It's like, the metaphor I like to use is, is like baking bread. If I'm in relationship with you, I'm gonna bring you ingredients and recipes and stuff that I'm playing with and trying to figure out. But if I'm not in relationship with you, I will have that entire thing baked and then bring it out and see if you like it. But that's not collaboration, right? That's me by myself and how much better is the bread gonna be if somebody says, well, let's try this and let's try this and let's try this. So that's a relational Brian (08:49) So that sounds like that one in particular needs just a tremendous amount of trust to be effective. Jessica Guistolise (08:55) It does. really does. And I actually, I'll tell you a story about this because, so I, I was working with, an individual who had an interesting problem to solve another agile coach. and he'd come up to me and he was like, I have this interesting problem. Do you have anything in your coaching toolbox or knapsack that you can pull out for me really quickly? And I was like, Hmm, you know what? actually don't. but let me think about And so I went, was doing some other things and sort of in the back of my brain. And then I had just an absolutely ridiculous idea. I mean, it was like, I, I felt silly even thinking it, let alone saying it out loud, but I was in really great relationship with this other individual. So I ran across the hall and I said, okay, I have a really dumb idea. And he goes, okay, let's hear it. And I told him, and he goes, wow, that's really dumb. Let's play with it. And so we played with it and got it into something and he took it back to the team and it worked spectacularly. And I think he's still using it today as an exercise that'll help with the team's collaboration. but if I hadn't been in relationship with him, I would have had that dumb idea and then I would have let it go. Brian (10:10) Right, right, because you know, you don't want to get made fun of or you don't want to be made to feel dumb or anything. So yeah, absolutely. You got to have that trust and sense of safety with them to be able to bring it up. That's a great Jessica Guistolise (10:23) Yeah. The second one is one that I wish I had more of and I just don't. So some people identify as expressives. If you're an expressive collaborator, you are ready to dive in at any moment. Like somebody can throw out a topic and you've got, you're the first voice in the room. You love using visuals and drawing out your ideas and throwing up sticky notes and emojis. You're one of those people that's I'm ready to, I'm just ready to share. I really wish I had more of that. Sometimes I think of them as blerters. Like they're just willing to blurt it out. Whatever is there on top of mind and a brainstorm. And I just, think that's so admirable and it's just not a skill that I have. Brian (11:09) So less of that filter then. mean, it sounds like they don't necessarily need to have that basis of trust. They're just sort of always willing to say what's on the top of their mind and get it out in the open. Jessica Guistolise (11:22) Yeah, yeah, I think it's a great way of expressing themselves. And they also have maybe a harder time spending that time getting into relationship and all of that ooey gooey stuff. And they're like, let's get to the work, you know. But if we have an awareness that I as an expressive am working with a relational collaborator, some of the work is getting into relationship. So now I feel more comfortable spending that time because I know that the work we're going to do after that is going to be greatly Brian (11:57) And correct me here if I'm wrong, because I'm just trying to make sure that we're understanding all speaking the same terminology here, but it sounds like the way you describe this, that expressives are not necessarily verbal expressives. Like you mentioned, someone who's more sketch note based or anything like that. So they may not feel comfortable speaking, but they're very comfortable with the concept of getting an idea out of their head quickly in one way, or Jessica Guistolise (12:26) Yes, exactly. It could be in visual form. think of like people who always have memes or GIFs at their fingertips. Like they're just ready to go and send out these their ideas into the world and not hold on to them tightly. know, they hold them on, hold on to them, Lucy, please, because they're coming out in the world. Brian (12:44) Hold on loosely, but don't let go. Awesome, I love that. Okay, and then was there another one? Jessica Guistolise (12:52) There is. So the last one is introspective. So an introspective collaborator, I dip my toe in introspective collaboration as well. Deep work is really, you love deep work. Spending time really processing, thinking through, chewing on an idea, tossing, playing with it a little bit yourself before beginning to share. It's the opportunity to do some research, do some brain writing, spend some time in ideation. And you might even feel comfortable having a conversation with one person rather than if you have a giant group of people sending them into breakouts to have individual conversations. sending out thoughts about what's going to happen before the meeting or the event so that they've got that time to themselves to say, here's what I'm thinking about this topic. before throwing them into a room with a whole bunch of people and expect them to just go. Brian (13:57) Right, right. Yeah, no, I mean, of these three, yeah, that one sounds very close to what I would identify with for sure. And yeah, I mean, I think one of the characteristics I would kind of try to relay that home to everybody is I love when a collaboration session spills over across days because I love having the ability to go home and sleep on it Jessica Guistolise (14:18) Yes. Brian (14:24) you know, when I'm walking my dog or getting ready in the morning and the shower or something that that's when the brilliant idea will strike is when my brain is actually distracted and thinking of something else. That's when I can really think about things. And I, I feel like I need that time to sort of let it percolate and kind of, you know, seep in a little bit before I can come back and really contribute. Jessica Guistolise (14:46) Totally. One of the things that I really appreciate that we do at Lucid. So that meeting that I was talking about where I walked out and I went, I provided zero value in that meeting. We've got an open board for that for after. And there's an expectation that if you have ideas afterwards that you have the opportunity to come back to it the next day or the day after that. It's not, okay, we collaborated, close this. That's it, we're done. but you actually get the chance to do some of that asynchronous follow on day, day after kind of collaboration. Brian (15:20) Love that. Well, and two, Scrum Masters out there, hear that, listen to that, right? Think about that from that kind of a meeting. This is just a normal meeting, right? But we sometimes can get so structured into the idea of a retrospective being only at this time and this confines, and we have our time boxes and everything else. But yeah, if we can have some spillover time as well, pre or post, right? Just having that ability Jessica Guistolise (15:30) Hm. Brian (15:49) let people think through and contribute after the fact, that can really deliver some great results and allow you to include all these different collaboration styles. So then relational, expressive, introspective, these are kind of the three styles that you guys highlighted in your talk. All right. So let's say I'm a Scrum Master and I might identify with one of these. How does that help me? How does that help me to do my work with my Jessica Guistolise (16:23) Yeah, fantastic. So Brian, you immediately recognize your own sort of tendencies or collaborative tendencies, collaboration styles. But if you think about those you work with, do think you could kind of identify what different styles other people you work with on a regular basis might have? Brian (16:43) Yeah, I think so. mean, most people who are listening to this know my boss. I would, it's kind of funny. If I was going to try to pin Mike Cohn down in one of these three. Gosh, you know what's funny is I'm not sure because he sort of has a blend of all three. Jessica Guistolise (17:08) Well, that's absolutely like I mentioned, I'm sort of I'm a relational with an introspective kind of toe in introspection. And so I think there's a lot of people who are a little bit of a mix. And so the easiest thing to way to find out is to ask, share what these styles are, and ask what find out what's going on with your team, if they were to self identify, because it's easier to self identify, obviously, And then now you've got a great understanding of what's going on with the rest of your group. It was so fascinating to me when we did the conference talk, we had everybody self -identify and then collect in your self -identified group. So all of the expressives were together, all of the relationals were together and all of the introspectives were together. And then we had them do some work together and they were describing what helps them. to collaborate best. And the expressives were loud and they were right away writing all over the sheets of paper that we had for them. were, you I mean, it was like, it was a boisterous part of the room. The relationals immediately, hi, I don't think we've met yet. Let's get to know one another very quickly. You know, what do you love about your collaboration style? I mean, they really spent that time getting to know one another. And they were kind of coming to consensus before, Brian (18:23) Hahaha Jessica Guistolise (18:35) before writing anything on their page, because they were making sure that everyone was relating and getting their voice in. The introspectives, quiet, quiet, quiet part of the room, and they all had sticky notes and they were writing their ideas and then they were putting the ideas next to each other that might be similar, and then they started having conversations. So as a scrum master, as a facilitator, to know what your team's style is, is again, going to help you create the experience of inviting each one of those styles to collaborate in ways that best work for them. I mentioned introspectives, send out the agenda beforehand, make sure that they know the topics, have some silent brain writing time, because expressives are going to start putting their stickies out anyway, but allow that quiet moment to be there to accommodate those styles. You may put them into breakout rooms or have them meet with one other person. Especially if you've got like a larger collaborative of that, where you've got a bunch of people together, one -on -one first, then maybe four -on -one, know, one, two, four -all kinds of experiences are going to help those introspectives be able to bring their voice forward. You'll also have a moment of connection. Nobody likes icebreakers, so I think of them more as like relationship activities. If we're going to have a relationship activity, that feels way better than an icebreaker. Brian (19:52) Ha Jessica Guistolise (20:00) And spending time really allowing for, how are we feeling today? Let's bring some awareness to what's going on collectively as a group. All of that is helpful because then your relations, they've gotten their relationship moment. They feel connected to the people that they're working with, which means they're going to feel connected to the work that they're doing. So that connection before content allows the contact to be significantly improved. and expressives, give them the space to do it. mean, really allow them to be that voice in the room that jumps in and gets everyone excited. They bring people along. So building your events in ways that allow people to bring, be their best collaborative self is so helpful. The other thing that I think is really helpful trying to make sure you've got diversity of collaboration styles on your team. I'm a huge proponent of DEI and diversity and bringing together wildly different perspectives and ideas. And I just think that all of these interesting and complicated human problems that we're trying to solve need interesting, complicated humans and interesting, complicated teams. Brian (21:20) Hahaha Jessica Guistolise (21:22) And if you've only got introspectives on your team, there's going to be these relation, relationship type thoughts that are going to be missed and same with expressives. And so I think as you're building out a team, or if you have a team, just thinking about like, Ooh, do we have a diversity of collaboration on our team? And am I making sure that each one of those styles are cared Brian (21:44) Yeah. Yeah. I mean, like we, I know we talked about this quite a bit on our podcast. know, there are different neuro types, people think in different ways, people have different preferences and you're absolutely right. You know, what, what we need is people who see things from different angles. you know, if we all see things from the same perspective, then we're, don't have anything really to share. We all can just observe one thing and give our own perspective on it. But how much better is it if you have someone who's standing on the opposite side and says, wait a minute. There's actually another dimension to this that you guys aren't really able to see and bringing that to the table can make all the difference in the Jessica Guistolise (22:20) complete difference. And isn't it more fun? Everybody thought the same things that I did. Boy, the whole, it would just be boring. And it's a delight to see the ways in which other people see things and to go wander over and see their perspective. like you said, it brings more dimension to the things that we're working on. Brian (22:45) Yeah, and at the end of the day, we need some of that conflict. It's not all conflict is bad conflict, If I have a different viewpoint than you, then you're challenging my way of thinking and I'm challenging yours. And hopefully we end up at an endpoint that is a better endpoint because it's been challenged, because we haven't just accepted as rote what somebody thought. Jessica Guistolise (23:14) Absolutely. I'm totally agree. I think healthy conflict, healthy conflict and collaboration is, is helpful. I collab. I should have said in that moment, I don't collaborate like this. Can we get to know one another? And I probably would have met some folks in the organization that I, because it was, it was not people that I spend a lot of time with on a regular basis, I would have met people across the organization that I would have. Brian (23:28) Right. Jessica Guistolise (23:43) would have liked a number. Brian (23:45) Well, and I think it's amazing how powerful it is to have a name for something and be able to just kind of say, hey, this is what this means and this is what this is behind this. And if I know I am relational, then I know kind of what I need to be successful. I know what's gonna set me off. I know what's gonna be difficult for me. And I have a much higher likelihood of being productive in that kind of environment because I'm aware of those sorts of things. I think I know the way that you guys started was to try to get people to understand a little bit about where they were first before thinking about others. And I think that that was a genius way to approach that because I think you're right. You kind of know where you are on the map a little So yeah, we've talked about this a little bit when I kind of did my research and work on neurodiversity and different neuro types and stuff and how these different things relate. yeah, it's just like we were saying, right? You need different perspectives. You need different kind of approaches to problems if you're going to solve them and think in different ways when you approach issues. All right. If we understand there's relational, there's expressive, there's introspective, we kind of can pin where we are. We're starting to see where others are. How do I put this into practice? If I'm designing a retrospective, let's just say, and I know my team is made up of, I got five people, I got, you know, of three introspectives and two relationals on my team and no expressives. How's that gonna change how I prepare my Jessica Guistolise (25:36) yeah. Well, probably don't just have them start talking about it. I mean, so, you know, as you're thinking through the as you're thinking through the five stages of a retrospective, what you might do is like, okay, so if I'm going to open the retrospective, how might I open the retrospective in a way that's going to cater to my relational? That's an easy one to grab on to, right? Let's let's talk about Brian (25:41) No open discussion, Jessica Guistolise (26:04) What's something interesting that's in your wallet or your purse or just something that's gonna help the group begin to be in relationship with one another? You'll wanna have some quiet time. Allow them to spend some time on their own thinking about what happened over the course of the last week before you even start throwing things up. You might have just a five minute, close your eyes walk yourself through the last sprint and think about what were the big things that happened before even going into the writing. There's some really nice introspective time to chew on what happened, what's going on. You may put them, like I said, in small groups of two or three instead of having them come together to try to come up with experiments as a whole wide group right off the bat. So when When you figure out, here's the things that we want, here's the topics, here's what the data is telling us, and here's what we want to run an experiment on. Again, allow for that time to go back and really chew on. So we have this thing that we want to work on in the next iteration. So I'm going to spend some time thinking about maybe 10 different ways that we might experiment on that instead of having the whole group have that conversation right off the bat. So there's a whole bunch of different things you could do. to kind of unlock the collaboration in all of your team members. Brian (27:37) Yeah. Yeah. We were talking a little bit before our podcast about how we're music nuts and, you know, really get into that world. you know, the ideas crossed my mind. It's sort of like, you know, when you think about composing music or you think about a piece of music, right? If everything wasn't a major key, that would get boring. You know, we like to have minor keys on occasion or sometimes augments. augmented keys or different time signatures and different rhythms and things that kind of come to play in a piece of music. And sometimes we'll even shift those in the course of a single song. So if you think about a retrospective kind of in that or a facilitation session even larger than a retrospective, but just any facilitation session, right? You don't want it to get boring. You don't want to just cater to one thing. You want to be able to have some variety and that makes it interesting that keeps people's attention. Jessica Guistolise (28:32) Please. It does. mean, think about just even how you might shift things up in a daily scrum. Every day come to it, okay, so today we're gonna do an expressive scrum. Warn your introspectives that that's coming. Today we're gonna do a relational scrum, daily scrum. Think about how you might add these elements into your planning session, because that's a deeply collaborative session, and you wanna make sure that there's space for each one of your collaborative. collaboration style team members to have the ability to you I think everybody would be surprised how much more information comes when we feel comfortable collaborating in these different styles and There's edges in each of us right so helping to kind of Walk those edges I've I have been working really hard on trying to be more expressive I asked expressives. How do you do that? And really a lot of it is I don't hold my expresses, the things that I express tightly. They're just ideas and I'm willing to just throw them out. And so for me, that's an edge for me that I can walk up to. And so you can help your team members because they're not always gonna be on a team that has an understanding all of these styles exist. Although as a team member, I might say, hey, let's all talk about our collaboration styles real quick as a part of our working agreement. But you may find yourself on a team that doesn't have that same understanding of the collaboration styles. And so if you work on kind of moving that edge further and further, you're stepping into it a bit, then you're going to be more comfortable collaborating in multitudes of environments. And ladies and gentlemen, and all of those in between, We want to hear your voice. so doing the self work in some of that I think is also really important. Brian (30:37) Absolutely, yeah, I couldn't agree more. Well, I can't thank you enough, Jessica. Thank you for taking time out and coming in and explaining this to us. It's just, one of the joys of getting to do this kind of thing that I get to have these kinds of conversations with the Agile community and different members of our community. So thank you for making time and sharing your wisdom on this with everyone. Jessica Guistolise (31:00) Yeah, thanks, Brian. This has been an absolutely delightful conversation. And if people want more information on the collaboration styles, there is a report out there. And with the report, there is also a quiz you could take that says, wait a minute, what is my collaboration style? And you could have your whole team take the collaboration style quiz. And then you'd really have an understanding of where is everybody at? And how can we make sure that their voice is in the system? Brian (31:22) That's an awesome suggestion. We'll definitely put that in our show notes, too. So we'll make sure everyone can just find that in our show notes and not have to hunt for it or anything. But that's an awesome suggestion. Well, again, thanks, Jessica. I appreciate you coming on and speaking with us. Jessica Guistolise (31:39) Yeah, thank you so much for having me. It's been a delight.

This week, your hosts, Dan Neumann and Justin Thatil, share seven tips for Agile Facilitation. Collaboration is necessary when solving a problem, and Agile Coaches and Masters work to enable a Team to cooperate. Every event is unique, which is why Facilitation could be considered a form of art.   Key Takeaways Contextual Awareness: Teams and events are filled with unique variables that the facilitator cannot always anticipate; as a result, reading the overall atmosphere of a room and the individuals' body language is a fundamental skill for Facilitators. Every Facilitator has to remember that they are facilitating for a specific audience. Who is this meeting for? What is the value for these participants? Use Time boxes. A Facilitator must master the flow of the meeting to achieve the goal in a timely manner. A Facilitator should design the session with the intended activities, promote collaboration from collaborators, and be flexible enough to adapt to changes. Mastering the act of active listening: Listening is achieved when being fully present. Seek to understand. Facilitators must be able to paraphrase what they just listened to to ensure they understand what the collaborator is saying. Are collaborators listening to each other? A Facilitator must also promote active listening among participants. A Facilitator must foster an open and inclusive communication environment. A Facilitator must become a master observer of the room. Who is participating? Who is silent? Design a power start! Set the purpose and the intended outcome for the meeting. This will improve participant engagement. Specify how participants can engage. Visual Facilitation tools are incredibly beneficial for a better Facilitation. A Facilitator must handle conflict with grace. Conflict is inevitable, especially in a collaborative environment. Participants should be encouraged to learn from each other. Conflicting perspectives must both be validated. A Facilitator must be clear about which behaviors are acceptable. Safe boundaries are essential to hosting a psychologically safe environment. Facilitators must continuously improve their skills. Facilitators must apply learnings in a setting first to realize how they can be improved. Pairing with other Facilitators can be a great way to keep learning continuously.   Mentioned in this Episode: Empowered: Ordinary People, Extraordinary Products (Silicon Valley Product Group), by Marty Cagan and Chris Jones   Want to Learn More or Get in Touch? Visit the website and catch up with all the episodes on AgileThought.com! Email your thoughts or suggestions to Podcast@AgileThought.com or Tweet @AgileThought using #AgileThoughtPodcast!  

Jaques Smit: The Role of Coaching in Organizational Change, A Key Skill For Agile Coaches 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. How can leaders effectively motivate and guide teams through significant changes? Jaques shares his journey in leading a traditional development team towards creating their own games. He highlights the challenges of facilitating change without sufficient coaching skills and the importance of creating a desire for change. Jaques introduces ADKAR, SCARF, and coaching techniques, ultimately leading to successful organizational transformation. In this episode, we also refer to Constructivist Learning, and Adult learning theory.    [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 Jaques Smit Jaques is a seasoned Agile coach and Scrum Master with extensive experience in leading and transforming teams in the game development industry. His expertise lies in fostering team collaboration, resolving conflicts, and facilitating effective retrospectives. Jaques is passionate about continuous learning and empowering teams to achieve their full potential.   You can link with Jaques Smit on LinkedIn and connect with Jaques Smit through his website.

In this podcast episode, we delve into the various obstacles that Agile coaches encounter when attempting to quantify and demonstrate their impact and value within organizations.Join Shawna Cullinan, Jörg Pietruszka,  Diana Larsen,  Sheila Eckert, Sheila McGrath, Hendrik Esser, Ray Arell, and all the callers to the monthly live event as we explore this topic.  For details on the next live event or how to support our show, please visit  acnpodcast.org.Support the Show.

Doug Rabow: Daily Standups as a Success Barometer in Agile, And Other Lessons For Scrum Masters 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 segment, Doug discusses the dual aspects of success for Scrum Masters: defining it and demonstrating it to others. We also talk about how the quality of daily standups reflects the overall health of the Agile practices in the team. We also explore how fostering an environment of good-faith feedback and continuous improvement can lead to success for Scrum Masters and Agile Coaches. Featured Retrospective Format for the Week: Asking Questions In this segment about Agile Retrospectives, Doug highlights the importance of asking pointed, empathetic questions during retrospectives to uncover deep insights about team dynamics and challenges. We learn about the role that well-crafted questions play in driving continuous improvement. And learn how Doug's approach of integrating impactful questions into conversations, helps teams to navigate and overcome obstacles more effectively.   [IMAGE HERE] Retrospectives, planning sessions, vision workshops, we are continuously helping teams learn about how to collaborate in practice! In this Actionable Agile Tools book, Jeff Campbell shares some of the tools he's learned over a decade of coaching Agile Teams. The pragmatic coaching book you need, right now! Buy Actionable Agile Tools on Amazon, or directly from the author, and supercharge your facilitation toolbox!    About Doug Rabow Doug is a passionate practitioner of Lean-Agile strategic management with a focus on developing empowered teams and Lean process improvement.   You can link with Doug Rabow on LinkedIn.  

Mit dieser Folge möchte ich mit den Top3-Change Mythen aufräumen: 1) Wir müssen die Mitarbeiter befähigen! 2) Training und Coaching führt zum Erfolg! 3) Wandel dauert viele Jahre! Folgende Inhalte erwarten Dich: Kapitel 1: Change-Mythen in Banken und Sparkassen (00:15 - 03:34) Zu Beginn der Episode räumen wir mit einigen weitverbreiteten Mythen auf und inspirieren zum Neudenken. Wir sprechen über die Übergangsphase in Banken, die mit vielen Herausforderungen verbunden ist, und betonen die Wichtigkeit, mehr aus dem eigenen Institut herauszuholen. Kapitel 2: Empowerment und Veränderungskompetenz (03:34 - 11:23) Wir diskutieren die häufige Fehlinterpretation von Empowerment und erörtern, warum es wichtig ist, Mitarbeiter nicht nur zu befähigen, sondern sie auch zu bestärken. Die Rückblicke auf persönliche Veränderungen dienen als Stärkung für neue Herausforderungen. Kapitel 3: Führungskräfte und Veränderungsprozesse (11:26 - 14:10) Hier erinnern wir uns an erfolgreich gemeisterte Veränderungen, die als Motivation dienen. Die Rolle der Führungskräfte bei der Unterstützung dieser Prozesse wird hervorgehoben, ebenso wie ihre Aufgabe im Change-Management. Kapitel 4: Agile Coaches und Veränderungsprozesse (14:10 - 19:52) Die Bedeutung von Agile Coaches für die Gestaltung effektiver Veränderungsprozesse wird diskutiert. Wir sprechen auch über die Herausforderungen, die bei der Implementierung von Agilität in bestehenden Strukturen auftreten. Kapitel 5: Training, Coaching und Veränderungsprozesse (19:52 - 29:31) Das Zusammenspiel von Training, Coaching und der Anpassung organisatorischer Strukturen wird analysiert. Die Bedeutung von Verhaltensänderungen und der Arbeit an Organisation und Kompetenzen für erfolgreiche Veränderungen wird betont. Summary: Überlegung, wie die Mitarbeiter nicht nur befähigt, sondern bestärkt werden können. Training und Coaching anbieten, jedoch nicht ausschließlich ohne Anpassung der Strukturen, Abläufe und Prozesse. Die Organisation so positiv zu irritieren, dass automatisch die Veränderung möglich sein muss. Diese Episode ermutigt hoffentlich jeden von uns, positive Irritationen als Chance für Veränderungen zu sehen. Ich hoffe, die heutige Diskussion inspiriert euch, sowohl die eigenen Komfortzonen zu hinterfragen als auch aktiv an der Gestaltung der Zukunft eurer Institute mitzuwirken. Wenn Dir diese Folge gefallen hat, dann freue ich mich über Deine Bewertung mit 5 Sternen bei Apple Podcasts und wenn Du meinen Podcast weiterempfiehlst. Mail mir gerne Deine Gedanken zur Folge unter jw@juergenweimann.com. Liebe Grüße, Jürgen Abonnier hier meinen Newsletter: https://juergenweimann.com/juergen-weimann-newsletter/ Liebe Grüße, Jürgen Abonnier hier meinen Newsletter: https://juergenweimann.com/juergen-weimann-newsletter/

BONUS: Transitioning from Non-Tech to Tech Roles with Mariana Trigo, A Guide For Scrum Masters, and Agile Coaches 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, Mariana Trigo, a pioneer in assisting professionals transition from non-tech to tech roles, shares stories about transitioning from non-tech to tech jobs. Starting the Transition "It's all about realizing that your career is not moving forward and finding out what will work for you in the tech industry." Mariana began her journey in the tech world in 2021, identifying a significant demand for professionals seeking to pivot their careers into technology. She observed that despite having good jobs, many were dissatisfied and felt their careers stagnated. This led her to found Tekya, a company dedicated to aiding professionals in moving to tech without a coding background and leveraging their careers to build their dream life. "Conquering the mindset that you can perform even if you are not tech-savvy is the first step towards building a career that truly gives you the life you want." One of the first hurdles Mariana noticed was the limiting beliefs held by individuals. Many feel inadequate and struggle to convince hiring managers of their worth due to a lack of tech-specific skills. Essential Skills for Scrum Masters and Agile Coaches "Hire for character, train for skills. Focus on small improvements to continually develop both yourself and your teams." Mariana stresses the importance of soft skills such as communication, conflict resolution, and servant leadership. These skills are pivotal for anyone aspiring to roles like Scrum Master or Agile Coach. "Understanding and mastering the hard skills of your chosen tech role will not only improve your confidence but also build trust with your team." Hard skills are equally crucial, with Mariana emphasizing the need to understand the Scrum framework, Agile methodologies, organization, metrics, and engineering best practices. She also mentions the importance of becoming familiar with the tech vocabulary specific to each company. For learning these essential skills, Mariana suggests starting with understanding the day-to-day routine of a Scrum Master or Agile Coach. She recommends finding courses that cover both soft and hard skills necessary for these roles. "Changing your mindset is crucial. Be prepared to invest time and some money into structured learning paths like those offered by Tekya." Building a Professional Identity "Showcase how your past experiences have prepared you to add value in the tech industry." Mariana advises starting immediately to tailor your LinkedIn profile and other professional materials to reflect your new career path, emphasizing past experiences and how they relate to your future in tech. "The support from a professional community can be the most comforting part of your transition journey." Networking is vital in the tech industry. Mariana encourages speaking with those already in the role and participating in communities like Tekya to find mentors and expand your professional circle. "Understand the mission of the company and align it with your values to increase your chances of getting hired." When it comes time to apply for jobs, Mariana recommends focusing on companies whose mission and products you are passionate about. Ensuring your LinkedIn profile and cover letters are top-notch will help you stand out. Further Learning and Resources "Real stories from real people can provide the motivation and roadmap for your own career transition." For those eager to learn more about this employment transition, Mariana suggests listening to success stories from individuals who have successfully made the transition. About Mariana Trigo Mariana Trigo's professional journey began in biology, transitioned through retail, and found its niche in technology. She excelled as a Scrum Master and grew into an Engineering Manager role, always focusing on helping teams deliver more effectively and enjoyably. In 2021, she launched Tekya to empower professionals to move into tech roles, enhancing their careers and achieving their life dreams without necessarily having a coding background. You can link with Mariana Trigo on LinkedIn. You can follow Mariana's work as a coach and Tekya, her company's work with budding Agile Coaches and Scrum Masters on Instagram and LinkedIn.

Peter Müller: Fostering Future Agile Leaders, An Inside Look at the Apprentice Program for Agile Coaches and Scrum Masters 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, Peter introduces us to an innovative “Apprentice Program” designed to cultivate accountability and enhance skills among developers, scrum masters, and product owners. This transformative initiative not only equips participants with practical agile skills but also fosters a cohesive agile community within the organization. By involving leadership and aligning learning objectives with organizational needs, the program sets a precedent for sustainable, organization-wide agile adoption. What can other organizations learn from this approach to develop agile leaders effectively? Learn how the Apprentice Program Peter and his colleagues set up can help you overcome a stalled Agile adoption.   [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 Peter Müller Peter is a seasoned Agile coach and transformation consultant with extensive experience in fostering agile environments and enhancing team dynamics. His expertise in solution-focused coaching has helped numerous teams optimize their operational efficiency and adapt to agile methodologies effectively.   You can link with Peter on LinkedIn and connect with Peter on Twitter.

Bio Dr. Jeff Sutherland is the inventor and co-creator of Scrum, the most widely used Agile framework across the globe.  Originally used for software development, Jeff has also pioneered the application of the framework to multiple industries and disciplines. Today, Scrum is applied to solve complex projects in start-ups and Fortune 100 companies. Scrum companies consistently respond to market demand, to get results and drive performance at speeds they never thought possible. Jeff is committed to developing the Agile leadership practices that allow Scrum to scale across an enterprise.   Dr. Sutherland is the chairman and founder of Scrum Inc. He is a signatory of the Agile manifesto and coauthor of the Scrum Guide and the creator Scrum@Scale. Jeff continues to teach, create new curriculum in the Agile Education Program and share best practices with organizations around the globe. He is the founder of Scrum Inc. and coauthor of, Scrum: The Art of Doing Twice the Work in Half the Time, that has sold over 100,000 copies worldwide.    Social Media:                 LinkedIn: linkedin.com/in/jeffsutherland                 Twitter: @jeffsutherland Website: Scrum Inc https://scruminc.com               Books/ Articles: The Scrum Guide by Jeff Sutherland and Ken Schwaber http://www.scrumguides.org/index.html Scrum: The Art of Doing Twice the Work in Half the Time by Jeff Sutherland The Scrum Fieldbook by JJ Sutherland Agile Competitors and Virtual Organisations by Steven Goldman, Roger Nagel and Kenneth Preiss https://www.amazon.co.uk/Agile-Competitors-Virtual-Organizations-Engineering/dp/0471286508 Accelerate: Building Strategic Agility for a Faster Moving World by John P. Kotter Leading Change by John P. Kotter Process Dynamics, Modeling and Control by Babatunde A. Ogunnaike and Harmon W. Ray A Scrum Book: The Spirit of the Game by Jeff Sutherland, James Coplien, Mark den Hollander, et al    Interview Transcript Ula Ojiaku: Hello everyone, my guest today is Dr Jeff Sutherland. He is the inventor and co-creator of Scrum, the most widely used Agile Framework across the globe. Originally used for Software Development, Jeff has also pioneered the application of the framework to multiple industries and disciplines. Today, Scrum is applied to deliver complex projects in startups and Fortune 100 companies. Dr Jeff Sutherland is the Chairman and Founder of Scrum Inc. He is a signatory of the Agile Manifesto and co-author of the Scrum Guide and the creator of Scrum at Scale. Jeff continues to teach, create new curriculum in the Agile education programme and share best practices with organisations around the globe. He has authored and co-authored a number of books which include Scrum: The Art of Doing Twice the Work in Half the Time – which has sold over 100,000 copies worldwide. In this episode, Dr Sutherland shares the backstory of how he and Ken Schwaber developed the Scrum framework. I was pleasantly surprised and proud to learn that one of the inspirations behind the current Scrum framework we now have was the work of Prof Babatunde Ogunnike, given my Nigerian heritage. Dr Sutherland also talked about the importance of Agile Leadership and his current focus on helping organisations fix bad Scrum implementations. I'm sure you'll uncover some useful nuggets in this episode. Without further ado, ladies and gentlemen, my conversation with Dr Sutherland.   Ula Ojiaku: Thank you, Dr. Sutherland, for joining us on the Agile Innovation Leaders podcast. It's a great pleasure to have you here. Jeff Sutherland: Glad to be here. Looking forward to it. Ula Ojiaku: Fantastic. So could you tell us about yourself? Jeff Sutherland: Well, I grew up in a small town in Massachusetts. And I always felt that I would go to West Point of the United States Military Academy, even at a very young age. And I finally made it there. I spent four years there. And I went on to a program where a certain number of cadets could join the Air Force. And I told the Air Force, if they made me a fighter pilot, I would move into the Air Force, which I did. I spent 11 years as a fighter pilot in the Air Force. And most of the operational aspects of Scrum actually come from that training. My last tour in the Air Force was actually at the US Air Force Academy, I was a professor of mathematics. And I had gone to Stanford University in preparation for that position. And I had worked closely with the, at the time he was Head of the Department of Psychiatry, became the Dean of Stanford who had studied under my father-in-law, he had become an MD under my father-in-law, who was a brilliant physician. And I was working on research papers with him, both at Stanford and at the Air Force Academy. And I asked him for guidance. And I said, I'm thinking about, given all the work we've done in the medical area. Starting in Stanford, I'm thinking maybe becoming a doctor - become an MD. And he strongly recommended against that he said, ‘you'll just go backwards in your career, what you need to do is you build on everything you've done so far. And what you have is your fighter pilot experience, your experience as a statistician, and a mathematician, you want to build on that.' So, I had already started into a doctoral program at the University of Colorado School of Medicine, which was not far from the Air Force Academy. And so, I talked to my department Chairman there who offered me a position in the department running a large research grant, funded by the National Cancer Institute and so, I decided to exit the Airforce and join the medical school. While I was finishing up my doctoral degree. And as soon as my doctorate was finished, I became a professor of Radiology, preventive medicine and biometrics. I was a joint across multiple departments. And I was doing mathematical research on modeling, particularly the human cell on a supercomputer, (to) determine what caused cancer. And to do that required extensive mathematical research as well as the medical research. But at the end of the day, what we found was for any complex adaptive system, like a human cell, or a person or a team, they go through different states. And they're moved from one state to the next by some kind of intervention. And so, if you understand what causes those changes… turned out in the case of cancer, there were four different states that led to a tumor. And in every state, there were certain interventions, and if you knew what they were, you could prevent them and prevent cancer. Or you could even, to my surprise, take a cancer cell and make it go backward into a normal cell. So, this fundamental understanding is the theory behind Scrum. So, while I'm doing this all at the medical school, a large banking company came by and said, ‘you know, over the medical school, you guys have all the knowledge about the technologies; the new technology, we're using (for) banking, you're using for research.' And they said, ‘you guys have all the knowledge but we have all the money and they made me an offer to come join the bank'    Ula Ojiaku: [Laughs]You couldn't refuse Jeff Sutherland: Not just me, it was my family. So, I wind up as Vice President for Advanced Systems, which was effectively was the CTO for 150 banks that we were running across North America.   Each was, you know, a dozen, 50, 100 branches. And of course, we were mainly doing the software, installation and support to run the banking operation, which is largely computer stuff – (this) is what banks run off. And as we're building these systems with hundreds and hundreds of developers, one of the first things I noticed is that all the projects were late. And I look at what they're doing. And they're using this process where they spend, you know, six months defining requirements, and then they put all the requirements into a Gantt chart. And then they, they plan on taking six months to build something, but it's never done. Because as soon as they start testing that they find there's all kinds of things that are broken. So, virtually every single project of the bank is late. So, as a head of technology, one day I walked into the CEO's office and I said, ‘Ron,  have you noticed all your projects are late?' He said, ‘Yes'. He says, ‘Every morning at least five CIOs or CEOs of the banks, they call me up.' And he says, ‘they scream at me.' I said, ‘wow', I said, ‘You know, it's going to get worse, not better. Because these guys are using this, these Gantt Charts.' And I showed him one. And then being a mathematician, I mathematically proved that every project would be late at the bank. And he was stunned. And he said, ‘what should I do?' I said, ‘we need a completely different operating system in the bank.' This is back in 1983. ‘Let's take one business unit. Let's take the one that's losing the most money, okay, the worst business unit' Ula Ojiaku: They have nothing to lose then. Jeff Sutherland: And it was the automated teller division that was rolling out cash machines all over North America. It was a new technology and they had a ton of problems. So, I said, ‘let's take that unit and every one, sales, market, support, installation, we're going to split them down into small teams. And we're going to have Product Marketing come in on Monday with a backlog prioritized by business value. And at the end of the week, on Friday, we're going to deploy to 150 banks.' ‘And I'm going to train them how to land a project every week, just like I trained fighter pilots to land aircraft. I'm going to give them a burndown chart, we're going to throw away the Gantt Chart, I'm going to give them a burndown chart to show them how to land the project.' So, he said, ‘Well, that's gonna be a big headache.' I said, ‘look, the bank needs to be fixed.' He said, ‘Okay, you got it.' So, I took that unit. I told them, ‘I know it's gonna take several weeks,' today we call them sprints, ‘for you to be successful.' Because as new pilots, trained to land, these high-performance jets, they tend to come in high and then they have to come around and try to land again, they over and over, they practice until they can nail it. And it took them six weeks, six sprints to actually nail the end of the week (and) deploy (to) 150 banks. But within six months, it became… it went from the worst business unit in the bank to the most profitable business unit in the bank. And the senior management said, ‘you know, Jeff, here's another 20 million dollars to throw at whatever that thing you're doing  it's the most profitable thing in the bank, we're gonna put more money in that. So that was the first prototype of what we call today Scrum at Scale. Now, I've been CTO of 11, or CTO or CEO of 11 different companies. And for the next 10 years, I prototyped that model and advanced technology teams until in 1993, at a company called Easel Corporation, we found that because of the tooling we were building and selling to customers, we needed to build the tool with what today we call Agile Practice. Ula Ojiaku: Yes Jeff Sutherland: And we need to train the customer to use the tool by having teams do an agile practice. So, in order to train our customers properly in 1993, we actually had to formalize what I've been prototyping for 10 years. And we wrote it down and at the time we were reading this paper, we're going through 1000 papers in the journals I, you know, I had done many new technology. And, in every one of them, you have to read everything that's ever been done so that you can go beyond. You can use everything that's been done, but then you go beyond, okay? Ula Ojiaku: Yeah Jeff Sutherland:  So, it's a tremendous amount of research to launch new technology. And at about the 300th paper in our file, it was a paper out of the Harvard Business Review, which really surprised me, by two Japanese Business School professors, Professors Takeuchi and Nonaka. And in there, they described the best teams in the world. They were lean hardware teams that reminded them of a game of rugby, they said, ‘we're going to call what they're doing Scrum Project Management.' So, I said to the team, ‘we need a name for this thing that we're going to train our customers in, and let's call it Scrum.' And off we went. So, for the next two years, we were actually using Scrum within Easel deploying products. But it was not public, to the general industry. And Easel got acquired by a larger company. And at that time, I felt that this needed to be rolled out into the industry because we had benchmarked it with the best tooling in the world from the leading productivity company, and showed that it was… that (it) went 10 times faster. The quality was 10 times better, which is what you need for a new technology innovation. And so, I felt it was ready to go to the industry as a whole. So, I called up an old friend, Ken Schwaber. And he was a CEO of a traditional Project Management software company, a waterfall (methodology). He sold these methodologies with 303 ring binders, a software package that would make Gantt Charts. So, I said, ‘Ken, I want you to come up and see the Scrum, because it actually works and that stuff you're selling doesn't work – it makes projects late.' And he agreed to come in, he actually came up, he met with me. He stayed for two weeks inside the company, working, observing the Scrum team. And at the end of those two weeks, he said, ‘Jeff, you're right. This really works - it's pretty much the way I run my company.' He said, ‘if I ran my company with a Gantt Chart, we would have been bankrupt a long time ago.' So, I said, ‘well, why don't you sell something to work that works instead of inflicting more damage on the industry?' So, he said so we said ‘okay, how (do) we do it?' I said, ‘it needs to be open source, it needs to be free.' Ken felt we needed to take the engineering practices, many of which appear today in extreme programming… Ula Ojiaku: Yes Jeff Sutherland: …and let Kent Beck (creator of eXtreme Programming, XP) run with them because Kent had been sending me emails, ‘Jeff, send me every...', he had been following the development of Scrum, ‘…send me everything on Scrum, I'm building a new process. I want to use anything that you've done before and not try to reinvent anything.' So, he (Ken Schwaber) said, ‘let Kent take the engineering practices, we'll focus on the team process itself.' And we agreed to write the first paper on this to present at a big conference later that year. And writing that paper was quite interesting. Ken visited DuPont Chemical Corporation, the leading Chemical Process Engineers there that they had hired out of academia to stop chemical plants from blowing up. And when Ken met with them, they said, describe what we were doing in the software domain. They said, ‘you know, well, that process that traditional project management is a Predictive Process Control System. We have that in the chemical industry.' ‘But it's only useful if the variation in the process running is less than 4%.' They said, ‘do you have less than 4% change in requirements while you're building software?' Ken says, ‘no, of course not! It's over 50%!' And they started laughing at him. They said, ‘your project's going to be exploding all over the place.' ‘Because every chemical plant that has blown up has been somebody applying a predictive control system to a system that has high variability. You need to completely retrain industry to use Empirical Process Control, which will stop your projects from blowing up. And they said, here it is, here's the book, they had the standard reference book for Chemical Process Engineering. And in there, there's a chapter on Empirical Process Control, which is based on transparency, inspection, and adapting to what's happening in real time. Okay, so those are the three pillars of Scrum that are today at the base of the Scrum guide. Ula Ojiaku: Do you still remember the title of the book that the chemical engineers recommended to Mr. Schwaber by any chance? Jeff Sutherland: Yeah, so I have a, when I do training, I have a slide that has a picture of the book (Process Dynamics, Modelling and Control). It's written by Ogunnaike and Ray. But that is the root of the change that's gone on in the industry. And so then from 1995, forward, Ken and I started working together, I was still CTO of companies. And I would get him to come in as a consultant and work with me. And we'd implement and enhance the Scrum implementations in company after company after company. Until 2001, of course, Scrum was expanding but Extreme Programming in 2001, was actually the most widely deployed. They were only two widely-deployed agile processes at the time of Scrum and Extreme Programming. Extreme Programming was the biggest. And so, the Agile Manifesto meeting was convened. And it had 17 people there, but three of them were Scrum guys - that had started up Scrum, implemented it in companies, four of them were the founders of Extreme Programming. And the other 10 were experts who have written books on adaptive software development or, you know, lightweight processes, so, industry experts. And we, we talked for a day and everybody explained what they were doing and there was a lot of arguments and debate. And at the end of the day, we agreed because of this book, Agile Competitors, a book about 100 hardware companies - lean hardware companies, that have taken Lean to the next level, by involving the customer in the creation of the product. And we said, ‘we think that we all need to run under one umbrella. And we should call that Agile.' Ula Ojiaku: So, did you actually use the word umbrella in your (statement)? Oh, okay. Jeff Sutherland: Often, people use that right? Ula Ojiaku: Yes, yes Jeff Sutherland: Because at the time, we had Agile and Extreme Programming, and now everybody's trying to come up with their own flavor, right?  All under the same umbrella of ‘Agile'. And that caused the both Scrum and Extreme Programming started to expand even more, and then other kinds of processes also. But Scrum rapidly began to take dominant market share, Scrum today is about 80% of what people call Agile. The reason being, number one, it was a technology that was invented and created to be 10 times better. So, it was a traditional new technology developed based on massive amounts of research. So, it worked. But number two, it also scaled it worked very well for many teams. I mean, there are many companies today like Amazon that have thousands of Scrum teams. And Extreme Programming was really more towards one team. And (reason number) three, you could distribute it across the world. So, some of the highest performing teams are actually dozens of teams or hundreds across multiple continents. And because of those three characteristics, it's (Scrum has) dominated the market. So that brings us to in 2006, I was asked by a Venture Capital firm to help them implement Scrum in their companies, they felt that Scrum was a strategic advantage for investment. And not only that, they figured out that it should be implemented everywhere they implemented it within the venture group, everybody doing Scrum. And their goal was to double their return on investment compared to any other venture capital firm. They pretty much have done that by using Scrum, but then they said, ‘Jeff, you know, we're hiring you as a consultant into our companies. And you're a CTO of a healthcare company right now. And we don't want to build a healthcare company, we want to build a Scrum company.' ‘So, why don't you create Scrum Inc. right here in the venture group? We'll support it, we'll do the administrative support. We'll write you a check - whatever you want.' So, I said, ‘well, I'm not going to take any money because I don't need it. I understand how that works. If the venture capital firm owns your company, then (in the) long term, you're essentially their slave for several years. So, I'm not taking any money. But I will create the company within the venture group. If you provide the administrative support, I'll give you 10% of the revenue and you can do all the finances and all that kind of stuff. So, that's the way Scrum Inc. was started to enable an investment firm to launch or support or invest in many dozens of Scrum companies. Ula Ojiaku: That's awesome Jeff Sutherland: And today, we're on the sixth round of investment at OpenView Venture Partners, which was the company the six round is 525 million. There's a spin out from OpenView that I'm working with, that has around this year, 25 million. And over the years, just co-investing with the venture group I have my own investment fund of 50 million. So, we have $570 million, right this year 2021 that we're putting into Scrum companies. Agile companies, preferably Scrum. Ula Ojiaku: Now when you say Scrum companies is it that they facilitate the (Scrum) training and offer consulting services in Scrum or is it that those companies operate and you know, do what they do by adopting Scrum processes? Jeff Sutherland: Today, Scrum Inc sometimes help some of those companies, but in general, those companies are independently implementing Scrum in their organizations.   Ula Ojiaku: Right Jeff Sutherland: And okay, some of them may come to Scrum training, maybe not. But since Scrum is so widely deployed in the industry, Scrum Inc, is only one of 1000 companies doing Scrum training and that sort of stuff. So, they have a wide variety, wide area of where they can get training and also many of the startups, they already know Scrum before they started the company. They are already Agile. So, what we're interested in is to find the company that understands Agile and has the right team players, particularly at the executive level, to actually execute on it. Ula Ojiaku: No matter what the product or services (are)… Jeff Sutherland: Products or services, a lot of them are software tooling companies, but some of them are way beyond that, right? So, turns out that during COVID… COVID was a watershed. The companies that were not agile, they either went bankrupt, or they were crippled. That meant all the Agile companies that could really do this, started grabbing all the market share. And so, many of our companies, their stock price was headed for the moon during COVID. While the non-agile companies were flatlined, or are going out of business, and so the year of COVID was the best business year in the history of venture capital because of Agility. So, as a result, I'm spending half my time really working, investing in companies, and half of my time, working with Scrum (Inc.) and supporting them, helping them move forward. Ula Ojiaku: That's a very impressive resume and career story really Dr. Sutherland. I have a few questions: as you were speaking, you've called Scrum in this conversation, a process, a tooling, the technology. And you know, so for some hardcore Agilists, some people will say, you know, Agile is all about the mindset for you, what would you say that Scrum is it all of these things you've called it or would it be, you know, or it's something (else)...? Jeff Sutherland: So, certainly the (Agile) mindset is important. But from an investment point of view, if the organization can't deliver real value, quickly, agile is just a bunch of nonsense. And we have a huge amount of nonsense out there. In fact, the Standish group has been publishing for decades. 58% of Agile teams are late over budget with unhappy customers. So, when you get these hardcore Agilist, that are talking about mindset, you have to figure out ‘are they in the 42% that actually can do it or are they in the 58% that are crippled?' My major work with Scrum Inc. today is to try to get to fix the bad Scrum out there. That is the biggest problem in the Agile community. People picking up pieces of things, people picking up ideas, and then putting together and then it doesn't work. That is going to that's going to be really bad for agile in the future. If 58% of it continues not to work. So, what we found, I mean, it was really interesting. Several years ago, the senior executive (of) one of the biggest Japanese companies flew to Boston wanted meet with me. And he said to me, ‘the training is not working in Japan for Scrum.' He said, ‘I spent 10 years with Google, in Silicon Valley. So, I know what it looks like what actually works. And I can tell you, it's not working in Japan, because the training is… it's not the training of the Scrum that is high performing. And in fact, our company is 20% owned by Toyota, and we are going to be the trainers of Toyota. And we cannot deliver the training that's currently being given to Toyota, it will not work, it will not fly. And we want to create a company called Scrum Inc. Japan. And we're a multibillion-dollar company, we're ready to invest whatever it takes to make that happen.' To give them the kind of training that will produce the teams that Takeuchi and Nonaka were writing about in the first paper on Scrum. And as we work with them to figure out what needs to be in that training, we found that the Scrum Guide was only 25% of the training. Another 25% was basic Lean concepts and tooling, right? Because the original Scrum paper was all about Lean hardware companies. So Lean is fundamental to Scrum. If you don't understand it, you can't do it. And then third, there are certain patterns of performance that we've developed over the years, we spent 10 years writing a book on patterns - Scrum patterns. And there's about a dozen of those patterns that have to be implemented to get a high performing team. And finally, scaling to multiple teams. It turns out, right about this time I started working with the Japanese, I was at a conference with the Agile Leadership from Intel. And they told me that they'd introduced Scaling Frameworks into Intel division, some of which had more than 500 Scrum teams in the divisions and the Scaling Frameworks had slowed them down. And it made the senior executives furious and they threw them all out and they said, we did not want to hear the word Scrum at Intel anymore. But you guys need to go twice as fast as you're going now. So, they came to me, they said, ‘we're desperate. We have to go twice as fast. We can't even use the word “Scrum”. What should we do?' And they blamed me, they said, ‘Sutherland you're responsible you caused problem, you need to fix it.' So, I started writing down how to do what today we call Scrum at Scale. And everybody, you know, most of those people in the industry were implementing IT scaling frameworks. They were all upset. ‘Why are you writing down another framework?' Well, it's because those IT frameworks do not enable the organization to show Business Agility, and win in the market. And in the best companies in the world, they're being thrown out. So, I've had to write down how do you add, how do you go to hundreds and thousands of Scrum teams - and never slow down as you're adding more and more teams. You know, every team you add is as fast as the first team when you start. Yeah, that's what Scrum at Scale is all about. So, there's two primary things that I'm focused on today. One is to fix all this bad Scrum. Second is to fix the scaling problem. Because it turns out that if you look at the latest surveys from Forbes magazine, and the Scrum Alliance on successful Agile transformations - I learned recently, that almost every company in the world of any significance is going through an Agile transformation or continuing transformation they'd already started years ago. And 53% of them do not meet management expectations. And the MIT Sloan Business Review did an analysis of what happens if an agile transformation fails, and 67% of those companies go out of business. So, this is becoming really serious, right? To be successful today, if you're competing in any significant way, you have to be agile. And number two, if you try to be agile and fail, you have a 67% chance going out of business. And the failure rate is 53%. So, this is the problem that we're wrestling with. And half of that 53% failure is due to the bad Scrum we talked about, but the other half is due because of the leadership not being Agile. Ula Ojiaku: I was just going to say, as you said something about the leadership not being agile. In my experience, you know, as an agile coach in some organizations whilst the teams would embrace you know, Scrum and embrace Agility - the practices and the processes and everything. There's a limit to, you know, how much they can get done… Jeff Sutherland: Absolutely… Ula Ojiaku: …if the leadership are not on board. So… Jeff Sutherland: …you hit this glass ceiling. So, I've been, you know, giving presentations on Agile Transformations around the world. And I can remember multiple times I've had 300 people in the room, say, and I say okay, ‘How many of you are agile, in Agile transformations or continuing the ones you'd started?' Of course, everybody raises their hand. ‘How many of you have waterfall traditional management that expects you to deliver all the old Gantt Chart reports that we always got, and don't understand what you're doing?' There's 300 people in the room and 297 people raised their hand. I said, ‘you need to give your leadership the book by Professor Kotter called Accelerate.' Professor Kotter is one of the leading change experts of the world. Ula Ojiaku: And he also, yeah, He also wrote ‘Leading Change' as well - the book, yes. Jeff Sutherland: And in that book, he says, if the leadership of the Agile part of the organization is traditional in their mindset and requirements, the Agile Transformation will eventually fail 100% of the time. Ula Ojiaku: Those are sobering statistics in terms of, you know, the failure rate and how much of you know the success hinges on business agility and the leadership being agile as well and taking the time to know and care what it means. Yeah. Jeff Sutherland: And what's happening is that the Agile Leadership today, if you look at some of the companies that have been most successful during COVID, one of them is John Deere Corporation, the biggest farm equipment manufacturer in the world, probably the oldest. Their stock price went up more than Amazon during COVID. And the board of directors gave their Agile Leadership, the Agile Coaches, Scrum Masters, the highest award in the Corporation for producing that result. So that's another reason I'm trying to communicate to Agile people. The success and survival of your company depends on you. You think your management's going to save you but no, if they are old-style people, they are going to run that company out of business. And you need to either save it before it goes out of business or run to another company before bad things happen. Ula Ojiaku: It's impressive that, you know, John Deere being a farm equipment manufacturer… I think they were ahead of the curve you know, (compared to some of their contemporaries in that industry as well) and embraced agile ways of working. Do you know how their Agile Leadership were able to quantify their contributions to the company? Jeff Sutherland: John Deere started to get Agile more than 10 years ago. So, they've been at it a long time. But in recent years, they really started to build… build internally… Agile leadership, you know, based on my work and they started applying that across the company. I mean, the major focus has not been software actually – it's been in other parts of the company. What has to happen to run a company that's building tractors? Well, there's all kinds of things that have to happen, you know - purchasing, there's legal, there's acquiring all the pieces, it's putting them together at the assembly line, you know, software is a piece of it. You know, that's probably the easiest piece to fix with Agile, it's the rest of the company that's the challenge. They have started doing that really well which is reflected in their stock price. Ula Ojiaku: Amazing. So, you said something about you know, you're out to fix a couple of things, the problem with bad Scrum out there. And, you know, the problem with scaling agile. Jeff Sutherland: Right Ula Ojiaku: So, with respect to the first one, the point about bad Scrum, what in your experience would be the root cause of bad Scrum implementations in organizations? Jeff Sutherland: There're about 11 things, that if you fix them, the team will go twice as fast. And it's multiplicative. So, you know, we have extensive data on, you know, really big companies. What's the difference between the fastest team and the slowest teams? The fastest teams are 2000 times faster than the slowest teams. So why is that? Well, first, the team has to be small. The optimal team size is four or five people. If you have a 10-person team, that's going to take at least 50% longer to get anything done. If you go out, look at the team size, you'll see companies have even not only ten-people teams, they have 15 people in a team, 25 people in a team, okay? Those teams are never gonna meet Agile performance. Second, the backlog needs to be really ready in a sense of small, it's clearly understood, it's properly prioritized. So, you need somebody managing that backlog that can get it right, because we have extensive data for multiple case studies showing the team's production doubles immediately. As soon as you get that backlog right. So you go into many companies, you'll see, there's still arguing about what's the top priority, right? Or everything's top priority. That's just gonna create a massive mess. Third, teams are constantly interrupted. You know, the only teams I know that aren't interrupted are people… these teams and defense contractors working on top secret stuff. And they work in a locked room, the door, it says ‘no managers can enter' and they don't get interrupted. But for the rest of us, there's always somebody coming in wanting something else done. And there's a way to manage that using a pattern we call the interrupt buffer. And if you don't have that pattern implemented properly, you're gonna go half as fast. If you're lucky, you might go half as fast. Ula Ojiaku: And what do you say the Scrum Master has a part to play in making sure the interrupt buffer is there and it's enforced? Jeff Sutherland: The scrum master needs to set this all up. Fifth, in high performing teams, we see this pattern called swarming, where multiple people are working on a story together. That increases the process efficiency, which doubles the performance of the team. So, if people are specialists working independently, that team is going to be really slow. So I'm up to number five, there are six more things, but you probably want to go through them. It's very clear, what makes agile teams suck, we know exactly why. And it needs to be fixed. So, I appeal to anyone listening to this help fix bad agile, it's hurting us all. Ula Ojiaku: Thank you for sharing that. Would this be in any of any of your books or in any of your articles that you've written? Jeff Sutherland: Yeah, it's everywhere and (in) everything I've written, but the best summary, it's the red book Scrum … Scrum, The Art of Doing Twice the Work and Half the Time And we've had people pick, pick this up. A CEO in Kenya came to New York to one of my courses, he said, ‘Jeff, I just read your book. And I'm CEO with three new energy startups in Kenya. And my teams implemented that, and they're going… they're doing three times the work and a third of the time. So, your book is too conservative.' He says to me, this guy, he only read the book, he had no training. So, this book is enough to really get off on the right foot. And if you're having problems, it's enough to fix things. In fact, recently before COVID when we could get everybody together, we had an Apple employee in the class and she said, Jeff, do you know why Apple always meet its states? I said, no, you know, Apple is really secretive. They don't tell anybody anything. She says ‘it's because they do Scrum by the book.' So, I said, ‘What book?' She says, ‘The Red Book - Scrum, The Art of Doing Twice the Work and Half the Time - they do it exactly by the book.' So, again, my message to the Agilists out there: Apple is winning. They are the most valuable company in the world. And it's because they do Scrum exactly by that book. So, you probably should read it. Ula Ojiaku: Definitely. So going by the book, would you say there's any wriggle room for adapting to one's context, or is it about you know, going, ‘check- we've done page 123…' Jeff Sutherland: Well, the whole thing about adapting is fundamental to Scrum. So, one of the things I'm constantly doing in my talks, training, is I'm going back to before Scrum and reading a paper from the leading researchers on complex adaptive systems, in which they mathematically proved, you model things on the computer, that systems evolve more quickly, if they have more degrees of freedom, up until you hit a boundary where the system goes into a chaotic state. So, from the very beginning in Scrum, maximizing the freedom and the decision capability of the team has been fundamental. And we talked about this as self-organization. Now, unfortunately, that term has been so misused, misunderstood that we had to take self-organization out of the Scrum guide. And what we inserted was self-managing. And we put next to it goals, okay, the theme is self-managing to achieve a goal. And to make that happen, they need a commitment to do that. And so, this is one of the fundamental things for Agile teams that work that they have that self-managing commitment to achieve a goal. And the teams that are not working, they're fuzzy about that, right. So, we want the maximum degree of adaptation, the thing that they don't want to change is the basic structure that's in the red book, if they change that, it has the control mechanisms to allow the maximum degree of self-organization - not to go off the rails. Ula Ojiaku: Right. Jeff Sutherland: So, we see a lot of Agilists, ‘oh, you know, let's just tweak the framework this way or that way.' And then the self-organization takes a team off the rails, and then they fall into that 58% that can't deliver, they're late, they're over budget, the customers aren't happy. And so, this is the really one of the hardest things to communicate to people. There're certain things that you absolutely have to be disciplined about. You have to be more disciplined to get a great Agile team than in all ways of working. And that discipline is what allows the maximum degree of self-organization and self-determination, right? So, understanding those two things together, you know, it makes it makes people's brain explode, right? It's hard. Ula Ojiaku: But it works. Jeff Sutherland: But it works right.  Ula Ojiaku: You've already mentioned a lot of books in the course of this interview session, and these would be in the show notes. So, would there be anything any final word of advice you'd have for the leaders that would be listening to this podcast in terms of their transformation journey? Jeff Sutherland: So, one of the things we did to Scrum at Scale is that the difference between that and most of the other scaling frameworks is that it's all about the leadership. So, we need an operating leadership team, that is a Scrum team that needs a Scrum Master, a Product Owner, backlog. And its objective is to improve the Agile implementation of the organization. On the prioritization side, we need a leadership team that, led by a Chief Product Owner, that is prioritizing backlog across the organization. So, you know, I've had the Chief Product Owner of Hewlett Packard in my course, he had a $200 billion portfolio. He learned from that class. Says this class is pretty good.' He said, ‘In just one slide I figured out how to get $20 billion more a year with no additional resources'. Just by understanding how to work the framework right? At the $200 billion level. Ula Ojiaku: And you're talking about the Scrum at Scale course, right? Jeff Sutherland: No, this was a product owner course. Product Owner course. He came to it. We're now doing a Scrum at Scale… we're actually doing a Chief Product Owner course. So, a Product Owners at Scale course which it has been really well received by the leading Agile Practitioners. (They) really like that because they need to work more in the large than in the small often. Ula Ojiaku: Definitely. That means this available on the Scrum Inc site? Jeff Sutherland: Yes. Ula Ojiaku: Okay. Jeff Sutherland: So, one of the things I would recommend I would really recommend is the Scrum Field Book. It's a bunch of case studies for organizations, large and small, that have tried to take the whole organization to Scrum. Well, thank you so much, Dr. Sutherland - it's been a great pleasure having you and hopefully we could have a you know, follow up conversation sometime. Jeff Sutherland: Yes. Thanks for inviting me and glad to do it again. Ula Ojiaku: That's all we have for now. Thanks for listening. If you liked this show, do subscribe at www.agileinnovationleaders.com. Also share with friends and leave a review. This would help others find the show. I'd also love to hear from you, so please drop me an email at ula@agileinnovationleaders.com. Till next time, take care and God bless!    

Is The Party Over For ScrumMasters and Agile Coaches? Join V. Lee Henson as we continue the conversation around the great transition of roles and titles in the Agile Community... How to connect with AgileDad: - [website] https://www.agiledad.com/ - [instagram] https://www.instagram.com/agile_coach/ - [facebook] https://www.facebook.com/RealAgileDad/ - [Linkedin] https://www.linkedin.com/in/leehenson/

Johannes Andersen: Disjoint Silos, The Illusion of Teamwork and How it Affects Agile Coaches' Work 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 segment, Johannes reflects on his transition from a business unit to an HR position, which initially seemed promising due to the team-based approach they embraced in HR. However, he soon discovered that the HR team lacked unity, with various small roles not functioning cohesively as a team. Tasked by his manager to enhance the HR team's effectiveness, Johannes found himself dedicating much of his time to internal issues rather than organizational improvement. The core issue was the absence of a shared goal, leading to misalignment and lack of collaboration within the team, effectively making them "disjoint silos" rather than a unified force. We discuss Vasco's mnemonic of “One Team, One Goal” andthe importance of aligning around a single, shared goal to foster true teamwork. Featured Book of the Week: "The Goal" by Eliyahu M. Goldratt In this segment, Johannes discusses how "The Goal" by Eliyahu M. Goldratt profoundly influenced him. Appreciating its novel-based approach, he found it uniquely effective for teaching new concepts, allowing readers to empathize with the learning process. Johannes admires the book's focus on outcomes and its clarity on defining a company's "goal," highlighting its system thinking approach as a critical aspect of understanding and solving organizational problems.   [IMAGE HERE] Do you wish you had decades of experience? Learn from the Best Scrum Masters In The World, Today! The Tips from the Trenches - Scrum Master edition audiobook includes hours of audio interviews with SM's that have decades of experience: from Mike Cohn to Linda Rising, Christopher Avery, and many more. Super-experienced Scrum Masters share their hard-earned lessons with you. Learn those today, make your teams awesome!     About Johannes Andersen Johannes comes from a finance and fintech background, and is now an enterprise agility maestro at a leading telco in Copenhagen! He focuses on optimizing the flow from strategy to execution, championing portfolio management with a keen eye on doing the right things, even if imperfectly. Johannes is an international speaker on product development topics. You can link with Johannes Andersen on LinkedIn.

BONUS: Beyond Frameworks, A Vision for Agile Coaching Excellence with Rahul Bhattacharya 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, we explore Rahul's experience with Agile Coaching and how he developed his coaching approach systematically and beyond any frameworks. His latest book is: Coaching Agile: A guide for Agile Coaches and Scrum Masters to build and scale their coach approach, and now available on Amazon.  The Agile Coach's Toolbox: Beyond Frameworks  Rahul's journey from startup co-founder to Agile Coach is a story of evolution and adaptability. His experience in the corporate world, starting as a product manager, led him to realize the power of Agile methodologies. Rahul emphasizes the importance of a broad perspective, advocating for a framework-agnostic approach in Agile coaching. He shares invaluable lessons about what works and what doesn't, offering a treasure trove of practices that transcend specific frameworks. This holistic approach is crucial for Scrum Masters and Agile Coaches who wish to apply the most effective strategies in diverse environments. The Agile Coach vs. Scrum Master: Clarifying Roles and Expectations  Rahul draws a distinct line between the roles of an Agile Coach and a Scrum Master. While a Scrum Master focuses on framework specifics, an Agile Coach takes a more versatile approach, borrowing practices from various frameworks. This differentiation is pivotal for professionals in the field, especially when navigating job roles and expectations. Rahul's book provides a roadmap for understanding these roles better, even as early as during the interview process. His insights on clarifying expectations and preparing for roles are invaluable for anyone aspiring to excel in the Agile domain. Understanding Products and Markets: The Agile Coach's Edge  In a striking perspective shift, Rahul highlights the necessity for Agile Coaches to deeply understand the products or services they're working with. This product-centric approach adds substance and context to Agile coaching, enabling coaches to have meaningful conversations about impact and efficiency. Rahul's background in product management becomes a vital asset here, showcasing how product knowledge can dramatically enhance the effectiveness of Agile methodologies. His emphasis on product discovery practices and on-site observations offers a concrete strategy for Agile Coaches to integrate product understanding into their coaching framework. Rahul's interview is a goldmine of insights for Agile Coaches and Scrum Masters. By focusing on these three key areas – an expansive toolbox, role clarity, and product understanding – Rahul provides a roadmap for professionals to elevate their Agile practices. For more on Rahul's systemic approach and his journey in the Agile world, visit Rahul's website and connect with him on LinkedIn.

Kulsoom Pervez: The Struggle for Team Unity, And How To Recognize Our Limits As Scrum Masters 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, Kulsoom shares her experience with a group of skilled individuals who struggled to function as a team. As their Scrum Master, she noticed a lack of accountability and ownership, issues with completing sprint stories, and a blame culture during retrospectives. The team, marred by tension between developers and QA, created an unhealthy environment. Despite her efforts to revitalize retrospectives and foster change, progress was slow and draining. Eventually, Kulsoom and several team members left the company, leading her to understand the limits of her influence and the importance of self-care and mental health for Scrum Masters and Agile Coaches. Featured Book Of The Week: Crucial Conversations: Tools for Talking When Stakes are High by Grenny et al. Kulsoom delves into how the book "Crucial Conversations" profoundly influenced her role as a Scrum Master. She emphasizes the book's impact in shaping her approach to crucial conversations, vital for anyone in a change agent role like hers. Highlighting the importance of courage and skill, Kulsoom discusses the book's framework for managing critical discussions effectively. She underscores how having a structured approach to conversations is essential for effective communication and problem-solving in agile environments.   [IMAGE HERE] Do you wish you had decades of experience? Learn from the Best Scrum Masters In The World, Today! The Tips from the Trenches - Scrum Master edition audiobook includes hours of audio interviews with SM's that have decades of experience: from Mike Cohn to Linda Rising, Christopher Avery, and many more. Super-experienced Scrum Masters share their hard-earned lessons with you. Learn those today, make your teams awesome!     About Kulsoom Pervez Kulsoom is passionate about constructing sustainable, resilient, and high-performing teams, consistently delivering value to customers through the transformative power of Agility. She embodies a leadership style that inspires, empowers, and fosters the growth of her colleagues. Kulsoom enjoys reading and has also dabbled in blogging. You can link with Kulsoom Pervez on LinkedIn.

BONUS: Unleashing the Power of Tension (Meetings) in Agile Teams with Sara Clark Are you an Agile Coach or Scrum Master looking to revolutionize your team dynamics?  Dive into our latest podcast episode featuring Sara, a pioneer in "Tension Meetings."  These meetings can transform conflicts into fuel for growth.  But what exactly are they? How can they reshape your team's future? Keep reading and uncover the secrets to harnessing tension! The Genesis of Tension Meetings Sara's journey from higher education to Agile methodologies led her to discover "Tension Meetings" while working in a volunteer collective. Despite the initial failure, these meetings proved instrumental in addressing underlying conflicts. The concept, rooted in Holacracy, begins with the premise that "something feels off," serving  Tension Meetings in Action Imagine a software team sitting down to address their unspoken challenges. Sara provides invaluable tips on setting up these meetings, emphasizing collective problem-solving and approaching tensions with curiosity. The key? Building trust within the team and creating a non-threatening environment for open dialogue. Wondering how to facilitate a tension meeting effectively? The podcast episode is packed with insider tips. The Transformative Impact of Tension Meetings: Sara shares real-world examples illustrating the profound impact of Tension Meetings on team dynamics and problem-solving. By carving out space for these discussions, teams can not only resolve current issues but also proactively address future challenges. Intrigued by the potential outcomes of Tension Meetings? The podcast sheds light on real success stories. As Agile Coaches and Scrum Masters, it's vital to continuously evolve and embrace innovative practices. Here are your key takeaways from our conversation with Sara: Identify and Embrace Tensions: Recognize the signs of unresolved tensions and see them as opportunities for growth. Facilitate with Curiosity and Trust: Learn to guide your team through these meetings with an open mind and a focus on building trust. Transform Tensions into Team Strengths: Use these meetings to turn challenges into collective goals and future-focused solutions. For a deeper dive into "Tension Meetings," including practical tips and real-life examples, don't miss our full podcast episode. Hear from Sara herself and start transforming your Agile practices today!

BONUS: Unveiling True Agility in Project Management, with Johanna Rothman 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.

SPaMCAST 788 is our annual SPaMCAST panel featuring most of the podcast regulars including:  Jeremy Berriault, Keis Kostaqi, Jon M. Quigley,  Jeremy Willets, and Tom Cagley appears in the ringmaster role.  Tony Timbol and Susan Parente, regular contributors, were unable to join and we missed them (this time of year is busy). Maybe I should do the annual panel in February, no one is busy in the colder parts of February.  During this year's panel, we talked about using AIs in coaching, working in the office, Jon tent, and took a look into 2024. This is a long podcast so I will keep the chit-chat down to a dull roar.  Learn to Solve IT's Dirtiest Secret! Work input, which includes prioritization and sequencing, is how work gets to an organization or team. If you get it wrong you are throwing time and money away. Simply put, poor work intake means “no agile for you”. Jeremy Willets and I have written tackling the topic that JRoss Publishing will publish in January 2024. In support of the book, we are building a live, workshop-based course for anyone deciding on what work gets completed!  This includes Agile Coaches, Scrum Masters, Product Owners, Project Managers, Program Managers, and Portfolio Managers - lots of people are involved which is part of the problem! The workshop will cover why work intake is the biggest challenge to teams and organizations today. Attendees will also learn what to do to solve this challenge. This cohort-based course will combine concise lectures, discussions, and exercises. It will provide space to learn and share with peers. We're using a survey to build a waitlist for the first cohort – link below. We will use the list to alert you when the workshop is available.     Next SPaMCAST  SPaMCAST 789 we will continue on our tour of some of the least talked about and most scary work intake problems. This is in the run-up to the release of  on January 9th. Preorder your copy now! We will also have a visit from Mr Jon M Quigley who is bringing his Alpha and Omega of Product Development column to the podcast.  

This week we continue in the minefield of why starting everything you are asked to do is problematic that we began in SPaMCAST 785. Framing the discussion is a text from a friend of the cast which highlights those requests that you just can't say no to. Lots of rationalizations and negative impacts. We will also have a visit from Susan Parente and her Not A Scrumdamentalist column. In this installment, we discuss the idea that everyone has a book in them.  Re-Read Saturday News Vacanti begins Chapter 3 of , by reminding the reader: “A predictable process behaves in a way we expect it to.” Further a predictable process exhibits only routine variation which means learning to distinguish signal and noise. Buy a copy and get reading - .  The current re-read entry Week 1:  – Week 2: – Week 3:   -     Learn to Solve IT's Dirtiest Secret! Work input, which includes prioritization and sequencing, is how work gets to an organization or team. If you get it wrong you are throwing time and money away. Simply put, poor work intake means “no agile for you”. Jeremy Willets and I have written tackling the topic that JRoss Publishing will publish in January 2024. In support of the book, we are building a live, workshop-based course for anyone deciding on what work gets completed!  This includes Agile Coaches, Scrum Masters, Product Owners, Project Managers, Program Managers, and Portfolio Managers - lots of people are involved which is part of the problem! The workshop will cover why work intake is the biggest challenge to teams and organizations today. Attendees will also learn what to do to solve this challenge. This cohort-based course will combine concise lectures, discussions, and exercises. It will provide space to learn and share with peers. We're using a survey to build a waitlist for the first cohort – link below. We will use the list to alert you when the workshop is available.     Next SPaMCAST  SPaMCAST 788 we will feature the annual SPaMCAST panel. As always the conversation will be rollicking. The topics will cover AI, working in the office, and a look into 2024.  

Sofia Katsaouni: Adapt and Thrive, A Success Perspective For Scrum Masters And Agile Coaches 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, Sofia defines success for Scrum Masters as achieving team self-organization by fostering independence and ownership. Emphasizing adaptability in the evolving dynamics of organizational living systems, she advises focusing on changes and working to create acceptance. Sofia shares a practical tip of viewing the Kanban board from right to left. Success, to her, is marked by team members raising previously discussed topics, indicating ownership. Featured Retrospective Format for the Week: Separating Event From Impact, A Lesson In Coaching And Reflection Skills In this episode, Sofia discusses a retrospective format focusing on "What happened?," "Impact on you," and "Your learnings." This format effectively separates events from their impact, encouraging diverse team experiences and fostering open communication. Sofia shares a retrospective involving an MVP release, highlighting how team members' perspectives enriched the discussion.   [IMAGE HERE] Retrospectives, planning sessions, vision workshops, we are continuously helping teams learn about how to collaborate in practice! In this Actionable Agile Tools book, Jeff Campbell shares some of the tools he's learned over a decade of coaching Agile Teams. The pragmatic coaching book you need, right now! Buy Actionable Agile Tools on Amazon, or directly from the author, and supercharge your facilitation toolbox!    About Sofia Katsaouni Sofia is a dedicated Agile and Organizational Coach who places people and their needs at the forefront. Transitioning from electrical engineering, she applies analytical skills to empower high-performing teams. With an emphasis on trust and psychological safety, Sofia enables startups and scale-ups to foster human-centric, performance-driven cultures. You can link with Sofia Katsaouni on LinkedIn. 

Software Process and Measurement Cast 784 features our conversation with Kevin Surace. Kevin is an AI Inventor, Futurist, and Keynote Speaker. We talk about the hype and promise of AI and whether you can ignore using AI in the workplace. My synopsis, embrace AI or live under a bridge. That might be a bit of hyperbole but if you lived through the PC revolution and the birth of the internet I think not.  Kevin's Bio Kevin Surace, is a renowned futurist, disruptive innovation keynote speaker, and pioneer in the AI space since the 1990s He is the  CTO of Appvance.ai which applies AI in the testing space.   Kevin has an impressive portfolio of nearly 100 worldwide patents, including the groundbreaking technology behind Siri and other virtual assistants. He is the visionary creator of one of the world's first smartphones and a dynamic speaker featured in over 15 thought-provoking TED and TEDx talks. His accomplishments have earned him accolades such as Inc. Magazine's Entrepreneur of the Year, CNBC's Innovator of the Decade, and an esteemed induction into RIT's prestigious Innovation Hall of Fame. LinkedIn: https://www.linkedin.com/in/ksurace/ Personal Website: KevinSurace.com Twitter: @kevinsurace Business Website: https://appvance.ai/ Re-Read Saturday News This week we begin the read of by Daniel S. Vacanti in earnest covering Chapters One and Two. These two chapters provide a statistical cautionary tale and then go on to define variability. The definition of variability is a foundation that much of AA Volume II builds on. Buy a copy and get reading - .  The current re-read entry Week 1:  - Week 2: -     Learn to Solve IT's Dirtiest Secret! Work input, which includes prioritization and sequencing, is how work gets to an organization or team. If you get it wrong you are throwing time and money away. Simply put, poor work intake means “no agile for you”. Jeremy Willets and I have written tackling the topic that JRoss Publishing will publish in January 2024. In support of the book, we are building a live, workshop-based course for anyone deciding on what work gets completed!  This includes Agile Coaches, Scrum Masters, Product Owners, Project Managers, Program Managers, and Portfolio Managers - lots of people are involved which is part of the problem! The workshop will cover why work intake is the biggest challenge to teams and organizations today. Attendees will also learn what to do to solve this challenge. This cohort-based course will combine concise lectures, discussions, and exercises. It will provide space to learn and share with peers. We're using a survey to build a waitlist for the first cohort – link below. We will use the list to alert you when the workshop is available.   Next SPaMCAST  In SPaMCAST 787 we continue in the minefield of why starting everything you are asked to do is problematic. Framing the discussion is a text from a friend of the cast which highlights those requests that you just can't say no to. We will also have a visit from Susan Parente and her Not A Scrumdamentalist column.

I was asked, “Why shouldn't I say yes and start everything that comes my way?” As we celebrate the impending publication of (it is going to the printers very soon) we continue the discussion of work intake scenarios that bedevil teams and organizations. Controlling work entry is controlling WIP which helps us be our best selves. But are there times when you have to say yes when you don't want to?   We also have a visit from Jeremy Berriault bringing his Evolutionary Agilist Column to the cast! Mr Berriault and I discussed the concept of root cause. Everybody is looking for one but very few understand the concept.  Re-Read Saturday News This week we begin the read of by Daniel S. Vacanti. This is the second of Mr. Vacanti's books we have covered in Re-read Saturday. The 260-page book includes a Preface, 14 Chapters broken into two sections, two appendices, endnotes, a bibliography, and an index (hooray).  I am planning to cover this book in approximately 16 weeks. Reviewing the book, there are several chapters that I can see combining into a single week and a few chapters that will take a couple of weeks to think through. I also suspect that I may lose one or so weekends to holidays. I am targeting completing this read on March 31st.  Buy a copy and get reading - .  The current re-read entry Week 1:  - https://bit.ly/4adgxsC   Learn to Solve IT's Dirtiest Secret! Work input, which includes prioritization and sequencing, is how work gets to an organization or team. If you get it wrong you are throwing time and money away. Simply put, poor work intake means “no agile for you”. Jeremy Willets and I have written tackling the topic that JRoss Publishing will publish in January 2024. In support of the book, we are building a live, workshop-based course for anyone deciding on what work gets completed!  This includes Agile Coaches, Scrum Masters, Product Owners, Project Managers, Program Managers, and Portfolio Managers - lots of people are involved which is part of the problem! The workshop will cover why work intake is the biggest challenge to teams and organizations today. Attendees will also learn what to do to solve this challenge. This cohort-based course will combine concise lectures, discussions, and exercises. It will provide space to learn and share with peers. We're using a survey to build a waitlist for the first cohort – link below. We will use the list to alert you when the workshop is available.   Next SPaMCAST  Software Process and Measurement Cast 784 will feature my conversation with Kevin Surace, AI Inventor,  Futurist and Keynote Speaker. We will discuss the hype and promise of AI.

Software Process and Measurement Cast 784 features our interview with Michaele Gardner and Brian Hackerson. We talk about their Agile Best Self Initiative. We also, and perhaps more importantly, discuss being in control of yourself so you can truly deliver value to those around you. As we start to close out 2023 it is a wonderful opportunity to reflect on how you can be your best self. Michaele Gardner started out as a counselor at an emergency crisis line. Clients were too messy: clear inputs did not lead to predetermined outputs. So she moved into the world of IT and has not looked back. Becoming a developer on an XP team brought together her interests in psychology, flow, teamwork and problem solving. She quickly realized that many teams (and organizations) poured their hearts and souls into projects that added little value. Her next natural step was to help engineers and organizations understand business value at a micro and macro level. At all levels, Michaele loves giving change agents tools to define their own “why” and stay emotionally resilient. LinkedIn: https://www.linkedin.com/in/michaele-gardner-0829205/ Brian R. Hackerson is the co-creator of the Agile Best Self mindset, the VP of People Operations and Enterprise Agile Consultant at . An innovator at the intersection of Agile practices and personal development, Brian has revolutionized team engagement and performance in various leadership roles. His approach uniquely blends professional growth with personal empowerment, embodying his belief in the transformative power of aligning individual journeys with Agile principles. LinkedIn:   Agile Best Self:   Re-Read Saturday News Chapter 11 of is titled Saving The El Faro. In this final chapter, the author could have just as easily reimagined the outcomes of the Pinto design or the Deepwater Horizon disasters. The theme throughout the book is that Industrial-age thinking fails more often in the age of Knowledge Work.    My final thoughts on this book? Not to put too fine a point on it, this is Marquet's most important book yet. Use the links below to read all of my final thoughts on and to catch up on previous installments. Week 1: –   Week 2: –   Week 3: –   Week 4: – Week 5: –    Week 6: –   Week 7: –    Week 8: –   Week 9: –   Week 10: –   Week 11: –   Week 12: -   Next week we begin the READ (my first time) of ; which is available at LeanPub.  We re-read Volume I in 2018 () that book was life changing…I am looking forward to Volume II. Learn to Solve IT's Dirtiest Secret! Work input, which includes prioritization and sequencing, is how work gets to an organization or team. If you get it wrong you are throwing time and money away. Simply put, poor work intake means “no agile for you”. Jeremy Willets and I have written tackling the topic that JRoss Publishing will publish in January 2024. In support of the book, we are building a live, workshop-based course for anyone involved in deciding on what work gets completed!  This includes Agile Coaches, Scrum Masters, Product Owners, Project Managers, Program Managers, and Portfolio Managers - lots of people are involved which is part of the problem! The workshop will cover why work intake is the biggest challenge to teams and organizations today. Attendees will also learn what to do to solve this challenge. This cohort-based course will combine very short lectures, discussions, and exercises. It will provide space to learn and share with peers. We're using a survey to build a waitlist for the first cohort – link below. We will use the list to alert you when the workshop is available.     Next SPaMCAST  As we celebrate the impending publication of (it is going to the printers very soon) I will continue the discussion of work intake scenarios that bedevil teams and organizations. Controlling work entry is controlling WIP which helps us be our best selves.   We will also have a visit from Jeremy Berriault bringing his Evolutionary Agilist Column to the cast!

This week, Dan Neumann and his co-host Justin Thatil are joined by Hal Hogue, who has transitioned from an Agile Coach position to a Managing role and today shares the features of such a shift.   In this episode, Hal discusses his journey from working with managing engineers to becoming one of them. He mentions the particularities of both of these roles, the overlaps between them, and how these positions can work together to advocate for Agility and fast flow.   Key Takeaways What are Agile Coaches? The Agile Coach is a leader (just like the Manager). Agile Coaches are focused on letting others grow (individuals or Teams). Agile Coaches also serve as teachers. Coaches teach the true meaning of being Agile by living the values and principles specified in the Manifesto. Agile Coaches are change agents, helping organizations avoid becoming stagnant. The manager role is not defined in the Scrum Guide, but that does not mean it cannot exit. Manager accountabilities: A Manager's first responsibility is to know about the people part of the Team. A Manager needs to know what motivates the Team and their aspirations. It requires a lot of active listening and asking questions. A Manager should set clear expectations and roles for the Team. The Team should clearly know the reasons why they do their jobs. There is a critical relationship between the Engineering Manager and the Product Owner. These two roles need constant communication, aligning goals not only for the product but also around quality. A Manager should not decide things for the Team but should take essential matters to the Team and let them be part of designing the solution by giving them options and tools; this requires a lot of trust in both directions. Managers can help with impediment escalation or performance issues. The Engineering Manager and Product Owner is a critical relationship, as well as the Manager and Agile Coach or Scrum Master. A leader must be a coach and a servant leader for the Team but also for the Product Owner. A Coach can help a Manager understand what Agility is, its principles, and its values.   Mentioned in this Episode: Team Topologies: Organizing Business and Technology Teams for Fast Flow, by Matthew Skelton and Manuel Pais   Want to Learn More or Get in Touch? Visit the website and catch up with all the episodes on AgileThought.com! Email your thoughts or suggestions to Podcast@AgileThought.com or Tweet @AgileThought using #AgileThoughtPodcast!  

In this episode we unpack the fourth commitment of the Code of Ethical Conduct for Agile Coaching;  Navigating Conflicts of Interest. Join host Leslie Morse as she explores Navigating Conflicts of Interest with Natascha Speets and Femi Odelusi.  About the Featured Guests Natascha Speets is an experienced Agile Team and Enterprise coach. Natascha helps her clients reach maturity in Agile by curating focused Agile coaching programs. In 2020, Natascha started an Agile community project to draft an Ethical Code for Agile Coaches, and It only made sense to join forces with the Agile Alliance and create a Code of Ethics that truly reflects the needs of the coaches and their clients. Femi Odelusi is a Professional Coach accredited by ICF and EMCC. He has excelled in organizational change and enabling innovative, digitally enabled business solutions. He has guided a variety of organizations as they transform in today's world of digitisation. Follow Femi on LinkedIn Follow Natascha on LinkedIn Reference(s) Code of Ethical Conduct for Agile Coaching https://www.agilealliance.org/resources/initiatives/agile-coaching-ethics/ International Coaching Federation: https://coachingfederation.org/ European Mentorship & Coaching Council: https://www.emccglobal.org/ The Women in Agile community champions inclusion and diversity of thought, regardless of gender, and this podcast is a platform to share new voices and stories with the Agile community and the business world, because we believe that everyone is better off when more, diverse ideas are shared. Podcast Library: www.womeninagile.org/podcast Women in Agile Org Website: www.womeninagile.org  Connect with us on social media! LinkedIn: www.linkedin.com/company/womeninagile/ Instagram: www.instagram.com/womeninagile/ Twitter: www.twitter.com/womeninagileorg  Please take a moment to rate and review the Women in Agile podcast on your favorite podcasting platform. This is the best way to help us amplify the voices and wisdom of the talent women and allies in our community! Be sure to take a screenshot of your rating and review and post it on social media with the hashtag #womeninagile to help spread the word and continue to elevate Women in Agile. About our Hosts Leslie Morse is an agilist at heart. She was leveraging agile practices and appreciating agile principles long before she even knew what they were. Her agile journey officially started in 2010 and she never looked back. Her career has taken many twists and turns. She led a digital marketing start-up in college, was involved with replatforming Lowes.com while they adopted agile practices, provided training and coaching for agile transformation across a wide array of industries, and now serves as a Product Owner for Scrum.org. She is trained in Organization and Relationship Systems Coaching (ORSC) and has been involved in with Women in Agile since its original inception at Scrum Gathering 2013 in Las Vegas. You can follow Leslie on LinkedIn. About our Sponsor Scrum.org is the Home of Scrum, founded in 2009 by Scrum co-creator Ken Schwaber focused on helping people and teams solve complex problems by improving how they work through higher levels of professionalism. Scrum.org provides free online resources, consistent experiential live training, ongoing learning paths, and certification for people with all levels of Scrum knowledge. You can learn more about the organization by visiting www.scrum.org.

Chris Garvey: The SPINE Model: Simplifying Change Leadership for Scrum Masters and Agile Coaches Chris offers us a reflection on a change leadership challenge, acknowledging the failure of linear approaches in that context. He emphasizes simplicity and introduces the SPINE model. Starting with a clear contract with clients and understanding the purpose of the Agile journey are crucial steps. Chris underscores the importance of documenting the "why" and the problems to be addressed before delving into practices and tools. Communication is key, and sharing observations with teams using phrases like "what comes up for me is..." fosters understanding. He advises against seeking future certainty and emphasizes that it's people who must undergo change, not be changed. Ultimately, success is defined by the client, not the coach's agenda.   [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 Chris Garvey Chris is passionate about people, and creating empowering spaces where people can thrive. He is a coach at heart having been a Life Coach before becoming an Agile Coach. For close to 10 years he has been working in the agile space as a Scrum Master, then Agile Coach, then trainer, and now as an Enterprise Agile Coach. You can link with Chris Garvey on LinkedIn.

Making One's Self Redundant “The goal of a Scrum Master is to make themselves redundant” So I preached this mantra, and always managed to get a good deal of nods by those around me. Then came along one day when I was made redundant. Literally. I was hit by a wave of lay offs, and this made me reflect thoroughly on what I had been preaching for so long. In the time I was given to work in that organization, did I succeed in making myself redundant, or did I push myself to the fringes, making myself irrelevant? In the latest version of the Scrum Guide, the authors changed the term “roles” to “accountabilities”. It is because a role has to be filled, an accountability needs to be carried. Often we see organizations looking to “fill in the role” of Scrum Master in order to fix a bureaucratic void, a bucket of disparate and non-value adding tasks that someone needs to carry out but none of the existing personnel are actually willing to. Tasks like “running daily standups” and “updating the team board” top the list. In these situations, organizations are looking to create roles to give such tasks a home, and they call these roles Scrum Masters or Agile Coaches, or any other related fancy name. Accountability demands more than executing such tasks. I link accountability to the impact on outcome. I think Scrum Masters are accountable to keep mastery of Scrum alive among the team members. By this I mean the mastery of thinking about the client, the potentially shippable increments, the prevention of waste generation, the championing of courage, focus, respect, commitment and openness. They do so by coaching, teaching, facilitating and mentoring, and they develop other team and organization members into Scrum Masters. They succeed when most or some of it is done by someone else in the team and not just them. Their own redundancy, in that sense, is part of the accountability Scrum Masters need to carry. I have done my share of slipping into irrelevance myself. Here are some of the ways this irrelevance can manifest itself, and some questions to help mitigate it: When we allow ourselves to calcify in our stances, turning ourselves into uninspired masters of ceremonies. What was the initial objective of this meeting? Is it still relevant to the team's or organization's current situation? If so, in what ways can I help the group remain true and connected to this objective? If not, how can I bring this to the group's eyes in a way that invites them to play a more central part of the meeting's running? When we hold a sentence or phrase from the Scrum Guide above the team's will to experiment and adapt. If we look at the Scrum Guide in its full context, how does the team's idea break any of the values or principles? How can we use the team's enthusiasm and initiative to turn this situation into a learning opportunity, conserving their appetite for experimentation? When we position our opinions and knowledge on Agile above everyone else's, overriding the voice of the team and of the organization. In what ways can we give more space to the team's voice to emerge? What pearls of wisdom can we take away from the team's voice so our teaching stances are more aligned to the their mindset, challenges and innate ideas? When we resist to embrace new ideas, new technologies, like ChatGPT, and remain orthodox in our craft of promoting the habit of learning through experimentation. What is the real challenge behind the method of learning? Why does new technology seem to be a threat? How can we embrace technology to reinforce our teaching message, even if this means dealing with our inner uncertainties and possible failure? https://medium.com/serious-scrum/redundant-but-not-irrelevant-the-mission-of-a-scrum-master-e39ac26d528a How to connect with AgileDad: - [website] https://www.agiledad.com/ - [instagram] https://www.instagram.com/agile_coach/ - [facebook] https://www.facebook.com/RealAgileDad/ - [Linkedin] https://www.linkedin.com/in/leehenson/

In this episode we unpack commitment 2 of the Code of Ethical Conduct for Agile Coaching; Acting within my Ability. We explore the inclusion of this commitment in the Code and what it means for Agile Coaches.   About the Featured Guests Sarah Skold has spent most of her career in Human Resources and Learning and Development. She came across Agile as a philosophy and way of working, and LOVED IT! Sarah jumped ship and moved into a customer experience team working in agile philosophy, and is now a Scrum Master. Alex Sloley is an avid member of the agile community and published his book “The Agile Community” in 2022. He speaks regularly on the global stage and is an organizer of conference organizers. He specializes in agile training, coaching, and transformations. Alex is the Shepherd of the global Agile Coaching Retreat Advisor Team and the Co-Chair of the Agile Alliance Agile Coaching Ethics Initiative Team. Follow Sarah on LinkedIn  Follow Alex on LinkedIn  Follow Alex on Twitter (@alex_sloley) Reference(s) Code of Ethical Conduct for Agile Coaching https://www.agilealliance.org/resources/initiatives/agile-coaching-ethics/ The Women in Agile community champions inclusion and diversity of thought, regardless of gender, and this podcast is a platform to share new voices and stories with the Agile community and the business world, because we believe that everyone is better off when more, diverse ideas are shared. Podcast Library: www.womeninagile.org/podcast Women in Agile Org Website: www.womeninagile.org    Connect with us on social media! LinkedIn: www.linkedin.com/company/womeninagile/ Instagram: www.instagram.com/womeninagile/ Twitter: www.twitter.com/womeninagileorg    Please take a moment to rate and review the Women in Agile podcast on your favorite podcasting platform. This is the best way to help us amplify the voices and wisdom of the talent women and allies in our community! Be sure to take a screenshot of your rating and review and post it on social media with the hashtag #womeninagile to help spread the word and continue to elevate Women in Agile.   About our Hosts Renae Craven has been coaching individuals, teams and organizations for over 13 years and has spent a lot of time investing in and formalizing her professional coaching skills in recent years. Renae's passion is leading and coaching organizations and as a Certified Team Coach with Scrum Alliance, she helps teams to find their rhythm and pace that balances learning with delivery. Renae established her own company NaeCrave Pty Ltd (www.naecrave.com.au) in 2020 and keeps herself busy with coaching and training delivery. Renae is also a certified BASI Pilates instructor and runs her own pilates studio in Brisbane, Australia. She has a YouTube channel called ‘Pilates for the Office Worker' which features short 5 minute guided sessions that anyone can incorporate into their day, especially those of us who have been sitting down for extended periods. Subscribe to her channel Crave Pilates. Renae has been organizing the Women in Agile group in Brisbane since 2018. You can follow Renae on LinkedIn.   About our Sponsor Scrum.org is the Home of Scrum, founded in 2009 by Scrum co-creator Ken Schwaber focused on helping people and teams solve complex problems by improving how they work through higher levels of professionalism. Scrum.org provides free online resources, consistent experiential live training, ongoing learning paths, and certification for people with all levels of Scrum knowledge. You can learn more about the organization by visiting www.scrum.org.

Khwezi Mputa: From Silos to Synergy, A Story of Agile Coaches and HR Integration during change 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. Khwezi shared insights from an Agile transformation journey involving collaboration between Agile coaches and the Human Resources department HR business partners. They recognized overlap in their responsibilities and merged into a cohesive team. Challenges surfaced through joint meetings, leading to the realization that their work needed to be aligned. They adopted the SPINE model for effective change, emphasizing starting with the "need" for change. Co-facilitation and shared knowledge enhanced their efforts. To bridge communication gaps, HR partners were encouraged to attend Agile bootcamps. Khwezi emphasized the universality of Agile principles, advocating for their application beyond IT teams, and promoting tool-sharing for wider team benefits.   [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 Khwezi Mputa Khwezi is an experienced Agile coach, trainer, and IT professional since 2008. With diverse roles like Scrum Master, Agile Project Manager, and Business Analyst, she's active in the Agile community, promoting diversity. Passionate about teaching, she empowers individuals and organizations to reach their full potential through coaching and mentoring. You can link with Kwhezi Mputa on LinkedIn.

BONUS: Reimagining Agile Coaching with Opportunity-based Agile Coaching, Peter Rubarth   In this podcast episode, Peter introduces the concept of "Opportunity-based Agile Coaching." He clarifies that it is not a new method but rather a deliberate approach to leveraging existing momentum in Agile software development. The goal is to understand and harness what is already happening or about to happen, using both the company's energy and the coach's energy efficiently. A key tip is to identify what people are paying attention to, what they care about, and where the energy lies. By doing so, you can effectively facilitate the desired changes in a different and more effective way. Agile Coaching Beyond the Plan: The Magic of Opportunity-Driven Approach This approach distinguishes itself from other coaching methods in two ways. Firstly, it contrasts with a planned transition approach where a desired state is predetermined, which contradicts the Agile nature. Secondly, it differs from the problem-based approach, where coaching focuses on specific stakeholder issues. However, this approach identifies missed opportunities and encourages fostering requests. It involves aligning personal ideas of agility with company strategy and culture, using these as an umbrella for coaching. It suggests searching for coaching openings through conversations, leveraging cultural insights and challenges, which is a unique selling proposition (USP) for internal Agile coaches. From Aversion to Alignment: Unleashing Transformation through Opportunity-Based Coaching During an engagement with autonomous teams working on a shared product, Peter encountered gaps in collaboration due to a prevailing aversion to alignment within the organization. Acknowledging the importance of alignment, Peter initially waited for an opportune moment. Eventually, a strategic shift within the organization created a need for alignment and inter-team collaboration, serving as the catalyst. Emphasizing the goal over "change," Peter partnered with stakeholders, positioning the alignment as a step toward the goal rather than a disruptive change. In a workshop, teams shared their focus in relation to a shared leadership-communicated goal, leading to insights and a surge of energy. This emergent process of opportunity-based agile coaching highlighted that aligning with the goal, not just altering processes, drives positive transformation. The experience showcased the power of harnessing existing momentum, underscoring the value of recognizing and utilizing opportunities within the Agile coaching process. This approach not only facilitated change but also nurtured an environment where coaching opportunities naturally arose, validating the effectiveness of opportunity-based agile coaching. Tackling Challenges of Agile Coaching through Opportunities Agile Coaches navigating opportunity-based coaching face several challenges. Humility is key, acknowledging that one doesn't possess all answers. Embracing the Probe-sense-respond approach, coaches learn, observe, experiment, and adapt without a predefined plan. Observational skills are vital, allowing judgment-free insights to form a holistic understanding. Building hypotheses through observations is essential. Maintaining team interaction, earning trust, and accessing stakeholders at various stages are critical. Productive sponsor conversations are advised, while curiosity and continual learning must be cultivated. Overcoming these challenges empowers Agile Coaches to effectively employ opportunity-based coaching for meaningful change and enhanced collaboration. From Frustration to Fulfillment: The Journey of Agile Coaches with Opportunity-Based Coaching Opportunity-based Agile Coaching contributes significantly to the growth of Agile Coaches. By unveiling the organizational dynamics and facilitating effective change, coaches overcome frustration and gain renewed energy. It offers practical insight into making Agile practices work, nurturing confidence and motivation. The approach's rapid pace demands a well-prepared toolbox and a focus on experimentation, fostering an empirical approach. Notably, the principle of moving on when energy is lacking ensures coaches remain adaptable and attuned to opportunities, cultivating continuous development and an enriched coaching skill set. Recommended Resources To delve deeper into the concept of opportunity-based Agile coaching, I recommend the book "Art of Action" by Bungay, which delves into the notion of "directed opportunism." This resource helps framing managerial intentions to guide execution while allowing room for seizing opportunities. Additionally, Peter's blog post on "opportunity-based agile coaching" offers further insights into this approach, detailing how to transition from recognizing existing momentum to deliberately fostering it for effective Agile coaching.   About Peter Rubarth Peter's fascination with agile began when Scrum helped to transform a seemingly impossible mission into triumph. This motivated his passion for guiding teams towards outcome-focused agility. Embracing these principles in his agile coaching, Peter champions the cause of elevating agile coaching as a profession. You can link with Peter Rubarth on LinkedIn.