Scrum Master as coach

Scrum isn’t new, but the questions teams are asking about it are evolving. In this episode, Brian and Cort Sharp compare notes on what they're hearing in class, in the community, and behind the scenes.

Overview

In this episode of the Agile Mentors Podcast, Brian Milner welcomes Mountain Goat Software colleague and community manager Cort Sharp for a real-time pulse check on what’s top-of-mind for Scrum teams today.

From overloaded calendars to misunderstood metrics, Cort and Brian dig into the patterns and questions they’ve seen across classes and conversations lately. They unpack common friction points like meeting overload, velocity confusion, misused roles, and daily scrums that eat the whole morning, and offer grounded suggestions for handling each one. Whether you're a Scrum Master trying to protect team time or a developer wondering how to work more collaboratively, this episode offers helpful context (and practical nudges) to help your team work better, together.

References and resources mentioned in the show:

Cort Sharp
#143: What Still Makes Teams Work (and Win) with Jim York
#152: The Five Pillars of Real Agile Improvement with Mike Cohn
7 Advantages of Scrum (Plus 1 Hidden Disadvantage) by Mike Cohn
What Is a High-Performing Agile Team? by Mike Cohn
Mountain Goat Software’s Working on a Scrum Team Course
Subscribe to the Agile Mentors Podcast

Want to get involved?

This show is designed for you, and we’d love your input.

• Enjoyed what you heard today? Please leave a rating and a review. It really helps, and we read every single one.
• Got an Agile subject you’d like us to discuss or a question that needs an answer? Share your thoughts with us at podcast@mountaingoatsoftware.com

This episode’s presenters are:

Brian Milner is a Certified Scrum Trainer®, Certified Scrum Professional®, Certified ScrumMaster®, and Certified Scrum Product Owner®, and host of the Agile Mentors Podcast training at Mountain Goat Software. He's passionate about making a difference in people's day-to-day work, influenced by his own experience of transitioning to Scrum and seeing improvements in work/life balance, honesty, respect, and the quality of work.

Cort Sharp is the Scrum Master of the producing team and the Agile Mentors Community Manager. In addition to his love for Agile, Cort is also a serious swimmer and has been coaching swimmers for five years.

Auto-generated Transcript:

Brian Milner
(00:00) Welcome in Agile Mentors. We're back for another episode of the Agile Mentors Podcast. I'm here as always, Brian Milner. And today we have Mr. Court Sharp with us. Welcome in Court.

Cort Sharp (00:10)
Hey Brian, thanks for having me on again. Brian Milner (00:13) Yeah, Court has been a frequent guest of our show. If you've been around for a while, you probably remember some episodes we've done with him. Court works with us here at Mountain Goat Software. He is a producer and other things, community manager, other things. But he sits in on just about, well, not every class, but he sits in on a lot of classes and helps produce them and make sure that they work. We previously have had Court on with sort of this theme that, you know, Court has his finger on the pulse of things a little bit more because he sees the classes through multiple trainers. He hears the Q &As that take place in all the classes. You know, he even sees some of the emails and some of messages come through the Agile Mentors community from his work there. So Court just has some insight that maybe... a trainer like myself who only gets to see how people question in my classes that I might not have. So we like to have Kordon to get a broader voice of the people approach, if you will, into things. So we wanted to talk a little bit about what are people talking about now? What are the questions? What are the concerns?

Cort Sharp (01:18)
You

Brian Milner (01:29)
What are we hearing now in classes as opposed to maybe a year ago or six months ago? So I think probably a good place to start there, Court, is when people are talking to us about just the common, hey, here's things that's a problem, here's things that are a pain point, how do you deal with this? What are some of the more common things that you've been hearing across the classes and across the interactions with people who are in our our system.

Cort Sharp (01:53)
Right, right. Yeah, I guess I am kind of the collector of questions. ⁓ But even outside of our classes, I'm hearing a lot of questions about, I'm hearing a ton in our classes about this, but outside of our classes, whether it's on various social medias, various emails, of just questions in general to people who are newer to Scrum or I guess Agile as a whole, but specifically about Scrum.

Brian Milner (01:58)
Ha ha ha ha.

