Transcript
A (0:01)
Hello, everyone. Quick heads up before we start today's episode. The Global Agile Summit is happening on May 4th. Yes, May 4th. And even with a big blowout Star wars party, you have to join. It will be online and it's like always free to attend. We have four tracks this year that I'm really excited about and I think you will too. Stick around to the end of the episode to know what they are. If you want to check it out already now you can check it out at bit ly globalagile 26. That's the numerals 2 and 6 at the end. So one more time, that's bit ly globalagile 2, 6, all one word, all lowercase. And 2 and 6 are the numerals 2 and 6. So stick around till the end of the episode and I'll tell you what's in store. But for now, on to today's episode. Hello, everybody. Welcome to our Team Tuesday. This week we have with us Nate Amidan. Hey, Nate, welcome back.
B (1:09)
Hey, pleasure to be back. Divasco.
A (1:11)
Absolutely. So today's Team Tuesday, we'll talk about how sometimes team become their own worst enemies. But before we dive into that, do share with us, Nate, what's the book that most inspired you in your career as a Scrum Master?
B (1:29)
Do I have to pick one?
A (1:31)
You have to pick at least one, but okay, maybe not more than ten.
B (1:36)
I'm gonna give you two. Okay. The first one I think every Scrum Master should read is Deep Work. And so the reason why Deep Work is so important is because software engineering is complicated and complex and it takes a lot of focus. And now that we're back in the office, a lot more teams are back in the office understanding that shoulder taps are expensive. And what I mean by that is there might be a time as a Scrum Master, you have a mildly irrelevant question. Like if you go and just bother an engineer or someone that's in the zone in Deep Work, you know, you're adding about a 15 minute time for them to get back into that zone. So I have everyone in my company read that book because at, at the core of we're serving servant leaders of Scrum Masters, we need to, we need to, to safeguard our engineers time. It needs, that needs to be one of the most important things that we do as Scrum Masters. Give them more time to do the things that they do because we can't do what they do. And then the second one I think is also really important for Scrum Masters is project to product. Now this one's A little more senior. You know, if you're a junior Scrum master just coming in, it's probably a good read. But if you start moving into more agile coaching and you starting to influence how organizations are thinking about how they operate at a program, at a programmatic level or a program level, really thinking about the importance of the team structure. And so, and I say this all the time, which is, look, you, the team needs to be sacrosanct and work should go to teams and people should go to teams and those teams can change and they can fluctuate. But the idea that there is a team of people that own a specific thing and they're responsible for that specific thing I think is one of the most important aspects to any sort of agile implementation, especially at an organizational level.
