Pooyan Razian

Scrum Master vs Scrum Slaves! 🛑

Scrum Master vs Scrum Slaves! 🛑
Published: April 10, 2024

It seems that Scrum Masters love to be named "masters" and they do everything they can to protect it! But as long as the term "Scrum master" exists, developers are seen as "Scrum slaves"! 🛑

You might say ...

You might say: aah! but we are just the "process master"!

Let's be honest with yourself and admit this can't be true as long as you have the power of people/team management, and you insist on wanting people to call you a kind of "master"!

You might say ...

You might say: aah! but master just means we are expert of this thing that we call it "Scrum"! And as Scrum is originated from copying the process of making Toyota cars in Japan, "master" should have a similar meaning as it has in martial arts.

The main problem with this kind of mindset is that martial arts originate from the science used to build traditional militaries in societies where hierarchy and being/having a master/king/general/whatever were highly appreciated. A military-based hierarchical approach and its terms are NOT attractive to the smart software developers building our modern societies.

If you still insist, this "topic expert mastership" might work between senior/lead developers and junior developers who do the same thing. But, will a Kung Fu trainee/disciple call a boxer his/her master? The same applies to developers vs. people with other skills. Developers don't need to be reminded 10x a day by calling you the whatever "master"! No matter how much you love it.

Remember ...

A valuable software developer should be a "kind of philosopher" who can understand and map reality to another form (software), not just followers who accept orders from their masters.

Remember, the choice of wording influences us to do things based on their meanings. We are human, and our brains can easily be trained by repeating the same term over and over, leading us toward wanted or unwanted changes in our societies.

Last but not least, I love the fact that no one even thinks about other terms like Scrum facilitator, Scrum coach, or Scrum servant, etc. and we have managers who are very much protective about being called "masters" while they say: "But we serve our teams"! 😀🤥💚

If you liked the article, feel free to share it with your friends, family, or colleagues. You can also follow me on Medium or LinkedIn.

Copyright & Disclaimer

  • All content provided on this article is for informational and educational purposes only. The author makes no representations as to the accuracy or completeness of any information on this site or found by following any link on this site.
  • All the content is copyrighted, except the assets and content I have referenced to other people's work, and may not be reproduced on other websites, blogs, or social media. You are not allowed to reproduce, summarize to create derivative work, or use any content from this website under your name. This includes creating a similar article or summary based on AI/GenAI. For educational purposes, you may refer to parts of the content, and only refer, but you must provide a link back to the original article on this website. This is allowed only if your content is less than 10% similar to the original article.
  • While every care has been taken to ensure the accuracy of the content of this website, I make no representation as to the accuracy, correctness, or fitness for any purpose of the site content, nor do I accept any liability for loss or damage (including consequential loss or damage), however, caused, which may be incurred by any person or organization from reliance on or use of information on this site.
  • The contents of this article should not be construed as legal advice.
  • Opinions are my own and not the views of my employer.
  • English is not my mother-tongue language, so even though I try my best to express myself correctly, there might be a chance of miscommunication.
  • Links or references to other websites, including the use of information from 3rd-parties, are provided for the benefit of people who use this website. I am not responsible for the accuracy of the content on the websites that I have put a link to and I do not endorse any of those organizations or their contents.
  • If you have any queries or if you believe any information on this article is inaccurate, or if you think any of the assets used in this article are in violation of copyright, please contact me and let me know.

Scrum Master vs Scrum Slaves! 🛑

Scrum Master vs Scrum Slaves! 🛑
Published: April 10, 2024

It seems that Scrum Masters love to be named "masters" and they do everything they can to protect it! But as long as the term "Scrum master" exists, developers are seen as "Scrum slaves"! 🛑

You might say ...

You might say: aah! but we are just the "process master"!

Let's be honest with yourself and admit this can't be true as long as you have the power of people/team management, and you insist on wanting people to call you a kind of "master"!

You might say ...

You might say: aah! but master just means we are expert of this thing that we call it "Scrum"! And as Scrum is originated from copying the process of making Toyota cars in Japan, "master" should have a similar meaning as it has in martial arts.

The main problem with this kind of mindset is that martial arts originate from the science used to build traditional militaries in societies where hierarchy and being/having a master/king/general/whatever were highly appreciated. A military-based hierarchical approach and its terms are NOT attractive to the smart software developers building our modern societies.

If you still insist, this "topic expert mastership" might work between senior/lead developers and junior developers who do the same thing. But, will a Kung Fu trainee/disciple call a boxer his/her master? The same applies to developers vs. people with other skills. Developers don't need to be reminded 10x a day by calling you the whatever "master"! No matter how much you love it.

Remember ...

A valuable software developer should be a "kind of philosopher" who can understand and map reality to another form (software), not just followers who accept orders from their masters.

Remember, the choice of wording influences us to do things based on their meanings. We are human, and our brains can easily be trained by repeating the same term over and over, leading us toward wanted or unwanted changes in our societies.

Last but not least, I love the fact that no one even thinks about other terms like Scrum facilitator, Scrum coach, or Scrum servant, etc. and we have managers who are very much protective about being called "masters" while they say: "But we serve our teams"! 😀🤥💚

If you liked the article, feel free to share it with your friends, family, or colleagues. You can also follow me on Medium or LinkedIn.

Copyright & Disclaimer

  • All content provided on this article is for informational and educational purposes only. The author makes no representations as to the accuracy or completeness of any information on this site or found by following any link on this site.
  • All the content is copyrighted, except the assets and content I have referenced to other people's work, and may not be reproduced on other websites, blogs, or social media. You are not allowed to reproduce, summarize to create derivative work, or use any content from this website under your name. This includes creating a similar article or summary based on AI/GenAI. For educational purposes, you may refer to parts of the content, and only refer, but you must provide a link back to the original article on this website. This is allowed only if your content is less than 10% similar to the original article.
  • While every care has been taken to ensure the accuracy of the content of this website, I make no representation as to the accuracy, correctness, or fitness for any purpose of the site content, nor do I accept any liability for loss or damage (including consequential loss or damage), however, caused, which may be incurred by any person or organization from reliance on or use of information on this site.
  • The contents of this article should not be construed as legal advice.
  • Opinions are my own and not the views of my employer.
  • English is not my mother-tongue language, so even though I try my best to express myself correctly, there might be a chance of miscommunication.
  • Links or references to other websites, including the use of information from 3rd-parties, are provided for the benefit of people who use this website. I am not responsible for the accuracy of the content on the websites that I have put a link to and I do not endorse any of those organizations or their contents.
  • If you have any queries or if you believe any information on this article is inaccurate, or if you think any of the assets used in this article are in violation of copyright, please contact me and let me know.
Copyright © 2025 - pooyan.info