Should Scrum Masters Make More than Software Developers?
It’s been a little while since I’ve done a reader question. Let’s fix that today by examining a question that is simple in the asking and complex in the answering. Should scrum masters make as much or more money than software developers?
The actual question was a little more nuanced, and it came from the Developer Hegemony Facebook group.
The numbers on this chart show that scrum masters could make as much as some senior level developers in Los Angeles. I’d be curious do you guys think this is a “market distortion” brought on by the fact that the “MBAs” need a way to manage the “propeller heads” or do you really feel the market is accurately reflecting the true value a scrum master can bring to a team?
So let’s dig in. But first, let’s make sure that everyone reading is up to speed.
What Is a Scrum Master, Anyway?
If you’re in the software world, you’ve probably heard the term “Scrum Master” before. But let’s level-set with a definition, because for a lot of you reading this might have a fuzzy definition. Let’s go back to first principles and snag a definition from the Scrum guide:
The Scrum Master is responsible for promoting and supporting Scrum as defined in the Scrum Guide. Scrum Masters do this by helping everyone understand Scrum theory, practices, rules, and values.
The Scrum Master is a servant-leader for the Scrum Team. The Scrum Master helps those outside the Scrum Team understand which of their interactions with the Scrum Team are helpful and which aren’t. The Scrum Master helps everyone change these interactions to maximize the value created by the Scrum Team.
First of all, this is sort of ingenious and fascinating from a meta perspective. Scrum is a wildly successful approach sold by consultants to organizations. It’s so successful that it’s created a job whose primary purpose is marketing the product being sold to the company. I say this because job one is, apparently, “promoting and supporting Scrum.” This would be like Microsoft convincing a .NET shop to create a job whose primary purpose was extolling the virtues of Microsoft products.
The Scrum Master in Practice
But I digress. Apart from process evangelism, and the unfortunate use of a term that I personally detest (“servant leader”), the Scrum Master does provide some serious potential value. They serve as sort of internal referees for the team, officiating collaboration and keeping it on track. But, perhaps most importantly, they defend the team from outside distractions. And that matters.
Of course, someone in a role like this will also develop situational dynamics with the team. They’ll develop a knack for goosing development along, keeping people happy, and finding other ways to pitch in.
So think of Scrum Master as being sort of a process-specific hybrid of dev manager and project manager, but (most likely) without direct reports. If you wrap your head around that concept, you can see a person whose value to the team could fluctuate pretty wildly based on myriad factors.
And What is a Scrum Master Salary?
The reader question was specifically about the Los Angeles area. Let’s broaden that, at least, to the US. At the time of writing, here is what Salary.com had to say for the US:
- Salary range was $76,490 to $103,157
- Average base salary was $88,171
- Average total comp was $91,760
I also perused Glassdoor and found figures that seemed to corroborate this.
How about a Software Engineer Salary?
Now, let’s look at the range for software engineers, which is a bit more complicated. This is because we software engineers are comically accomplished at stack ranking ourselves, depressing our own salaries, and creating a weirdly large pay band.
Indeed, on Salary.com for Scrum Master, you have two position titles: Scrum Master and Senior Scrum Master. With software developers, there’s like 30 at a casual glance. Let’s narrow the field by just considering only software engineer (which has I, II, III, IV, and V, of course 🙄 ).
- Salary range across these positions is $58,657 to $161,126.
- The midpoint of that is $109,892. (I don’t know the average because it’s distributed across multiple roles)
Other software-y roles seemed to pay less, so let’s just say, for argument’s sake, that the average software developer salary is around $100K.
So, via a fairly cursory bit of research, it looks like a Scrum Master might fall in the 40th percentile of software developer pay ranges. And they clearly make more than developer closer to the entry level.
What “Should” Someone Make is a Fraught Question
Our task now, then, is to ask whether this is how the world “should” be. Are scrum masters “worth” more than 40% of developers?
Everything is worth what its purchaser will pay for it.
— Publilius Syrus
Channeling Adam Smith a millennium and a half before there was an Adam Smith, Syrus has the right of it for our purposes. A scrum master (and any employee) makes what they should, in a market sense. And it becomes a challenge to frame and answer the question otherwise. Consider the following arguments that would be easy to make.
- Developers “should” make more because they have skills that require years to acquire, rather than a week-long certification program.
- Scrum masters “should” make more because they’re sorta management and management makes more.
- Developers “should” make more because they could act as scrum master, but the reverse is not true.
- Scrum masters “should” make more because they’re (potentially) force multipliers.
You get the idea.
So let me give my answer to this question in a different way.
A Hypothetical Team and a Fixed Budget
Recently, I’ve been talking with a friend and business partner about a possible venture for which we could probably secure investment. This would involve something like $1M in runway, as a nice round number. And I SWAG that we could build the thing with a nicely-sized software team over the course of year, with revenue starting to flow in upon completion.
So what should this team look like?
- 8 seasoned, self-managing software developers?
- 6 seasoned developers and a more expensive dev manager/CTO type to run it?
- 5 seasoned developers, 1 QA pro, and the CTO?
Etc. The combinations kind of explode in a hurry. But let’s be serious here. This is the software industry, where demand is through the roof. So the team we wind up with will likely be whatever combination we could staff.
So we’d do our best to find and hire a team of good folks, get them together, and set them up for success.
When And Why Does A Scrum Master Make a Good Hire Here?
The question for our purposes becomes, “when would scrum master be a good hire, and when would scrum master be worth more to me than the next incremental developer hire?” Well, let’s review what they do and the implications for my team.
- We’d need to be a scrum team, since otherwise, well, ya know, scrum master isn’t a thing.
- The team members would need to be unfamiliar enough with scrum to need help, and to be unable to serve as scrum masters.
- We’d need a lot of interruptions, to justify a role frequently dedicated to fending them off.
- The team would need to struggle to self-organize so that the scrum master could help.
- We’d need a lot of blockers and impediments, so that the scrum master could spend a good bit of time removing them.
- It would probably help to have internal conflicts for the scrum master to mediate.
- You need a butler with leadership skills (sorry couldn’t resist — have I mentioned that I loathe the term “servant leader”?)
It seems that a dedicated scrum master is an excellent hire if you’ve built a dysfunctional scrum team. But if everything is clicking along smoothly, the role is likely superfluous.
Should Scrum Masters Earn More Than the Devs Around Them? Probably
This finally brings me around to answering the question. Scrum masters, when needed, should probably earn more than software developers.
Well, for the same reason that I tend to charge a lot of money for assessment engagements designed to get software programs back on the rails. The scrum master is coming in to make an untenable situation tenable. If the scrum master is truly needed, you have an organization that’s investing in developer salaries, equipment office space, etc. and in danger of under-perfoming on those investments.
So you’d bet it’s worth paying a pretty penny for a hire that could turn that around.
But over the longer haul, this is a penny-wise, pound-foolish strategy. Righting a ship should be a temporary effort, rather than a permanently staffed hire. If you permanently need a scrum master (or any ship-righter), it’s worth asking whether you have the right staff/process/resources/leadership. Is there no other way to stop people from interrupting software developers than with a 90K/year permanent employee? Could a wall maybe suffice instead?
So I’ll draw this to a conclusion with as definitive an answer as I can give.
Should a scrum master make more than a developer, when the scrum master role is necessary? Yes, but in the same way that short-timer consultants make more money. Should the salaried role of scrum master exist at all? Almost certainly not. If it does, your organization has bigger problems than the pay matrix.