This thread is all problems a no solutions. I also don't like traditional scrum and meaningless ceremonies but there is value in some of the methodology. Ther

This thread is all problems a no solutions. I also don't like traditional scrum and meaningless ceremonies but there is value in some of the methodology. There is one thing in particular that no one here is addressing. Underperforming developers. Every comment assumes that all developers are fully equipped to excel if management would just get out of their way. Um, no. I've seen extremely knowledgeable and talented developers who, left to their own devices, fail miserably. You "empower" them to do amazing thing and set them up for success and they get almost nothing done. If there's no one holding them accountable, they just coast. The truth is that some people and teams need the extreme rigidity and process that comes with scrum or they will simply not ship. Other teams will die in a fiery explosion or wither quietly into attrition if you force process on them. The best you can do is set a foundation and course-correct as the team succeeds or fails. You might end up with very little meetings or 2x scrum ceremonies. Whatever it takes for the team to be productive and happy. There is no "One Process to rule them all" and leaving developers total freedom to do whatever they want is definitely NOT the answer. The best process for a team will likely change over time due to many factors like company stage, # of members, their experience levels, their commitment levels, their personalities, etc... The job of a manager is to tailor the team's process to what achieves both the business goals and keeps people happy. It's a difficult and thankless job which few do well.