Scrum is actually nothing really genious. It consists of few pillars that are hard to design differently. For example, having a regular meeting is nothing wrong and any other development process / framework may incorporate that. How regular these meetings are and which team members should join them is debatable. Scrum makes some clear recommendations here. Whether that all is the absolute best way is unclear, I would doubt so unless there are studies prooving that. The studies would need to take into account thousands (if not millions) of software projects that follow different processes/ frameworks and then comparing their success metrics (time, money, quality, etc) with each other. Its hard to make such studies correctly (too many parameters and uncertainty).