The Scrum Master Mistake of Copy-Pasting Success Instead of Recreating the Journey | Nigel Baker

Summary

---

Scrum Master Toolbox Podcast: "The Scrum Master Mistake of Copy-Pasting Success Instead of Recreating the Journey"

Episode with Nigel Baker | March 2, 2026
Host: Vasco Duarte
Guest: Nigel Baker, seasoned Agile Coach

---

Episode Overview

In this engaging episode, Vasco Duarte sits down with seasoned agile coach Nigel Baker to explore the pitfalls of "copy-pasting" successful scrum practices from one context to another—a common mistake for many Scrum Masters and Agile Coaches. Nigel shares his journey into Agile, early experiences as a Scrum Master, and the valuable lessons learned about supporting teams authentically rather than imposing pre-baked solutions. The conversation delves into the nuances of leadership presence, self-awareness, and daily Scrum practices.

---

Key Discussion Points & Insights

1. Nigel Baker’s Origins as a Scrum Master

• [01:57]–[06:41]
  • Nigel entered the world of Scrum “by accident,” starting out as a software developer at British Telecom’s fast-paced tactical unit (“Fast Track”).
  • Fast Track was known for its eclectic, rebellious, and unconventional approaches: "You've never seen a bigger bunch of pirates than the people in Fast Track. These are people who can get stuff done, but, oh, how they got it done." – Nigel Baker [03:25]
  • Scrum was adopted in the team not to speed up an already fast group, but to introduce rigor and guide their energy productively.
  • Nigel wasn’t the first pick for Scrum Master, humorously noting: “I found out years later I was the third person to be asked.” [05:22]
  • He accepted the role and quickly grew to love it: “I loved being a Scrum Master. I’ll say that to my dying day.” [01:57]

2. The Trap of Copy-Pasting Success and the Importance of Context

• [06:42]–[08:50]
  • Nigel identifies a frequent novice Scrum Master mistake: assuming that a successful practice or process can be simply "copied and pasted" to another team or context.
  • "That is what killed me to begin with: trying to recreate the results of our team, not recreate the journey." – Nigel Baker [07:39]
  • The real value lies in going through the process with each new team, allowing the group to evolve its own practices.
  • Nigel contrasts the relative smoothness of his early Scrum Master roles with the turbulence that emerged when he became an Agile Coach and tried to duplicate past successes.

3. Early Failure: Mistaking Documentation for Leadership

• [08:51]–[10:00]
  • Nigel recounts his very first Daily Scrum in the early 2000s, when literature about 'bad Scrum' was lacking.
  • He proudly brought a large leather notebook to the daily, meticulously writing down what each member planned to do, echoing project manager tendencies:
  • "I wrote down what every single team member was doing. Thinking like I’m some sort of like proto project manager… I’m here to lead them and tell them what to do. And it’s such a silly thing to do.” – Nigel Baker [09:06]
  • The information was already tracked in their internal system, making his role redundant and unintentionally signaling command-and-control thinking.

4. Leadership Presence: How to Participate Without Dominating

• [10:07]–[13:32]
  • The discussion shifts to how Scrum Masters can remain present and attentive without drawing unnecessary focus or dominating the team.
  • Vasco shares his experience as a "recovering project manager," using note-taking (not for records, but to help him stay silent and focused) as a meditative practice.
    • “I actually started doing what you were doing … just writing to make sure I heard what was being said and I wasn’t tempted to talk because I wasn’t able to write and talk at the same time.” – Host [10:48]
  • Nigel observes that sometimes, appearances matter more than intent:
    • Watching a project manager doodle helped Nigel realize not all note-taking means disengagement; sometimes it’s a mindfulness tool.
    • “It’s about how you appear, not just about what you’re doing... being self-aware is key. If you’re self-aware of your flaws, you can mitigate and manage them.” – Nigel Baker [12:05]
  • He shares practical advice:
    • Use Post-it notes (actionable, not documentation-focused) to capture meaningful takeaways.
    • Pay attention to body language—looking thoughtfully away can signal active listening, but looking distracted undermines team confidence.

