Why Scrum and Kanban do not contradict each other?

Scrum and KANBAN are considered the most widely used agile methods. Organizations often ask themselves the question “Is Scrum or Kanban a better fit for us”? At consistency, we are only too familiar with the comparison of the advantages and disadvantages of the respective methods. But we say – KANBAN and Scrum do not have to be at odds with each other. It is not absolutely necessary to choose one or the other option at the beginning of an agile organizational transformation, as they start at different levels. While KANBAN initially focuses on the transparent presentation of a system’s current processes, Scrum expects the teams to implement key change measures such as team assignments, role definitions and sprint lengths right from the start. KANBAN pursues an evolutionary change approach. This means that we start by presenting existing processes transparently and understanding them together with all those involved. Our experience shows that this approach already identifies initial process bottlenecks and challenges that are the motivation for direct changes. Once an initial KANBAN system has been set up, the continuous improvement process begins immediately. KANBAN helps to identify process errors and make the effects of improvement measures measurable. Unlike Scrum, it focuses on the management of work and not the management of teams.