The problem here is toxic corporate culture. Scrum and Agile are not magic spells that miraculously turn idiots into reasonable people. Sure, they could be used as levers to change that culture, but the culture absolutely needs to change, otherwise it's not going to work.
And that's something you can throw in their face: that they're not taking Scrum and Agile development seriously. If they say they want Scrum and Agile, then make sure you understand what they really mean, and hammer on it every time they trample on the autonomy of the developers. Every time they ask why things aren't done, tell them management is interfering with the process.
I'm just fed up with this Agilescrum thing. My present RnD workplace have been transitioning to it in the last years and it's really bad. The prior V-iteration process was good enough. We are mostly just making up estimates and report time accordingly to make the burndown chart look good.
Except in the minds of absolutely every single person who applies them to anything.
Just start pointing this out to people every time this comes up. It's not an exact time estimate, it's an abstract complexity estimate. Insist that the idiots get some actual training in Agile before they start corrupting it beyond recognition. If they want Agile, then they should invest in training people for it, and in spreading the culture that goes along with it. Because Agile is perhaps more about culture than about process.
This, in short, is the core of value that Scrum adds to the ideas of Agile.
The only problem is that people insist on misunderstanding these simple ideas and try to do Scrum as wrong as possible. The problem isn't Scrum, the problem is people insisting on doing it wrong.