Cort Sharp (02:18)
organizations that are newer to Scrum is time management. So like how do we fit all of this new stuff? Like all this new stuff is great. All of what we talked about is great. All that we know about it is great. We were on the same page of like, hey, here's, it's a good time to check in daily with our daily Scrum, make sure we're all on the same page, right? We do need stakeholder feedback with the sprint review. It's good of us to kind of retrospect. and use our retrospective to check in on our team and our process and make sure we're doing the right stuff. But how do we fit all of that in with all of the other meetings and stuff that we already have? And you and I were talking a little bit about just kind of what we're going to talk about a bit more. But we were talking about this before we started recording. And I think I told you literally three or four days ago, I just had a conversation with one of my friends who they're working in a tech software, they're doing a software project in some organization and they're like, yeah, they're trying to get us to move to Scrum because they've heard about this thing. And I just, I don't know how you push this man. I don't know how you do this. I don't know how you live in this world because they got me in six hours of meetings a day and they expect me to get four hours of work done. And I'm not sitting at the office for 10 to 12 hours a day. That's ridiculous. So I think the biggest one is the the time management specifically with all of these meetings. And I know my personal take is I think all of these or a lot of these organizations, I can't say all a lot of these organizations are looking at Scrum as an additive to their current process, not a substitute or replacement. you do you see that, Brian? Do you agree with that?

Brian Milner (03:53)
Yeah. Yeah, I agree. mean, if they already have a huge slate of meetings that they're, I mean, there's going to be some things that Scrum isn't going to replace and shouldn't replace, for example, like, you know, one-on-ones with your manager, right? There's not a function inside Scrum for a one-on-one meeting with your manager, nor should there be, because that's not about how a team builds something. That's more general management and HR, you know? so those kinds of things, no, it's not going to replace and there are going to be other meetings outside of scrum. It's not intended for scrum to replace all of them, but it is intended to replace some of what you already did. and if you, so for me, it's all about purpose. You know, that's, that's where I think that you should start with everything is what's the purpose. And if you understand the purpose,

Cort Sharp (04:46)
Mm-hmm.

Brian Milner (04:54)
then you can compare, ask yourself what the meetings that you have now, what's the purpose of this meeting? And if you can't answer that, then I would challenge it. I think that an agile organization should be open to challenges for any part of the process. And you should be able to say, hey, I'm not sure why we're doing this. And if we can't really articulate, here's the purpose behind it, it should be gone.

Cort Sharp (05:10)
Mm-hmm.

Brian Milner (05:19)
We should get rid of it. So I think you're right. I think there is sort of this layering on top of, and if we don't allow the scrum meetings to replace some of the things that we've done previously, yeah, can be, it can seem like a lot more of a meeting heavy kind of system, but the meetings in the system, let's be clear, right? First of all, depends on how long your sprint is, but let's just go with the sprint that's the sprint length that's the average or most common, which is two weeks. If I have a two week sprint, first day of the sprint, I'm gonna have sprint planning. That is going to be a long meeting. There's no two ways around it. The official time box is up to eight hours if you have a month long sprint. Most people would half that if it's a two week sprint.

Cort Sharp (05:45)
Yes.

Brian Milner (06:07)
So maximum maybe of around four hours. So half a day, let's just say, right? Half a day of your first day is gonna be in planning your sprint. Then maybe you finish that meeting up with a small sort of mini daily scrum, but that's it for that day. So you have half the day on day one. Day two, day three, day four, almost all the days of the sprint that are remaining, you have 15 minute meeting. That's it. If you, if you layer on maybe a backlog refinement, maybe you have another hour long meeting in the middle somewhere, but there's no other scrum meetings every day. It's a 15 minute meeting until you get to the last day. So first day, last day, right? First day, four hour meeting last day, you're going to have the sprint review and the retrospective. So there's going to be some time probably in the first part of your day that you have a sprint review. It's going to be some time in the the back part of your day for a retrospective. But those two combined, they're not gonna, maximum I would say there, if you combine those two, would be the same as the sprint planning, maybe up to about four hours or so, maximum. So maybe half a day. So two days of your sprint, you've got half the day for meeting, two out of 10. And the other days, you've got 15 minutes every day. So yeah, there's a lot of those 15 minute meetings, but they're just one a day. And otherwise you have the entire rest of the day to do whatever you need to do to build. So percentage wise, it's actually a small percentage of the total time that you have to work in the course of two weeks. ⁓ If the meetings are not being kept in their time boxes,

Cort Sharp (07:32)
Mm-hmm. Right.

Brian Milner (07:55)
then that's the issue, right? If we have a daily scrum that goes for an hour, yeah, I would feel like that's a beat down as well. That's not what it's intended to be.

