Well, if you don't communicate, don't plan or don't do any retrospectives then those omissions will have a high probability to cause problems. In that sense sc

Well, if you don't communicate, don't plan or don't do any retrospectives then those omissions will have a high probability to cause problems. In that sense scrum is like "training wheels for self organizing teams". Once you understand the benefits, a small team should be capable of modifying the system. If we look at productized processes Kanban is much better at getting the essential framework in place. Scrum is not the worst process that could be applied to software production for large orgs. Worse examples include for example a no-process, hardware companies shoehorning software development into hardware development framework and so on. IMO as a junior dev over a decade ago it was nice to have scrum when I started at a company since that framework made it very explicit what the rules of the process were. A no-process would have been much worse and stressful. But high performing teams tend to realize there is no one shoe fits all solutions to complex processes and then evolve their own system.