5. Servant Leadership and Self-Awareness

• [13:33]–[14:02]
  • Nigel emphasizes that leadership in Scrum is about supporting the team, not controlling them.
  • “I’m there for them, they’re not there for me.” – Nigel Baker [09:54]
  • The importance of demonstrating presence while letting the team own their process and conversations is discussed, with both practical tips and humor—Nigel jokes about sticking Post-its on his forehead as a visible action cue. [13:33]

---

Notable Quotes & Memorable Moments

• On Scrum adoption by pioneers:
  "Ignorance is a fantastic defense against obstacles. If you don’t know something’s impossible, it’s possible." – Nigel Baker [04:15]

• On being a third-choice Scrum Master:
  "I found out years later I was the third person to be asked." – Nigel Baker [05:22]

• On the mistake of copying process, not journey:
  "Trying to recreate the results of our team, not recreate the journey, you know, and so that’s really, really interesting." – Nigel Baker [07:39]

• On the false security of recording everything:
  "I wrote down what every single team member was doing... thinking like I’m some sort of like proto project manager..." – Nigel Baker [09:06]

• On self-aware leadership:
  "If you are self aware of your flaws, you can mitigate and manage them, you know? So for instance, if you know you talk too much, you go, okay, I will be very consciously aware of this and do tricks like you said to avoid that." – Nigel Baker [12:05]

• Light-hearted moment about note-taking:
  "If you’re listening to this and not watching it, I’m holding a post it up. Thanks everyone. Post it notes." – Nigel Baker [13:32]

---

Timestamps for Important Segments

| Timestamp | Segment | |-------------|------------------------------------------------------------------------------------| | 01:57-06:41 | Nigel’s agile origin story and Fast Track BT’s agile pirate culture | | 06:42-08:50 | The dangers of copy-pasting Scrum successes; learning to recreate the journey | | 08:51-10:00 | Nigel’s early Scrum failure: treating Daily Scrum like a project manager | | 10:07-13:32 | Note-taking, presence vs. authority, and self-awareness for Scrum Masters | | 13:33-14:02 | Servant leadership, team focus, and using post-its effectively |

---

Tone & Atmosphere

The episode is candid and humorous, with both Vasco and Nigel sharing self-deprecating stories. The tone underscores learning, humility, and practical wisdom for Scrum Masters. Nigel’s warmth, creativity, and thoughtful humor shine throughout.

---

Practical Takeaways for Scrum Masters

• Don’t shortcut the team’s evolution by imposing pre-made solutions.
  Success comes from co-evolving practices with the team, not by copying what worked elsewhere.

• Leadership is about presence, not control.
  Learn how to support and observe without dominating or signaling authority.

• Self-awareness is your superpower.
  Understand your own impulses (e.g., to talk, to control, to document) and use rituals or props (like doodling or post-its) to manage your behavior.

• Daily Scrums are for the team, not for you.
  Resist the urge to use them as "status meetings" or personal databases.

• Practical cues and body language matter.
  Be mindful of how your actions are perceived—what you do to stay focused should not signal disinterest or authority.

---

This episode is a must-listen for Scrum Masters seeking to deepen their craft, avoid rookie mistakes, and cultivate authentic servant leadership.

Transcript

[Vasco Duarte]

Hey there, Agile adventurer, just a quick question. What if, for the price of a fancy coffee or half a pizza, you could unlock over 700 hours of the best agile content on the planet? That's audio, video, E courses, books, presentations, all that you can think of. But you can also join live calls with world class practitioners and hang out in a flame warfree and AI slop clean slack with the sharpest minds in the game. Oh, and yes, you get direct access to me, Vasko, your Scrum Master Toolbox podcast. No, this is not a drill. It's the Scrum Master Toolbox membership. And it's your unfair advantage in the Agile world. So if you want to know more, go check out scrummastertoolbox.org membership, that's scrummastertoolbox.org Membership. And check out all the goodies we have for you. Do it now. But if you're not doing it now, let's listen to the podcast.

