I have become what I cannot stand a Scrum Master. Not that I believe that what I do for a living is not valuable. It is highly valuable as I spend my whole entire existence in support of creating and delivering high-quality, high-impact software on a regular basis. In fact, my mantra for my scrum teams is “We provide business value.” There is nothing better in my mind than delivering solid business value. It is worth the money they spend on me (and much more). The problem I have with my job is the title Scrum Master. It is the second most pretentious job title I have ever had the pleasure of knowing (that of web master predates it so wins the pretentious gold medal by a nose). Every time I tell someone what I do for a living, I die a little inside.

What is it about software development that leads us to such titles? And the job search terms. Why is it that only cults and IT would use the term guru all the time? Do we have a problem with self-importance? I wasn’t always titled as such – in the past I have been Software Development Manager, Director of Software Development, etc. even while I ran multiple scrum teams. It hasn’t been too long that I finally became a full time Scrum Master. I like the job. I just want a new title.

Here are some suggestions for replacing the title Scrum Master: Software Delivery Manager, Software Delivery Facilitator, Software Process Technician, Software Delivery Practitioner, Software Process Manager, Software Process Improvement Manager. Of course, we can always go completely the other way: Software God, Doctor of Software Goodness, Master of Software Universe, Super Software Man.