I am not really seeing the problem here, nor do I agree with the premise that scrum turns X developer into Y developer. Your success as a developer is primarily driven by your desire to succeed, but also by a combination of the team, project, and company culture. Scrum is not at fault here, because bad management, lazy team members, and a toxic work environment can make any worker in any discipline complacent, no matter which system is used. I’ve worked for 20 years in this industry and have seen various management and development methodologies used, and my conclusion is that what matters most is the attitudes of the people themselves. If you have even one toxic coworker or even worse, a toxic leader, it can change the morale of an entire team and possibly even put an entire project at risk. That’s what can turn a great developer into an average one. If you have below-average developers, scrum will do nothing to actually make them more motivated; they will probably remain average, despite appearances that they are moving tickets quickly.<p>Like any other system, scrum can be abused and twisted into something it was never meant to be. A project I worked on had daily scrum-style standups as well as daily, weekly, and monthly status reports; We also had Jira and our boards were closely scrutinized by every level of management and the customer. We happened to use scrum, but you couldn’t look at this and say scrum was at fault for such duplication of information and ridiculous reporting requirements.