Cort Sharp (08:06)
Right, right. And I've also heard the other really common complaint is about the daily scrum of, I understand it's only 15 minutes. I understand that it's a check-in. There's been, I've heard complaints about other, or seen complaints about other meetings where the point of the meeting isn't really well understood across the team, which I think we'll get into a little bit later. But specifically about the daily scrum, the biggest complaint I've seen is, okay, it's 15 minutes, but is it actually really only 15 minutes of your day? And again, same buddy of mine, same friend of mine who threw this out to me, and he was like, so let me paint this picture for you. I get in the office, let's say at 9 a.m. I sit down, I eat. respond to a few emails. look at my emails, I check that out until about 9.30. Our daily standup is at 9.30. Our daily scrum is at 9.30. I have to do minimal work because I can't get into any deep work. I can't get into any major thought work in that first 30 minutes. So I can't really do a whole lot there. Maybe I'll grab a cup of coffee and hang out. That's what most of my days look like. 15 minutes. And then there's always 15 minutes after that 15 minutes to kind of coordinate with whoever needs to, whoever I need to work with to get stuff done, to help remove bottlenecks or anything, which is totally fine, right? We encourage kind of that 16th minute, so to speak, outside of it, but the meeting officially ends at 15 minutes and unless you need to coordinate with someone else, you're free to go, right? So he's like, okay, there's normally another about 15, maybe 30 minutes. So that takes me until about 10, 15. Well, lunch is at 11, so I got another 45 minutes of nothing. Can't really do a ton of work, and that's basically my whole morning just gone, right out of the gate, right? So it's a 15 minute meeting, but in my friend's world, it's a lot more than 15 minutes. ⁓ I know what I would say to that. I'm curious what you would say, and then I'll share what I would say to that.

Brian Milner (10:02)
Yeah. Okay. Yeah. I'm going to say something that may blow people's minds. What if you don't have the daily scrum first thing in your day? Right. Maybe what the issue is here is the time of your daily scrum. If it's at 9.30 and that's messing with your day because you can't really get anything done before that. And then afterwards you're spending more time. So it's taken time and then there's not enough focus time before lunch. so you feel like half your day is gone, well, what would happen if it was the last thing in your day? What about if you ended the day with a daily scrum? What about if you did it first thing after lunch? There's nothing that says it has to be first thing in the day. The team can decide any point of the day to have the daily scrum, and I encourage the team to experiment with it. I've had some teams before who

Cort Sharp (10:48)
Right. Mm-hmm.

Brian Milner (10:58)
really love end of the day daily scrums because they felt like at the end of the day, we check in with each other. We get together and say, all right, what happened today? Right. And they can all, it's all fresh in their mind because they just finished the day. They can talk through it all. All right. So what does that mean for tomorrow? All right. When we come in tomorrow, we're going to do this. And one of the things that allows is if you have, most of the places I've worked,

Cort Sharp (11:02)
Hmm. Mm-hmm.

Brian Milner (11:24)
You have developers who have sort of different time schedules. Some people will sleep in and come in late and work late. And other people like to come in really early because they like to avoid the traffic. If you have that kind of situation, if you put it towards the back part of your day, then when people come in in the morning, it doesn't matter what time they come in, they have a big chunk of focus time, but then they can dive in and do things. to me, your friend's problem is more about

Cort Sharp (11:32)
Mm-hmm.

Brian Milner (11:50)
that interrupting the block of concentration time and it just needs to be moved to a place where it doesn't, you know, kind of split that block of focus time.

Cort Sharp (11:54)
Mm-hmm. That's a much better answer than I gave him. I just said, well, what else would you be doing in your morning? And he said, well, probably, you know, putzing around, checking email, doing nothing until lunch anyways. ⁓ Right, right.

Brian Milner (12:06)
Ha ha ha! Well, there is always that, right? mean, just because you've got the opportunity to have focus doesn't mean you're going to focus, but that's a whole other set of issues, right? Yeah.

Cort Sharp (12:24)
Right, yep. And really, I guess my additional answer to him was also, when you're working in an organization, you're making a reciprocal commitment to that organization to say, I will get this amount of work done, you will give me this type of compensation, and there will be communication between everyone. ⁓ And to me, the Daily Scrum is that communicative part, maybe not necessarily with the organization as a whole.

Brian Milner (12:44)
Right.

