Ironically, for each of Scrum's events, there is, IMO, a better approach for achieving what that event is intended for.

As such, to me, Scrum is actually a set of ANTI-patterns.

Example: the daily Scrum. To me, that is a _terrible_ way to ensure that people stay aware of things. There are far better ways.

Example: the sprint. IME cadence-based development is very disruptive, and is counter to the notion of continuous flow.

Example: the retro: Getting people together to "think on what to improve" is a terrible approach to encouraging continuous improvement.

Example: sprint planning: Getting the whole team together to go over stories is wasteful and disruptive. There are better ways. What the team needs to actually meet about is how everything will work together, in a technical sense - design discussions.

Scrum is a set of anti-patterns.