[Host]

Hello everybody. Welcome to one more week of the Scrum Master Toolbox Podcast. And this week, joining us from the UK is Nigel Baker. Hey Nigel, welcome to the show.

[Nigel Baker]

Thank you for having me, I really appreciate it.

[Host]

Absolutely. So Nigel is a seasoned agile coach with a keen intellect, warm creativity and thoughtful humor. You will see a lot of that this week, I'm sure. With a career spanning software engineering, consultancy and global training, he inspires teams to thrive, not just perform outside work. He loves bold ideas, good conversation and a life well lived. So, Nigel, that was a short intro. Tell us a little bit more about yourself and how did you end up becoming a Scrum Master.

[Nigel Baker]

So here's I love being a Scrum Master. I loved being a Scrum Master. I can't. I'll say that to my dying day. I really enjoyed it. I kind of fell into Scrum Mastery is the best way to say it. So I this now we're winding right back to the start of Agile, let alone Scrum. So this is like 2002. Okay, so as a team, I'm working in a, what we would call a tactical unit for a large scale British telecommunications company. Right. But I won't name them bt. Ah, there we go. But I worked for British Telecom as a graduate. I had been there about 10 years. I was a developer, a software developer. Now the arm of the business I was in was called Fast Track and it was Tactical Delivery. And the reason it existed is because BT was a telephone company that used to be part of the UK government. It was nationalized. It used to be part of our post Office. So it Was slow. Unbelievably slow. Nice place to work. Lovely place to work, but slow. So they developed up this whole tactical arm to basically, okay, we haven't got two years, what we're going to build in the short term to cover the two years. Now, the problem with this tactical arm was a lot of people used it strategically, so because if you're going to take you two years to do something, they'll just order it off, usually.

[Host]

Alas.

[Nigel Baker]

If you've ever seen the film Pirates of the Caribbean, because I come from Bristol in the uk, in England, which is where pirates come from. Treasure island was set here. And you've never seen a bigger bunch of pirates than the people in Fast Track. These are people who can get stuff done, but, oh, how they got it done. And so the most eclectic, exciting, weird and wonderful collection of individuals who could do stuff right, Rebels, pirates, and everything in between. I was not one of those people, by the way. I was one of the people internally going, oh, can we not do it like that? Suffice to say, we start doing agile very early. Very early. We've got a project, it's going poorly, it's behind times. The classic. The project manager lost control, it got weeks behind schedule. And one of our developers, a contractor, said, hey, we should try this Scrum thing. It's really good. It's really popular in America. Spoiler alert. It wasn't popular in America. No one has heard of it, right? But ignorance is a fantastic defense against obstacles. If you don't know something's impossible, it's possible. So we start doing Scrum and we look great. My first Scrum Master, who actually now is very famous, Jeff Watts, he was our first. He did one of the first Scrum courses on Earth and came back and said, hey, we should do this. We started doing it. We look great right now. The company. And Jeff won't mind me saying this, the company loved Jeff. Oh, my God, they love Jeff. They thought Jeff was brilliant. They thought Jeff did this all on his own. So Jeff got sort of taken off and moved ahead and promoted again and moved on. And so there became a space for Scrum Master. And they said to me, would you like to be Scrum Master right now? I found out years later I was the third person to be asked, okay,

[Host]

well, that's good to discover years later, by the way.

[Nigel Baker]

So they asked John McNeil, who was the guy who introduced Scrum, do you want to do it? And he said, no, I'm a developer, I hate the idea. They asked another colleague of ours, Steph, does he want to do it? And he said no, I'm a developer, I hate the idea. And they said, Nigel, do you want to do it? And I said sounds great. Is it more money? And I can't. I don't. It may have been a bit.

[Host]

Probably not.

[Nigel Baker]

