Whoever has come up with the term "Scrum master" should have seen developers as "Scrum slaves"! 🛑 ✋

Published: June 2, 2023

Whoever coined the term Scrum master should have seen developers as Scrum slaves

Image generated by AI

The term "Scrum master" may have been coined with good intentions, envisioning a leader who guides and empowers development teams.

However, the reality for many developers often seems more akin to being "Scrum slaves." The misuse of Scrum as a mere daily report mechanism rather than a tool for effective planning and continuous learning has led to frustration and dissatisfaction among many in the developer community.

Sadly, this discontent has manifested in numerous individuals abandoning programming, changing their career paths, or transforming their roles from a technical person to a Scrum master to be on the other side.

Unfortunately, it is widespread that the misuse of Scrum has turned it into a traditional managerial tool (with a new shiny mask - Kanban, Scrum, Agile, and now Agile2! 😀 ) focused on adding meetings, pointing at developers for not delivering fast enough, and "daily reporting to management" rather than a manifest for valuing collaboration, flexibility in planning, openness to change, continuous improvement, and concentrating on what matters the most to the business/customers.

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.