This is a good summary.

As I’ve expected while opening your article, there will be a lot of non-developers who will argue against what you said. I’ve written an article similar to yours and similarly received negative feedbacks. But well done for speaking up. But do remember that there are non-developers who needs companies to run Agile in order to have a job (even though we might argue whether they are actually value adding to the organization).

Now, one point you might have missed is that companies usually don’t realised that with Scrum, what happened is that most likely, the code behind the end product is a messy bunch of unmaintainable code because proper technical design wasn’t done up (since requirements were never firmed up from the start). The question here is, before all the agile madness, have you ever heard of technical debts and refactoring?

Unfortunately, the hype now is Agile. It’s a way for companies who have never experienced it to adopt it in order to promote themselves. Of course, pain will come later rather than sooner and it will be too late for them. Too many negative consequences like users getting lazy, developers getting restless and unmotivated (like what you said, software developer is not longer a creative process), scrum masters and agile coaches having to deal with uncontrollable mess due to technical debts, etc.

I am glad that I began as a developer before taking the Scrum Master course and having done both, I feel you.

Of course, as a few comments rightly pointed out, the way agile is implemented in your company can be better. My company does differently and is slightly better but still suffers from the intangible consequences that are hard to measure.

Good luck! And all the best!