Yeah, probably not, but it may have been, but. And so I took it on. I took it on and I loved it to bits. I really enjoyed it. I had a real great time doing it. And then that's how it got going really. And I remember telling people I'm a, I'm a Scrum Master. And they're like what's that? And I'm. Yeah, I know, yeah, it's not something

[Host]

you would bring up at a dinner party for sure. No, no, you would just to provoke people. But Nigel, so when you got into that role and I can already see the group of pirates, all mostly developer fol, wanting to get things done quickly, I can already see the opportunities for chaos. But maybe the story you have for us next is not from there, I don't know. So I'll just ask the question, what is that one story of failure that you bring with you today to recall one of those critical lessons you learned back then.

[Nigel Baker]

Yeah, because we actually did Scrum to gain rigor, not to gain speed. So like most organizations are like we're so slow and in fact BT started spreading agile across the entire company after us because they loved the idea so much. But a lot of that was we need to speed up a very slow process. When with us it was kind of like putting some guide rails on some CAN do people to stop them doing so much can to try and get it going in the right direction. Okay. And so it's really funny because my Scrum Master experience has actually always been pretty good. It's been pretty good. There's not been many lumps and bumps. When I made the jump to Agile coach, that's when we got, that's when we got crashes and birds, a lot of them. Because you start, you know what you like as a new Scrum Master, you, you work together, you evolve a process together, you get to a good spot. And then the classic Scrum Master mistake, which we may come to later, is thinking that version that you've evolved has cross applicability like copying and pasting across other teams. And, and that is what killed me to begin with, trying to recreate the results of our team, not recreate the journey, you know, and so that's really, really interesting in terms of actual Failures of SCRUM Master I. The. The. My favorite one. I've mentioned this probably a thousand times, but I did because this was so new. There was no literature out there about bad Scrum, you know, like it's not all the videos about bad Scrum mastery and what bad Scrum masters do. So on my very first daily Scrum, and bearing in mind this is so long ago, we all sat down and you know how people sit down in scrums again now, but it's taken 20 years to get like. So there was no standing up. I got a big leather book, I booked my local stationers, nice big leather, serious book, opened it up and I wrote down what every single team member was doing. Write it all down, this lovely little book. So what are you doing next, Steph? What are you doing, John? Sabrina? And I wrote it all down thinking like I'm some sort of like proto project manager, you know, like I'm here to lead them and tell them what to do. Right. And it's such a silly thing to do.

[Host]

Database.

[Nigel Baker]

Yeah. Well, it's like the worst thing is, it's like we've already got this all written down, so we actually. What's interesting is. And again, you see how the world changes. In bt, they had this home brew requirement system they built internally, like a website, right? And we got them to change it to make it agile and it was called arms. Right? Now it was cheap, cheerful and better than Jira to this day because it was just simple and configurable. And so people were writing in ARMS and you could do what we've got the information. Like the only reason basically why I. I don't know what I was thinking. If I knew what I was thinking, it was probably something like, oh, I'm the boss, you know, like probably something along those lines.

[Host]

Controlling everything.

[Nigel Baker]

Yeah. Not consciously. It wasn't like I thought of myself as their leader, but I just. There's a. There's a. There's a subconscious vibe there about them telling me what they're doing. That's a classic mistake made. I'm there for them, they're not there for me.

[Host]

That's actually interesting because I have another take on writing things down. So let me put that for hear your thoughts. When I started as a Scrum Master, I found it. I was a project manager, recovering project manager, as I usually say, and I found it very hard to stay silent during the daily meeting. Extremely hard. So in order to try to stay silent but still stay focused, I actually started doing what you were doing at the time which was writing everything down. Because now I wasn't writing it for record or any. I was just writing to make sure I heard what was being said and I wasn't tempted to talk because I wasn't able to write and talk at the same time. And I think it can be a great, even meditation practice for the scrum master in that daily meeting to stay focused on what's being shared without, and this is the other thing, without attracting other people's eyes. Because at the time we were all co located because otherwise people will start start looking at you and talking to you instead of talking to each other. What do you think about that?

