Easy Agile Podcast Ep.3 Melissa Reeve, VP Marketing at Scaled Agile

"I really enjoyed speaking with Melissa Reeve, VP of Marketing at Scaled Agile about how non-software teams are adopting a new way of working."
It's more important than ever to be customer-focused.
We talk about the danger of 'walk-up-work' and how to avoid this through proper sprint planning.
Melissa also gives an update on how agile is spreading to non-technical teams.
Transcript
Sean Blake:
Hello everyone. And welcome to the Easy Agile Podcast. We have a really interesting guest with us today. It's Melissa Reeve, the Vice President of Marketing at Scaled Agile. We're really excited to have her on today. Melissa Reeve is the Vice President of Marketing at Scaled Agile, Inc. In this role Melissa guides the marketing team, helping people better understand Scaled Agile, the Scaled Agile Framework. In other words, SAFe and its mission. She also serves as the practice lead for integrating SAFe practices into marketing environments. Melissa received her Bachelor of Arts degree from Washington University in St. Louis, and she currently resides in Boulder, Colorado with her husband, chickens, and dogs. Melissa, thanks so much for joining us on the podcast today.
Melissa Reeve:
It's such a pleasure to be here. I really appreciate it.
Sean Blake:
Great. That's great. I really like your enthusiasm straight off the bat. So what I'm really interested in hearing about, Melissa is a little bit about how you got to where you are today. What have been the highlights of your career so far and how as a marketer, did you find yourself in the Agile space?
Melissa Reeve:
Well, thanks for asking. And I have to tell you, but just before the podcast my husband knocked on the door and he was all proud because we just got a new set of chickens and one of the chickens had laid its first egg. So that's been the highlight of my day so far, not necessarily the highlight of my career.
Sean Blake:
So you'll be having scrambled eggs and eggs on toast probably for the next few weeks now.
Melissa Reeve:
I think so. So back to the career, I really fell into marketing. My background was in Japanese literature and language. And I had anticipated this great career and international business in Asia. And then I moved out to the Navajo Indian Reservation and just pivoted. Found my way into marketing and found my way into Agile right around 2013 when I discovered that there was an Agile marketing manifesto. And that really was a changing point in terms of how I thought about marketing. Because up until that point, it really considered marketing in what's termed waterfall. Of course, marketers generally don't use the term waterfall.
Melissa Reeve:
But then I started to think about marketing in a different way. And when I came across Scaled Agile, it brought together so many elements of my career. The lean thinking that I'd studied when I studied in Japan and the lean manufacturing, it was Agile marketing that I'd discovered in 2013 and just education and technology have always been part of my career. So I really consider myself fortunate to have found Scaled Agile and found myself in the midst of scaling Agile into both enterprises, as well as marketing parts of the enterprise.
Sean Blake:
Oh wow, okay. And I noticed from your LinkedIn profile, you worked at some universities and colleges in the past. And I assume some of the teams, the marketing teams you've worked in, in the past have been quite large. What were some of those structures that you used to work in, in those marketing teams? And what were some of the challenges you faced?
Melissa Reeve:
Yes, well, the largest company was Motorola. And that was pretty early on in my career. So I don't think I can recall exactly what that team structure is. But I think in terms of the impediments with marketing, approvals has always been an issue. No matter if you're talking about a smaller organization or a larger organization, it seems like things have to go up the chain, get signed off, and then they come back down for execution. And inherent in that are delays and wait states and basically waste in the system.
Sean Blake:
Right. So, what is Agile marketing then and how does it seek to try and solve some of those problems?
Melissa Reeve:
Well, I'm glad you asked because there's a lot of confusion in the market around Agile marketing. And I can't tell you how many news articles I've read that say marketing should be Agile. And they're really talking about lowercase Agile, meaning marketing should be more nimble or be more responsive. But they're not really talking about capital-A Agile marketing, which is a way of working that has principles and practices behind it. And so that's one aspect where there's confusion around Agile marketing.
Melissa Reeve:
And then another aspect is really how big of a circle you're talking about. In the software side when someone mentions Agile, they're really talking about a smaller team and depending on who you talk to, it could be anywhere from five to 11 people in that Agile team. And you're talking about a series of teams of that size. So when you're talking about Agile marketing, you could be talking about an individual team.
Melissa Reeve:
But some people, when they're talking about Agile marketing, they're talking about a transformation and transforming that entire marketing organization into an Agile way of working. And of course, in the SAFe world, we're really talking about those marketing teams that might be adjacent to a SAFe implementation. So, I think it's a good question to ask and a good question to ask up front when you're having a conversation about Agile marketing.
Sean Blake:
Okay. Okay. And for those people that don't know much about SAFe, can you just explain, what's the difference between just having a marketing team now working in a capital-A Agile way, and what's the difference between an organization that is starting to adopt Scaled Agile? What's the difference-
Melissa Reeve:
Sure.
Sean Blake:
...between those?
Melissa Reeve:
Yeah. So what software organizations found is that Agile teams, so those groups of five to 11 people, that way of working works really well when you have a limited number of software developers when you started to get into the world's largest organizations. So I think of anybody on the Global 2000, they might have tens of thousands of software developers in their organization. And in order to leverage the benefits of Agile, you needed to have cadence and synchronization, not only within a team, but across multiple teams up into the program level and even the portfolio level.
Melissa Reeve:
And the same holds true with large marketing organizations. Imagine you're a CMO and you have 6,000 marketers underneath you. How are you supposed to get alignment to your vision, to your strategies that you're setting if you don't have a way of connecting strategy to execution. And so the Scaled Agile Framework is a way of taking those Agile practices across multiple teams and up into the highest levels of the organization so that we're all moving in a similar direction.
Sean Blake:
Okay. Okay, I think that makes sense. And from a software team's point of view, one of the benefits of Agile is that it helps teams become more customer focused. And many would argue, well, marketing has always been customer focused. But have you found in your experience that maybe that's not so true? And when marketing teams start to adopt Agile, they realize what it really means to become customer focused.
Melissa Reeve:
Yeah. I mean, you raised another great point because I think most marketers think that they're customer focused. Like many things in the world, the world is a relative place. So you can, in your mind, in theory, be thinking about the customer or you can be actually talking to the customer. So I just finished what I call the listening session. And it was during our hackathon, which is our version of an innovation, couple of days worth of innovation. So it was eight hours on a Zoom call with somebody South Africa. Just listening to her experience and listening to her go through one of our courses, slide by slide, by slide, explaining what her experience was at each step of the way.
Melissa Reeve:
So if you think about somebody who is sitting in a large enterprise, maybe has never met the customer, only knows the customer in theory, on one end of the spectrum. And you think about this listening session on the other end of the spectrum, you start to get an understanding of what we're talking about. Now, your question really pointed to the fact that in Agile practices, you're thinking about the customer every time. In theory, every time you write a story. So when you write a story, you write the story from the perspective of the customer. And I would just encourage all the marketers out there to know the customer personally. And I know that's not easy in these large organizations. It's sometimes hard to get face time with the customer, but if you aren't speaking directly to a customer, chances are you don't actually know the customer.
Melissa Reeve:
So find a way, talk to the sales folks, get on the phone with some of your customer service representatives. Go to a trade show, find a way to talk directly to the customer because you're going to uncover some nuances that'll pay dividends in your ability to satisfy the customer. And when you go to write that story again, it will be even more rich.
Sean Blake:
Oh, that's really good advice, Melissa. I remember from personal experience, some of these large companies that I've worked in, we would say, "Oh, this is what the customer wants." But we actually didn't know any customers by name. Some of us personally were customers, but it's not really the same thing as going out and listening to people and what did they find challenging about using that app or what do they actually want out of this product? So there's a huge difference, isn't there, between guessing what a customer might want or should want? And then what their day to day actually looks like, and what are the things that they struggle with? That's hugely important.
Sean Blake:
For someone who's in one of these big companies, they're in a marketing team, perhaps they don't have the power or the influence to say, "Okay, now we're going to do Agile marketing." What would your advice be for someone like that, who can see the upside of moving their teams in that direction, but they don't necessarily know where to start?
Melissa Reeve:
Well, there's a philosophy out there that says take what you can get. So if you are just one person who is advocating for Agile marketing, maybe that's what you can do is you can advocate. Maybe you can start building alliances within the organization, chatting casually to your coworkers, finding out if you have allies in other parts of the organization and start to build a groundswell type movement.
Melissa Reeve:
Maybe you can build your own personal Kanban board and start tracking your work through your own Kanban board. And through visualizing your work in that way, it's a little bit harder now that we're all remote, but should we get back into offices somebody could in theory, walk by your cubicle, see your Kanban board and ask about it. And now you might have two people using a Kanban board, three people. And really start to set the example through your mindset, through your behaviors, through your conversations in order to start getting some support.
Sean Blake:
Oh, that's really good. So be the change that you want to see in the organization.
Melissa Reeve:
Exactly.
Sean Blake:
Okay. Okay, that's really good. And when these companies are moving towards this way of working, and then they're looking to take the next level, let's say it starts in the software development teams and then say marketing is the next team to come on board. How does it then spread throughout the whole organization? Because I know from personal experience, if there's still that part of the organization that's working anti-Agile it actually still makes it really difficult for the Agile teams to get anything done. Because there's still the blockers and the processes and the approvals that you need to go through with those other teams. And I guess SAFe is the answer, right? But how do you start to scale up Agile throughout the whole organization?
Melissa Reeve:
Sure. And what you're talking about is really business agility, is taking the whole business and making the business Agile. And you pointed out something that's key to that, which is once you solve the bottleneck and the impediments in one area of the business, then it'll shift to another area of the business. So the advantage of business agility is that you're trying to keep those bottlenecks from forming or shifting. But what a bottleneck essentially does is it creates what we call a burning platform. So it creates a need for change. And that's actually what we're seeing in the marketing side is we've got these IT organizations, they're operating much more efficiently with the use of Agile and with the use of SAFe. And what's happening is the software teams are able to release things more quickly than the teams that are surrounding them, one of which could be marketing.
Melissa Reeve:
And so now marketing is incentivized to look at ways of changing. They're incentivized to take a look and say, "Well, maybe Agile is the answer for us." So let's just say that marketing jumps on board and all of a sudden they're cranking along, and except for that everything's getting stuck in legal. And so now legal has a case for change and the pressures on legal to adopt it. So there is a way to let it spread organically. Most transformation coaches will understand this phenomenon and probably encourage the organization to just go Agile all in, obviously not in a big bang kind of way, but gradually move in that direction so that we're not just constantly shifting bottlenecks.
Sean Blake:
Okay. Okay, that makes sense. And when these companies are trying to build business agility across the different functions, are there some mistakes that you see say pop up over and over again? And how can we avoid those when we are on this journey of business agility?
Melissa Reeve:
Yeah. So I feel like the most common mistake, at least the one that I see the most often in marketing, although I've seen it in software as well, is people thinking that the transformation is about processes or tools. So for example, in marketing, they might adopt a tool to "become more Agile." Maybe it's a Kanban visualization tool, or maybe they're being suggested to adopt another common ALM type tool. And so they adopt this tool and they learn how to use it, and they wonder why they're not seeing big improvements.
Melissa Reeve:
And it's because Agile at its heart is a human transformation. So we're really taking a look at in trying to change the way people think. One of the topics I speak on is the history of management theory. And while it sounds pretty dry, in reality, it's eye opening. Because you realize that a lot of the habits that we have today are rooted back in the 20th and 19th centuries. So they're rooted in assembly lines. They're rooted in French management theory, which advocated command and control.
Melissa Reeve:
They're rooted in classism. There was a management class and a laboring, and the management class knew the one best way of doing things. So more than a process, more than a tool, we're talking about transforming this legacy of management thinking into a way that's appropriate for today's workers. And I feel like that's the number one mistake that I see organizations making as they're moving into transforming to Agile, an Agile way of working.
Sean Blake:
Mm-hmm (affirmative). Okay. Yeah, that's really interesting. And it really is eye opening, is it? When you look at how the nine to five workday came about, because that's the time when the factories were open and all the history around how organizations are structured. And it's really important, I think, to challenge some of those things that we've done in the past that worked back in the industrial age. But now we're moving into the information age and into these times of digital transformation. It probably doesn't work for us anymore, does it, some of those things? Or do you think some of those things are still valuable now that we have distributed teams, a lot of people are working remotely? Are there any things that come to mind that you think actually we shouldn't get rid of that just yet?
Melissa Reeve:
Oh, I'm sure there are. John Kotter has presented in his book, Accelerate, this notion of a dual operating system. So that you have the network part of the organization, which moves fast and nimble like a startup and then you have the hierarchical part of the organization. And the hierarchy is very, very good at scaling things. It's a well oiled machine. You do need somebody to approve your expense report. You do need some policies and some guidelines, some guard rails. And so we're not actually saying abolish the hierarchy. And I do feel like that's part of this legacy system. But what we are saying is abolish some of the command and control, this notion that the management knows the one best way, because the knowledge worker oftentimes knows more than his or her manager.
Melissa Reeve:
It's just too hard for a manager to keep up with everything that is in the heads of the people who report to him or her. So that's a really big change and it was a change for me. And I think why I got so fascinated in this history of management theory is because I came across some notes from my college days. And I realized that I had been taught these historic management theories. I'd been taught Taylorism, which stems from 1911. And I realized, wow, there's a lot of undoing that I've had to do in order to adopt this Agile way of working.
Sean Blake:
Well, that's great. Yeah, that's really important, isn't it? I've heard you speak before about this concept of walk-up work, especially in the realm of marketing. But I suppose, well, firstly, I'd like to know what is walk-up work. Why is it so dangerous, not just for marketers, but for all teams? And how do we start to fight back against walk-up work?
Melissa Reeve:
Yeah. So, marketers in particular get bombarded with what I like to call walk-up work. And that's when an executive or even a peer literally walks up, so think again about the cubicle farm, and makes a request. So how that looks in the virtual world is the slack or the instant message, "Hey, would you mind?" One is that it results in a lot of context switching and there's time lost in that context switching. And then the other part is rarely do these requests come in well-defined or even with any sort of deadline detach. In marketing, it might look like, "Hey, can you create this graphic for this email I'm sending out?" So now you've left your poor graphic designer with this knowledge that here she has to make a graphic, but they don't really have any of the specs.
Melissa Reeve:
So it's very, very helpful to put these things into stories, to follow the Agile process, where you're taking that walk-up work to the product owner, where the product owner can work with you to define that story, keep the person who's doing the work on task, not making them context switch or do that. Get that story in that acceptance criteria very well defined and prioritized before that work then comes into the queue for the graphic designer. And this is an anti-pattern, whether you're talking about an organization of 50 or 5,000.
Melissa Reeve:
And what I've found is the hardest behavior to change is that of the executives. Because not only do they have walk-up work, but they have positional authority too. And it's implied that, that person will stop working on whatever they're working on and immediately jump to the walk-up work being defined by the executive. So I feel like it's really dangerous to the whole Agile ecosystem because it's context switching, it interrupts flow and introduces waste into the system. And your highest priority items might not being worked on.
Sean Blake:
Okay. So how many people do you have on your marketing team at Scaled Agile?
Melissa Reeve:
We're pretty small, still. We've got about somewhere in the 20s, 23, 25, give or take or few.
Sean Blake:
So how do you-
Melissa Reeve:
I think right now we're three Agile teams.
Sean Blake:
Three. Okay. So those 20 something is split into three Agile teams. And do they each have a product owner or how does the prioritization of marketing work in your teams?
Melissa Reeve:
Yeah, it's a good question. So we do have individual product owners for those three product teams. And what's fascinating is the product owners then also have to meet very regularly to make sure that the priorities stay aligned. Because like many marketing teams, we don't have specialized skill sets on each of those teams. So for the group of 23, we only have one copywriter. For the group of 23, we have two graphic designers. So it's not like each team has its own graphic designer or its own copywriter.
Sean Blake:
Yes.
Melissa Reeve:
So that means the three POs have to get together and decide the priorities, the joint priorities for the copywriter, the joint priorities for those graphic designers. And I think it's working. I mean, it's not without its hiccups, but I think it's the role of the PO and it's an important role.
Sean Blake:
So how do you avoid the temptation to come to these teams and say, "Drop what you're doing, there's something new that we all need to work on?" Do you find that challenging as an executive yourself to really let the teams be autonomous and self-organizing?
Melissa Reeve:
Yeah, I think the biggest favor we've done to the teams is really, I don't want to say banned walk-up work, but the first thing we did is we defined it. And we said, "Walk-up work is anything that's going to take you more than two hours and that was not part of iteration planning." And iteration is only two weeks. And so, in theory, you've done it within the past 10 days. So if it wasn't part of that and you can't push it off to the next iteration planning, and there's a sense of urgency, then it's walk-up work.
Melissa Reeve:
And we've got the teams to a point where they are in the habit of then calling in the PO and saying, "Hey, would you mind going talking to so and so, and getting this defined and helping me understand where this fits in the priority order." And really that was the biggest hurdle because as marketers, I think a lot of us want to say yes if somebody approaches us with work. But what's happened is people have, myself included, stopped approaching the copywriters, stopped approaching the graphic designer with work. I just know, go to the PO.
Sean Blake:
That's good. So it's an extra line of defense for the team so they can continue to focus on their priorities and what they were already working on without being distracted by these new ideas and new priorities.
Melissa Reeve:
Yes. And in fact, I think we, in this last PI reduced walk-up work from 23% down to 11%. So we're not a 100%. And I don't know if we'll ever get to be a 100%, but we're certainly seeing progress in that direction.
Sean Blake:
Oh, that's really good. Really good. And so your marketing teams are working in an Agile way. Do you feel that across the board, not only within your organization, but also just more generally, are you seeing that Agile is being adopted by non-technical teams, so marketing, legal, finance? Are these sort of non-technical teams adopting Agile at a faster rate, or do you feel like it's still going to take some years to get the message out there?
Melissa Reeve:
Yeah. And I guess my question to you would be, a faster rate than what?
Sean Blake:
Good question. I suppose what I'm asking is, do you feel like this is a trend that non-technical teams are adopting Agile or is it something that really is in its infancy and hasn't really caught on yet, especially amongst Scaled Agile customers or people that you're connected to in the Agile industry?
Melissa Reeve:
I would say yes. Yes, it's a trend. And yes, people are doing it. And yes, it's in its infancy.
Sean Blake:
So, yes?
Melissa Reeve:
Yeah. So all of those combined, and I'm not going to kid you, I mean, this is new stuff. In fact, as part of that listening session I mentioned and we were talking about all these different parts of the business. And there was mentioned that the Scaled Agile Framework is the guidance to these teams, to HR, to legal, to marketing could be more robust. And the answer is absolutely. And the reason is because we're still learning ourselves. This is brand new territory that we're cutting our teeth on. My guess is that it'll take us several years, I don't know how many several is, to start learning, figuring out how this looks and really implementing it.
Melissa Reeve:
Now, my hope is that we'll get to a point where Agile is across the organization, that it's been adapted to the different environments. When I've seen it and when I've thought through things like Agile HR, Agile Legal, Agile procurement, the underpinnings seem to be solid. We can even things like the continuous delivery pipeline of DevOps. When I think about marketing and I think about automation. And I think about artificial intelligence, yeah, I can see that in marketing and I can see the need for this to unfold, but will it take us a while to figure out that nuance? Absolutely.
Sean Blake:
Okay. And can you see any other trends more broadly happening in the Agile space? You know, if we're to look forward, say 10 years, a decade into the future, what does the way of working look like? Are we all still remote or how are team's going to approach digital transformations in 10 years time? What's your perspective on the future?
Melissa Reeve:
Yeah, I mean, sometimes to look to the future I like to look to the past. And in this case I might look 10 or 12 years to the past. And 12 years ago, I was getting my very first iPhone. I remember that it was 2007, 2008. And you think about what a seismic shift that was in terms of our behavior and social media and connecting and having this computer in our hand. So I ask myself, what seismic shift lies ahead? And certainly COVID has been an accelerant to some of these shifts. I ask myself, will I be on airplanes as frequently as I was in the past? Or have we all become so accustomed to Zoom meetings that we realized there's power there. And we don't necessarily need to get on an airplane to get the value.
Melissa Reeve:
Now, as it pertains to Agile, I feel like in 10 years we won't be calling it Agile. I feel like it will look something more like a continuous learning organization or responsive organization. Agile refers to a very specific set of practices. And as that new mindset, well, the practices and the principles and the mindset, and as that new mindset takes hold and becomes the norm, then will we be calling it Agile? Or will it just be the way that people are working? My guess is it'll start to be moving toward the latter.
Sean Blake:
Well, let's hope that it becomes the normal, right? I mean that it would be great to have more transparency, more cross functional work, less walk-up work and more business agility across the board, wouldn't it? I think it would be great if that becomes the new normal.
Melissa Reeve:
Yeah, me too. Yeah. And I think, we don't call the way we manage people. We don't say, "Oh, that's Taylorism. Are you going to be practicing Taylorism? It's just the way we've either learned through school or learned from our bosses how to manage people. And that's my hope for Agile, is that we won't be calling it this thing. It's just the way we do things around here.
Sean Blake:
Great. Well, Melissa, I think we'll leave it there. I really enjoyed our conversation, especially as a marketer myself. It's great to hear your insight into the industry. And everything we've discussed today has been really, really eyeopening for me. So thank you so much for sharing that with me and with our audience. And we hope to have you on the podcast again, in the future.
Melissa Reeve:
Sean, it's been such a pleasure and I'd be happy to come back anytime.
Sean Blake:
Great. Thanks so much.
Melissa Reeve:
Thank you.
Related Episodes
- Text Link
Easy Agile Podcast Ep.29 From Hierarchy to Empowerment: Agile Leadership Paradigms
"Great convo with Dave & Eric! Key takeaway: revamp Easy Agile's org structure representation. Exciting stuff!"
Nick Muldoon, Co-Founder and Co-CEO of Easy Agile, is joined by Dave West, CEO, and Eric Naiburg, COO, from Scrum.org.
In this episode, Nick, Dave, and Eric unpack the current agile landscape, discussing the role of the agile native and emphasizing the importance of building connected teams by flipping the hierarchy and putting leaders in supporting roles.
They emphasise the importance of empowering the people closest to the problem to make the call, and ultimately creating an environment for success to happen.
We hope you enjoy the episode!
Share your thoughts and questions on Twitter using the #easyagilepodcast and make sure to tag @EasyAgile.
Transcript:
Nick Muldoon:
Hi folks. Welcome to the Easy Agile Podcast. My name's Nick Muldoon. I'm the co-founder and co CEO at Easy Agile, and today I'm joined with two wonderful guests, Eric Naiburg, the Chief operating officer at scrum.org, and Dave West, the chief executive officer at scrum.org. Before we begin, I'd just like to acknowledge the traditional custodians of the land from which we broadcast today, the people of the Dharawal speaking country. We pay our respects to elders past, present, and emerging, and extend the same respect to all Aboriginal, Torres Strait Islander and First Nations people that are joining us today. So gentlemen, thank you so much for making some time. We really appreciate it.
Eric Naiburg:
Thank you.
Nick Muldoon:
I guess I'd love to just jump in and, Dave, I've got a question for you first and a follow on for you, Eric. I'd love to just get a quick assessment, Dave, of the Agile landscape today and I guess the shifts that you may have seen now that we're out of these COVID lockdowns, these back and forth, COVID lockdowns.
Dave West:
Yeah, it's interesting. So I've been the CEO almost eight years here at scrum.org, and it has changed a bit during those eight years. I think what we're seeing and is a, dare I say, the deployment phase, mass deployment of these Agile ways of working and this Agile mindset throughout industries and throughout all organizations. It's more than an IT software development thing. And I think that that was accelerated during COVID. What's interesting though is many of the characteristics of Agile that became so important during COVID, particularly around empowered teams, particularly around trust, particularly around the hierarchy and the reduction of hierarchy, some of those things are being challenged as we return to the new normal, which some people would rather was just the normal. So I am seeing some of that. However, generally Agile is here, it's here to stay. I think the reality is that most knowledge workers, particularly those knowledge workers dealing in complex work are going to be using some kind of Agile approach for the foreseeable future.
Nick Muldoon:
And last week you... Was it last week? I believe you were in Paris for the first face to face?
Dave West:
[foreign language 00:02:37] I was and it rained the entire time actually, Nick. So yeah, I spent a lot of time inside in Paris.
Nick Muldoon:
Well, what was the sentiment from the Scrum trainers there, from the conversations they're having?
Dave West:
Yeah, it was interesting. We talked a lot about at scale, enterprise adoption, the challenges. It is funny that the challenges are challenges that you expect, and most of them are about people, legacy systems, people status, power position. We talked a lot about the challenges that teams are getting in these large complicated organizations. That continues to be the conversation. There is, obviously, this is Europe, they're very close to Ukraine and the conflict there. So there's definitely some conversations about that. We have six Ukrainian trainers and also about the same number of Russian trainers as well. So that's always a conversation. And then there's a general downturn of the economy that was also being talked about.
Layoffs are happening throughout Europe, and particularly in the technology sector, but I think that's growing to some extent. Vodafone just announced today that they were laying off, it's about 6,000 employees, and they're one of the biggest telecommunication companies in Germany, for instance. So there was definitely some of that, but so if you add enterprise, you add conflict uncertainty, you add economic uncertainty, those three things will come together. But what was funny in it is that throughout all of this, they were incredibly upbeat and excited. And I think because they're talking to people that they've never spoken to before, they're talking to people about how Scrum is a natural way of working, talking about the challenges of empowered teams, empiricism, continuous improvement.
And I had some really exciting conversations with trainers who were like, Yeah, well we're doing this in this aerospace company or this electric car supplier in Germany or whatever, or this financial services startup that's using blockchain for the first time. And of course they're using Agile. And so it was funny. It was almost as though all of those things, though there were the backdrop, it was still incredibly positive.
Nick Muldoon:
So this is interesting, and I guess if I reflect on the background for both of you, Eric, I'm looking at, you two have worked together from rational days-
Eric Naiburg:
A few times.
Nick Muldoon:
... a few times, but the prevalence of the Agile... I would describe you two as Agile natives and it sounds like, Dave, you've got your tribe there in Paris last week that are Agile natives. And I guess Eric, for you, what's the sense around the people that you are interacting with from a leadership perspective in these companies? Can you identify the Agile natives? Yeah, I guess is it an easier conversation if you've got Agile natives in leadership levels?
Eric Naiburg:
It's definitely an easier conversation if they're there. Sometimes they're in hiding, sometimes they're not Agile natives masquerading as Agile natives as well, which always makes it a little bit difficult because you have to peel back that onion and peel through who are they and what's their real agenda. I was talking to a CIO last week, and he was talking about the typical CIO lasts two to three years. So what is their real agenda? What are they trying to achieve? And Dave mentioned the people part of this, and people often become the hardest part of any Agile transformation or working in an Agile way. People want to protect themselves, they want to protect their turf, they want to do the things that they need to do to be successful as well. So you see that as talking to leaders within organizations, and they want to do better, they want to improve, they want to deliver faster, but they've still got that pressure. Organizations, at least large organizations, haven't changed. They still have boards, and they still report to those boards, and those boards still have their agendas as well.
Nick Muldoon:
You're making me recall a conversation that I had, this is several years ago, but on a trip through Europe, and it was with the Agile native, that was the Agile practice lead and probably wasn't masking, probably was legitimately an Agile native, yet they were talking about the mixed incentives for their, maybe not their direct leader, but the VP further up. And it was actually a, I don't want to say a zero-sum game, but there was some kind of fiefdom thing going where the various VPs would fight for resources, people, whatever, because that would unlock further bonus. But at the end of the day, it was not optimizing the entire financial services company. Are we still seeing that today?
Dave West:
Oh, very much so. In fact, a colleague of ours says, "Science used to have a saying, science progresses one funeral at a time." And I think Agile definitely has some of that, not funerals hopefully, but retirements.
Nick Muldoon:
Retirements
Dave West:
Retirement.
Nick Muldoon:
Yeah.
Dave West:
Yeah. The reality is that when you don't have incentives aligned, where you don't have teams aligned to those incentives and leadership aligned to those consistent incentives, then you're going to always be dealing with some challenges. What's so frustrating is we all know the industrial revolution, and particularly the recent revolution of mass production and oil, which just happened in the deployment phase just after the second World War, was enabled by changing working practices created by people like Ford and Deming and all of these people. We all know that. The digital revolution is happening around us. It may even pass us if you believe the AI buzz that's happening. We may be put to the side and computers may just take over, but this digital is happening, and you are in with leaders and they're like, "Yeah, totally respect that. We are going to be a hundred percent digital. We are an airline, but really we are a digital company with wings."
They describe themselves in this way, and then they don't want to challenge the fundamentals of how authority, how value is managed, how risk is made transparent, how governance is, it happens, how funding is made and planning, et cetera. They don't want to challenge any of those assumptions. They like that the way it is. But we are going digital. It is ironic that it still is happening. However, that isn't totally hundred percent. The organizations that get it, the organizations that have leaders that are either insightful, either motivated, or maybe they want to write a book or something. Maybe their reasons aren't always as clear, but those leaders are dragging these organizations into the 21st century.
Great example. Proctor and Gamble, Gillette. Gillette, the latest exfoliating razor. I can see you haven't used it, unfortunately, Nick, with your rather handsome beard. So yeah. Anyway, I use it a lot, as you can tell. The exfo... Was built using Scrum and Agile. This is Proctor and Gamble, an ancient, okay not ancient, an older organization, but really has got it. They realize that if they want to keep up with their customers, their partners, their suppliers, they need to work in quite different ways. And so it isn't roses, but there are roses in the garden as it were.
Eric Naiburg:
And it goes beyond, when you think of that organization, you think of what Gillette has done, is it goes beyond traditional Agile thinking. Traditional Agile thinking, we think software, and this is engineering, this is manufacturing, this is bringing together marketing because in those types of organizations, marketing drives what the product's going to be, and then engineering figures out how to deliver that product and so on. So it's really bringing together the whole organization into how do we deliver something, and deliver it together. I think that's one of the big things that we're seeing. And one of the big changes that Agile helps to drive is that team. So you talked about incentives and team incentives, that's a piece of it, but it's team ownership. It's team togetherness.
It is that ultimately they all feel accountable, and bringing that accountability together as a team versus, and I think even... So my wife's in manufacturing and it's always... She's on the R and D side of it, and complaining about the marketing people. You have those conversations of, "Well, they don't realize what it takes to actually build this thing. They just have the dream." And by bringing them together in that team, and really they're having their daily scrums, they're planning together and they're having those hard conversations respectfully, that starts to build that team and build them in a way that they're able to actually deliver faster and more what the customer wants.
Dave West:
Can I just lean in, I'm sorry, we just taken over here a little Nick, but I just want to lean into something that Eric said around it is all about the teams. One of the fundamental problems we see in many organizations is hierarchy. Because if you get these massive hierarchies, obviously there's, "I've got to be in control of something. I need to take ownership of things. I need to be off irresponsible for certain things." That's how hierarchies work. And so that often undermines the ability of a team to effectively function. We need to flip that so that these hierarchies become, instead of being on top of the teams, they need to be underneath the teams supporting them. Think of them as those support trusses on bridges or whatever. You have some fabulous bridges in Australia and in Melbourne and in places like that and in Sydney.
So think of it upside down, holding up the teams. But that means, going back all again to incentives again, that those leaders need to understand what they're responsible for in this new world. And they're doing it for very good reason. They're doing it because the teams need to be, they're closer to the problem, they need to be empowered to make the decisions in real time based on the data, the information they have, they need to have clean line of sight to the customer. All of those things are the reason why a hierarchy is just too slow to respond and too bureaucratic. So we need to flip it and enable those teams. And that's a huge challenge.
Nick Muldoon:I Love this. You two have given me something to ponder. So for the first six years of the company's life, of Easy Agile's life, we did have a very simple team page, and Dave and I as co-CEOs were at the bottom of the page. And then you had the leaders of the pillars. So you had, at the time, Tegan was the head of product, the leader, and they sat on top of Dave and I, and then the team sat on top of that. And it's interesting, I'm actually trying to reflect now, it's probably only in the last 12 or 18 months as we went through 40 people, that that page or that visualization has flipped. I've got an action item obviously to come out of this, thank you gentlemen, to actually go and flip it back because it's a communications mechanism, but if we actually put ourselves at the foundation in this supporting role for supporting the folks, that sets the tone, I imagine, for the team members in how they think of themselves and maybe that accountability piece as well, Eric.
Eric Naiburg:
Yeah. Yeah. That's interesting because sometimes it's those little things that change how people think and feel. I use a lot of sports analogies when I talk and meet with people, and especially with where Dave was talking of empowering the people closest to the problem. We have to do the same in sport. If we have to wait for the manager to tell us to pass the ball, it's never going to happen. We've got to allow the people to make decisions and make those decisions on the field. We need to apply that to business as well. Allow the people who are closest to the problem, closest to what's happening, make those decisions within the business as well.
Nick Muldoon:
So if we come back to Proctor and Gamble, and we don't have to rabbit hole on it, but they're one of the large, long-lived companies, and I don't know about their approach, in particular, but I think about GE, and GE had their internal training university program, and they were training their leaders, training their managers how to manage, training their leaders how to lead. How does a Proctor and Gamble go about shifting that conversation internally, and what's that timeframe? Because presumably you've start with someone that's on a team. Do you have to elevate them over time through the hierarchy of the company?
Dave West:
It is interesting. I'm fortunate to spend maybe because we're both British people living in Boston, I'm fortunate to spend quite a lot of time with, and there's videos on our site with this, by the way, interviews with Dave Ingram who runs R and D for male grooming, it's called, in the Gillette part of P and G. And the case study is out there. So I talked to him a lot about how you drive it in a huge organization where they've got everything to lose. They've got products that are amazing, they've innovated, those products are the products that you put into your shopping cart as you walk down the aisle. They don't want to muck that up. Let's be frank. If suddenly, because of some innovation, there's no razors on the shelves, then I, as a board man need a razor. So I will buy an alternate product, and it's possible that then I'll always buy that product.
So they've got to be very, very careful. They've got more to lose. So we talk a lot about how you manage change and it's all of the above. What he's done very smartly is he's empowered the product owner role or the person, the glue role, whether it's using Scrum or something else, and he's really invested in these change agents in his organization, and he's definitely led by doing, he's been very honest and open about that, and very clear that he doesn't have all the answers and he's looking for them to help him during this, which isn't perhaps what you'd expect from a traditional organization where-
Nick Muldoon:
The leader might need to feel that they have the answer to all of these questions.
Dave West:
Exactly. And he's done a really, really good job of doing that. And primarily because he says, "Well, my success is ultimately their success, so if I can make them be a little bit more successful, there's more of them than me, so let's make it work." Which I think is an unusually honest and very insightful view of it. So he's driven it predominantly through product management ownership areas. He's then provided a support environment around that. He's then definitely advertised the successes. He's spent a lot of time building cross-functional teams. The thing that Eric was talking about. And really been very careful working with their leadership. If you're material science, there's a whole department, if there's marketing, there's this whole channel thing that they have. Basically working with their leaders to create the environment for success to happen. And I don't think it's easy. I think there's many surprising roadblocks along the way, and I can't speak for him on this, but he's taken that divide and conquer approach, focusing on that catalyst role.
Nick Muldoon:
Because you, obviously, you're providing a lot of training for various, well, I guess people at various levels in these companies. And obviously it's a far cry from having a CST and a CSM and a CSPO certification going back a decade, decade and a half. What's the uptake around the leadership training? And what does that look like, Eric? Is there renewed interest in that at the moment or are people demanding more of that leadership training? Is it fit for purpose for today's leader?
Eric Naiburg:
So I think to a point it is. We're certainly seeing growth in the leadership training. Matter of fact, Dave and I were just looking at those numbers earlier this week or yesterday, I guess. Today's [inaudible 00:21:29]
Nick Muldoon:
Are there are any numbers you can share with us?
Eric Naiburg:
It's hard to share the exact numbers, but we're seeing double-digit growth in number of students taking our leadership classes. Both how do you measure, so our evidence-based management classes, as well as our leadership training, but that also only goes so far because a lot of those folks, depending on how high up, especially in the organization you go, aren't willing to take lots of time out to take such training. So a lot of it happens in that coaching. They're hiring the executive coaches or the Agile coaches that are in there. The scrum masters that are in there are actually working to help coach those folks. And a lot of it's less about the training and more about the mindset shifts. So if you look at our Agile leadership course, a large part of it is spent on getting people to think differently. And really some of it's hit you over the head type of activities, where it really helps to drive those points across of, "Wow, I need to think differently. I need to work differently. I need to treat people differently."
Nick Muldoon:
Differently.
Eric Naiburg:
It's that, and we're seeing good success with that because especially when that light bulb goes off for folks, and that light bulb that goes off saying, "Wow, this is different." We have some exercises in our classes that really get you thinking and get you... There's one, for example, where you're thinking you're doing the right thing for the customer, and you're thinking you're doing exactly right until it kills the customer, because you didn't necessarily think through the whole. It's, "Well, this is what the customer wanted, so we need to do it, but maybe I should have got together with the team and let the team make decisions." I'm going a little extreme, but-
Nick Muldoon:
No, I appreciate it.
Eric Naiburg:
... it's those sorts of things that we have to change. And a lot of what we do in the course is educate leaders on what those teams are going through, and what the individuals on those teams need, and the type of support that they need, not how do you manage those teams, not how do you manage those people. But how do you empower and enable those people to be successful?
Nick Muldoon:
I want to just rewind for a second, sorry.
Eric Naiburg:
Killing people.
Nick Muldoon:
It sounded like there's a friction point in actually getting these leaders to take the time out of the office to go and get some education.
Eric Naiburg:
There is, yes.
Nick Muldoon:
Is that correct?
Eric Naiburg:
Yeah.
Dave West:It's incredibly hard if you're at a large organization, in particular, when your schedule is overlapping meetings continuously eight to nine hours a day for them to take that moment to step back. Everybody, I believe very strongly, Nick, that everybody needs to take time to invest in their own personal and professional development. And that time is not a waste. Ultimately it is an incredibly good investment.
Nick Muldoon:
Yes.
Dave West:
We know-
Nick Muldoon:
It's great ROI.
Dave West:
Totally. Even if it just resets you, even if you have that moment of clarity because of it. it's not a surprise that people like Bill Gates go on retreat every three to six months and he takes his big bag of books-
Nick Muldoon:
Books.
Dave West:
And he goes off grid for a few days just to reset. I think that that time is incredibly effective. But what's interesting is, we are under, in America in particular, and I'm sure it's true in Australia, it's certainly true in England, where I'm from, motion is more important than outcomes. It's all about the motions. If you look busy, you're not going to get fired. And I think to some extent we learned that in school. I don't know if your parents said to you or maybe you got your first job. I was working on a delicatessen counter at the co-op supermarket, and I remember there was an old worker there, turned to me, he goes, "Whatever you do, when the manager walks by," Mr. Short-
Nick Muldoon:
Look busy.
Dave West:
... was his name. And he was everything that name implies. "Mr. Short walks by, look like you're doing something, start cleaning something, otherwise he'll take you off and make you do provisions, and you don't want to dealing with that milk, it's rancid." And I remember that. Look busy. And I think we've got a lot in our culture. I try to take time every week. I book, for instance, my lunch hour, I book it and I always try to do something in it. I try to watch a TED talk, read something, just to clear your mind to think about something different. I think that time is incredibly important. However-
Nick Muldoon:Get exposed to some new perspective, right?
Dave West:
Exactly. Even if it means, even if the stuff you're watching or whatever isn't that relevant necessarily. Sometimes that lack of relevance is exactly what you need because your mind does something.
Nick Muldoon:
A mental break.
Dave West:
Exactly. And however in corporate America, and I think that's corporate in general, that doesn't happen. People are overly leveraged, they're incredibly busy. They have to attend these meetings, otherwise their profile is diminished. And I think that's at the detriment of the organization and the company. Here's a question, Nick.
Nick Muldoon:
Yeah.
Dave West:
Who have you helped recently?
Nick Muldoon:
Who have I helped recently? I spend most of my time, and I get most of my energy out of coaching conversations with individuals. So on my [inaudible 00:27:35] profile, I've got futurist very high up, and so I love exploring what is your life and your career going to look like in five years time? They're the conversations that I really get jazzed by.
Dave West:
And that's what everybody... Who have you helped is more important than what have you done.
Nick Muldoon:
Yeah.
Dave West:
And I think you need to balance that.
Nick Muldoon:
I pulled up these stats because I thought you might find them interesting. We did a survey last year of a subset of our customers. And we had 423 teams. So it's not a huge sample size, but 423 teams. And the reason I think about it is because there's a lot of, what was the statistic here? So just to give you a sense, most common sprint duration is 14 or two week sprints. Most teams have six people that are involved. Fibonacci for story pointing, an estimation. 10% of these teams achieved what they set out to achieve at the start of the sprint. And so the teams, this 10% of teams, the subset, they did add work into their sprints, but teams that were unsuccessful, rolled work from sprint to sprint.
And so perhaps what it indicated to us is that there are teams that over commit and under deliver, and in fact 90% of them, 90% of the survey teams, it would appear that they over commit and under deliver. And then there are teams that are, maybe, leaving time, Dave, maybe for some education or some spare time in their two-week sprint. And they actually happen to pull on more work and they achieve that. And I'm just thinking about that from a sense of, are 90% of these teams trying to be busy or are they trying to be perceived to be busy? Even if it's at the expense of actually delivering?
Eric Naiburg:
Or are they even pushed into it? It's interesting, there's a question on our professional scrum master one, our PSM one test that often people get wrong. And I think it's a great question, which is, I'm paraphrasing because I don't remember it exactly, but it's essentially how much of the sprint backlog needs to be filled coming out of sprint planning. And a significant number of people say it needs to be complete coming out of sprint planning. Which goes in the face of Agile and Scrum.
Dave West:
Exactly.
Eric Naiburg:
Because we don't know there. There's that uncertainty. All we need is enough to get started, and once we get started, but I think people are fearful of, "Well, we've got two weeks, we need to be able to plan those two weeks and we better be able," and this is some of that top-down pressure that we talked about. "Well, we need to show that we've got two weeks worth of work here and that we're not sitting around, so let's fill it up." And those are some of the misnomers about Agile and Scrum. "Well, it's a two-week sprint, we need to plan two weeks." Well, no, we don't. We need to have a goal. Where are we going to get to? How we achieve it is going to take time because we're going to learn as we go. As a matter of fact, the scrum team that I'm on right now, we were running a three-week sprint, and two weeks in we've actually achieved our goal. And now we're able to build upon that goal. And we already delivered on that goal a week early, which is great.
Nick Muldoon:
Do you think, Eric, that there's a fear from leadership that if people haven't got two weeks worth of work teed up, that they're just going to be twiddling their thumbs?
Eric Naiburg:
I don't know that it's a fear from leadership. I think it's a perception that the workers have of what leadership is thinking. I think it's more that. And I think it's the, "Well, we said we've got two weeks," and they are going to ask us, management's going to say, "When will you deliver?" I don't know that we'll ever get away from that when will we deliver question, even though we continually try to get away from that answer. But they're going to ask it. So if they're going to ask it, I better be prepared, which means I better have a whole bunch of work laid out. And that just breaks everything that we teach. It breaks everything that we think in Agile.
And all I need in planning is I need a goal, and some idea of how I'm going to get there. And over time let's revisit it and let's continue to revisit it and go to it. But it amazes me how often that some of the answers to that question are, you have a full sprint backlog go coming out of sprint planning, you have enough to get started. I forget what some of the others are. But it amazes me how many times when I review tests people put the full back sprint backlog where it even says, right in the scrum guide, "You're going to inspect and adapt throughout the sprint." Well, how do I inspect and adapt if I've already decided what I'm going to do?
Nick Muldoon:
Who's the onus on? If it's not actually the leadership's wish that you fill up all your time and you operate at a hundred percent capacity, then is the onus on the leader to make it known or is the onus on the team to engage in the conversation?
Dave West:
It's the leader.
Eric Naiburg:
Yes.
Nick Muldoon:
Yeah. Yes, both. Yeah.
Dave West:
I think it's more the leader because I think they have to create the environment where the team actually can challenge it, and actually have that very clear conversation. What worries me about your stan is the fact that I don't... The first few sprints. Yes, maybe you get overly excited, maybe you fill the sprint, which you don't need to. Maybe you're just keen. That's okay. The thing is, what happens on sprint three or four or five, when the same pattern is manifesting itself over and over again. That's worrying. And I think that speaks really clearly to the lack of help the team's having. Whether you call it an Agile coach, and in Australia, I think the Agile manager is a phrase that's used, or whether it's an Agile, or whether it's a scrum master, whatever. Scrum.org has a scrum master.
And the reason why we have a scrum master isn't because we don't know scrum, though there's some days it might be questionable. But cobbler's children, all that stuff. But the reality is, we do know Scrum, we talk it, we breathe it, we love it. But having somebody that steps back and says, "Hang on, Westy, what have you done there? Have you forced encouraged the team to fill the sprint? Have you set them an unrealistic goal? Have you listened to them and asked them the questions? Or have you told them what you want? And what do you think that's going to do?" I know that I have, because Eric and I fund the sprints, as it were. When we go to a sprint review and we say stuff, because a sprint review is ultimately there to provide feedback to the team, to allow them to inspect and adapt for the next sprint.
You can't change the past, but you can change the future based on feedback. If I go in with, "Oh, well that's rubbish and you should do this, and what about that?" Yeah, it's going to have an impact. So ultimately we have to think about, as leaders, what we bring, and also have somebody often helping us to be the leader that we need to be because we get excited and we get enthusiastic and we get, "Oh, you can do this and that? Let's do it. That sounds awesome." And sometimes that can...
Eric Naiburg:
And that's part of why I say it's both. That's why I said the yes. It's on the leader, but the leader needs to be reminded of that. The leader needs to be supported by that, especially by the product owner and the scrum master. The product owner has to be able to say no. The product owner has to... I talk about happy ears and most CEOs and senior leaders are-
Nick Muldoon:
Happy ears?
Eric Naiburg:
Yeas. Most CEOs and senior leaders I've worked with have what I call happy ears. They come from one customer or they talk to one person and heard something that-
Dave West:
Do this.
Eric Naiburg:
... that one person might have thought was great. And next thing you know, they're putting all these new requirements on the team. And I've worked in many startups and big companies where, even at IBM, that happened. And the product owner needs to be able to say, "Whoa, hold on. That's a great idea. Let's think about it. And we'll put it on the backlog, we'll think about it later. But let's not distract the team right now from what we're trying to do and what we're trying to achieve." And that's why I say it's both. It's not just on the leader. You're not going to fully change the leader. You're not going to fully change them to not have those exciting moments. And that's what makes them entrepreneurs. That's what makes them who they are.
But the team needs to be able to push back. The leader needs to be accepting of that pushback and the scrum master and the product owner, as well as others on the team, need to be able to have that pushback. I remember very, very early in my career, I worked for a company called Logicworks. We had a data model, a little data modeling tool called Irwin. And I remember sitting in my cube, and the CEO had just come back from a meeting with one client, and comes over, and I was a product manager-
Nick Muldoon:
Eric, do this.
Eric Naiburg:
And starts talking about, we need to go do this now, and blah, blah, blah, blah, blah. It's like, well, hold on. It's like, but blah, blah, blah said they'd buy it. Well one, did you actually talk to the people using it? Or did you talk to somebody way up here who has no idea how they're actually using the tool? Which the answer was talking to CEO to CEO conversation. And just because they'll buy it, will anybody? But you have to be able to have those conversations. You have to build that trust with the leader from the team, and from the team to the leader, to be able to have those pushbacks and be able to say, "That's an interesting idea. We'll take it under consideration for the future, but right now we have a focus. We've got a sprint goal and we're not going to destroy our sprint goal because you got excited about something."
Dave West:
As you can see, Nick, I have a really hard time getting any of my ideas into our organization because they ask things like this. So annoying, Nick. They say, "Okay, that's great. Is that more important than these five things that are currently driving our product goal?" I'm like, "Ugh, what do you mean? I can't have dessert and main course and an appetizer? I have to pick one that's just so not fair." And they said, "Well, we could spin up another team and then that requires investment. It's going to take time." And I'm like, "Oh gosh, don't you hate it when you have intelligent, smart teammates?" It's just hard.
Nick Muldoon:
Dave and I have definitely, so Dave Elkin, my co-founder, he comes from an engineering background and I come from a product background. And we've definitely noticed in the last, again, probably in this timeframe, in the last 18 months, as the team's grown or through a certain inflection point, in the past, we would quite come comfortably have conversations about what about this idea and how about that? And we'd try and tease things out, and we'd tease them out with the team, but there was no expectation that that stuff would get picked up. And then we had few examples where teams would go and take on and think that they needed to look at this stuff and we're like, "Oh, no, no, no, sorry, we should clarify that we just wanted to get a brainstorm or we wanted to get a thought out of our head, and we wanted some perspective on it, but this should absolutely not mean that you should chase it down." And so the language and how we've had to approach things like that, or activities like that, has certainly changed.
Eric Naiburg:
I've seen that a lot lately-
Nick Muldoon:
[inaudible 00:39:50] Inflection point.
Eric Naiburg:
... probably in the last two or so years. And I think maybe because of remote, it's made it even worse, because you don't get all the emotion and things. But I've definitely seen a lot more of that, of, "Well, I'm just," I've been told this doesn't translate, "but I'm just spit balling and I'm just throwing an idea out there just to have a conversation." And because the leader said it, people think it's fact and that they want to do it. And all they were doing is, "Hey, I heard this thing. What do you think?"
Nick Muldoon:
What's your perspective?
Eric Naiburg:
Yeah, exactly. And I think as leaders, we have to be very careful to understand the impact of what we're saying, because we may be thinking of it as, "I'm just throwing it out there for some conversation." Somebody sitting at the desk just heard, "Oh, they want us to go do that." And I've seen that a lot in companies recently, including in ours, where the way something's said or what is said is taken on as we must do this versus, "Hey, here's an idea, something to noodle on it." So you're not alone, Nick.Nick Muldoon:
I love it. Hey, Eric, Oregon, that's a great place to call it. That is, and you have given me, you've both given me a lot to noodle on, so I'd like to say thank you so much from our listeners and from the crew at Easy Agile for joining us today. I really appreciate it. It's been wonderful having you on the podcast.
Dave West:
Well, thank you for inviting us. We're really grateful to be here, and hopefully some of this has made sense, and yeah, let's continue to grow as a community and as a world working in this way, because I think we've got a lot of problems to solve. I think the way we do that is people working effectively in empowered ways. So let's change the world, man.
Nick Muldoon:
I love it. Okay, that's great. Thank you.
- Text Link
Easy Agile Podcast Ep.31 The Release Train Engineer + SAFe Summit 23
"Lieschen's wealth of experience is absolutely incredible! Not only did she provide invaluable advice, but I thoroughly enjoyed our conversation."
In this episode Caitlin Mackie is joined by Lieschen Gargano Sr, Release Train Engineer at Scaled Agile. They delve into the role of the Release Train Engineer, sharing tips and tricks, FLOW activities, lessons learned and how to get started in the role. With SAFe Summit 2023 just around the corner, Lieschen also takes some time to talk about what she’s most excited about for the event and shared some advice for first time attendees.
If Lieschen's expertise and passion have piqued your interest, be sure to explore the Scaled Agile RTE course. It provides comprehensive training, equipping you with the necessary skills and knowledge to excel as an RTE.
We hope you enjoy the episode!
Transcript:
Caitlin Mackie:
Hi there. Welcome to the Easy Agile Podcast. I'm Caitlin, your host for today's episode. At Easy Agile we specialize in developing apps for Atlassian Jira that help your team move from simply doing agile to truly being agile. Our apps have gained recognition and trust from over 160,000 users across top companies worldwide. With our products, teams can transform their flat Jira backlogs into something visually meaningful and easy to understand. Whether it's sprint planning, retrospectives, or PI planning, our apps are designed to foster seamless team alignment.
Before we begin the episode, we would like to say an acknowledgement of country. This is part of our ongoing commitment towards reconciliation. Easy Agile would like to acknowledge the traditional custodians of the land from which we broadcast today. We pay our respects to elders past, present, and emerging, and extend that same respect to all Aboriginal Torres Strait Islander and First Nations people joining us today. Let's jump into today's episode. So today I'm joined by Lieschen Gargano, a senior release train engineer at Scaled Agile. Lieschen is a highly experienced professional when it comes to change management, system design and stakeholder engagement, and has a passion for developing teams and connecting strategy to execution. Lieschen welcome to the Easy Agile Podcast.
Lieschen Gargano:
Thank you. I'm happy to be here.
Caitlin Mackie:
So Lieschen, you are a release train engineer. For our listeners, can you explain a little bit about the role? For anyone that's not familiar, how would you describe a Release Train Engineer?
Lieschen Gargano:
Yeah. I think one of the easiest ways for people to think of a Release Train Engineer is kind of like a coach or scrum master for the art, for the Agile release train. A servant leader facilitating all of those art events, facilitating the processes and process improvements. And really measured in value delivery, and using flow metrics to measure those improvements and support of the arts.
Caitlin Mackie:
So you mentioned flow metrics there. I've heard a lot about this recently and optimizing flow. What are some of those flow activities that a RT is responsible for?
Lieschen Gargano:
I like to look at feature flow and cycle time. So really looking like are we bringing all of our features in progress at once or are we managing our WIP, not just at the team level but at the art level. Are we taking the whole PI to get a feature through the system, or are we able to finish something before we start the next thing? So I look at that a lot and also just are we making and meeting commitments. Those PI objectives that we set, are we in that 80-100% range? A lot of people want full credit, extra credit and to be in the 120, but for us, predictability really means you tried really hard and you stretched, but you also still made and met commitments. So I look at that really closely too.
Caitlin Mackie:
I love that. You mentioned just then quite a lot of different responsibilities that a RTE has. Do you think that there is one in particular that you really need to get right from the start?
Lieschen Gargano:
Oh, as an RTE, I think the biggest thing is building the relationships and intention. As a servant leader, we really are there to help make the art better, to make being on the art enjoyable and productive and flow. So building that trust and those relationships as a servant leader is the first thing. If you get that wrong, no one will help you do the rest.
Caitlin Mackie:
Yeah-
Lieschen Gargano:
And you need a lot of help. You're not doing anything alone as an RTE.
Caitlin Mackie:
Yes. Yeah, for sure. I can definitely imagine that. Let's go a little bit deeper on that servant leadership that you just mentioned. Can you share your approach and what servant leadership means to you?
Lieschen Gargano:
Servant leadership to me is helping people understand the direction, communicating early and often so that they know where you're going. And then not just saying, "how can I help you get there? What can I do?" But saying, "how can we go together?" A lot of coaching and understanding the problem to solve and connecting it to how it benefits the people. Just like we ask them to connect their work to how it benefits the customer. As the RT, they're my customer. How does what I'm asking you to change benefit you? Not changing is always easier than changing even if we don't like our current state. So why is it worth it?
Caitlin Mackie:
I love that. Yeah, always asking the why and being really clear on it. Yeah, I think that's great. I've done some LinkedIn digging of your profile, as you do, had a little bit of a stalk and noticed that you hosted a webinar recently on tips and tricks and lessons learned as an RTE. Can we start with maybe some tips and tricks? What can you share?
Lieschen Gargano:
The first thing I will say is lean on the Scrum master team, and if you're lucky enough to have an Agile coach or another RTE, lean on that team. Your lean Agile Center of Excellence, those people have the expertise. They're also building the relationships. They're there to help you. Don't try to just prove yourself or go it alone, it's not possible. That team is your team for success. So 100% go to them. They're a wealth of knowledge, a wealth of relationships, and the best support.
Caitlin Mackie:
Yeah, I know it's so important to have that support network around you. You just mentioned the Agile Center of Excellence. Maybe for some of our listeners aren't familiar, could you explain what that is?
Lieschen Gargano:
Yeah, so the Lean Agile Center of Excellence can look a few different ways depending on your organization. At our organization, it is the coach, release managers, RTEs and Scrum masters or team coaches. And some larger organizations than ours might have that hub and spoke model of a centralized change leader. And then RTEs and Scrum masters that are in different arts and around the org. And some even have separate laces in different parts of the organization if it's really big. But really they are that community of practice that holds your lean Agile practices and the standards of those practices and talks to each other and debates and evolves them to make sure that it's consistent throughout the org. That the org is getting consistent coaching, consistent guidance, and they're not being told five different things about how to transform. Because again, change and being lean is so hard. If you add too many voices into that coaching, it gets really overwhelming for folks.
Caitlin Mackie:
Yes, 100%. And an Agile transformation is already overwhelming as it is, so you can imagine that laid on top. I suppose speaking, if we explore a little bit around those on an agile transformation journey, at what point would you say it's important that that lean Agile Center of Excellence is formed?
Lieschen Gargano:
Oh, I think it should be in place pretty quick. I mean, we talk about training your leaders, training your experts and then doing safer teams and launching trains. You need that Center of Excellence there from the start so that they can go out to the rest of the org that they can do all that training and they can be there to support people through title changes, role changes. Launching an art can feel very scary to folks. If you don't have that in place beforehand, you're going to have a lot to reel in after the fact.
Caitlin Mackie:
Yeah, I really like that. It's almost having this really solid foundation and unified voice to sort of go forward and support the rest of the org.
Lieschen Gargano:
And it's so great to have consultants support, to have partners come in and help you and to have the right tools, but they need the help of people inside. They need that lean Agile Center of Excellence of employees inside the company to help you be successful. As an RTE, you need your team. Anybody, any tool, any people trying to do a change, a transformation are going to need that Center of Excellence because all those parts, that's what makes the whole.
Caitlin Mackie:
Yeah, yeah, definitely. So you mentioned as an RTE, a big tip or trick is to rely on that lean Agile Center of Excellence. What do you think has been your biggest lesson learned as an RT?
Lieschen Gargano:
There are a few things that have been particularly difficult for me. One of them is that I don't like to say no and not in that I take on too much or whatever, but more in that if someone has passion for something, I want them to be able to take it on. I want them to be able to move forward with it. And there are times where we really have to say it's too much change. It's too much for this group to manage. In particular, the Scrum Masters and RTEs people come to us for a lot of things and they need that consistency from us, and they need predictability in a change to feel like we know where they're going and if we introduce too many things or if we try to hold too many things at once, it's easy for us to forget about it later or drop something else. So learning when and how to say no, again not necessarily in that capacity way, but just in the width of change, if that makes sense.
Caitlin Mackie:
Yeah, definitely. I think that what you just said there, learning how and when to say no. I think that's not even exclusive to the RTE role as well. I think that's an amazing piece of advice for anyone listening and to share across our audiences, because I know it's definitely something I struggle with as well. So that's my takeaway from this is to, okay, I'm going to constantly imagine like 'no Lieschen told me to when and how to say no', and just focus on that. So yeah, I think that's a great piece of advice. What was your journey like to an RTE? I know we caught up last week and I got a little sneak preview into this, and I know it wasn't straightforward, so if you can share a little bit about that, that would be great.
Lieschen Gargano:
Yeah. I actually started in conflict resolution. I worked in public private reconciliation doing a lot of natural resources facilitation, so hundreds of people, governments, companies, private landowners, residents, trying to bring all those people together to get to consensus or at least to build relationships that allow them to move forward. So really strong foundation and facilitation in particular, and just day-to-day conflict. When we say conflict, we get so worried, 'oh, I don't do conflict', well conflict's everything all the time. It's all the disagreements we need to succeed in life. So that gave me a great foundation when I became a scrum master, and I did that for a few years working with development teams. One of my favorite teams was our infrastructure team, 10 foot pole because no one wanted to touch their work or the 10 foot pole, and I learned so much there and eventually became a coach and started doing more strategic planning and coaching parts of the organization that weren't used to being on arts. Marketing and other groups, which helped me transition to Scaled Agile, where I started working with our CMO and as he grew the marketing team, helping coach that marketing group into an agile way of working, a safe way of working, before actually becoming a product owner, because I loved organizing around value, and I loved those different topics that we were working on internally.
And one of the people I work with at Scale Agile said, "well, help us develop the product then for everybody else". So I did that for a little while, which gave me so much power in that learning how to say no and prioritize and coaching people to decisions is one thing, but as the product owner, I had to practice being where the buck stopped. There are five right decisions, just make one so that people are unblocked, and that prepared me really well for transitioning into RT.
Caitlin Mackie:
Yeah. You have such a wealth of experience there across so many different roles, and you can really see that each of those key roles have taught you something valuable that you can take into this RTE role. So I think that's amazing. It's so cool to see that even though it's not this straightforward linear journey, there's all these parts that there's traits within each that ladder up to helping you succeed as an RT. So I think that's really cool.
Lieschen Gargano:
And I know people are afraid to make some of those lateral moves sometimes, but the skills that you can build might just be that thing that gets you other open doors that you didn't even think about.
Caitlin Mackie:
Yeah. Yeah. I absolutely love that. Yeah, just embrace every opportunity for what it may be, what it may not be. You don't know until you give it a shot. So I think, yeah, I love that. I think that's really great advice. So everything we've spoken about in regards to being a Release Train Engineer may have really hit the spot for some of our listeners. How does someone get there? Were there certifications, courses? What's the process that way?
Lieschen Gargano:
Another thing I probably did backwards. I started with a scrum master cert and then actually ended up getting a SPC certification through Scaled Agile when I was a coach. Because I was a coach before I was an RTE, and I learned about so many other parts of the business that way. But then to become an actual RTE, taking the safe RTE course, but then actually there's a community of RTEs... Which we didn't really talk about this, but being an RTE is a lonely thing. I said earlier, if you're lucky to have another RTE, this is a lonely role. You're really kind of on your own. So not just getting that cert, but being part of that community and being able to send people messages and ask them crazy questions was part of my certification process, but also just community building to where I could feel like I had the connections and competence. So yeah, I found all of them similar to holding each of the roles, also getting that certification, just another tool in the tool belt.
Caitlin Mackie:
Yeah, for sure. I don't want to touch on something you said there about an RTE being sometimes quite a lonely role. What do you think makes it lonely?
Lieschen Gargano:
It's a role that a lot of people have strong opinions about what they need and what success looks like based on where they are in the organization. And there are usually few of you, and even if you're in a large organization with many, you're with your art, you're very focused on your section, and so having all of those pulls and expectations and not having anyone who understands what that feels like just makes it kind of lonely. Now that we have two RTEs and a coach at Scaled Agile, it makes a big difference for me because they are right there in it with me and it's very helpful.
Caitlin Mackie:
Yeah. You can see in that scenario why that community of RTEs is like you said, so important to lean on them as well. Yeah.
Lieschen Gargano:
I find even just connecting to RT's outside our organization too. I grabbed beers with one a couple weeks ago. Those little things, even if you can find that person, meet them at a summit, meet them out in the wild, find them on LinkedIn and just say, "Hey, we live in the same area. We have the same role". It can go a long way because it may seem weird to reach out like that, but they probably are looking for that connection too.
Caitlin Mackie:
Thank you so much for sharing. And for any of our listeners, I might pop some links to any certifications and some scout Agile courses. I'll pop that in our episode notes, so feel free to check those out. You mentioned about connecting with other RTs and meeting at summits, which is a really nice segue to the next part of our conversation. Just around the corner is the 2023 Safe Summit and we're heading to Nashville Music City. What can we expect from Safe Summit? What are you looking forward to?
Lieschen Gargano:
Well, what I'm most looking forward to is that I am putting together an RTE breakfast. So all RTEs are welcome, or even if you're a solution train engineer or you do the role of an RTE with a different title. I'm really excited to meet with those folks over breakfast and just chat it out. And my goal with that really is to have people to connect with so that as we go through the rest of the summit, listening to the talks that we have people enroll, that we can check back in with over drinks and stuff on the later days and say, 'oh, what do you think? How might that work?' So that's what I'm most looking forward to.
Caitlin Mackie:
Amazing.
Lieschen Gargano:
But obviously there are going to be some great talks and the product labs are always really fun. We get to play with the product together.
Caitlin Mackie:
Yeah, cool. Tell me a little bit about the product labs, what's involved in that?
Lieschen Gargano:
The product team puts it together and they have computers set up and you can bring your own and they talk through some of the new releases or things they're working on and help you log into it and use it in your context, but also try to get some feedback on how it works or how you might use it in your organization. So it's a nice two-way street. It's sort of, 'I need this, how might I do it?' And then them saying, 'well, why don't you try and let me see how it works and how we should change it based on how you interact with it'. So it's just really fun. It feels really practical because it's so hands on.
Caitlin Mackie:
Yeah, amazing. I love that. I'm definitely going to have to try and come along and suss that out. It sounds really great. Where do you hope or where do you think we'll see a lot of conversations focused at this year's Safe Summit?
Lieschen Gargano:
At Safe Summit I think the conversations will be really focused on just the day-to-day of Safe. We have new topics that come up. We obviously have new ideas that are going to be presented. But every time I go to one of these, it really is the connecting one-on-one to say, here's where I'm stuck, here's what I'm trying to learn. So we'll hear a lot about Flow, we'll hear about Team Topologies, but we'll also hear those 'I'm just getting started and we're stuck, we have change fatigue. We don't know if our arts are set up correctly'. A lot of those classic conversations that are just really impactful and why people come together.
Caitlin Mackie:
Yeah, definitely. Yeah, I love that. Creating these spaces for people to bond over shared experiences and problems they're facing or wins they're seeing and sharing them. I think that's where these events are amazing for creating that kind of environment. Lieschen, this is my very first Safe Summit. I haven't been to one before and I'm really excited. What advice would you have for first time attendees, returning attendees, what's the way to get the most out of Safe Summit?
Lieschen Gargano:
If you're attending with other people from your organization, the best thing is to split up so you can cover more ground and then come back together and share. The second advice is find people with a similar role as you, because again, you can do that same thing with those folks and split up and then meet up again and try to talk about it in your context. It's great to do that at the parties too, because we throw great parties, but that's the best because no matter what room you end up in, what talk you end up at, you're going to get a great nugget. But where it really sinks in for me is talking with someone else about what I heard and then thinking about, 'okay what does that mean?', when I go home.
Caitlin Mackie:
Amazing, great advice Lieschen. If anyone listening happens to also be attending Safe Summit and they see Lieschen on the floor or myself, make sure you say hello, and if you've got any questions for Lieschen about the podcast episode, I'm sure she'll be more than happy to answer and engage in a great conversation. And anyone looking to get advice around the RTE role, make sure you find her and have a chat. Lieschen I'm really excited to meet in person. We've done this podcast with yourself in the States, myself in Australia, so I'm excited to connect over in your world. And yeah, really thank you so much for your time. I hope you enjoyed the episode. I know, I sure did.
Lieschen Gargano:
I did. Thank you.
Caitlin Mackie:
Thanks, Lieschen.
- Text Link
Easy Agile Podcast Ep.30 Aligned and thriving: The power of team alignment
"Every time I meet with Tony, I'm always amazed by his energy and authenticity. In this conversation, that really shone through."
In this episode Hayley Rodd - Head of Partnerships at Easy Agile, is joined by Tony Camacho - Technical Director Enterprise Agility at Adaptavist. They are delving into the highly discussed subject of team alignment, discussing what it means to have synchronized goals, cross-functional collaboration, and a shared agile mindset.
They also cover the fundamental building blocks to get right on your journey to team alignment, like the power of listening and embracing mistakes as learning opportunities, stressing the importance of following through on retrospective action items + so much more.
We hope you enjoy the episode!
Share your thoughts and questions on Twitter using the #easyagilepodcast and make sure to tag @EasyAgile.
Transcript:
Hayley Rodd:
Here at Easy Agile, we would like to say an acknowledgement of country. This is part of our ongoing commitment to reconciliation. Easy Agile would like to acknowledge the traditional custodians of the land from which we broadcast and meet you today. The people of the Darova-speaking country. We pay our respects to elders past, present, and emerging, and extend the same respect to all Aboriginal, Torres State Islander and First Nations people listening in today. Hi all and welcome to the Easy Agile Podcast. My name is Hayley. Here's a little about us here at Easy Agile. So we make apps for Atlassian's Jira. Our applications are available on Atlassian's marketplace and are trusted by more than 160,000 users from leading companies worldwide. Our products help turn teams flat Jira backlog into something more visually meaningful and easy to understand.
From sprint planning, retrospectives and PI planning our ups are great for team alignment. Speaking of team alignment, this is what this episode is all about. Today I'm joined by Tony Camacho. Tony is the technical director of Enterprise Agility for Aligned Agility, which is part of the Adaptiveness group. I've met Tony a few times during my time here at Easy Agile and have learned that he's one of the most generous people along with being funny and a clever human being who is incredibly knowledgeable about Jira and a bunch of other agile related topics. It's really wonderful to have Tony on the podcast today.
Hey, everyone, we've got the wonderful Tony Camacho on the podcast today. This is our first time recording from our Easy Agile Sydney office, which is super cool. Tony, I'm not sure if you know, but Easy Agile is based out of a place called Wollongong, which is just south of Sydney. But we've got a Sydney office because we've hired a bunch of Sydney team members recently who wanted a place to come and hang out with each other. So we created this space, but it's 7:00 AM in the morning, so I'm all alone right now. That's how much I love you. So Tony, let's get started on the questions. Team alignment. What does it mean for a team to actually be aligned?
Tony Camacho:
So for us in an agile space that we're having, it's a collective understanding, a synchronization of your team members towards goals, principles, your practices that you're going in. Even more so I would even go down to the point of cadence, you would have those synchronizes. So it's a matter to be consistent with your agile principles and values, your mindset, your shared goals and vision, your synchronized work practices, DevOps, [inaudible 00:02:44], how we're going to put this out. Cross-functional collaboration between the teams, getting your tea shaped partners/teammates shining at that moment, learning from each other, roles, responsibilities things of that type. That's what it means to me. It really means.
It's all about human beings and at that point, having everybody aligning and working to our common goal, that objective that we want to do for the business partner. There's the gold that we're all after as a team. Does that make sense for you guys? We have the same objectives for this initiative and our practices. And finally for me, which I know this is not typically is we're coming to an agreement on the tools we're going to use and how we're going to use them and have a system source record where we know where we can get our troops, our dependencies, find out which teams do have capacity and move forward from there. That would be my overall definition of an agile team.
Hayley Rodd:
Wow.
Tony Camacho:
And teams.
Hayley Rodd:
You've had lots of experience over the years. I guess where my mind goes when you say all those really wonderful things about team alignment is that in my experience when team alignment is when people get it right, it's super great. When people get it wrong, it's really hard. And I actually think it's pretty hard to get team alignment right. You got to really work at it. What's your experience in that?
Tony Camacho:
To me it's like it can be a bad marriage or a great marriage, but it needs work. As we know, all relationships need work. We're human beings, we're not the same. Each one of us brings something to the table of value. So let me give you one example that I've lived with on a team. I'm an extrovert by nature, and I'm a developer, an engineer and typically that is not two skill sets that you hear together. So I've had to learn that when I'm working with my teammates that happen to be sometimes introverts slow down, listen, wait. They've also had to try to learn to respond faster because as an extrovert, if I ask you a question, all of a sudden I'm looking at you, I'm not getting a response, I'm thinking you're not understanding the question. I rephrase the question and now you're in a deficit to two questions.
And now I'm even worse because now I'm like, "Hayley isn't understanding me. What's happening here? Let me rephrase it again." And it can easily fall apart. What I have seen when teams aren't in alignment is that the team isn't a team any longer. It's miserable to go to the team. It's miserable to come into work, when the team is truly aligned, you're rocking and rolling. It's a feeling like you've never had. It's hard to explain to people that when you see the team, because you know it when it's working and you obviously know when it's not working, you're starting to miss deadlines. Integrations aren't happening on time. You don't have a single source of truth. You start having people explaining the same thing in two, three different matters, different priorities. We're not working from the same hymnal. The thing that I took from my... I'm an SPC, so as an instructor, the one thing I always try to explain to everybody, you may have the best of everything out there, but that's not necessarily mean it's going to work together.
So you have to have that type of understanding, how we're going to work together, what is our priorities, what's the tool sets we're going to have and what is our values as a human beings to this team if that... I'm hoping that helps describe some of the things that I've seen that have gone really bad. I have seen it at, I can share a customer that I have seen it gone, but we started off with good intentions. It's a financial institution in the United States and they were trying to make the jump to mobile applications. And at first we were on the same page as a team, but they decided that they didn't believe that cadence was required to be the same across the board. They didn't believe that we could use the same one tool set, we could use multiple different tool sets.
They had spreadsheets flowing all over the place. And what was happening was we lost trust. We were redoing work, there was ambiguity everywhere. We were misaligned and we started paying for it because our customers started complaining. They could see it in the quality of the work. One team had one schema, one background, one type of... You could see the difference when they integrated, it seemed like it was two applications being put out there mashed together. And when you're misaligned, that comes through very, very quickly in your work. There's a saying that we have here. There's a scrum master, I know her name was Sophia Chaley, one of the best I ever met. And what she will always tell people is what a team delivers is what the team is doing is learning. It's building knowledge, it's expressed as code. When we're misaligned, we're learning different things and we're expressing it differently in the code, if that makes sense.
Hayley Rodd:
Like thinking about the fundamental building blocks of team alignment, is there something that a team really needs to get right to be successful at alignment? And what is that in your mind?
Tony Camacho:
Oh, that is for sure. They had to get that right. First of all, the size of the team.
Hayley Rodd:
Yeah, okay.
Tony Camacho:
Human beings, and I'm not referring back... Going back to say for our scrum practices, I am a CSM. I do know they recommend 8 to 13 people. My best teams have been typically a little bit larger than that. But we had to have the same agreed to the size of the team where it didn't became, didn't become too large where we were over running each other and we weren't listening to each other. We had to understand our goals. We all had the same goals. We used to practice this by, when I worked at Microsoft, we used to have what we used to call our elevator speech. And we would stop somebody and I would go, we're working on this. Watch your elevator speech for this. And if your elevator speech wasn't... It wasn't meant that it had to be in sync with mines, but if I didn't understand it, we had a problem.
Or if it was a different goal where I'm looking at you going, but we're building a Volkswagen, but you're describing to me a Lamborghini, we have a problem. And those were the type of things that we also had to have to make sure that we had the right... Same practices and the tools. That's where I find Easy Agile exceeds. I mean it just exceeds, it meets above the market. It's transparent and it shows everything in front of you right there for me. So when we had the same tool and we were having the same cadence and we could see our dependencies and we could see what I had to deliver for somebody else or somebody had to deliver it for me, that was the types of things we had. We had to have respect. Somebody seems to always forget that we always had to have respect for each other.
We had to embrace the same values of collaboration, adaptability, transparency. The practices that we all know, but somehow we seem to forget when we get into a place where we are not aligned and if you respect my ideas and I respect yours and we're working together, we do not have to agree. But that respect will drive us a long way towards getting to that project vision that we want. And we're trying to meet the customer's needs. And those are the type of things that we needed. We needed leadership. Leadership, I can't say, and if you notice I'm not using the word management, leadership is where you're putting yourself out there in a situation where it can go bad for you as a person, as that leader, trying to make sure that we're making the right choices empowering the people and making them very clear what they can make decisions on and they can't. And it sounds so simple when I talk to you like this, but every time I've had to do some type of transformation, the baggage that sometimes we bring as human beings, the fears, the lack of trust that we have, that's where the scrum masters of product owners come in. And then you need something to make sure that you're having that vision to communicate that vision across. As I mentioned before, some of the tool sets that we have out there. Is that making sense for you at all?
Hayley Rodd:
Yeah, it really does. It's really resonating with me. I think when you talk about coming together as a team and putting together a set of values and a vision, it seems so much like a a "duh" moment. It's like, of course you would do that as a team, but I think at the end of the day as teams, we get in the daily business as usual and we think, I don't have time to get together as a team and set that vision because I've got to do X, Y, and Z, that's due next week. But I think it's one of those fundamental building blocks that really sets you up for success to do X, Y, Z quicker down the track. So that's what I've taken away from that.
Tony Camacho:
And I would agree with you. And you came up with a perfect example because a lot of people do that. I have ABC to do for next week, daily. I don't have time. And the problem is that if they would suddenly realize, and it does become apparent to your practices. So once you agree on your practices, your daily standups, if you're doing that, your retros at the end of your sprints and moving forward, once the person feels that they have that respect for you and they're not fearful, they can share that with you, "Hayley, I'm having a problem. I'm having way too much work. I don't know if I am going to be of value here. Or Do you really need me?" "Yes Tony, I do need you, we're going to discuss this and let's discuss your A, B, C and see how I can help you." And they suddenly realized they're not on an island alone. Developers by nature being introverted, we have to break that habit. We have to be able to share. And it's funny, I'm not saying share my lunch, fine, sure, let's share our lunch, but share the workload.
The one thing that I always try to mention to teams, and again that's... I'm sorry, but I do believe in Easy Agile, using this tool. That's where easy Agile also to me makes it apparent. A story belongs to a team, not to a person. And once you know that you suddenly realize, I'm not alone. I'm here working as part of a bigger thing. And most human beings want to be part of a bigger thing. You suddenly realize that it's almost like the baseball metaphor that I use for teams. And I know the market is not baseball, but I think it would apply for other sports, be cricket or sports like that. When I'm batting, it's me against everybody. When I'm on the field, it's us against... I prefer being with the us. And generally that's where things like that, let's do that.
Also, when you're working with more people as a team, there's things that happened there. You minimize the project risk, which I hate using the word project. It should be initiative. It's long living. You're usually a much more adaptable. I don't know all the answers. So when I worked with you, Hayley, and you showed with me some things there, you're one of the most humble people I've met, and I loved it. But when you walked through, you walked me through the tool, it became very apparent, you know it, you feel it, you love it, it's part of you. And that to me is invigorating. It's energy. Who wouldn't want to work with somebody like you? Why not? Let's do this. Right?
Hayley Rodd:
Thank you Tony. I guess one of the things that I wanted to touch on is when you're in a team and you're coming together as a team, you're working on something, how does an individual who seeks recognition for what they're doing, how do they get that? Or how do you leave that? How do you put that ego aside and say, "I'm doing something as a team to the better of the team?" Have you ever come across that or considered that? I'm interested in your thoughts.
Tony Camacho:
So the people that I felt that needed to have that typically how I... Yes, that's a great question because I'm thinking specifically. There was one, a scrum master that I thought that did it the most amazing way ever. Basically she would call out the ideas even if it wasn't that person's, yeah. I feel that Hayley is... You're not having a good day, Hayley. You're not having a good day. And I know you are not getting used to doing, working in the scrum team. It's new to you and everything else. And what she did typically was in front of everybody would be, and it wasn't even your idea sometimes. And she would just say, and Hayley came up with this wonderful idea that's going to save us something, move us forward. Hayley said this to me, it made us think as a team. And we went around it, we talked and we did it.
And that person always usually would be like, "Wow, I got credit for something. Good scrum-masters will see that. Or good product owners will point that out." The other way that I've done it was using something like Easy Agile. It's a great tool to use, believe it or not. I would back off, I'm a developer, but I also played the role of Scrum masters for years. I would step back and I would let one of my teammates run it, hear their voice, feel empowered. It's amazing when you can have people feel empowered because what you're all talking about, there really is about a lack of trust, a lack of psychological safety. And it's for us to be an aligned team, you have to have trust there and you have to break down the fear of judgment. So the other thing that one time happened with a scrum master that I thought was wonderful was is that again against Sophia Chaley, chief stood in front of her room when there was this a bad sprint.
The sprint didn't end well. And she stood up in front of everybody and she basically went, "Sometimes you win, sometimes you learn. This was a learning sprint." She pulled up Easy Agile, she was using at a time, pulled it up, showed the things that didn't work out the way they thought they were going to work out. And she said, these are the actions we're going to take to improve this. And then when somebody who was in management, again not using the term leadership, now I'm using the term management on purpose, was looking to assign blame. Her response was, not screaming, not raising her voice. Her response was, if we need to get rid of somebody or blame somebody, blame me. But I'm here to solve the problem. Let's move forward.
Hayley Rodd:
Wow.
Tony Camacho:
She wouldn't tell. And that was to me was one of the most outstanding moments I've ever seen. And she was at that point actually using Easy Agile that wasn't a financial institution in the United States. I would let you know that teachers use it, figure it out. And she basically showed the board and just went through everything and did that. That was leadership. That was leadership. And generally your teams will follow leadership and they will suddenly step up and you'll see that that's what people who want to stand up. Now, not everybody wants to do that. Some people want to just be team members and that's okay. That is perfectly okay, but the thing that's not okay is that if they don't have trust, right? And to me, that's the biggest thing. When you have people who are resisting change or siloed in their world, they suddenly realize if you can get them to open up it's really, they're just telling you, I don't feel safe.
I've been doing this all my life. I'm great at it and now you're asking me to do this. And you need to somehow get them to get the feel that they are bringing something of value. They are helping you move forward. And you're meeting them halfway if you have to. But yeah, that's the biggest problem I've ever seen that we've always, it always comes down to the human being in that. The rest of it, you can always come, you can always change that. But there's some of the things that you also have to do. I think that some people run into Hayley that I think me and you live in our world as we're moving up is sometimes we are, there's an ambiguity of the things that we have to do. And I've seen you do that, people in our roles will have suddenly, even if it isn't part of our role, will take it on and we have to learn. That's it. But yes.
Hayley Rodd:
Yeah, I think that, yeah, it's so true that the [inaudible 00:19:23] the psychological safety needs to be there. And I think back to so many teams that I've been a part of that it isn't there. So you have to feel like you got to lay your mark or put your mark on something and show your value. Because if you're not showing your value, then you get questioned. And so I think that that's such a common thing that I see in teams and it actually creates, not a camaraderie, but a competition between teammates and it breeds the wrong environment. So it's just really interesting. One thing that I did want to touch on that you spoke a lot about a couple of questions ago was respect and making sure that teams have respect for each other. How does a team member show respect for their teammates? What are some really good examples of respect and how can we display it or embody it or enact on it as team members?
Tony Camacho:
So let me show you a lack of respect right now. Yeah. Hayley, we're talking about this.
Hayley Rodd:
Looking off camera, avoiding me. Yeah.
Tony Camacho:
One of the main things was to really to learn to listen. Sit down, believe it or not, I found the best thing is sometimes taking a deep breath, listening, not responding, recognizing what that person may be feeling and going through at that moment because it's hard what we do. It's half art and it's half science. Let them learn that making a mistake is not a failure, it's a learning moment. Have that discussion there. Take their concerns real. So it's funny because you just made me think of something. That's one thing where I could show respect to my teammates would be as a scrum master, if I was a scrum master, hold effective retros. Really listen to what they're saying in the retros, report back on the things that you said you're going to improve in the retros. So we said these are the three things we're going to improve on or these are things that are assigned to me.
Make it real. Make it a story. Show it on the board and say, "This is where we're going. This is what's happening. This is what I'm blocked by. Can somebody help me?" But I am working this for you. Get them, really be sincere. I don't mean buying pizza or bring a lot of scrum masters will bring pizza and donuts to the office. No, it's make their lives really better. Be that advocate up for them. And if you're a teammate, be an advocate for each other and be sincere. Have the bravery to stand up and say that's not a fair assessment. But the biggest thing is to really listen. Because a lot of times when somebody's saying something to me, I'll make it personal. Me, I have sometimes have, I know I'm feeling uncomfortable, but I cannot explain why. And just having you there, looking at me and talking and going through it, I suddenly realize it may have been something different and I want to hear your ideas.
But I would have to, if I wanted to show myself to help that teammate, I also got to make myself vulnerable. If you're coming to me, I should share, but I should active listen, right? And really I respect your different perspective. It's okay. We all have different perspectives. Problem I find is that in ourworld, that we're moving so fast sometimes we don't stop to listen. We lack patience. We're moving too fast. So I'll share one for you that I'll be sincere. I had something medically came up and I was being a little abrasive with the team. So finally I called a meeting with our team and they saw me cry. I was okay with it. I was like, "I had no reason to be like this. You guys were showing me love, you were showing me respect, you're backing me up, helping me with my work. And I was still being utterly terrible."
And it hurt me. It hurt that I was doing that, but I needed them to see me and I needed them to listen to me, give me that second to get it off my chest. And in the end I started crying. A 60-year-old man crying in a meeting going, "I shouldn't have done that to you. That was wrong." And it wasn't contrived. Some of the people there were 20 year old people on my team and they were in tears. And it was because they felt, they told me after this, they felt my pain that I was in, because I wanted to help. It's the most frustrating thing. To your point before, how do I feel? I wanted to help. I wanted to be there and I couldn't. Physically, I wasn't there. My mind was all over the place and I was being rude, being blunt, and I could use some other terms. Please don't. But that's really the main thing for me was it's really simple what we do. I just listen and just show respect for other people. And sometimes we forget.
Hayley Rodd:
I think that so many of the messages that you are talking about are not just for developer teams, they're for every team, every team in every walk of life. I think that they're just so fundamental to successful human relationships, whether it be personal or professional, I think so. I think there's just so many good messages. One thing that I wanted to touch on was that you're talking about active listening and when you think back on your career, and maybe this is totally off script, but when you think back on your career, how have you become a better active listener over the years? How have you improved that skill? As you said, you're an extrovert, you want to get in there, you want to fix the problem. How do you get better at that?
Tony Camacho:
I had some very, very smart people that put up with me, listened to me, and then had the courage to approach me after and teach me and teach me and didn't embarrass me in front of anybody. Did it in a manner that they said, "Do you think maybe this could have been better Tony?" As I said, I'm 61 and still I'm an extrovert and I still have high energy and I still make mistakes. As I tell everybody, every day I wake up, I make a mistake, I just got up. But I could have stayed in bed longer. But also the thing that I've learned, and it's just by the nature of getting older, it's not the age part of it. It was watching people come up trying to do the same thing I did that I failed at and I was an instructor for Microsoft for a long time.
And seeing how, because to me seeing how a person's minds works is amazing. So what happens is I'll just... You know what I tried that, it didn't work for me, but I will say after class with you to show it to me again because maybe you solved it. I'm not that arrogant. And the nature of our business is that I find this, that the more you learn, the more you realize how little you know. That was the biggest thing that opened my eyes. Now it's like, oh my Lord. You meet somebody like John Kern, you meet somebody like Sophia Chaley who come from different perspectives, brilliant people, and you suddenly see that they happen to do things slightly different and you just watch them and you're like, "Wow." And the thing that I love about our job, which I guess you must love, everywhere we go, every team we work with, it's different. It's different.
Everybody always asks me, how do you do that. And I'll tell them, "Look, I will share with you the ways I did it. I have a varied background. I've always been consulting." I've done the ATM space, I did for space enabled warfare, I've done for health industry, everyone's been different. Someone from government regulation, but most of the time different human beings. So I have a saying, I've earned every scar in my back, their minds. I've learned people, you have to give people the chance to have their scars. Yes, it may be pain, I'm not saying fail, I won't let them fail. But sometimes people want to do something. So that's the way I would do it. Let them do it. And I just watched and learned that what happened was as I went in and the more I learned and I suddenly realized how little I know, I was like, I started with FORTRAN, I used to work in the dead 28.
And then you start working your way up and you start realizing, "Wow, I don't know as much as I thought I know." And I had the luck of running into working at Microsoft and having the pleasure of meeting Bill Gates. Now, no matter what you say about Bill Gates, because a lot of people do say some crazy things and some of them may be true or may not. But the one thing you can't take away from him is you go into a room with him and you suddenly see how he puts all these ideas together and comes up with a bigger picture. You suddenly realize, "Wow, people tell me I'm really smart, not that smart." And then you learn, humility is a good thing.
Hayley Rodd:
Yeah, I think humility is just such an important asset to have and to try and grow on because leaving your ego at the door and being open to learn from other people and not think that everything is definitely a life lesson that sometimes you need to go through. And some people go through it and still don't take away the life lesson. So yeah, I think it's so interesting. I guess we don't have too much longer left, but I wanted to touch on thinking about it from an ROI perspective. How important is team alignment from a return on investment? What do you gain from a business perspective when you have an aligned team?
Tony Camacho:
So I'm going to use a term that I dislike and Hayley, you can smack me the next time we meet. But I'm trying to use it as, I don't because it's effective resource utilization, right? But I'm not referring to human beings to that point because it may be human beings. The problem is that's a large market. But as Agile people I won't refer to you as a resource, I refer to you as a fellow human being, you are a partner on my team. You're my teammate. You're not a piece of wood. But that is unfortunately a term that is used. And we will have effective utilization, we'll have common goals across our organization. If you're using any of the message less, bad, safe, pick it, you start focusing on your value streams. You should have improved product quality because we have the same cadence. We're putting things out there and we're having the same views there.
You'll have I think better customer satisfaction and loyalty. They start seeing your product quality going up, being consistent, look and feel and hopefully you are delivering what they want. When you have your teams aligned, you're much more adaptable. Hayley, your team's got capacity? I don't. We don't have capacity to do this. Do you have capacity? Yes I do. Or we find someone or we break it down together and we present an idea to our partners. That's the things I like and I think in the end you have reduced risks at that point.
Also, I think that the thing that they have in is that it's indirect, but nobody knows about. Nobody really talks about it is that if I was upper management C-suite, when we start doing this and we're having the teams aligned, first of all, your teams become safer, your teams feel more comfortable, they're working with the same people. They start becoming very effective and they start producing ideas. They're the knowledge workers. They know this better than anybody else and then they feel empowered to share ideas. The places that I thought that I had the best teams was once they asked... Well, and I got it, I don't know how, I was running a train and they asked to talk to the CTO and all they wanted to do was to talk to the CTO and make that person human. They asked her what she did in a previous job. Amazing. She worked as a factory worker and she also worked in construction. She used to drive, one of the things, nobody would've believed this. And what happened was they started sharing ideas with her and she embraced them. You know what that did to the team, the teams all, they were like, now that's out there, that's ours. Look at that. That was ours. I mean ownership, it's unbelievable.
And unfortunately we are working on a capitalist market, which is fine, that's who we are. I mean we're in IT, it's a return on investment. Return on investment in the end, you start seeing much more efficient use of your money, much more efficient use of your dollars. Also, I would also imagine for the people above who are in the C-suite, they suddenly realize that the organization is going in the same direction. I think psychologically they feel that we now I have this team behind me pushing towards the same goal where a lot of times, every time I do an agile transformation, the first thing we always hear is we know they're working. We don't know what they're working on. And that's where something like Easy Agile bridges that and then you can use that information to go further. And that's wonderful because then at that point, everybody's on the same page. So you're a team now all the way from top to bottom. As opposed to I'm going to my team at work and that's it. So it's just really about return on investment, making sure that we are hitting our customers with everything we got. And I don't mean in a bad way, but we're delivering for our customers with everything we got. It's now efficiency, right? And that's it. That's about it.
Hayley Rodd:
Yeah, that's so powerful. I think it sort of nicely ties everything together because we've talked about a lot of things in the last half hour or so. And I think that at the end of the day, if you can get team alignment, just as you said, there's this ROI that can really shine through and it's a powerful thing for the whole organization to get right and to see the fruits of that work. So one last thing. Can you share your perspective on PI planning? I know you just mentioned safe a little bit for being the initial launchpad for team alignment.
Tony Camacho:
I love it. You have everybody in the room, you get to meet the people, you start making those connections to people. You start seeing them as human beings, not as this email or this text that you're sending across that you're going through there. So could I share one real experience from that? That's a PI planning house.
Hayley Rodd:
Please
Tony Camacho:
Do. So when I was working at Microsoft, I work for product quality online, which I know right now, considering the problems Microsoft is having, you're pretty much going now, "You suck Tony."
Hayley Rodd:
Never.
Tony Camacho:
No, we had our people distributed all over the world. And what was happening was that when I would talk to my short teams, I would ask them, and I was being facetious at a point because I just couldn't get the true answer was I would ask him, can you build the Twin Towers by tomorrow? And the answer would inadvertently be yes. Next day would come. Obviously you can't do the twin towers overnight. Ask them again, will you get it by next week? The answer would be yes. And they were feel for all of that. So when we had the PI planning, we did.
Microsoft went, got a hotel room in Seattle, a hotel room, a hotel in Seattle, rang our offshore teams. And then when they got to see me in person, they suddenly realized that I wasn't telling them I need the twin towers by tomorrow. I really wanted them to tell me when they could get me the twin towers. And I would defend it because they saw me right there in PI planning, defending, saying, "No, this is not possible." And when they saw me doing that, suddenly it was like the sky's open, sun's came through and now I was getting true answers. And what happened was it gave him an opportunity. And I realized that guys, you keep hearing me as sermon. It's always about the human beings, it's about those connections. It's about seeing the people. It's hard. It's two days of a lot of work. But once you get that work done, you come out of there a line, sharp direction. We know what our north is, now, do we know exactly where our true north is? As an agile team, we shouldn't, right? We should be refining it as we get there.
Find out exactly. But we know more or less where the direction is. We more or less know we're all on the same page. We all know that what we have to deliver to make this work out what other people have to deliver for us or we have to deliver for other people. So we suddenly feel part of something bigger. Bigger, right? We are now talking to the, if you're a developer or an engineer, software engineer, you're starting to see the power brokers and why they're doing this. You get the chance to ask them questions. What more could you ask for, right? I finally get to see the people who are making the decisions and I can ask them why. And they can tell me what the business value is and I can make the argument to them that maybe I don't think that's as much business value or we need to fix these things first before we can get that right and move our way on. What more could I ask for? I have an opportunity to make my case and I get to see the other people I'm working with. It becomes, when you're dealing with 125 people and you're on a train, you will become family.
We spend more hours sometimes with these people than we do with our family members at times. And it also gives you a sense of... Besides trust, a sense of a safety. You know it's not just you, it's all of us. So the saying that usually I see that the better executive say, I heard that in one PI planning, you fail, I fail. I fail, you fail. My job is to keep you employed. Your job is to keep me employed and to keep this company together. It's synergy, right? So it's amazing.
Hayley Rodd:
Beautiful.
Tony Camacho:
Yeah, I know. I'm all about the human. Sorry.
Hayley Rodd:
No, I am right there with you. I'm so glad that we got to have this conversation. We've talked a lot over the little while and every time we meet, I'm flabbergasted by your energy and your authenticity. And I think that this conversation that really shown true, so thank you Tony for taking the time to be with us. I'm going to say goodbye to all our listeners. I'm going to say another big thank you to Tony. So Tony is part of aligned agility and that is part of The Adaptivist Group. And yeah, thanks Tony for being here with us and thank you for everyone who has tuned in and listened to this episode of the Easy Agile Podcast. Thank you.