Cort Sharp (12:51)
but you're still communicating with your team and you're getting on the same page, you're getting aligned so that you all can meet your reciprocal commitment. So really, is the daily scrum for the team or for the organization? I think you can make an argument for either, but at the end of the day, it's for everyone to get on the same page so that we can move forward, which you were going to say something? Go ahead.

Brian Milner (13:12)
No, just going to say, part of that as well is just, this is some of the stuff that we talk about in our working on a Scrum team class that we're launching here at Mountain Goat Software is really these kind of more subtleties of how the team works together. When you take a Scrum Master class or something like that, you'll learn that, it's a 15 minute meeting and there's a time box. You may not hear that kind of thing of, well, what works best for this team? Maybe it's the end of the day. Maybe it's the middle of the day. Those are the kinds of things that we try to focus on in a WoWs class is what's the best way for your team to actually do this thing and actually make it successful. ⁓ One of those other areas that I think is kind of a classification of problems is that classification of things and just kind of general process confusion.

Cort Sharp (13:49)
Mm. Mm-hmm.

Brian Milner (14:00)
You know people who just don't understand You know chunks of the process or why things are done a certain way or how to do certain things What what kind of issues have you heard along those lines? Cort Sharp (14:01) Right. I cannot tell you how many times I have heard and seen and had conversations with people about velocity and how velocity, some piece of after it's explained to them, they totally get it. They're on the same page. That's all good. Then they run into the issue of explaining it to their leadership. But the understanding of velocity is that it's a changeable or it's a metric to compare teams.

Brian Milner (14:21)
Ha

Cort Sharp (14:41)
And I'm on team A and we have a velocity of 20. You're on team B. You have a velocity of 30. Someone looks at that, bigger number, better, right? Brian's team is better than Court's team. No, that's not what it is at all. That's not how it should be used. That's not how it should be handled. That is a misuse of the process. That is a confusion point on what velocity actually is. Velocity, I guess we'll explain it here.

Brian Milner (14:52)
Right.

Cort Sharp (15:06)
Velocity is just a measurement of how much one specific team gets done in a period of time. That's it. How many points? And points are all relative. So story points are relative. They are not the same from one team to the next. So therefore, your velocity cannot be the same from one team to the next or comparable from one team to the next. You might have the same velocities, but it's not like saying, OK, my US American dollar is the same as your US American dollar. Those are two very similar, those are the same exact thing. Those are very comparable. We're working with different types of measuring is really what it comes down to, right?

Brian Milner (15:43)
Right. Well, and I get the confusion because Mike's phrase is, estimate size, derive duration. So when you start to say, well, a story point is a measure of size, not time, you sometimes get pushback from people to say, yeah, but you're eventually going to translate it into time anyway. And you're right. We are. We're deriving duration from it. But the split we're trying to make there is when we estimate, right? When the developers are doing the estimation, we don't want them thinking in terms of time. We don't want them to make that process forward leap to say, well then the story point equals this number of hours. So let me do the calculation in my head and figure out how many story points this is gonna be. I say this in class. If your organization has a conversion chart like that,

Cort Sharp (16:12)
Mm-hmm.

Brian Milner (16:33)
a story point equals this number of hours, you're gonna have to convince me and explain to me what benefit there is of doing that. Because I have yet to hear anyone say, oh, well, we do that because it gives us this benefit. Other than saying because that's the way our tool works, right? Our tool we use to manage our process or whatever takes it in this way. And so we have to make the conversion so that we can use this tool.

Cort Sharp (16:42)
Mm-hmm. Right. Mm-hmm.

Brian Milner (17:01)
Now the problem is the tool is driving your process. But other than that, there's not really a benefit that anyone can show me for making that conversion, because what the developer ends up doing is estimating in time. And if they're going to estimate in time, wouldn't it be easier just to say, our estimate is in hours rather than story points? ⁓ It's six hours to do that. It's not one story point. ⁓

Cort Sharp (17:19)
Mm-hmm. Right. Right.

Brian Milner (17:26)
That's what I encourage people to do. the confusion comes from the fact that we do make that duration, we do drive the duration eventually, but that's for the long range forecast. I mean, we say very clearly in our other classes, but we talk about this in the worst class and the working on a scrumpting class, that when you're estimating something, you're thinking in terms of size, you're thinking in terms of risk. comparative to other things. And there's really only two reasons that we would use Story Points. One is to make those longer term forecasts, but the other is to help the product owner to know the relative cost of things so they can prioritize. But the thing you're mentioning, Core, is to use it as a performance metric, and that's where people fall into, I think, a big trap. When you use it as a performance metric, it actually destroys the other two reasons. Mike says this, we have a good thing going with the other two reasons. Organizations want to be able to forecast forward. Organizations need the product owner to be able to know the relative cost of something so they can prioritize. Those are good things. So why go in and destroy it by also trying to use it as a performance metric? Because those two things are needed still. And we won't have a way of doing those.

