In my experience as a dev... Kanban is a useful tool that helps teams organise work, break it down, be flexible. It helps the whole team to see what needs doing, identify dependencies and where to help each other out. Scrum OTOH looks similar on the surface, but is a form of micromanagement and becomes a system to be gamed. Project Managers become more concerned with velocity and burndown charts and whether specific stories were done in specific sprints or within the specific story points, than whether actual useful productive work is happening that moves the organisation forward. In the version of Kanban I've been in, you can chuck in the occcasional tech debt story into the so-called "sprint" (basically the 2 weeks between planning meetings) and no-one minds. Thus something that's slowing you down can be fixed. Whereas in Scrum, you'd have to haggle with the project manager to be "allowed" to do something like halve the build time in CI or something.