[Nigel Baker]

Well, this is really interesting as well, because how do you stay focused on the conversation without drawing focus to yourself in that conversation? So I remember on the basic, on the first coaching experience I had, no, but maybe about the first half dozen, another guy, the project manager used to be was writing things down, right. So I thought, I wandered over and had a look and he was doodling, just drawing. And he's not doing that because he's disinterested. He's doing that because that helped him focus on the conversation. It helped like just like give him handsome to do so we could really hear. But I realized with a lot of things is it's about how you appear, not just about what you're doing, you know. So for instance, like I, when I'm trying to pay attention, and you may see it by the way, on this video, I will look away. It's not that I'm distracted by something, it's because I'm trying to focus my ears reduce the stimulation so I can really hear the conversation right now actually, in a daily scrum, that's not a bad idea as long as you're focusing on something that doesn't look disinterested. So if you're looking up at the football results, you look like you don't care.

[Host]

Yeah, looking out the window, right?

[Nigel Baker]

Yeah, exactly. But if you focus on something in the middle distance, that can be as you're giving the sign that I am focusing. So I think I talk a lot about scrum mastery these days. Or just leadership is being very self aware. You can be flawed, you could be a horribly flawed individual. But if you are self aware of your flaws, you can mitigate and manage them, you know? So for instance, if you know you talk too much, you go, okay, I will be very consciously aware of this and do tricks like you said to avoid that. If I get distracted, I'll do trick. But you have to be have this awareness of yourself so that you can counter, program or balance out your behaviors so you don't give the appearance of authority or appearance of absence of authority. Like I don't care. Disinterested trying to be present whilst not in control. Yeah, it's like when I used to write things down, but I just used to use post its. So if you're listening to this and not watching it, I'm holding a post it up. Thanks everyone. Post it notes. So I would use post it notes as a way because they're obviously not making notes on you. I'm capturing actions or something and we want to be able to capture actions in a format that's useful. A simple post it note is a great trick for that in a especially

[Host]

if you put it in your forehead just like you did.

[Nigel Baker]

Just like I did. I stuck on my forehead. I wasn't going to mention that because actually when you stick it on your forehead when you're bald like me, everyone out there, I've got a lovely full head of hair. Not when you pull it off your head. You can take some of your skin with you, which is not the most pleasant experience. But the idea is some sort of note taking device that isn't note taking. I action taking, not recording what people are doing.

[Host]

That's a great point. Great point. Hey, it was a great set of tips for how to stay present even though you want the team to be in control. So thank you for sharing that, Nigel.

[Vasco Duarte]

All right, I hope you liked this episode, but before you hit next episode, here's the deal. This podcast is powered by people like you. The members who wanted more than just inspiration. They wanted real tools and real connection to people who are practicing agile. Every day we're talking access to over 700 hours of agile gold, CTO level strategy talks, summit keynotes, live workshops, E courses, deep dive interviews, books, and if you're into no estimates, we got the pioneers of no estimates in those deep dive interviews as well. Agile Business intelligence, creating product visions, coaching your product owner courses, you name it. You'll get invites to monthly live Q&As with agile pioneers and practitioners, plus a private Slack community which is free of all of that AI slop you see everywhere. And of course, without the flame wars. It's a community of practitioners that want to learn and thrive together. It's the best place to connect with community and learn together. So if this podcast has helped you before, imagine what you will get from this podcast membership. So head on over to scrummastertoolbox.org membership and join the community that's shaping the future of Agile. We have so much for you, so check out all the [e-mail] membership because listening is great, it's important. But doing it together, that's next level. I'll see you in the community.

[Nigel Baker]

Slack

[Host]

we really hope you liked our show. And if you did, why not rate this podcast on Stitcher or itunes? Share this podcast and let other Scrum masters know about this valuable resource for their work. Remember that sharing is caring.