Cort Sharp (18:24)
You Right. Right. Mm-hmm. Right. Yeah, totally. I agree with that. I don't really have anything to add. I you just kind of knocked that one out of the park there, Brian. Good job.

Brian Milner (18:48)
Yeah. Yeah, no, mean, velocity, some of these, part of it's, you know, these are all new terms for a lot of people as well. And so you hear terms like velocity and think, oh, what does that mean? And, and I get it, you know, if you're a manager and you're not really familiar with this kind of stuff and you hear the term velocity and you think, oh, that's the speed of the team. Well, yeah, it is the speed of the team. Right. And if it's the speed of the team, why can't I use that to judge one team against the other? Because it's like using, um, you know, Fahrenheit and Celsius. I mean, it's

Cort Sharp (18:56)
Right.

Brian Milner (19:18)
metric and imperial. They're different measures. And so one number doesn't equal the same thing as the other. ⁓ Now, there are some scaled frameworks like safe that we'll try to level set across teams by having a little cheat sheet saying, hey, this is an example of a five-point story. This is an example of an eight-point story. So that the teams can maybe relatively compare against the same definitions of

Cort Sharp (19:25)
Right? Right. Mm-hmm. Mm-hmm.

Brian Milner (19:45)
sizes. ⁓ But I gotta say, even there, the teams are going to be off. The teams are not going to be perfectly aligned. That's the only thing that you can really do to try to align those. But they still have their own conversations. They still reach their own conclusions. And so the scales aren't going to be perfectly aligned no matter what you do.

Cort Sharp (19:46)
Mm-hmm. think even more importantly beyond they have their own conversations or I guess more fundamentally, not more importantly, more fundamentally, is that they have different people on different teams. You have different skill sets, you have different abilities, you have different people working on different stuff. I think I've programmed a little more recently than you have maybe, or it might be vice versa. I know you've recently just built a website again. But I would probably wager my programming skill set in like, I don't know, Ruby on Rails is probably a little, I got a little edge up on you right there, right? So if we were on different teams, Court's on this team, Brian's on that team, how can we possibly compare this different skill sets to each other and expect the same result, the same speed, the same pace?

Brian Milner (20:37)
Yep. Yep, definitely so.

Cort Sharp (20:55)
You were talking about, oh, it's like comparing using Fahrenheit and Celsius. The first one that popped into my mind was miles per hour or miles and kilometers per hour, miles per hour, kilometers per hour. Right. Speed in different cars. And then even beyond that, I guess, building on the car analogy, that's like comparing a high end Ferrari to my little first car ever, which was a Saturn Ion little beater. Could barely get up to 60 miles an hour thing. Those are two different cars. They're two different skill sets and they require two different viewpoints to even be able to compare them. There are comparisons you can make, know, four wheels, steering wheel, whatever. But at the end of the day, one of those is going a whole lot faster and it was not my first car. I can tell you that. ⁓

Brian Milner (21:39)
Yeah. Yeah, no, I think that's a good way to compare it as well. What about things that have to do, and I'll kind of combine some thoughts here, but maybe what about things that are kind of more role-centric or even just how the team works together? What kind of issues have you heard people mention recently in those areas?

Cort Sharp (21:49)
Mm-hmm. So managers, for one, what is the role of managers within Scrum? What's the difference between a product owner and a product manager? Is there a product manager? Does that person even exist? Do we just need to fire all of our product managers or turn them all over into product owners? That one's very common. But I think another really common one is when does the Scrum master step in? And the first time I took my first scrum master class, I can't say first time I took one. I've only officially taken one. but I've been in, if you look at the title of a podcast episode, a couple, couple episodes ago, a rough estimate of a billion, scrum classes. Laura, Laura, Laura Kendrick and I have been in a billion scrum master classes. That was, that was the fun conversation we had, but. I made that that I needed that question to answer to help me kind of grasp what is this new role? This is not a very traditional typical thing that you see within organizations of the Scrum Master. Do I as the Scrum Master, do I help estimate? Do I help prioritize the backlog? What do I do? Am I am I a team lead? Is everyone trying to talk with me on the daily stand up and is it my role or my job to hold? take notes, hold people accountable to what they're saying? Or is that kind of just my job to say, okay, cool, we did it, we're good. I facilitated this meeting, I put it on all your calendars, you showed up and do your thing, I'm out, see ya, right? So I think the Scrum Master role as a whole, there's a bit of confusion on that and product or project managers, right? How do we manage those or handle those?

