> Teams produce less working code I write code for living, and I want to produce as little code as I can. That's also part of the agile principle, produce what

> Teams produce less working code I write code for living, and I want to produce as little code as I can. That's also part of the agile principle, produce what is needed. > Scrum ceremonies become more inane and waste development cycles The complexity of a team is greater than just its output. I don't know the context of the ceremonies, but sometimes reflection on what has happened is important, and definitely the planning part sound important. > Lower quality code is produced, more slowly Ummmm what? There might be an argument to be made about not having a design document which maps out the entirety of project but code quality is based on best practices, testing etc. > Software engineers enjoy less and less career satisfaction Really! This one is hard to digest, if you expect satisfaction to come from external sources then that's going to be a problem. But what is career satisfaction, I have not worked for one company where someone is satisfied by all the processes. > Product knowledge is lost over time > Process knowledge is lost over time Yeah that's a general problem, for all types of project and product management. > Developer's wages are being suppressed by forcing them to report to low paid laymen with Scrum certification At least it's not an argument blaming offshoring. > Scrum planning and grooming never produce anything close to predictable velocities or deliverable dates even after years of scrum on the same team I doubt even almost all projects pass the three tiers of development, on time, on cost, bug free. This is not unique to scrum. > Scrum masters who are mostly unqualified laymen, treat developers defensively and increasingly with hostility Given the tone of the site, I see hostility is no unique to scrum masters :) The majority of the rest are not failings of scrum, rather process failures. If you have a Scrum master who is writing tickets or not enforcing ticket structure which leads to those tickets missing vital information, you can point your finger straight at the scrum master. I had this situation with a product manager and after a cordial conversation, the tickets change, then they went back to not writing them correctly. That was not a failure of scrum.