
Sign up to save your podcasts
Or


Transcript:
Joe Krebs 0:10
Agile FM , radio for the Agile community, www.agile.fm. Welcome to another episode of Agile FM. Today I have Mark Kilby back to Agile FM. Because Mark was already here on the podcast in 2017. We spoke about remote teams at that point. And we're doing something very, very similar today, or at least we're going to kick it off this way. Mark, if you are not familiar with his work, is the author of from chaos to successful distributed agile teams, which was co-authored together with Johanna Rothman. Welcome.
Mark Kilby 0:55
Thank you so much. I can't believe it's been four years. Yeah, yeah. The time has flown. Yeah, you know, we did our little pre conversation, and I didn't even make that connection. It's like, wow, it has been that long.
Joe Krebs 1:11
Yeah. And the book has been out that long.
Mark Kilby 1:16
The book well, so the, the ebook version came out in fall of 2018. The print version came out in early 2019. And, yeah, it's been doing well. And, of course, we saw a spike in March and April of 2020. Why? Yeah. So yeah, it's, it's, it certainly has been an interesting year for remote work. I'll summarize it that way.
Joe Krebs 1:52
Right? Well, the book is filled with practical tips of how to work in a distributed way. So there's the word distributed is in the title, some teams just refer to it as virtual, some say remote. You chose distributed, they're not really interchangeable, right. So there's, there's a little bit something behind it. Some people are very, very specific and say it should be remote, because it's still in person, because you look at each other on video.
Mark Kilby 2:21
So to be honest, and in Johanna and I have had this conversation, we just, we finally had to settle on something for the title. I don't like any of those terms. Because it sets up a bias. So if you say remote, within who's local, if you sent a virtual, well are some people real or not real. And, and the way we treated remote work or distributed work before 2020, that's that those biases were very much present. There was very much in us versus them. Then in 2020, us and then became all of us. And the big difference was very few people had a choice. Were those before 2020. Many of us chose to work remotely, we chose how to work remotely, we had a lot of time to develop that. Were, you know, this time last year, everyone was just trying to figure out, you know, do I need to work remote for a month, two months? No one, no one I don't think except for a few of us thought it was going to be, you know, over a year. And we're still in it as as the time of this recording, although there's light at the end of the tunnel.
Joe Krebs 3:46
It's definitely light at the end of the tunnel. But I think there is there's a lot of learning that came out of these last 12 months, right? So we're recording this in March 2021. We have seen 12 months of distributed work. Let's just settle on this term here for for this podcast, right? So we have 12 months of distributed work. What is it? We we learned from this? I mean, there was a general misunderstanding or misconception about remote work was like remote teams don't deliver, right. So they're in their home offices and who knows what's going on in their home offices? Are they are they actually working like whatever its underlying kind of mistrust and
Unknown Speaker 4:30
well, remote teams don't deliver, remote teams aren't innovative, remote teams can't respond well to change. So I heard many different myths around remote teams. And, and the funny thing is, it's really more around the organizational culture. So if the organizational culture supportive people kind of slipping through the cracks and not really producing it would matter whether you've remote or not. With remote work, because people are doing it by choice, they're coming in with a tension of, I want to do my best work possible. That's how we've recruited people. So when when I was working at as a full time internal coach, for the prior company I was at, we actually screened for that. So if somebody if somebody was wanting to work remote, just because oh, I can work at home. And again, this is pre pandemic, they were out if, if we heard, I want to work remote, because I want to work with a top level team, I want to do my best work, I want to be able to do my best work when I work at my best. That's what we listen for. And that's what we recruited for. When we when we heard that that's who we brought in, all those remote first companies are, that's who they're recruiting. That's who they been recruiting for years now. And these are not just small companies, if you look at companies like automatic, which produces WordPress and many other products, if you look at GitLab, and others, these are companies that are well over 1000 people. I mean, these are these are large companies that work completely distributed. No offices. So
Mark Kilby 5:19
you see, all right, no, if you're just all or remote, it's actually very interesting, right? Because you just said like one of the myths is change, right, and being adaptable to change as a distributed team. And I mean, this change we just faced 12 months ago. I mean, it couldn't be a bigger change than that. I mean, it's like it proves that these that we are able to adapt to the situation, right?
Unknown Speaker 7:01
Yes, yes. And those, those who were able to adapt well are starting to go, Hmm, this could work for us. Those that may. And I'm not generalizing this for everyone. But for those who are a little more resistant to change, they're probably going to ready to go back, although going back is going to be completely different. It's not going to be what they think, yeah. But the other thing is, on the emphasis around choice, some people need a separation between work and home life. Some in I totally understand that. And now having everything in one place, and when when it's hard for them to have that separation, they need the office, some need, who are more on the extrovert side of the spectrum, they need that constant interaction with others. There was one coach I worked with several years ago. She was brilliant, but she worked at her best when she talked through concepts. That's that's when the brilliance came through. And, and so I recognized early on, some people need that interaction, I did not, I'm more on the introvert side of the spectrum. That means I get more energy from ideas than interactions. So so if I so coming on the podcast, great giving a talk or even better being an open space, like we talked about earlier, I get tremendous energy from that. Because I can I can go through all kinds of ideas and share them and pick up new ones. But some, some deed that ability to vocalize instead of write and do other things. So they they need a different kind of choice. Where some be the choice of I need more control over my schedule. I don't need office hours, I need my optimum hours. So I think a lot of people are going to think about more about their choices as they have the option to go back. What are we going back means?
Joe Krebs 9:19
So that's interesting. So you're getting your energy from in person the same way as you would get them from distributed kind of
Unknown Speaker 9:28
Oh, absolutely. Absolutely. The funny thing is, I was first Yeah, first week of March of last year, I was speaking at info Q London. And I was in invited by some other colleagues, Judy Reese, Lisette Sutherland. I had only met Lisette once. Before that in 2015. I had only met Judy once. There were two others there that I had never met, but we had conversed several times ahead good working relationship online for three to five years. And, and I'm able to do that, and I realize not everyone is so I don't think I am not on the remote is the future bandwagon. I don't believe it's for everyone. I think it's going to be an option moving forward. And so, so, so you so your listeners can, can breathe, breathe a deep breath, I'm not here to say remote is the way that's not what I'm here for.
Joe Krebs 10:32
So Right. So it's interesting that you said over the remote guys. So there are folks that have pre pandemic, they had a nine to five job, let's say, right. And, and that there's nothing wrong with a nine to five, right?
Mark Kilby 10:44
No, no.
Joe Krebs 10:45
Right. So but then when they worked in, in a distributed way, the nine to five didn't exist so much anymore, right? So it was a different it
Unknown Speaker 10:56
was, it was, it was more difficult to exist? Yes. Because now, especially during the pandemic, when some of us had kids at home, and kids at home trying to do schooling at home when they weren't set up for that they weren't prepared for that. When you had spouses, or significant others, you know, trying to figure out, okay, who has the maybe the one computer in the house, because maybe not everyone has multiple machines, or they maybe didn't have enough bandwidth. So they're dealing with all these challenges of timing, and resources, because they've been forced to work at home. And so the nine to five became near impossible for many people.
Joe Krebs 11:42
Yeah, so and they might not go back to a nine to five to a point, right. So when they come back to find a different environment that's like, why am I here? And those office hours, so to speak, right, I could be doing something very much personal right now. And I'm going to add the hours at the end of the day when, you know, when a document is signed, and comes back from overseas, or whatever the business situation is like, it's the flexibility that that is very interesting that has this changed everything a little bit. Obviously, it came in from, you know, just hit us, you know, full speed, last March with the pandemic, but you also said something about productivity, they don't deliver and stuff. These are like the typical myths. Key. Can we roll this out? After 12 months? pandemic? I think we can, right?
Mark Kilby 12:29
Oh, yes. Oh, yeah. Well, even even before the pandemic, when you when you have teams that look at, how can we work best together? And how can we work individually at our best? How do I, if I'm a if so I'm a morning person. So I know, for me getting up early five o'clock in the morning is a great time for me to start work, because that's where I'm gonna get my best work done. So there's a block of time where I do some solo work, because I can concentrate and get a lot of writing done helped develop the courses. And then there's time later in day for collaboration, where I can talk to you I can talk to partners, I can I can, the people I need to collaborate with, and I have those hours of overlap with that I set aside time for that. And then I block out other time for family, for exercise for other things that I need to also take care of, it's just not contiguous. Like in a nine to five job,
Joe Krebs 13:33
that's fine. And there's definitely productivity, I think we see the companies are delivering products by software products coming out, I didn't see any kind of delays, or new releases or anything from something I think we just manage. I mean, yes, there is. Obviously this is maybe the psychological impact here with a pandemic where rather than the distributed world the for separating the two things that people feel like hey, this is not really working for me, I'm sitting in my house, but the thing is, you might be on a lockdown or you might be on you're just more isolated right now let's just fast forward a few years and and hopefully we're out of this pandemic by then. And we can free roam again in in offices, but we have a working model like this, we might come back to this and say like, you know what, this is actually pretty good if I'm not isolated if I'm not in a knockdown situation. So this model might be seen more positive right than it is right now.
Mark Kilby 14:28
The pandemic was even difficult for me. So while I enjoy remote work, I also enjoy being in my community. So there's things my wife and I do to volunteer. I'm also active in the local Agile community. And that's been difficult because of things being shut down. Now fortunately, the local meetup has has adjusted well to online but some meetups completely shut down. Some it just like other services completely shut down. It just It just depends on who could support keeping going, who could support the social infrastructure. And and that's that's been the bigger stressor, I think over this last year for many people. So don't take that lack of connection as this is what remote is like all time. It's not.
Joe Krebs 15:23
Yeah, exactly. Right. So the other thing is, like, I see I work with a lot of teams out there, they have back to back zoom meetings, right, one hour, another 30 minutes, zoom, another 30 minutes. By the end of the day, they had massive amount of zoom meetings with other tools, not saying Zoom is the problem here. But what I mean, obviously, there's a lot of online meetings, and they're all like the same, it feels like you're going from one segment after another after another. But you wouldn't really be able to tell from the outside that this the agenda has changed, right? It's just a continuation of the same topic.
Unknown Speaker 15:59
What right because, well, they haven't they haven't stepped back, and really looked at what's the best way for us to communicate, what's the best way for us to stay in sync, what's the best way for us to move forward toward a goal. So those that have worked remote for a long period of time, realize there are times that we really need to be together. In a gathering, I'm not going to say meeting it for now, just say we need to gather, to decide on something we need to gather to debate something, we don't need to be together to give status to each other. We don't need to be together to to just give back and forth information. Some of that remote teams have figured out ways we could do this a synchronously, we can still carry on conversations asynchronously through any kind of medium, there's multiple ways to do that. And for the times that we really need to work with each other. When do we need to pair develop something so not just pair programming, but pair writing Pair? Pair creation, I've done lots of that over the last several years. And that's where you need to be in sync with the other person very closely. When When do example, from my last organization, I mentioned, the Senior VP did an excellent job of mixing asynchronous and synchronous communication. If there's any big change happening, he'd usually put a blog post out Sunday or Monday, there'd be a Wednesday all hands, and then he would have some asked me anything sessions after that. And he'd also have a special chat channel that people could reach out to him. So he had both ways of communicating so that people could say, Okay, I don't understand the implications of this change you just mentioned. Can you say more about that? So you, people who have worked remotely for a while realize you can use both asynchronous and synchronous and bounce that for number of things,
Joe Krebs 18:11
right? That is awesome. So there's a lot to be even improved, right? Even beyond this. And maybe in a shared model where we do a little bit of both. Maybe there's a spin on it. Now we probably work this way.
Mark Kilby 18:24
Even even retrospectives I've done a mix. I've actually I've done entire asynchronous rector's retrospectives. Awesome.
Joe Krebs 18:32
Yeah. Cool. Yeah. And the technology. Alright, we have great tools. Just curious. Without you endorsing any tools, is there anything that stands out like on your on your list where you would say this is a really cool tool to work with in a in a distributed fashion?
Mark Kilby 18:51
Well, boy, the tool set has changed so much in the last year. So you know, most people have seen zoom and all the changes happening there. I will say there, there is a wave of zoom contenders coming up out of the startup community, that will be interesting to watch, that will look nothing like zoom. So one in particular, I find, well, actually, there's there's a couple that are related. So if you look at tools like spatial chat, or wonder.me, both of those, take away the the walls of the breakout room. But you still can have breakouts, you could just move to different parts of space and just talk to people in that space. Or you can broadcast across if you have if it's a large conference, say several 100 people in these different small circles and say, Okay, I need to get something out to everybody. Here's, here's the keynote, or here's the announcement for a you might want to not miss this next presentation. So those tools have the way of reaching out individually small groups and much larger groups. or even even for conferences in, though you probably seen this one, hop in, has made huge strides. And they've had several acquisitions this year, too. So they're they're very much looking at how do you support hybrid events? And they're there. They're making some interesting moves there. So there's, there's, I think there's some interesting technologies that are happening and evolving. And the startup community, I think, is going to provide some, some, some interesting ideas over the next couple years, right. We'll see. Yeah, yeah. So still on top in two years.
Joe Krebs 20:46
What's spatial? Just as an example, I've played around a little bit myself, but super interesting, because you see who's there on one screen, right? You don't hear them talk until you move closer to them. So it's like this. It's an audio thing that has changed, which is obviously extremely intriguing to for networking, etc. So really cool. Thanks. Now, I want to switch a little bit because you're working. Currently it is my understanding on a new book. And yet, the new book is about open space, exploring an open space mindset is the is the working title. I don't know if that's going to be the publishing title.
Unknown Speaker 21:27
That's, that's the working title for now. And I'm co creating that with April Jefferson. So I say co creating because there's more than a book there. Yeah. So what we're doing is we're looking at some of the concepts, the principles, and the law of mobility. And how does that occur outside of the theater of open space? Where do people see that influencing how they work, how they interact in their communities. So we started sketching out several chapters, and we, we caught ourselves, putting many of our own stories in there. And we said, you know, this is about open space, we need to open this up. And so we started interviewing others, some in the Agile community, several outside of the Agile community. So we have some interesting, I will say the stories from outside the Agile community are probably even more intriguing. And how, how the law of mobility has showed up how the the right people have showed up, how the only thing that could happen, you know, what, what happened was the only thing that could happen for these particular people in certain situations. So we have many, many stories like that. We're also doing a series of workshops, we call them journeys, because we we go with them on the journey. So April and I are not, we don't see ourselves as instructors, we see ourselves more as guides, and we go on the journey with him. So we have we had a three hour reflection journey. What are different ways that reflection might look like for you? How will you step back and look at what's happened? And how you might reflect on different things that have happened? How did it happen? And how will you learn from that? So whether it's journaling, different types of grounding, we have some other unique things in there as well. We've got another one coming up soon on purpose. We've had some others on exploring options to think about your marketplace in an open space. So how do you how do you put the options out there to to see, and how do you how do you navigate those options? Right? So those those kinds of things we're curating for the folk in the project.
Joe Krebs 23:50
It's also connect to your previous topic about distribution. Open Space In a distributed world. Open Space, it's very personal thing, right? When people sit next to each other shoulder to shoulder but I don't see that happening in 2021, necessarily, right?
Unknown Speaker 24:06
No, no. But but it can also it can also help people explore how might you either work remotely or work with others who want to work remotely. So that that's were April, and I both have worked in person and remotely many, many different times. So that there is a bit of a theme under that as well.
Joe Krebs 24:33
Right? So the the book obviously, is all about the the mindset of stories it's journey. Is there anything else you can share about the book are you in addition to that, like the structure the size because I've had Harrison Owen here on my podcast before. Creator of open space, right? What's interesting about this is that I feel like the Agile community took hostage of open space because Harrison himself, he came out of a very different camp, right? He came out of a different camp. So what you're describing in your journey stories is going back to the roots. Right?
Unknown Speaker 25:16
We're we're very much trying to go back to the roots of open space. There's, and that's why I will say there are some, some agilists interviewed, but we were really trying to get a much broader set of stories. And where we're getting into those now. And it's it's interesting to see how the same principles show up in different ways for different communities.
Joe Krebs 25:46
And it's my opinion here any any story to be shared, this is good. Why because open space is so eye opening, if you as a listener, listening to our conversation right now might not have experienced open space, give it a try. There's a lot of right now, obviously distributed open spaces around the world with different kinds of technologies. But it's it's liberating, right? Yeah, well, not surprisingly, it's a liberating structure.
Unknown Speaker 26:13
Yeah, so and it's, it's in a way to emphasize, if you experience an online one, try to visit one with a different technology. So because then you'll realize it's not the technology. It's really about the space, how people curate that space, so that everyone in that space can freely share and learn from each other. That's really what that law mobility is about. If you're neither learning or contributing, you go somewhere else. And that is that is really a major element to any open space.
Joe Krebs 26:49
Right? As awesome. So I'm looking forward to that release. When do you expect this roughly coming out for...
Unknown Speaker 26:57
we're looking at the fall where we we still have chapters in in a bit of an outline mode, where we're going through the stories, figuring out where they will fit in some of the chapters. So it'll probably be an early draft here in the summer. And then hopefully get the final version out toward the end of the year,
Joe Krebs 27:17
into the 2021. People can register already newsletters, etc. For that book and get announcements at MarkKilby.com.
Mark Kilby 27:29
If they go there, look for books, they'll see the book listed and they can get on a special newsletter just for that book.
Joe Krebs 27:35
Awesome. Cool. And if somebody wants to get in touch with you on Twitter, that is MKilby that's your Twitter handle. All of that stuff will also be on the show page, I have some links to the material, etc. That was a great conversation. Thank you. And I hope we get out of this pandemic soon. And see another version of distributed development following that and maybe a shared one, mixed one, whatever, whatever that is being called. But
Mark Kilby 28:05
yeah, we could we could talk about this hybrid situations next time. That's a whole other set of conversations.
Joe Krebs 28:13
Let's do that. Exactly. Awesome. Thanks Mark. Thank you for listening to Agile FM, the radio for the Agile community. I'm your host Joe Krebs. If you're interested in more programming and additional podcasts, please go to www.agile.fm. Talk to you soon.
Transcript:
Joe Krebs 0:10
Agile FM radio for the Agile community, www.agile.fm. Thank you for tuning in to another episode of Agile.FM. Today I'm here with Chris Smith, who is the head of product delivery at Red Gate. And we have him actually explain a little bit what Red Gate does, but he's also posting information about the topic we're talking about here today on leadingagileteams.com. Our topic today is kind of a companion kind of podcast with something we have done just recently with Heidi Helfand and about dynamic reteaming. So this is the practical implementation on reteaming dynamic reteaming on the team at Red Gate. Welcome to the podcast.
Chris Smith 0:59
Thanks. Thanks, Joe, thank you very much for having me on.
Joe Krebs 1:02
That's awesome thing. So thank you for taking some time and spending some time with the listeners to talk about dynamic reteaming, we could say one more time. But last time I spoke with Heidi about the book, and some stuff that is important for people that are implementing this, but you're the person that actually implemented that at your company. Redgate.
Chris Smith 1:21
Right, yeah, that's right. So, so already talked about a continuum of freedom for reteaming. So where maybe one end managers, organized teams and tell people where they're gonna go, and then at the other end, everyone has gets to choose where they work. And we're moving closer to that second stage where we give people much more influence over where they work, and which teams they're part of. And we do that every year.
Joe Krebs 1:21
Right? Can you just give listeners maybe who are not familiar with Redgate, a little overview of just on a very high level? What is this company? What's the background? What's the size, geographical distribution, etc?
Chris Smith 2:01
Yeah, sure. So. So Redgate are a small medium size software company, we are based in Cambridge, our development hub is in Cambridge in the UK, but we have sales offices around the world. And we create software for database professionals. So that database administrators, database developers, and our tools, help them do their really important jobs of creating, maintaining and operating the databases that support all our systems, corporate and consumer, there's a database in there somewhere, and our tools help the people that make those and look after them. In the last, in the last five years, we've been really focused on helping those database professionals bring the database into an agile and DevOps environment. So you know, agile delivery of application code has been around for years and years, often the database gets left behind, it's scary to change it, it's scary to integrate it in like an agile continuous delivery process. So it gets a kind of a waterfall back backdoor process that gets the changes out, and we want to bring that in there and get the database delivered agile-ly alongside application code. So that's been a part of our mission for the last five years. And, and, and yeah, we've got a whole range of of database products that we really hope will help help people develop databases in a really agile way.
Joe Krebs 3:20
Yeah, that's actually a very good point is like, based on my experience working with teams with Agile teams. That is that is often a bottleneck if they are, you know, with a database administration, right, schema changes, etc. Right? So it's interesting to have like a product. So this is interesting for this podcast, right? Because we're dealing with a product that solvesor tackles a problem in the Agile community, but also Redgate itself is embracing agility. And obviously embraces some things that are about dynamic reteaming. Right. And that's our topic here for today. So tell me a little bit about how you came across this. Obviously, there is a book out there we I spoke with Heidi about but this is really about you taking some of those ideas into your organization. Now. How can how many times did you do reteaming? And how did you start with this?
Chris Smith 4:16
So reteaming something is always happens. It always happened at every company I've been at, and where people join teams, people leave teams, teams, split teams have to end. And that's re-team and that's the creation of, of new teams. And but what we've been doing for the last three years is deliberately reteaming all of our teams or making an opportunity for everyone for me team off the back of our strategy, review process. So for the last three years, we've asked everybody in our product development teams, where they'd like to work in the coming year. Would they like to stick in the team they're in at the moment, or would they like to go and do something interesting they can see across the range of things that we have, we have 11, software development teams at the moment, they're all covering different kinds of products at different stages of their lifecycle, which means very different work. You know, if you're in a, you're working on a product that is very early stage, maybe creating iterating, quickly creating code that might not be super maintainable in the long term you're trying to learn, the whole point there is to learn fast. And you might find actually that you stopped doing the work you're doing because that product hasn't found its market and you go do something else. So it can be quite ephemeral. And then you've got other products that really well established me when I grow and scale their addressable market. And they have a different kind of work. They're about maintainability, and scalability and new features. And that works very different. So reteam to let people choose which of those kinds of work they'd like to invest their work life in for the next 12 years and beyond. So, we've done that for three years now. And it's gone, it's gone surprisingly, well, it's gone, it's gone really well. And people have been really happy with it from both the kind of team members that are involved in it, and the governance that the leadership of the organization.
Joe Krebs 6:03
Right. So you have some metric points out there. So first of all, if you're doing this three times, while it tells me that it's kind of a success, because you would have stopped after one. You have success, right? And it's going very well. But you have some data points behind this too, right. And so I don't know if you know them from the top of your head, but there is some high percentage on satisfaction with this process among the employees, if not so much you but the employees that are impacted by this, can you share any? It doesn't have to be exact right? So but if you have anything that is like somewhere in the in the criteria, where you would say we're like in roughly high, I think I saw something on a blog post of north of 80% of satisfaction with the team that they picked, I think was even higher than ever.
Chris Smith 6:51
Yeah, so in terms of what happened, certainly, the first time we did it, so we asked people, we made it very clear what was out there, what what possible pieces of work were possible teams are out there, what their mission would be, what they were trying to achieve, what their impacts were we were going to have. So they had all these choices about where they might want to work. And we asked them for their preferences. So what was your first preference? Where would you like to ideally go? What was your second preference? What was your third preference? Why was that? Why were you saying this was your first preference? Was it because of tech? Was it because of the lifecycle? And, and that was a big leap of faith like well, we'll ask these people will that create an organization that's effective is that fit for purpose for what we're trying to achieve? Like, it felt like he could have gone really safe, we could have had, everyone wants to be on the same team. But instead, we did get this spread of preferences and interest. So we were able to allow, I think it was around 85% of people got their first preference. 80% of people got their first preference in that first year. So we were able to meet their first preference where they wanted to work. And then I think it was 95% or something, they got one of their preferences. And the last few, we had to fit in with an option that kind of fitted their personal development, but wasn't an option they necessarily chose. So in the end, we got a very high level of satisfaction from our team members that they gone to somewhere that really spoke to them. So we ran that again, that the following year, again, very similar numbers. And in this last year, which we did entirely remotely we had 83% of our engineers who were in the team that was their first preference again. And 98%. Again, we're in the first second or third preference, and in the end, we moved 37% of our team members, which seems a lot, right. But it's been absolutely fine. And in the previous two years, again, a third of people move. So this is what I'm saying we're not we're not we're not completely taking all the teams apart. And putting everyone in different team. We're allowing people the freedom to move, right and the freedom to give strong influence of where they spend their working lives. And not all of them want to move but a decent number do and that's entirely supportable, we can cope with that. Absolutely fine. The last three years.
Joe Krebs 9:15
It's awesome. 98% ended up with one two or 3 option, right? It's it's a very high number considering you know, delivery head of delivery like you would be assigning this you would have probably I would assume a lower percentage if you would assign people to teams, they might not like in the way they actually chose.
Chris Smith 9:37
I honestly, when I when we first time we did this I did not know what to expect. It was as you mentioned, Heidi, I mean Heidi was a was a big influence on this, but I think you know, we call down. We'd call that at Red Gate, that we believe that the best way to make software is empowering teams with clear purpose, freedom to act and a drive to learn. We tried to make that principle we choose what we do behind that principle. And yet we'd have retained in the old fashioned way of like managers in a room deciding. And then Heidi kind of I actually saw Heidi, a couple of conferences, talk about her subject on every team. But hang on a minute. We're talking about giving people purpose and freedom to act. And I'm telling them what team to go in, what am I doing? And it was that kind of push it said, don't be a hypocrite. If you say that you want to give people autonomy and purpose and mastery. Ask them where they want to work. Give them that that opportunity to have a say, it was obvious when I'd seen that. Yeah, and but the first time, I didn't know what was going to happen, I thought I hoped it would, it would be a, I suspected that quite a lot of people would like to move, but not everyone would. Some people like the stability, it's the point in their career or the point in their life, or they're really engaged in their mission, and they don't want to move Thank you very much. But other people are looking for that opportunity. And by making it deliberate and making a date in the candidate, where we will talk about this, it is free I think a number of people up to move that wouldn't have wouldn't have otherwise tried something different. And also given them that opportunity to self-select onto a new purpose to self select a new mission. And I feel like a sense of ownership of of what they do in their career. So yeah, it was first time was a leap of faith. But following that, I don't think we'd ever go a different way now, because it works.
Joe Krebs 11:25
Yeah, It's a, again, nerve wracking moment, right? If you're doing this the very first time and you're like, I have no idea how this very big event with so many people, it's gonna go and, you know, and it's big relief on the other side and, and prove that these things work. Once you go through it.
Chris Smith 11:42
Yeah, I think it was definitely the fear, the fears I had before I did it. And maybe that reflects with with folks at home that might have the same fears. If we ask people where they want to work, they're all going to choose the same exciting team, they're all going to choose where there's the new tech, where there's, you know, Kubernetes, and everything else that we've seen exciting, or they're all going to leave a team that is maybe more, maybe one maintainability, or looking after a large, successful product, but maybe it doesn't, doesn't need a lot more features, it's kind of done, but it needs to be looked after, we're going to see all these people move away from the crown jewels and the most important, most important tools to the business. And ultimately, as a delivery manager, I'm gonna get fired, because of all my people. So that fear was definitely something we had to get over. And, and just sort of step into it. But I think we also thought about the fear that might be on the case of the people involved in the process. So you know, people don't love change in general. And so if you're in a team that you're feeling secure and accepted to actually leave is a big deal. And it can cause a certain amount of anxiety, I step away from that, that comfort area and go and do something else. So with the process of Redgate, we've tried to think quite deliberately about how we can make it reteaming without the anxiety, both for leadership in terms of oh my gosh, we're not delivering the things we need to, to the people involved is I've got to change teams, that is frightening. And so our practice isn't just, you know, we go along to one big session for two hours. And by the end of it, we decided what team we're on, we take a bit more of expanded approach, where we will make it very clear what options are available in the teams, then we will let people explore them in their own time, kind of asynchronously now with remote working. And then we will coach everyone individually. We have coaching sessions with everyone to say what have you seen? What are you interested in? Why are you interested in that? Let me understand your preferences. And there is a process where a set of folks have a set of leadership folks get together and look at those preferences that people have and look at the kind of organizational structure and the investments we need in different products. And can we make those work? And sometimes we'll have to ask people to come together for their second preference and not their first because that's really going to help us unlock this. Well, can I move in a couple of months when we've been able to disseminate the knowledge, it's in your heads and to the rest of the team? Because people are involved in this change? Because it's a change with them and not to them? They've been really open about those things. Oh, yeah, I'll go to my second choice. Happy days. I mean, I understand why that works. Or I will delay for three months no problem, because I can see that my unneeded in this thing before I move. Once you include those folks in this re-org some might call it then it becomes a much more collective experience and a much kind of a less anxious project.
Joe Krebs 14:48
Yeah, it's interesting. Why because you might let's say I have a project one, then two and three as listed on my, my preferences right. And I might get assigned, let's say you as a department head without dynamic regime teaming to, let's say, option three. And for me, as a person being assigned to that team, I might have a negative association to it because I was assigned to it. But if I self select, and I pick three, all of a sudden, it's like I picked that I picked this team, and it was just my third option. But then I made this choice or sometimes, you know, human behavior might also deep down psychology always is like, was this somebody told me to be here, or I made the choice to be here. And even though it's the third option, I might still like
Chris Smith 15:37
Yeah, absolutely. I mean, I'm Have you read the book, The Chimp Paradox?
Joe Krebs 15:42
No.
Chris Smith 15:43
It's by a chap called professor, Steve Peters, and he talks about, he introduces a model that helps you understand how the brain works. And it's very abstract, but it kind of helps me understand it. And that kind of, it talks about your kind of inner, inner, inner Chimp, but the kind of the thing that's, that's kind of captured in your amygdala, which is very, it's very reacts, it's very emotional. And effectively, your chimp doesn't like being told what to do. So by a manager telling you that you need to go into one, you will quite naturally quite physically have a real reaction to that. But it's normal for you to think, Well, why are you telling me I should have a say in this, I need to have some self determination. And you're right, like some people could actually choose that team project one themselves, because they've got the choice. And then their experiences that will be totally different from from being told to go in it. Because they're included, and we cared about what they thought and we looked after their, their psychology and their inner chimp. I think another thing that's happened, that I've noticed, having done this for three years that it's completely normal, I think for, for people to look for someone to blame, if there's a difficult time, on a project, like it's on a project, it's getting really gnarly, there's something very difficult to hear that we got some real hard things we got to do. And it's kind of normal to say, well, they've done this to us, you know, that we've been put in this situation. I've been putting this I'm a victim, I've been put in this situation. And it's really hard. Whereas you, we chosen now to be in these teams, we've seen what's coming and the gnarly work that's coming, and we self selected onto that, and we're gonna give it a crack. And we're going to do our best here. So there's much more kind of, as you say, sort of, they understand why they're here. And they have chosen it. So they they're gonna crack on with it. Much less us versus them now that I see the around team mission, and the kind of the difficult stuff that teams have to take on.
Joe Krebs 17:40
I have a question like you've been with Redgate, prior to the time and you started reteaming, right. And so at one point, there was this moment where you said, I'm gonna try this, obviously, there could have been any kind of impulse, we said, you know, I, I need to do something like, I need to experiment with something, and it led to this process. But what was the time before reteaming? What were the challenges you were trying to solve? What was Redgate prior to reteaming? And just as compare now like, what was the business reason or the need to actually say we want to try something right? And then the path took you to that approach, which we now call dynamic reteaming. But just curious to hear, like, what was the trigger? So if somebody is out there and says, Well, you know, what was the problem that we're trying to solve?
Chris Smith 18:28
Well, there was, there was that piece where yet we were talking about these principles for organization and not living them by doing things in a different way. So there's that part, which was, which was important, but I take your point, it wasn't it wasn't the pure business driver. I think we wanted to make a big change. And we wanted to restructure in a way, where, as I said, we were clear about what our product teams were for. So where they were in sort of Kent, Beck's 3x model, were they exploring? Were they expanding, were they sustaining, and the work was very different, we want to be very clear on that. And then when we're clear on inside product x you are in, you're in exploring products, you looked at the folks in that team, and you knew that wasn't the kind of work they wanted to do some of those folks, they wanted to do some of the other work. They wanted to do some of the scalability and the performance work that is in an expand or sustained products. So you can see people were in the wrong place, and being clear about what the products were trying to achieve. So there was a problem of how do we get them in the right place, while not destroying everyone's morale and having this big, crazy real, where people tell everyone else what to do. So there was that but also, I think we were seeing real silos in the organization. So Redgate for a long time has been a product company. We've got product teams, literally. And we built up teams to be autonomous and self sufficient as much as possible. And when they do that, they stop talking to each other completely Naturally, they solve their own problems and a team that's sits next to them literally next to them, you know, when we're allowed in the office, they wouldn't necessarily share what they were doing. And we end up with components that did the same thing across products. So we saw these, these silos. And we also saw, I mean, I used to totally believe in like that kind of stable team that stays together forever. And that's the best kind of team. And this has changed my thinking, because what you see there is not only those silos, but also people that become the expert in a thing and never leave. And they never can leave, because all the knowledge is in their brain. And all the knowledge around the teams becomes tacit, it becomes part of the groupthink of the team, not explicit. So it's not written down anywhere, because the silo know all these things. So we were we were having a less agile organization, as a result of that siloing that ossification, that when it said, right, it's time to create a new team on product X. We weren't used to changing teams, we weren't used to people leaving and we didn't capture the knowledge in a way that could be shared easily when new people joined. So we needed to get good at reteaming, which is kind of the central central premises of Heidi Helfand's book. So with reteaming now, I think what we've seen is breaking down some of those silos. If you think about it, in the last three years, each time about a third of people have moved. You think about that dissemination of skills and relationships across our organization, that it's easy for me now to go and talk to Team X. Because I know, Jeff, because Jeff used to work with me last year, but we reteamed an error in different things. But I had that connection. Now, we're breaking down some of those silos and building up a kind of an organizational network, but quite naturally was going away because of the strong silos.
Joe Krebs 21:47
So innovation is therefore also like, there's a foundation for innovation, right? Because I might walk over to another person. I mean, you know, in your example, I think, Jeff, would walk over and have a conversation with that person and say, hey, you know what, I remember you from the last year's team we worked on together, and you mentioned XYZ, and I'm now seeing this. And that might be a big thing for us as a company. So as a platform for innovation,
Chris Smith 22:11
we also had probably an issue with allowing people to progress, their personal development, their learning and development goals. So not everyone, especially engineers, that don't want to be the manager or the team lead or the or the whatever. Next, they wants to widen their skill set, they want to learn new technologies, they want to get more experience in different areas. Yeah. And you can do that by changing teams by saying, Okay, well, I want to, you know, some of our teams or some of our products or plugins, to Microsoft IDs, but I want to work on a web tool. So actually, I need to widen my web skills. And I can do that by moving to that is that is that is my personal growth. That's my personal development. I feel like I'm learning I'm happy when I'm doing that, can we be needed to enable those because we weren't doing it within the teams.
Joe Krebs 22:59
So you have these events in the last event was a remote event. And so the first two were in person. The third one is remote. What's what's your takeaway from a remote event? And reteaming? Obviously, you might have gone into the same, like in the first one you had fear about this is going to work? Maybe another moment, a few weeks? I guess it's going to work in a remote way.
Chris Smith 23:23
Yeah, it went, it went really well. And I think I was confident as we went into it, because our organization the same as many organizations that have been forced to, forced to work more remotely is to have people away from the office and working from home from from distributed workplaces, is we've picked up tools. And we've learned techniques over that nine months of doing that they've helped us understand, like, we've learned how to collaborate remotely, we're using tools, visual organization tools like mural, and Miro, yeah, things like that, using virtual meeting spaces, so we can have big collaborative sessions, we've learned and with those tools that we're going into, I was quite confident. But actually, if you'd have asked me a year ago, before we got good at remote working, I would have told you it couldn't happen. It's impossible. It's too connected. It's it's a kind of a it's an experiential event, you've got to get everyone in the room, and they all like spark off each other. But actually, it was, it was probably better. Well, remotely. I think a couple of the reasons were, if you put everyone in a big room, and they talk at the same time, you can't hear anything. So our virtual space, using a tool called spatial chat, meant that you could actually move around the room and hear specific people and encrypt everything else that we could actually share some of the collateral to explain to team members what their teams, what the different teams will be doing next year, we could share that upfront. And people could consume that asynchronously in their own time that could really deep dive into what we call team charters, which we're painting A picture of what a team would be like in the coming year, they could really invest in those. And also as, as leaders trying to visualize all these preferences and work out if they fitted a tool that online that captured how things were progressing, and you didn't have to write up the notes from the meeting, because it was there in the tool. And we used to go into a meeting room, and we used to stick post it notes on a wall to help move people around, I'll just gonna go to that team. Julie's gonna go over here, but the post it notes will just fall off the wall. And then you'd be like, what was the team, like the team is I've got to put the team back together, because the adhesive isn't good enough against these walls. So if it was none of that kind of like logistics problems in putting the jigsaw puzzle together, because the remote tools were so good for helping that. So yeah, I actually think when we get back to a hybrid world, probably at Red Gate, where we have people in the office and back at the office, we will probably go home, all of us to do this process remotely on purpose, because it worked out well. And use the kind of time in the office and social time, it's collaborative time, it's kind of connection time. And this can be a process that actually happens remotely, right.
Joe Krebs 26:13
And you can even prepare the remote rooms. But sometimes you walk into a meeting room, and you have to prepare the room right here, I can actually prepare everything and you go in, that's might be a good time saver to.
Chris Smith 26:24
Absolutely, I forgot that about working in an office, when you go into a room like one minute before it starts, it's just a garbage dump. And there's things everywhere and the wall isn't being cleaned down. And then when you're finished at the end, and there's only a minute left of the meeting, and you've got all this stuff on the walls, and the next person is waiting to come in, you've got to take everything off the wall before you say I forgotten and that's what happened. But that's that's gone now, when we're doing these things remotely,
Joe Krebs 26:50
definitely has changed. You just mentioned something in your last comment about the team charter. And I want to explore this a little bit. Because if somebody listens to this right now, and we're talking about dynamic reteaming, and somebody's choosing Team A over B, or preferences, etc. They're not just going to make this out of the blue. Yeah, and this is gonna be this is not like personal favorites, I want to work with a specific person or something like that I like this person, there is a there is something that guides people in their decision making. Right? And that is the team charter. If I if I'm not mistaken, right? Can you just give listeners a little bit of an overview. So it's not like there is something behind it, which allows people to really self select the teams?
Chris Smith 27:30
Exactly, we have to give people the full context, the full idea of what it will be like in these things. It's a big deal to swat team sometimes, and they need to know what they're stepping into. And he's got to visualize what life will be like in that team, I think. So the team charter, which is just a lightweight canvas, filled in by the leadership roles around the team, who are in place, before other folks have in place, they're there to shape what that team will look like before we get people involved in joining as developers and designers. It calls out the mission. So as I said, before, we're getting saying we need to give you clear purpose. So that needs to be there. Why, why is this team here? What's the impact this is going to have for Redgate? Like, what are you doing? And so we're going to call that out, we can say what this team own? What's the scope of your work? Do you own this product? Or these two products? Or this part of this larger product? What's What don't you own? There's a legal understand again, what that kind of thing that we're doing. And also, you know, by then we should know what the product strategy is, how are we going to be trying to make these metrics move? We're going to be trying to do some competitive features, or we're going to be moving into a new database technology, what is what is going to be the strategy behind this work? And we'll also talk about what's life going to be like day to day and that team. So is this a team that really likes mobbing a couple of our teams do a lot of mobbing even remotely. And really heavy on pairing, it's worth knowing that before you go, you don't want to arrive at that team. Being someone that's, that doesn't really enjoy mobbing so much. And that's all they do every day, you need to know what because there is some variety in practices and techniques across our teams. So about those. And also we talk about and this is an important part of it, as well as the constraints. So for this team to be functional and able to do the job, it's therefore we need these things. So we'll need some people with experience with this product before we have to have people that know how these products work. We need people that have this product this skill with this with this technology react C sharp will need these skills and will need a mix of experiments perhaps on senior to junior we can take a few people that we need to mentor but we really have to have a strong senior in there. So we encourage leaders to be very clear about what they think they need in their team. And for that to be open to everyone so they can say oh, I can see how I fit in there. Yes, I'm a junior but they're okay with a junior so that could really be a good fit for me. And they do mobbing which is a great way for me to learn. That's a team I'd like to go to I'm not so bothered maybe About the higher purpose right now for me in my career, it's best that I can learn from experienced person. So that's the team I want to go to. So it's quite a multifaceted view on, on what the team will be like. But and then lightweight canvas, it's not a lot of words, it's a canvas that that people can fill in and absorb quite quickly, I think.
Joe Krebs 30:20
I mean, this is fascinating. I think this is important, right? Because people need to have the foundation for a decision, right? It's like, it's like, what is what is my skill level? Where do I want to go? Maybe there's a bridge between my current skill set and that future skill set. And there was a ton of people, if not the majority of people who like to learn, right? They want to learn some new skills, especially around technology. I mean, you want to just see something else, or you want to explore different product, or you know, what team you want to be associated with. But you mentioned, you had these three events, and they were annual events. So what if I pick the wrong team and made the wrong? Let's say, I pick number one team, and I got one, my first preference, and I got it, and I'm happy and I get started. And then I realize I'm not liking it. It's not my thing. Is there? Is there an opt out somehow? Or is that a static process for a year that I'm locked in into a team? How would that work that somebody like because it's dynamic, right? How do I possibly shift between teams, even after a reteaming event? How does that look like it? at Redgate.
Chris Smith 31:26
Yeah, it looks like people sharing their experience with their line managers, and then as its people moving, I think this process has allowed us to get good at reteaming has allowed us to build up the kind of explicit knowledge, the team building activities that we know how to run, just an acceptance that people will move teams, we're not so surprised when a stable team has to change because they always change. Yeah, so we're, it's not like we'll do we'll change once a year, and then you're locked into next year? Because I think I think an interesting point is, is we always were like that Redgate. We always said, if you didn't like where you were, and you wanted to move, you can ask the moon, that's fine. Like everything that I've been Redgate in 10 years. It was always the case. But nobody ever asked to move. Yeah, it wasn't a thing that you did. But now it is. Because every year we said, look, it's totally fair to move, you're not criticizing your teammates, you're not saying you don't like your team leader, you're just saying you need to move your career or your personal development or because you need a change. That's fine. So it's now a normal thing. So I think it's much more likely people say, actually, I want to move media and providing the can because clearly, we want investment in certain teams, and we don't want to leave teams under invested. So they're quite fragile. We need a certain size of team for it to be for purpose, provided we can do that. We will move people and we have moved people in media, if that's what they would like. And again, people are very open to saying, well, we need to we need to hire somebody to take your spot. So it might be couple of months. It's like fine, as long as I know, you've heard me and you're going to I'm going to go over there. This is fine. I it's not a problem. I will. I'll keep you in this team until until we ready.
Joe Krebs 33:15
Awesome. Yeah. Would you would you recommend anybody listening out there to go with that flow of yearly annual events? Or do you see any need for possibly shorter reteaming kind of experiences every six months or so? What is the pros and cons? And why did you guys settle for a year?
Chris Smith 33:34
So for us, it's it's yearly because we had previously an annual strategy review process. So with all our different products, obviously, we are trying to be agile, we're trying to respond to the market and change and not plan too far ahead and then respond to what happens. But we do have a yearly process where we say where do we want to invest? We can spend this much on teams, we can add this many people do we want to invest in this product or that product to this and changes do happen? We double down on some products, we spend a bit less than others and we need to create a new product. So it is there's an obvious change point, there's an often obvious reflection point for us in our annual calendar. So doing it then makes sense. There is obviously an overhead to reteaming like this. I think I said it wasn't a two hour meeting where you drop in. And then by the end of it it's we prepare these charters on the back of Product Strategy. We get our leaders in place and then we have that prolonged interaction where we show everyone what what is on offer and then we get their preferences and then put them in a place overall this year it took us 15 working days 15 working days from hear the charters to your in your new team go. It wasn't we weren't doing the work during that 15 days, but clearly people's heads were thinking about what can I do next and it's a bit of a distraction. So if you're going Do something like this. It feels like quarterly would probably be a bit too often to be a bit too much overhead. I could sort of see it six months if there was a reason. Yeah. If there was like that driver that change in strategy, that means we're actually now it's reflection point, we should do that. Again, no big project has stopped a big one starting and actually, there's some opportunity see, I can sort of see it's doing that. But firstly, it's working annually. quite nicely. And actually, we've had some people say, I wouldn't want it any more often. Maybe every two years like you asking quite a lot. Asking once a year. It's not that often but I think there's there's there's a comfort people happy changes in the year for us seems to be a sweet spot right now.
Joe Krebs 35:39
Yes. Wow, this is really awesome. Thank you for spending some time here and explaining some of the, you know, the ideas behind dynamic reteaming here, at Redgate. Okay, this is awesome. Thank you so much for for sharing those. And I just want to refer all the listeners also to your I call it the blog, the leadingagileteams.com Where you you know, somehow share your experiences from these events and experiences also throughout the year. So that's a great source for information. There's also some videos people can watch about you in action, so all cool stuff. Well, thank you, Chris, for that and I'm on the show page I'm gonna make all those links available for all the listeners. So thank you for your time.
Chris Smith 36:25
No worries. Thank you very much for having me on. It's been a pleasure.
Joe Krebs 36:27
Thank you for listening to www.Agile.FM, the radio for the Agile community. I'm your host Joe Krebs. If you're interested in more programming and additional podcasts, please go to www.agile.fm. Talk to you soon.
Transcript:
Joe Krebs 0:10
Agile FM radio for the Agile community. www agile.fm. Thank you for tuning in to another episode of agile FM. Today I have two guests to Christiaan Verwijs, and Johannes Schartau. They both wrote together with Barry Overeem a book called Zombie Scrum Survival Guide, which was released in November. It was released in November 2020. Why not on Halloween? That would have been the perfect release date for the Zombie Survival Guide on the 31st of October. But you came a few days after that. But first and foremost, welcome to the show. Welcome to Agile FM.
Johannes Schartau 0:55
Thanks for having us Yeah,
Christiaan Verwijs 0:57
thank you so much. It's a pleasure to be here.
Johannes Schartau 0:59
I think to answer your first question, we won't name any names, but there was a big publisher involved in our book. And not all publishers are very agile. So that wasn't possible. That was also our goal. But you know, we took what we could. And that was November.
Joe Krebs 1:20
November. Yeah, but just about that timeframe. So it's been a few months. Congratulations for the release. That is part of the professional scrum series that book, I think those are like five, six books or something like that in that series. So that's where we go Barry cannot be with us today on this show. But I will gonna talk a little bit about the survival guide. It hit the shelves, it's available, you're shipping it like crazy. So before we even get started, now that everyone here on on that show might be familiar with that. zombie Scrum, what is that? And why is it bad?
Christiaan Verwijs 1:59
Yeah, well, it's pretty bad right to Hamas. Yeah, well, I think I think there's just some of the old scripting for zombie scrum instead. It's something that looks like scrum from a distance. So you have all the events, the artifacts, the accountabilities that you would expect, but there's no beating heart. And that usually manifests as in a complete lack of working software stakeholders are not involved. There is no, no autonomy for the team to make any decisions of their own about the product that they're working on. And nobody seems to care about it, or try to improve anything. And I think that's sort of the thumbnail description of zombie Scrum.
Joe Krebs 2:41
Right. So what was the trigger for you guys writing it? I mean, what did you guys observe? Are there I mean, you're both training. Christiaan, you're a professional scrum trainer. Johannes you're an Agile coach. So I'm pretty sure you guys see a lot of Scrum out there. When working with clients, and what was the reason what triggered the book and like I said, there's something has to be done.
Johannes Schartau 3:04
Well, several years ago, we talked about what we were seeing in the industry and what we could make some kind of impact. So that's how our collaboration got started. And even with a deep question of what would actually make a difference. And what we both saw, and we later got Barry involved, was that Agile has reached that kind of maturity stage. So when we started out, it was just this weird thing that some people did and would never really catch on. But then suddenly, it did and got really successful. So what we saw though, was that there were all these books on Scrum and Agile, and they were all describing this perfect future and all the benefits you can you could get from Scrum. But most people we talked to, they felt like they were trapped in a system that didn't deliver on that promise, and it felt lifeless to them. And they also felt stuck and not able to change the whole system. So that's kind of what we identified that these people really needed some help. And while everybody was just talking about this, this is how you do it. And this is what it looks like in the perfect world that wasn't really addressing the the issue that people were facing, that this was, this was not the way that was playing out in their environment. Right. And so that we thought it's kind of weird that no one is actually talking about it. Because with our clients every time we mentioned that, and also said, it's not just you it's something we see more often there was this big relief, like Oh, really, that's like, you know, I thought it was just organization, but maybe it's a bigger thing, and other people are also having the same issues. And once we we gave it a name, that's really when it took off. So we were kind of hesitant at first because the metaphor can be maybe confronting to people and maybe offensive, but we tested it. And the response was just absolutely, overwhelmingly positive. And like I said, often when we're just the fact that we gave it a name, gave people the ability to talk about it and also feel connected to other people. And that's, that's when we knew we had to go deeper. And after some workshops we did and talks to conferences, we thought we should really write a book about this. Yeah,
Christiaan Verwijs 5:25
I think that that was something that we actually did somewhere in 2015, or 2016. That's when we started developing this idea, right. And to add the honest explanation of why we wrote a book, it's also that both Johannes, me and Barry, also, by the way, we have experienced scrum in teams where it works really well, where stakeholders are involved, where it's a lot of fun. I've been with a team for nine years, and it worked there. I mean, sure, we made mistakes. And we did some stupid stuff, some of which is in the book, by the way, but it works. And when I started looking, visiting other teams, I saw it wasn't always the case that it worked or not at all. And that kind of surprised me, because I wish for all teams to feel what it's like to work with Scrum effectively, and see how it actually helps them rather than be annoying or frustrating. And I think that that's also a big drive behind the book to show that it is possible and that you can do it.
Joe Krebs 6:23
Yeah. I mean, it's interesting, right. So in the beginning of of Scrum, like in the early 2000s, there were books about how to get started with Scrum and so on. Right, that avalanche of books of Scrum introductions, etc. This is, this is a turning point, right? Because now we're talking about how to do Scrum. right! So there's a lot of people that have been trained to have been gone through training programs, etc, right. And now they're applying it and they're falling into this into this. You know, Zobie kind of behavior here, right? What are some some patterns that I'd say there is a listener out there listening to us right now? And he's just like, I don't know if I'm doing Zombie Scrum or not? Right? Like, what is it like a pattern? Maybe you can describe one of those patterns that you would say that is an indicator for your running a zombie Scrum?
Christiaan Verwijs 7:11
Sure, I can take the first one. And you almost can probably add more to that. But I think the most important one that we see is that there is no working software at the end of the sprint. And if you put this in scrum framework terminology is there's no done increment that's that's released at the end or near the end of the sprint to stakeholders. And in the case of severe zombie Scrum, that never actually happens, or maybe a year down the road, maybe there are releases happening to an internal staging environment, but it's not actually going to customers that are paying for the product, it's not actually going to the people that are going to use it, it's just going to internal stakeholders, whoever they are. So this lack of working software at the end of the sprint, for us, that's one of the biggest indicators that you're probably dealing with zombie Scrum.
Johannes Schartau 8:01
Right. And I just want to mention that we have a survey that you can take at survey at zombie scrum.org which is going to help you evaluate and we we designed the survey a while back. And it also kind of informed how we structured the book. So we have five big sections. First one is, what is Scrum? And does your challenge actually match what what scrum has to offer, because that's usually where it kind of starts, then what Christiaan said about shipping and getting the whole empirical process. So what is often makes this so empirical process control, loop started and new transparency, inspection adaptation that can only happen when you actually have a product that you can inspect. And if you don't have that, then the whole thing doesn't really happen. And you just Christiaan to just touch briefly on it. So what you want to do in in Scrum and with Scrum is to deliver something that stakeholders actually need, which is interesting that, you know, when you talk to zombie Scrum teams, they believe that is what they're doing. But one of the questions is, you know, who are your stakeholders? And that that kind of gets this whole discussion started? Like, where does the need for your product actually arise? Who benefits from it who invests in it? And we often find that zombie Scrum teams are far removed from the real source of that need, or the the value that you that you want to ship, right? And with that distance, there's this again, there's a disconnect between If you ship you get feedback, if you're actually delivering value, but you also need to get from the right people. And the scrum doesn't really explain what stakeholders are. So people often assume that it's built from accounting or, you know, someone inside the company that they kind of put in place as the stakeholder because often they other people can cause trouble for the team if they don't do what they're supposed to do. But that doesn't really mean that yeah, that that is where the product starts or where, where the whole loop kind of closes.
Joe Krebs 10:22
I think that's that's an interesting thing. Right? So what do you what you said Christiaan? On on the done? Are you both talking about the the thing that is completed by the end of a sprint, right, that done increment is casually said, but this is, this is a tough thing to do. Right? And so this is not an easy thing to do. To be totally honest, right? And there might be a lot of people out there right now saying, Oh, we have we have something done by the end of the sprint, but it's not like we got something done. This is a this is a done increment, right? This is potentially shippable. And that's where we see a lot of Zombies. So this is not easy to do. Right? And we'll definitely make that Jahnnes thanks for that link reference, we're going to make that link reference also available on the Show page. So people can just click on it and assess themselves against Zombie now. This is not a rare occasion out there in the industry, right to be a zombie team. I think that's a fair statement. Right? So if you're thinking if you're listening right now, it's just all that it's not apply to me. You have any kind of percentage or anything like where you would say we're dealing with X amount, roughly. Obviously, we don't know every single team around the world doing Scrum. But do you have any indication based on the surveys you have so far? Like? What's the what's the percentage of zombie versus non zombie?
Christiaan Verwijs 10:54
That's a good question. So roughly, it's about 60% of the teams that participated in the scrum team survey have quite moderate to severe zombie Scrum, it's very hard to define a cutoff point. But that's, that's one way to think of it. And most of the other teams like the 40%, other of the other teams have some elements of it. And there are some things in there too. They're doing really well in all areas. But that's as you say, it's it's quite rare. And I think that's okay, too, right. It's the mission or what scrum asks of teams, and especially if the organization's those teams are part of, it's really hard. And in the book, we describe it as sort of exercising, like if you start lifting weights, the first time you do it, you can maybe lifted once or twice, and then you have insane muscle ache the next day. But if you do it more often, and you start building the muscle to do it frequently, and also increase the weights that you can lift and it's the same with Scrum, the first few times it will be very hard to release an increment that's even close to done. But the next time it will be easier the next time it will be easier and so forth. So it's a journey. And that's okay.
Johannes Schartau 12:49
We just want to do create that awareness that that is what that's the goal behind Scrum. And often people don't actually know that, or they don't know how far it actually goes. Because there are layers of organizational dysfunction between what they perceive as good Scrum and what the theory is. And it doesn't mean like everybody has to ship daily, for example, that's not what it means. But it kind of has to match the the speed of learning or the feedback loop that you're involved in. And it makes the whole thing come alive. And that's just the knowledge, like robbing people of the illusion that they're already doing really well. And that is something that we were aiming for just to to create some healthy tension, right, just to make people question and question what is happening in the environment and asking the questions. How far do you want to take this? What is really helpful for us? How quick do we need to be? And that is definitely different for every team, but just asking those questions for us. That's kind of the beginning of getting out of that zone. Right?
Joe Krebs 14:03
Well, so I mean, I could play devil's advocate right now and say, You know what I have I have a team that is a zombie team. And you know, they're doing Scrum check. You know, I could check off a checkbox and say, like, we're doing Scrum, and we're compliant with Scrum. And we're doing, we're doing, we're doing that Zombie Scrum, but at least I'm doing some Scrum, right. How would you encounter like somebody like one an executive leadership level of saying like, there's some significant business loss around being a zombie team, right? Is there anything you we could make a case for, like, even if you're doing a zombie Scrum and you feel like hey, my organization, there's, there's a ton of Zombie Scrum, but at least I am doing Scrum and they're having the daily Scrum and they're having all these kinds of events, and I can check, check, check, check. What's the business loss behind it? What's the benefit of going non zombie and and making them survive to speak in the language of The title of the book
Johannes Schartau 15:04
do you want to go ahead, I can take it,
Christiaan Verwijs 15:06
you start Johannes
Johannes Schartau 15:07
okay.
Well, it's difficult to put a number on it. But what we talked about in the book is that most organizations really optimize for efficiency. And that's kind of the prevailing mindset that they believe they set up some kind of process, get people really, really busy. And then something valuable is just going to turn out in the end. And that's usually not the case. And that is actually where scrum can be really helpful that it helps it be more effective in the sense of learning whether what you're trying to do is actually going to work. And that doesn't only mean you creating more value quicker or getting more cash. But it could also mean just finding out that something doesn't work, and then having the ability to stop it. And that's something that also organizations are usually not good at just saying, we should get off this dead horse and do something else and redistribute our more resources to something that is more promising. And so if you if you're trapped in that zombie scrum environment, that feedback mechanism is really delayed. And so you will definitely invest into things that don't return anything for much longer time. Again, this is going to be different for organizations. But I mean, I've worked with organizations, they had release cycles of nine years, for example, and just imagine, like nine years would go, what we thought the world was going to look like, and what it looks like now and then just having this massive splash of software and go like, Oh, this is what it is. Now, how helpful is that? You know, like it's if anything changes in the meantime, you don't have the time to change it anymore. And you, you definitely you won't be able to capitalize on that. On that change.
Joe Krebs 16:56
Nine years feels like yesterday when we started.
Christiaan Verwijs 17:02
So be Yeah, absolutely. And it's let's be honest, for many organizations, this is the reality, right? It's what you described Joe's, what a lot of organizations do they check the boxes, and we're doing Scrum. So everyone has a certificate. But hey, it's not working. So we need some other framework or light or certificate or something to make it work. But what we tried to do in the book is something that I was kind of missing in many books about Scrum is that usually other books talk about the how, what are you doing as part of Scrum? And that's really important. But why are you doing that? And how does this help the bigger picture? So what we really did put an effort into his to explain why are we actually doing Scrum? What's the advantage for the organization. Ultimately, it's about risk management, right. So if you release more frequently, and you can validate those assumptions, if you don't release every nine years, but maybe start with every few months, then at least you can validate if your assumptions were correct, and you're not wasting money, potentially a lot of features that no one's looking for. And ultimately, I think that's the best way to explain it to management, upper management in organizations, it's going to save you money, it's going to save you a lot of efforts that you don't have to spend on building something that no one's looking for. And if you do it right, you will have happier stakeholders, happier customers. And if you're a commercial organization, or a non commercial organization, that's what's keeping you alive. Right? Right.
Joe Krebs 18:34
Yeah, absolutely. And then also you know, morale maybe where folks might be in zombie , wow. This is this is empowering, talk talking about empowering you both are very hip on liberating structures where it is it's part of, of your day to day life and Johannes you even founded the user group in in Hamburg, Germany. And how important is it for teams to use I'm not saying liberating structures but techniques and you know, like these, these micro tools in their day to day work, how important is it to use those to prevent possibly zombie Scrum? What's What's the connect to you?
Christiaan Verwijs 19:19
Yeah, I think you always want wants me to start. liberating structures are really the core of everything that we do. And I can speak for Barry for me and Johannes altogether. And it's not a it's not about liberating structures as a as an approach, but it's about what they make possible. And I think one of the reasons why organizations get stuck in zombie Scrum is because everyone's trying to solve impediments only within their own little area, like within a team or are in a department but ultimately, you need to bring people together and make sure that they all have a voice in what what actually is the problem that we're trying to solve. Why are we not releasing frequently? Why are no stakeholders present, and then work together to overcome those challenges. And this is why liberating structures are so helpful because they make that possible to give everyone a voice everyone in the team, your stakeholders, management, the people from marketing to people from sales, get them into a room or a virtual room, use liberating structures and overcome those problems together.
Johannes Schartau 20:25
Yeah, there's this kind of sentiment in the Agile community that you just do let people figure it out, well, just people will talk about it, and then it's going to work. But in our experience, you need something else, you need to structure that interaction and make it actually effective. And that's, that's why we like liberating structures. And like Christiaan said, you can use anything else, it's mainly about getting people engaged at the right time for the right kind of problems. I mean, you don't want everybody deciding everything all the time. But there are definitely parts where it is so beneficial to include more people. And especially if it's about like making sense of your own environment and tackling your own problems, finding solutions for your own problems. That is where, especially in that whole change that scrum kind of elicits in an organization because it causes tension, and then you need to deal with that. But you cannot just have that traditional model of, you know, we will we need to escalate to the manager or something. But often, it's really that you need the people on the ground to kind of make sense of what is happening collectively and then find solutions on their own. And then maybe ask for for help. But with, at least I'm speaking for myself, but prior to liberating structures, it didn't really have the tools to actually make that happen. It just was. Sometimes it was just like, Okay, I'll just get people into the room. And then we were just arguing all the time, and people were frustrated. So that's kind of the gap that liberating structures fills for me.
Joe Krebs 21:59
Yeah, that's interesting way because I, in my my classroom activities, there was this one activity I always did. And I had no name for it. And I just did it. And every time I did it, it was a great thing. And then this book came out. And I was like, Oh, I can't believe like, let's take a look at this book. Right? If there is this technique, and I didn't was it was the shift in shale, right? And so I was like, Oh, it has a name now is a shift in share, right. And so I find that is, that's good. That is these patterns are proven in a way that it's this is not only me doing something in the classroom, right or in a project, but it's, there's also others found useful and actually picked up someone created it and then and then you get this confidence into your facilitation to write as a facilitator, this is not something I just came up with. This is done many, many times and many different people and whatever the route is of that technique. And
Christiaan Verwijs 22:54
I think it's also good to mention that the creators of liberating structures Keith McCandless and Henri Lipmanowicz. They came up with this 20 years ago, almost, I think, even even longer, I think in South America, and that was one of the first experiments took place. It's been around for a long time, but it never made it never connected to the Agile community. And I think, well, we were probably not the first but you're always an i, we you always had you read the book, I think, right. And you shared it. And we were excited about it started trying it out.
Johannes Schartau 23:26
I in 2014, I met someone in the states who was from Seattle, and he was actually working with Keith, and he introduced me, and then it kind of took off. And that's how I got introduced. But it was really about like when I had the first experience of what that was, and it was actually in a phone conference. But it works so well that I just thought what is this? Because we had been talking for think 45 minutes, it wasn't a one hour call. It went nowhere. Everybody was just like, Yeah, okay, so what else could we talk about? And then the guy just said, Okay, let's do this. And then let's do this. And then let's do that I was within the last 15 minutes was like 100 times more productive than the first 45 and I Yeah, people you just need to experience that. And it just helps teams also to it helps them feel productive and effective. While collaborating with can be really frustrating when you have some kind of Scrum Master Agile coach who always wants you to collaborate, and it doesn't feel like it leads anyway, it kind of feels like a waste of time. And if you if you get people to collaborate and it feels beneficial, and they're like, Hey, we actually got something really important off today. That has like a really good effect on the whole self organization team autonomy side of Scrum. Yeah.
Joe Krebs 24:48
Yeah, totally away just like you know, like, you know, the second day whenever these things are being introduced in an open space since 2009 at a conference in in New York, we do it every year and people are asking for it, right? Just saying, like, you're not doing a conference without open space, right? And it's like now it's like, Okay, we're coming, right? So. So it's like, it's like it really becomes part of the DNA of a culture and cool. Another thing you mentioned Christiaan is the something called certificates here, just want to bring this out, there's a ton of certifications going on. And just recently, I spoke with someone who said, there's a, an incredible number, I forgot the number. To be honest, I don't want to put in a wrong number out here. But an incredible number of people are being certified in scrum number is rising. And we're talking Scrum Alliance and scrum.org. All of those certificates are being handed out. But Zombie Scrum is increasing, too. So those two things are not going necessarily together, right. So one might actually create the behavior on the other side. What's What's your take on that? Both of you guys, but I know Christiaan is, is a scrum trainer was already versus others like me. Yeah. Yeah.
Christiaan Verwijs 25:58
So I can only say positive things about significance, right? Because I'm a trainer. No, I think it's interesting. Well, you could say that the rice and certifications can also be a sign that more and more people are starting to work with Scrum. And I can also explain why you're seeing more zombie Scrum, because it's so Zombie Scrum is just a large percentage of all the teams that are working with Scrum. But at the same time, I think there's also something to say for the idea that sometimes, and we also get those people in our classes is that the only reason they're there is to get the certificates. And that's what they need, because they can put it on the resume and or companies actually look for those certificates without asking anything else, just do you have that certificate, okay, then you're a scrum master. But obviously, it's much harder to do all these things, to be a good product owner, to be a good developer to be a good scrum master to be a good at any of those other roles that you can get certificates for. And sometimes I feel like that message is lost in the certification industry. And that can that can definitely be a problem. And I think that that's what we're seeing, in some cases. Absolutely. What's your take on that Johannes because...
Johannes Schartau 27:12
I'm so well, it's difficult to say because, for example, I am a certified team coach for the scrum Alliance. And I would just have to say I can only report really positive things about the whole process. I like what the scrum alliance is doing at the moment. And I also like at scrum.org, the, the later PSM classes really need you to reflect and they are essentially a learning journey. And that is something that I find really valuable, at least for me, I know that through that, gaining that certificate, my effectiveness as an Agile coach has really increased just because I had to, I had to talk about I had to write about my mental models, and just had to reflect on what it is that I'm actually doing. Because often I feel like we are, we're kind of using our intuition. But that doesn't always help with clients. So for example, if you want to tell them, This is how I look at your situation, or this is a model that we can use to assess your system together. And this is how I define success. How do you define success, and let's, let's see what that means for our work, for example, that is something that I learned just simply from telling other people about what it is that I'm doing while I'm working with a client. And that is really beneficial. So maybe the rise in certification should be accompanied by the encouraging people to pursue these higher certificates that really evolve, they really need a lot of effort for people to grow into. And maybe like the first step should be just clarify, John, if you get the certificate, it just means you have him you have read the scrum guide multiple times. And that's good, that's better than what other people do. But what you really what you should really strive for is something else. And so it's difficult, but I'm not against certificates. I have I personally have gained some really valuable experience from them. I can see why people don't like them. So I guess I'm somewhere in between.
Christiaan Verwijs 29:26
Nobody, I think of what you say it's a good point. Like it's not it's not certificates in themselves. That's the problem, but the way in which you achieve them. So is it is it a two day class or a one day class or even a bit of money that you pay for it? Or is there a learning journey that's part of actually getting that certificate? And that's what you're saying? Right? That's what's so important. You need to have that learning journey. Yeah, I agree with that. Absolutely.
Joe Krebs 29:52
Yeah. It's like owning a driver's license doesn't make you necessarily a good driver.
Christiaan Verwijs 29:55
Yeah, exactly. Yeah, yeah.
Joe Krebs 29:57
So, but it's also good To for me, personally, I feel like this certification is good. So I know what somebody else knows when they carry around that certificate. Why? Because there's like a, I want to say a standard of some sort, but at least like, you know, there was some, some evidence was about about the knowledge etc, if you don't have that it's just like this, there's probably a lot of conversation about what the things were, etc. And they could be quite different. Towards the end of our podcast here. I want to talk a little bit about something you just mentioned about Scrum guide, there was just recently a new scrum guide, I think it just fell exactly on the time when you guys published a book, what I want to hear your, your take on this because it's, it's the new scrum guide. Is that good against Zombie Scrum, like the product goal, for example, the the emphasis on that the addition of the product goal or the emphasis on the sprint goal, the commitment levels etc are these good things for Zombie or against Zombie Scrum?
Johannes Schartau 30:58
Biggest thing for me personally, it's kind of going in the right direction, I don't think the scrum guide itself can solve the root cause, which is you know, people just have different expectations or different imagined different things of what what Scrum is. And so they kind of bring that view and it makes them read the scrum guide in a certain way if they actually read it, because a lot of people don't. It was funny, because while we were writing the book, we were informed that there would be a new scrum guide. And we also knew what was going to be in it. And then the question was, should we change our book, but we kind of realized that most of what we wrote about is was actually compliant. So Christiaan, correct me, but for example, the, what we the whole chapter on on self organization. That was for us, that was one of the most interesting ones to write because we kind of knew what should be in there. But we also, we had to take our time to spell out what that is and what we actually believe, because it's, it's difficult to grasp. And one of the things we started out with was about when we started defining self organization and trying to compare it to self management, right. And so what we wrote about was, for example, that the scrum guide actually kind of means self managing instead of self organizing. And that was something that was actually addressed later, not because of us, but it just kind of happened at the same time. That was really interesting. Yeah,
Christiaan Verwijs 32:36
it was pretty cool. And I think that in our book, we pay a lot of attention to shared goals. The term product goal, we can't use that yet in our book, because the scrum guide wasn't updated yet. But we talked about having a vision strategy, a sense of where the product is going. We also talk a lot about sprint goals. So that's definitely something that's very much aligned with the changes that were made. But I do agree with Johannes. And I think that no matter how you write the scrum guide, it's not going to prevent zombie Scrum. It's a bit like, like, in a sense, sometimes think like it's a bit like the Bible, right? It's to describe what is actually a good moral person. But we've been spending 2000 years to figure out what it actually says about how to be a good moral person, no matter how many perspectives you add to it, it doesn't actually clarify it, you have to talk about it with the people around you. And that goes for the scrum guide as well. You have to make sense of this within your organization with with your teams and with all the books that are available, the blog posts, podcasts, etc. Yeah.
Joe Krebs 33:39
Cool, guys, I want to thank you guys for spending a little bit of time with me where the listeners talking about the new book, The zombie scrum Survival Guide, published by Christiane Verwijs, Johannes Schartau and Barry Overeem. And it's available, obviously for to be purchased to prevent Zombie Scrum. And I feel like I feel like we could have another show at some point, which is talking about liberating structures to take like, besides this book, we could continue to conversation about another topic. But that's for another time. How was that?
Johannes Schartau 34:15
Great,
Christiaan Verwijs 34:15
sounds great. And if people are interested in the book, they can go to zombiescrum.org. We have information there on where to get the book. You can also get it at every bookstore that you can imagine.
Joe Krebs 34:27
Awesome. I want to make all these links available in the show page. And as well as links to you guys and how are people get in touch with you? No, not beyond the book things other things that might be of interest. Thank you so much.
Johannes Schartau 34:40
Thank you.
Christiaan Verwijs 34:40
Thank you.
Joe Krebs 34:42
Thank you for listening to Agile FM, the radio for the Agile community. I'm your host Joe Krebs. If you're interested in more programming and additional podcasts, please go to www.agile.fm. Talk to you soon.
Transcript:
Joe Krebs 0:10
Agile FM, radio for the Agile community. www.agile.fm. Welcome to another episode of Agile FM. Today I have John Kern with me who is a one of the authors, a co author of the Agile Manifesto. He enjoys loud cars, travel, climbing beer, individual freedoms, small governments. That's what his Twitter profile says. So welcome to the podcast, John.
John Kern 0:44
Thank you, Joe. Appreciate it.
Joe Krebs 0:46
Yeah, we could talk about a lot of things here, including beer and travel, and you do travel quite a bit. But the one thing I want to talk about is the Agile Manifesto. We are recording this in February 2021. And that is also the 20th anniversary of the Agile Manifesto. So very timely recording you and I want to reflect a little bit on that day that weekend you guys had in Utah. So this is the how do you feel about this anniversary? Just like curious. It's been 20 years. And you know,
John Kern 1:18
yeah, I remember that the 10th anniversary. Yeah, that was kind of shocking. That was already 10 years. And 20 certainly seems like it flew by. So it's it's pretty amazing that the opportunity I've had that much of an impact over 20 years on so many millions of people is really humbling. And the fact that it's still relevant still worth talking about you, I think, is is a fairly amazing feat of happenstance. Frankly, nobody knew this would take off and anyone would care about it. Even 20 days from the day we we left Snowbird. So
Joe Krebs 2:12
yeah. So I mean, obviously, nobody could know what would come out of this weekend, right? It could have been just a fun weekend of skiing. Or there's more and there was more there is after 20 years, we're still talking about every time I talk about the Agile Manifesto, and I refer to it to folks I work with professionally. I always say this is a site. That is probably the one website in the internet that not a single pixel has changed in 20 years. I think.
John Kern 2:41
That's a great point.
Joe Krebs 2:41
Yeah, it's like it's still the same, right? And but there is something about that, that it is still the same. So it's still relevant in the same way, we're still talking about very similar topics and coaches, maybe on different levels, but they're also talking about the same topic. So it shows how instrumental this, this was. So thank you for that. How do you feel? How do you feel about agile in 2021? Now, like, I mean, obviously, there was a lot of things going on in the in the early days in 2001, 2002, financial crisis and all that kind of stuff that that was now we're in the middle of a pandemic. But so we went through a lot as a society, but from, from a community's perspective, where are we what how do you feel about agile as a as a topic in the community in the industry? And what companies out there do with it?
John Kern 3:32
Well, I think the weather, you know, I would say part of the problems that maybe anything like this face is is how folks embrace it, how they interpreted how they practice agile. So there's, it's been this way from pretty much the day we published it. It obviously resonated obviously struck a chord. I feel we got to the gist of the kind of how humans endeavor to build software. But yet, there's always going to be I don't want to say it's the Crossing the Chasm type thing. But, you know, there's still plenty of frustratingly non agile going on in the name of Agile. And I think that that's just you, the sort of the beauty of the Agile Manifesto is its its humility. Its its brevity. Its ambiguity, shall I even say, right? It's not it's not. It's not prescriptive. Yes. And that means you have to think and that means you have to apply it in context. And that means you have to be curious and to humble about your, your ways of working. And so I think those that get it it's a boon, right? There are kickass agile teams and agile companies and Agile and Lean companies, right? You can see there's a radical difference of those who get it, practice it, live it, breathe it. And then those who treat it more as a prescriptive, they might have latched on to Scrum or, or SAFe or, you know, some very prescriptive and then not moved on from there, you know, just still locked into a different I don't want to say draconian, but a different command and control way of being agile, I think, you know, that's, you can't have perfect, perfect interpretation of such a small document. So, you know, I It's understandable, but I think that's, you know, that's still going on, and I, you know, I hope folks push can push through that really get more of the benefit of the agile mindset, not just a handful of prescriptive recipes.
Joe Krebs 6:23
Right, very much like a declaration of independence, but also not. There's also room for interpretation. And that makes it so so flexible, right?
John Kern 6:32
Yeah, and with all due humility, I think I draw a parallel to a unique group of individuals came together, thought up some pretty amazing intense words, about in on the Declaration of Independence about how to how to govern people. Yeah, we were more of course, just the software side of things. But yeah, it's, it's getting to the gist of the problem domain, so to speak. And, you know, I think it's, it's very similar, how do you and you know, France, for example, screwed up, you know, their, you know, revolution, but and was not built on the right principles? versus, you know, the freedom that the Declaration of Independence, right, talked about? So I think Agile is very similar. You can it's interpreted and think you're going along that way, and still end up being a kind of a command and control, not happy place to work. But you're agile,
Joe Krebs 7:38
It's, that's what I what I often see is when people are talking about the Agile Manifesto, but they're not even aware of the 12 principles, right? It's just like the four value statements. And obviously, those are very vague and purposely, right. And that really leaves room for interpretation either way, and you're ending up with an organization so called Agile. That is, that is really far away from what you might be thinking of agile, or I will be thinking of agile, when are you are you nervous that this is might get washed away that term overtime? I mean, it's been around for 20 years, but with the current trends we're going through, do you feel like at one point, people will be like, alright, is agile? We don't have a handle on it, there is no clear definition. Are you nervous? Or are you feel like there is there will there's light at the end of the tunnel that will we're getting to this state of what do you guys thought of 2001?
John Kern 8:32
But that's a good question. I wouldn't be nervous because it's not my job to, to, to, you know, force people to get it. You know, it's, it's, I treat it as a personal practice, because it really does start with you. It's not, you know, organizations want to have an Agile transformation. But it starts with the individual. It starts with understanding, as you said, it's not only the the four tenets, but the the principles and, and even more, because we were humbled, like the one of the top words is uncovering. It's not even uncovered, right, we're not even past tense. You know, we didn't act as if we had, you know, God's gift to the answers of the world for software development, but we said we're uncovering because we're learning I practice a lot of Defense Department, heavyweight stuff and created in self defense kind of as a taxpayer a lighter weight methodology to work with my Defense Department. Customers, you know, so even there and you're we're constantly are we really left, in my mind left it clear that it's still going on. That was a certain point in time what we uncovered And what we were trying to address and heavyweight processes. And you know, I think going forward, you can, in my mind, those bullets still apply. Principles are still valid, and what you do with them, I'm not so much troubled, and I'm hopeful. I think this might, you know, this, this anniversary might inject because there's people, it's shocking to say there's, there's people that didn't hear of anything but agile in the industry now. They didn't, they didn't experience what, what I experienced with MIL standard 2167, or heavy waterfall type processes or some of the crazy stuff that was, you know, the elements that we were trying to combat in terms of heavyweight process. So a lot of people don't even know those existed. You know, it's a good opportunity to maybe reinvigorate some some of those who might have slipped into learned helplessness, you know, in a large organization, like, Oh, that's right, there's, there's, uh, there, it could be a light at the end of the tunnel, let's, let's return to some of these basics. Let's, let's try to try to get back to what Agile was all about in the beginning. So I'm hopeful, but yeah, like, whatever. You know, I
Joe Krebs 11:31
It was Arie van Bennekum, I spoke with here on Agile.FM a little while ago. And he was the one who actually said, John was the guy who said that everybody leaves their ego in front of the door before you come in at that weekend. So it was and that goes back to your statement about being humble, right? There were lots of people 17 of them different opinions. What was Why were you there? We know like people that were from, from scrum there was DSDM was extreme programming. So it was a broad mix of different kinds of streams, I would say at that point, right of development things were but just curious whether
John Kern 12:14
there was the, you know, the XP contingent. I was there because I was working with Peter code. And we were doing Feature Driven Development, we had to get rebuilt TogetherSoft at the time, a wonderful UML modeling tool that I remember messing around with Bob Martin with. So yeah, I mean, I co-authored some things, but I was not famous, like the others in the room. So I was on the coattails of Peter Coad. And Peter said, This sounds like they're right up your alley, John. So I attended and participated heavily, because because of my Defense Department days, and my pension for being pragmatic, and lean, and absolutely, to deal with the ambiguities of software development, I had a lot of opinions.
Joe Krebs 13:09
And you you're the one that I came across your notes from the event, right? So you captured notes and everything, you release those, it's almost like, it's like a museums artifact, almost like the personal notes from the from the weekend. And maybe we can hyperlink those on the Show page as well, for people to see. So that is all great stuff. What are you focusing on these days yourself? I know you do quite a bit of traveling, but from a software perspective. What are you focusing on these days?
John Kern 13:40
Well, right now I'm working at adaptavist adaptiveness.com, who you would think might be a little odd, because they are the probably by any reasonable measure, the biggest, badassed, best Atlassian partner, you know, and, and in many circles, the agilistas, you know, will shun Jira, or something like that. I've been using JIRA and Confluence since whenever the hell it came out. And I was using other tools before that. And I've been pitching for 20 years, people process and tools in that order. And tools are a real third distance. And I've sold tools, but I know where they live, you know, it's the people first. So. So there was an opportunity there. And one of the gentlemen one of the reasons why I knew somebody who worked there who insisted that I talk talk, talk to the CEO. So we're setting up more of a Innovation Center and helping other companies learn how to have more of an agile mindset. It's really hitting the people and culture side of things and process and tools. But it's the more of the kind of agile mindset and the workshops and some of the we combined and some elements of motivation, orientation and engagement. And we're also working with Heidi Araya who's, who has a lot of experience with larger organizations than I do, for example. And so we're really striking out on a pretty fascinating core, because until I met John, you know, some of the things that that, that we began talking about, and he helped shed light on about ways that people make their meeting different different, like leadership development profiles. So I learned why, in some cases, a technique that I would use worked like gangbusters with a team. And other times I've talked, and I'd be like, Knock Knock, Knock Is this thing on? You know, do you can even hear. And he, he, let me understand that? Well, actually, they weren't receiving on the frequency that you were transmitting. And sort of like, I may have been two steps in front of them, where the other team, I might have been only one step in front of them, and they could, they could, they, you know, was just slightly uncomfortable, but they could move their two steps was like a cliff. You know, so. So we're really, I think, opening up more of the realm around. I've been preaching it for a long time that the good people of their own will create a process. They don't need to read about anything in Scrum or write some somebody would you know, that they were really good focused on a vision, trying to get somewhere will create a process, I always say, you know, that a good people will trump every other thing that you tried to do. And they'll even create tools, right? It's just just now you have some places to start, if you want to, you know, begin with Scrum, or begin with anything, any kind of, you know, Kanban, or agile, lean any of that stuff. But it all boils down to the leadership and the people. And everything else is far secondary. So that's kind of what we've been doing. It's pretty fascinating to me, because we're, you know, really helping teams, and leadership, engage and understand a little bit more about their culture and their social networks or organizational network analysis, that kind of thing. You know, are they siloed? Are they control oriented with their motivation? So, so it's, to me, it's a, it looks like it could be the next wave of really trying to make an impact with the team, by understanding a lot of the, you know, where people are at today, and help nudge them towards a place in the future. But don't, you know, don't make them take two steps at once, one step at a time. Right. You know, so I think that's, that's pretty fascinating stuff. To me.
Joe Krebs 18:03
It was very interesting. Why because you all pointing out the cultural difference. And that's, that's something I see right now also, as a as a very big trend right now. Or we're designing adaptive having a culture of agility across the entire organization, then you do see, and this is, and I had worked with, just as an example, with Spotify in the past, right? People are now looking at, like, how do we map Spotify model to our organization? And it's, again, it's the, hey, we'll just use a process from somebody else, and we apply it to us, right? And then you get frustrated, why wouldn't work again, just to your point here, right? It's the, the incremental approach is taking step by step and taking a cultural from A to Z, but you know, every cultural or every organization is different set up and people and everything. And so there's just the whole idea of it. So we're falling into the same traps again, right,
John Kern 18:55
Yeah, that's, that's, that's a good way to put it. And the other thing that I kind of keeps me grounded is, since probably 2005, I've worked on a program for firefighters. So it's kind of a pro bono do good work, to help save lives and property and things like that. So I write code every week, I do BDD and TDD and deploy and that kind of thing. And it's extremely rewarding to get high NPS scores to get really good feedback from our customers. Because it's, it's real, right? I mean, agile. I experienced it myself how real it is. And being able to impact customers and get that kind of feedback that keeps me my fingers on, you know, and I've recently led teams through development so I'm kind of a favorite word is definitely building products doing software that's fun and tangible. And when engineering so
Joe Krebs 20:05
exactly what in this is what the manifesto is, the word software in it too, right? So there's a reason why that exists. And you pointed out earlier, there are listeners now on this podcast that might not have seen actually the, you know, the wrong way of doing it, or the one that is possibly causing a lot of difficulties and challenges. Are there a waterfall, for example, right. Now, what's interesting is that I think the manifesto came just at the right time. And we recently had time to mature into something, because what we're seeing now also is very different compared to 2001. Is, is the fact that in 2001, was we supported businesses with technology. Now, the business is technology, right? So a lot of companies are the when you said what your business is, like, it is cold, right? Was this before it was like, Hey, let's get a product from out of the way hours or something like that. And there was like IT solutions to support that, but it has drastically changed. Not talking about, like planes and embedded systems, and you name it. I mean, there's so much software everywhere in cars, you know? How do you how do you see all that complexity being handled, like more from a technical perspective, rather than the Agile Manifesto here, but what's your, what's your outlook? Is this going to? Most likely it's gonna get even more? So more complex? software is increasing?
John Kern 21:28
Yeah, in the scary part, as as an aerospace engineer, I would normally regularly, sarcastically say, if most buildings or aircraft or cars were built, like our software, or enterprise software, not a chance that I'm stepping in that building or walking over that bridge or right, because I submit the software and industry what I have to to focus on my shoulders that can fight it out about this, because you can you can argue both both sides. But in general, the the industry, I think, is very young still as an engineering discipline. And some would argue it's not even an engineering discipline, right. So I would say it's a lot of a lot of ad hoc. Not such good practices. But I'm assuming most folks applying software in what you might call a critical life critical or safety critical systems are still falling back on classic designs for failsafe, like, I'm pretty sure the elevator is going to still use a mechanical failsafe and not trust software. So but it certainly is scary to think the more systems and we started to see some, you know, the 737 max and started the a few things that are all of a sudden popping out of that's a pretty bad bug. Yeah, or bad testing or bad whatever. Certainly, we'll you know, we'll learn from it. And it's not like, you know, everyone's probably seen that the bridge there oscillating bridge, and wherever it was in Portland, or Oregon, or some or Seattle, you know, that that was an engineering, like, oh, turn that into oscillating vortices. All right, you know, with the wind, who knew? So yeah, it's not to say that everything will always be perfect. But it is a little scary to think of how how software in the past 20 years, really has become so dominant, and, you know, I used to say about technical debt, it can get so bad that you can go bankrupt. And the more that you are, is a software company, the more you better really care about being lean and agile and, and have a architecture and, you know, TogetherSoft 20 years ago, we rewrote the software probably every 18 months from scratch. Because we couldn't because we learned so much and we couldn't, we didn't do a good job of maybe always refactoring it but said screw it, just start over knowing what we know now, we architected make it leaner and meaner and then carry on, you know, keep both things going, you know, BaseCamp, you can still get the old version. Like there's a lot of different ways to think about solving problems. And you know, I think that the the more innovative companies will grab onto it, do it right because they'll understand talking to some a team In the development team about TDD and BDD, and hearing a developer, the ones that slow me down. Well, my you know, you're not born knowing you're not born with some knowledge. But you know, things like what will look quality will a QA people, write, write, these tests, man know, like, the gap between under like understanding the holistic aspect of what we do to try to deliver outcomes and the interdependencies between, you know, for me, having tests is like, a confidence booster. Right? I feel more comfortable. I'm not saying they're perfect. But it was more comfortable. Did it take more time? Maybe the first time but, but Right? It's that it's like, how do you? How do you break that mentality? Right, that now we just have to constantly be grinding out code. And we don't actually track all the debug later on, we don't actually track that we built the wrong thing we don't. So that kind of stuff is frustrating as hell, yeah. Or, you know, our profession.
Joe Krebs 26:10
I mean, I'm just this goes to the point of, you know, software getting more and more complex, you know, in the coming years, and there's just a trend, and I think it's gonna continue, right. It's obviously that more software is being included, I think, into lawn mowers everywhere, right? So it's like, so, software is going to be everywhere. And it becomes more important to have a good quality strategy around these things. Because we might have fatal accidents, we might have issues. So quality is a key thing. And that is that is deeply rooted in the Agile Manifesto. So I think that is the, you know, we were lucky in 2001, that you guys did this and wrote this, because it's going to be a guiding principle now for for these organizations who are dealing with this complexity. I always tell engineers, when I work with them through coaching and training, I always tell them, like the line of code they're writing is not the expense of you writing their line of code. It's, it's maintaining that line of code. Right? So and obviously, refactoring or rewrites are necessary, because the cost of that long term listing has to be upgraded, maintained, and possibly there's a side effect of defects on that line of code. So the writing the line of code, it's true, like minimal compared to, compared to the following costs.
John Kern 27:24
Yeah, that's so true. I would often say, you know, when someone puts something cryptic, like, it's not the one time you wrote it, it's like the 1,000th time someone's gonna read this later. Exactly. That's the penalty. Right? That's good. And it could even be your future self. Right. So yeah, it's, it's trying to build that, that, that professionalism, the craftsmanship and the, again, the understanding of beyond the the silo that you might think you're in being a broader thinking, individual understanding, we're trying to, we're trying to build something long term, hopefully, for for a piece of software. And we're trying to make our customers happy. And yeah, there's, there's good ways and bad ways to make that happen. You know, I liken it to two different styles of gardens. If I if I might do an analogy, my, my parents were big into square foot raised bed garden. So people probably have seen raised beds, so you don't trample on it and stamp down them. And then he could work compost into it. And the square foot technique was different plant you know, you have different boards with different holes on different centers, different types of plants needed to be planted on for it. Anyway, he also planted things cooperatively, like something could grow underneath another thing that would be beneficial. So it was a some of the most productive soil on the planet probably. And then you can have a giant garden, somebody's different tactic, maybe full of weeds. Not pretty to look at, not with nice wood chips in between the ego walk along, you can see his family aid, charities and the asparagus might not be pretty but it produces,
Joe Krebs 29:16
it produces Yeah.
John Kern 29:19
And the two CEOs running to those two different farms, you think they have a chance of comparing you know, input versus output any kind of process efficiency or right our industry is so bereft of being able to understand effort versus output and and you could even say well, I don't care I can get really cheap labor on that that big pile of land and out under every year and weeds at all, and it produces enough and I have cheap labor. And I just rewrite it every every year. Right? So I don't know the right I actually don't know the right answer because some industries It might be cheaper to throw it away and start over again. Yeah, in other industries, it might be worth to building a beautiful manicured English garden or something, right? Who knows what the answer is? No, no, no, no need to be, you know, gardens of Versailles. But we also don't all need to be, you know, weeds, you know, a garden full of weeds. I can barely find the plants. Is it a challenge in our industry? Yeah,
Joe Krebs 30:28
I agree. And it's a it's a great metaphor. No, thanks for that. Just by the end of our podcast here on our time together, is you you do travel a lot, and you travel to some remote places, as far as I can tell, right? And is there any kind of place you encounter where you still hear people's Agile Manifesto? What? Because it's always there's like, are you not not talking about your celebrity status? I know, we, you. You know, you're you're humble and everything. But are there still areas in this planet where you would encounter and people would not necessarily know that a there was an agile manifesto you've traveled to and that you were part of that?
John Kern 31:11
I don't know. It's a good question. Because I gave a talk with a group out of a few cities in China. They were big into it. I will say that. I think a couple years ago I was down in Colombia with with a friend of mine Ryan Lockard, who brilliant DevOps guy and beer maker friend of mine and I think it was their first we we keynoted their first I believe scrum day event, right? So it's gone de Colombia or something like that. But I will say that Colombia and I also spoke with a group in Mexico City and, and agile, agile Greece. In in each of those cases, especially the ones I was in first I was in person in Colombia and in person in, in Athens. It was it was like the early days of the manifesto. I mean, it was so heartwarming. Folks, were so excited about the possibilities. And I really don't want to say it was like the first time that they were learning about it, but it seemed like the community was was just beginning to blossom. I think agile Greece is a little more mature but but certainly struck me the in Colombia just wonderfully optimistic, and hopeful folks, and and when people come up, you know, what their pictures taken or thank you for the aftermath. I mean, that that is so meaningful to me, because in some small way, what we did in Snowbird had such a positive impact on people flocked. that's meaningful. I mean, it's, it's real, right? It's, it's not, it's not fake, and you can feel it in their gratitude. And it just, it was lovely to see that kind of enthusiasm again. So that's fun. Yeah,
Joe Krebs 33:33
totally. I can see and especially in those early days, right where you were like, wow, we're already seeing the initial signs of this there's more to it and this is going to be long lived. I mean, I can only speak for myself here. There was a lot of things in my life I got tired of very, very quickly not agile way to there's something to this this lifelong learning. There is always something to be uncovered, discovered. So it's, it's really fantastic so, and Agile FM my podcast wouldn't be called Agile FM without you guys, so thank you. Why don't you think you will next time we'll talk about beer or we talk about other things on your list. But this was all about the Agile Manifesto's 20th anniversary. Thank you, John.
John Kern 34:21
Thank you, Joe. And I'd be happy to talk about any any other subject anytime.
Joe Krebs 34:29
Thank you for listening to Agile FM, the radio for the Agile community. I'm your host Joe Krebs. If you're interested in more programming and additional podcasts, please go to www agile.fm. Talk to you soon.
From the publisher's feed
Radio for the Agile Community