Kanban allows for critical fixes/features to jump ahead of the line and its obvious what work is getting traded off for later. Kanban also flows very nicely wit

Kanban allows for critical fixes/features to jump ahead of the line and its obvious what work is getting traded off for later. Kanban also flows very nicely with a CI/CD process where when something is tested and ready to ship, it gets shipped. I believe the essence of agile is these two concepts - shipping working software and lean prioritization. Things getting stuck in a backlog is a good thing because that shows they aren't that important (other things keep skipping ahead) and you aren't building, testing and delivering software that is hardly used. As a manager in my org I'm not driving deadlines, that's the PM and they mostly know what can get done and are reasonable. Its expected that if you keep jumping the line with stuff, other things are delayed. One downside that is concerning is focus time on specific areas of an app for developers and tech debt in those areas. Its like they keep hopping around from tree to tree like a squirrel. People that like long projects where they are 95% of the time building new things and don't have to deal with production issues, bugs, etc. this org and work style isn't for them.