Scrum is an organizational framework. The key feature is the presence of a Scrum Master. Without this, Scrum is not Scrum.

The Scrum Master does not have the right to hire, evaluate and fire people. Otherwise, it’s not a Scrum master, but a project or department manager.

The Scrum Master only organizes procedures and helps with negotiations.

Quite often, a good Scrum Master is a “humanitarian” without any programming skills, but with good organizational skills.

Due to the current market situation, the Scrum Master usually receives fewer then programmers, project managers and department heads, because it is cheaper to find people without technical knowledge.

Thus, Scrum improves the quality of work (due to specialization) and reduces the cost (expensive technical specialists do not do organizational work).

At the same time, Scrum events (sprint, sprint planning, daily scrum, sprint review and retro sprint) and artifacts (product backlog, sprint backlog and increment) in fact, they never carried any kind of innovation, because they were used before Scrum. For example, Soviet flyers aka scrum daily, etc. Scrum in IT has brought a single name for these events. This is quite good. But you do not need to assume that Scrum is used, since Scrum is still about roles.

PS. Yes, I have been trained and certified as a Scrum master.