Brian Milner (23:43)
Yeah. Well, the other titles, no matter what other title that you have, first of all, let's separate out. This is part of what people need to understand. Do not confuse job title with scrum roll, right? Because you can have, let's say I'm a project, I'm hired as a project manager, but...

Cort Sharp (24:00)
Hmm.

Brian Milner (24:07)
now I'm gonna be on a Scrum team, I could be the Scrum master on that Scrum team. Does that change my job title? No, I'm still hired as a project manager. So that's kind of the thing that people need to understand. You don't have to have the job title Scrum master or now we're doing Scrum, so now we got to fire our project managers and hire Scrum masters, right? That's not necessarily the case. It's a role on the team. ⁓ So that being said, Scrum defines three.

Cort Sharp (24:15)
All right. Mm-hmm.

Brian Milner (24:33)
It defines Scrum Master, Product Owner, and Developer. It doesn't define any others. It doesn't mean you don't have them. Mike has this phrase that I love. says, the Scrum guy doesn't mention tacos, but it doesn't mean we don't have tacos. ⁓ The one I like to say in class is it also doesn't define a CEO. But I bet you have a CEO. I bet your company has a CEO.

Cort Sharp (24:47)
Right.

Brian Milner (24:58)
It's not saying that you don't need these other roles or that there's no place for them in an organization using Scrum. It's saying Scrum is going to define for you how a single team works. And if you have a product manager, maybe that's more of a scaled thing of how we manage that product across multiple teams. If you have project managers, maybe that's about coordinating information across teams. If you have business analysts, maybe that's helping product owners to write stories. Maybe they are a product owner. I don't know. If you have managers, managers are usually not on a Scrum team unless they're really expert at doing a certain skill. Sometimes I'll see managers who are developers on a team. But the power dynamic is a weird thing on a Scrum team and that's something to be careful of. If you do have someone who is a manager of any kind on a Scrum team, I would, if at all possible, try to make sure that they don't have any direct reports that are also on that same team. They can be on another team with other people that don't report to them, but if you have them on a team with people that directly report to them, now you got this weird power dynamic within this team that's supposed to be a team of equals, but it's not a team of equals because one person's going to fill out a...

Cort Sharp (25:56)
Yeah. Mm-hmm.

Brian Milner (26:12)
performance report on me. So how safe do I feel to say I made a mistake around a manager who's gonna put that on my performance report? That's the danger. ⁓ But yeah, I think you're gonna have any of these other roles. And as far as the Scrum Master is concerned, when does the Scrum Master step in? Well, let me ask everyone listening to think about this question. If you were a parent of a child, when do you step in if you have a child who's doing something that could be harmful?

Cort Sharp (26:21)
Right? Right.

Brian Milner (26:39)
Think about this, I didn't tell you what age the child was, right? If you have an infant, you're gonna step in a lot quicker. You're gonna protect them a lot more. If you have a teenager, you might give them a lot more leash and say, hey, that's your responsibility, right? You know kind of how to do this. And if they insist on doing something a way that you don't think is the right way,

Cort Sharp (26:42)
Mm-hmm.

Brian Milner (27:04)
a certain point as a parent, you have to just say, you know what, this is their lesson to learn. And, you know, they need to have the, I believe very strongly as a parent that you have to really defend your kids' rights to make their own mistakes. And I'm not saying developers are kids, or I'm not saying that, you know, you're, as a Scrum Master, you're the parent of the team. Please don't interpret it that way. But I am saying there's a parallel to this to say,

Cort Sharp (27:09)
Mm-hmm. Right. You

Brian Milner (27:29)
As a scrum master, knowing when to step in is an issue by issue decision. At this instance, how harmful will it be if they do this thing? Is this a kid running out in front of a truck coming down the street? Well, I'm gonna stop that. ⁓ Is this, hey, don't touch that plate, it's hot. I have told you 50 times, don't touch that plate, it's a hot plate.

Cort Sharp (27:35)
Right. Right.

