but they will gladly take the productivity hit from that time sink because it gives them teh ability to track employees. they'd rather know that everybody is working at 80% productivity than release that burden and just trust them. it's either this or filling out frustrating timesheets.
They literally implemented the most orthodox scrum you can imagine, with the one exception that they could sit on the sprint planning meetings and override the teams pulling tickets off the backlog into sprints (technical debt of course started to pile up).
The kicker is that after a few months of this, productivity slowed to a crawl. The retrospectives showed that the planning wasn't working because the planned work rarely got done - because we were always fighting fires. Work also slowed due to all the overhead that was added to implement scrum (I also had to participate, despite being in an DevOps role - that at the best of times is inherently interrupt driven and I'm servicing the work of developers). Despite the fact that the powers that be knew things were not working as well as they used to, no amount of feedback could loosen the reigns - probably because it inherently meant losing some control. We had to try everything else to get back to where we were, when empowered developers could make decisions. Things got worse of course as within 6 months we lost half our most experienced talent that wasn't going to put up with it (this was the peak 2022 tech hiring levels).
Eventually there was some mild "improvement" as we were allowed a "15% time" to work on what we thought was best, which still had to be justified and it was still the lowest priority during any given sprint. I still shake my head at the whole situation.