Kanban can be classified within the agile methods. Since Scrum and Kanban have many similarities but also many differences, we would like to focus on the Kanban method in this article in order to build up a basic understanding.

In simple terms Kanban is a three-part workflow. It is visualized with the help of a task board. The task board is divided into three columns and has the following headings: “To Do”, “In Progress” and “Done”.

Within the “To Do” column, all tasks are collected and prioritized that are still to be processed. The “In Progress” column represents the tasks that are currently in progress and the “Done” column collects all completed tasks.

Besides the columns there are also the so called Swimlanes on the task board. Here the team is free and can display a suitable structure or division. For example, you could draw a new swimlane for each topic block or according to the task type or the person who has to do the work.

Jeff.lasovski – A Scrum board suggesting to use Kanban

that this task is now in progress. If this task is completed, it is moved to the “Done” column.
The Kanban method is a pull-based method, analogous to Scrum. However, Kanban does not know time limits in the form of sprints. It is a continuous working process. The limiting factor in Kanban is the so-called “Work in Progress” key figure. This indicates the maximum amount of work a person or a team can do in parallel (i.e. work in the column “In Progress”). As soon as the capacity is reached, no further task “To Do” can be shifted to “In Progress”. First the current work must be completed “Done”.

Within Kanban there are also three different role types. The role Flow Master, Flow Manager or Delivery Manager is responsible for the adherence to the process and brings the whole team closer to the method.

The Service Manager, Product Owner or Product Manager is responsible for the respective product or service, i.e. the content.

The development team helps the Service Manager, Product Owner or Product Manager to implement the product. Compared to Scrum the development team can be much more diversified.

The advantages of Kanban lie in the basically pragmatic approach. It offers with simple means an increase in transparency for a smooth workflow, but also workload. It can easily be introduced into an existing organization and thus replace or even supplement existing methods.

The disadvantages of Kanban are that the work to be done can be cut into small packages. Also, dealing with fixed deadlines leads to an increase in complexity in one situation or another.

We would like to advise you in the implementation of the Kanban method for your company! If you still have questions or suggestions, please contact us!

Scroll to Top