Brian Milner (27:52)
Okay, well hey, maybe it's time for you to touch that hot plate and understand that, hey, next time I'm not gonna touch that hot plate, you know?

Cort Sharp (27:54)
Right. I totally agree. I'm a little more, and I understand I'm a little biased in this, but I'm a little more of a fan of the Scrum Master. The best or a good analogy of a Scrum Master is like a coach on a team, like a sports team is what I'm saying. And the reason I'm biased, right.

Brian Milner (28:12)
Gee, I can't understand why that would resonate with you.

Cort Sharp (28:16)
Who would have thought? I am a, well, recently, I'm a little hiatus right now, but I am a swim coach, head coach, and I think the parallel there is just much easier for me to grasp because think of a coach. You are supporting your team. You're stepping in when needed. You're talking with, whether it's officials or referees or someone that's a little higher up, has a little more authority. than you or your team has in a moment. You're not being disrespectful to them, but you're just communicating, you're conversing, you want to get their understanding and you want to communicate that to your team and work within whatever kind of scope is set there. You're working within the scope of the rules. So I like to view that as kind of like, here's the general organization rules that we follow and standards and practices and all that stuff. But I'm not the one, me personally, I'm not the one.

Brian Milner (28:48)
Yeah.

Cort Sharp (29:09)
jumping in the water and doing the races, right? I'm not the one out there on the court, dribbling a ball up and down. I'm not the one out there on the field tackling people, right? I'm there to help the team formulate a plan, help the team execute that plan and help the team really just do what they can't or remove as much of their stress as possible so that they can only focus on doing their job, which in the coaching space is

Brian Milner (29:15)
Yeah.

Cort Sharp (29:36)
sport coaching space is let the team go out and swim, let the team go out and play football, let the team go out and play basketball or baseball or softball or whatever it is, right? Let them do their thing. You're there to help them and make their day on game day on meat day as easy as possible and as seamless as possible for them. So there was there was something that you said there to Brian that kind of got my gears gears turned a little bit.

Brian Milner (29:55)
Absolutely, Kreen.

Cort Sharp (30:02)
You were talking about how the kind of power dynamic, if like a manager is on a team and someone reports to them, there's that power dynamic there. But you said that everyone is on an equal playing field within Scrum. we're all on the same level within our team. We might have different roles, but we're all on the same level. And that kind of got me moving into like, what have you seen that one kind of helps establish that we're all on the same team, we're all on the same playing field, we're all working together, you I might be the product owner, so I might have a little, or I do have guidance over here's the direction we're gonna go more so than maybe the Scrum Master does with the product development itself. But how do you kind of build that trust within a team to be able to say, yeah, I see you, Cort, as an equal contributor here, even though you're the one saying, We're going to do, we need to do this, this, this, and the other thing in the next two weeks. cause I see a lot of, I see a lot of questions about that. see a lot of struggles with that. And I think that's a very common issue that a lot of people face within a scrum team. Because again, it is so different from, I report to my manager. You don't report to your scrum master. You don't report to your product owner. You sit down and have conversations with them. So how do you, how do you kind of foster that and facilitate that? that type of environment.

Brian Milner (31:25)
Yeah. Great question. And like the kids used to say a while back, there's the rub. You know, that's kind of the key point there. There's a thing we say about Scrum where we, a lot of trainers and coaches will say this, Scrum is simple to understand, difficult to master. And that is precisely what's meant by that. And that's kind of some of the stuff that we try to capture in this working on Scrum team. Class is is that difficult to master portion because? You know, how do you how do you gain trust from someone else? well That's not in the scrum guide, right? I we're not gonna be able to you know, look that section up and say here's the rules on how you You know start to trust someone else that you're working alongside That's a difficult thing How do you do it? Well, it takes time You know, it's like a any kind of any other kind of relationship you have with another human being, you can't walk in from day one and say, hey, we're going to now have this deep trust with each other. You have to extend it and you have to earn it. That's the way that it's built. And that has to happen over time. You have to display that I have trust in you and I'm worthy of your trust. So when you put your trust in me, you can count on me. I'm going to be here and I'm going to do what it is you expect me to do. That's really the only answer that works for that. it's difficult. is the human working dynamic, I think, is the undervalued kind of glue that holds a lot of this other stuff together. ⁓

Cort Sharp (32:52)
Yeah. Mm-hmm.

Brian Milner (32:55)
And it's that kind of stuff that a good scrum master, I think, can really make an impact on because, hey, they're not just going to know a time box. That's kind of just Scrum 101. But they're going to also know, well, what happens when I have two team members who get into a big conflict, who disagree? My hand's off, and I just let that run. And all of a sudden, now we have a team that splits, that fractures along that line.

Cort Sharp (33:05)
Right. Right. Yeah.

Brian Milner (33:23)
Or do I get roll up my sleeves and get involved and have the skills to help them navigate that conflict and come back as a team without resentment, without losing trust in each other, but really working honestly with each other and being productive when we come back. That's the difficulty. And like I said, that's something we tried to capture when we kind of created that working on a Scrum Team classes.

Cort Sharp (33:23)
Right.

Brian Milner (33:48)
And what are some of those more subtleties of nuances that really are the heart of whether the team is going to work or not?

Cort Sharp (33:57)
Right. think even, even beyond just what do these look like? I think the way I view a working on a scrum team is it's for everyone on a scrum team, right? It's not just for scrum masters. It's not just for product owners. It's not just for developers. It gives you a big picture. Excuse me. Sorry. It gives you a big picture of how, how effective you can truly be when you are.

Brian Milner (34:18)
Yeah.

Cort Sharp (34:25)
working together on a Scrum team, right? You were talking a little bit about the human working dynamic or nature, one of those. And as soon as you said that, I was like, we should double click into that a little bit. But very briefly, maybe double click into it a little bit of when we work together and humans are working together and not working in siloed environments, not saying, hey, I'm the front end developer. I did my mock up.

Brian Milner (34:31)
Yeah, yeah.

Cort Sharp (34:52)
I'm out, I'm done. Figure it out everyone else. you're, struggling with your database stuff. Tough. I'm done with my thing. I'm going to sit back and sip a, sip a cool lot on, on Tahiti's beaches or whatever. Right. We're not doing that. We're, we're helping each other out. We're working together and we're saying, okay, cool. You're having database issues. I don't know anything about databases, but maybe I can help look up some stuff or I can find some. help you out in some way that isn't inhibiting you from doing your job. But it might not be like doing it. It's definitely not doing your job for you. And it's not like it's a, I know everything about databases or I know enough about databases to be able to get by. It could be even as basic as, you run into this error code. Cool. I'll look that up for you and send you the results and save you a little time, hopefully that way or something. But it's that team collaboration, it's working together as a team. I like the perfect example, which I'm pretty sure we talked about this in working on a Scrum Team course as well, of developers and testers working together in tandem and saying, instead of, we like to say, developers finish their code and then we throw it over the proverbial wall. And all right, testers, you got to catch it, figure it out. and then test it, developers maybe sit side by side with testers or hop on a call, not too dissimilar from what we're doing here, just hop on a call with each other and say, let's figure out the verification that the password meets the requirements. Okay, cool, tester, you want to write up the tests, I'll start developing or working on the code for it. Awesome, here's my code, here's my thought process. Do you have any thoughts, Tester? Do you see any edge cases right out of the gate that I should keep an eye out for or work on? I think that is the bigger picture that working on a Scrum team really highlights and really focuses on and allows a lot of people to kind of open their eyes a bit more and see the forest through the trees, so to speak, to be able to understand here's the value and here's what it actually means to be working on a Scrum team rather than just here's my role. I'm gonna go do my role, do my thing and see everyone else figure it out.

Brian Milner (37:08)
Yeah, not that it ignores the basic components and the ground rules that help us, but it goes beyond that to say, how do you actually make this thing work? So yeah, that's a great point. Well, this has been really useful. I really appreciate you taking time to do this, Court, and coming back. And I'm sure we'll do this on a periodic basis, just to check in and see, hey, what are you hearing now? What are the hot button issues now? So.

Cort Sharp (37:18)
Absolutely. Yeah. Yeah.

Brian Milner (37:32)
Thanks for sharing that and keeping your ears open and continue to do that so we can do more of these.

Cort Sharp (37:39)
Hey, happy to Brian always always fun just seeing what's what's going on out there. What conversations are are being had. And I hope this actually like help someone. Right. I hope this this helps solve either clears up some confusion about, know, maybe what the daily standup is for, what the daily scrum is for, who it's for. Hopefully it doesn't add more confusion. But if it does, you know, you know where to go. Right.

Brian Milner (37:59)
Hahaha. Exactly, All right, thanks, Cort.

Cort Sharp (38:05)
Yeah, thanks for having me.