Kanban vs Scrum

Projects are always more complex and therefore require more and more specialized management. Since the 2000, so-called "Agile" methods have spread, but it is not always easy to choose the one that will best suit the project. We will compare here kanban vs scrum which are two widely used project management methods.

Scrum

It is a method based on short development cycles, iterative, and especially adaptive. Communication is at the center of the method, with tools allowing information to circulate as smoothly as possible between Scrum team members and development team members.

Regular, daily, and at the end of each iteration (or sprint) progress points are made, allowing everyone to have the same level of information. The problems encountered are therefore pooled, which facilitates their resolution and the things that work well are also shared. We are therefore in a process of continuous improvement.

In order not to block the project, it is possible to adjust the list of tasks, their distribution or their complexity, while not calling into question the objectives of the sprint. The advantage of the scrum method is that it allows for regular deliveries, at short intervals, and therefore to adapt to the changing needs of the customer.

Kanban

In Japanese, Kanban means "panel" or "label". Kaban is an agile method from Japan whose main tool is a whiteboard. It is divided into several columns, ranging from the list of tasks to be performed to the list of completed tasks, through all the necessary steps: in progress, in test, delivered ...

Each task is modeled by a post-it. As a task progresses, its leader advances it from column to column to mark its state. Software like Nutcache can virtualize this array, but the use of a physical array is also possible. This makes it possible to visualize all the referenced tasks as well as their advancement status at a glance. It is also very rewarding for team members to see their post-it progress towards the "Finished" column.

Kanban brings a plus over other methods by limiting the number of tasks that can be placed in each column. We never end up with an endless list of tasks. The actions are prioritized and their realization is favored.

Just like in Scrum, Kanban is in a process of continuous improvement with the sharing of information among all team members, common problem solving and consideration of process improvement suggestions throughout the project. .

Kanban vs Scrum

Although both methods have many similarities, the approaches are different.

• With Scrum, the development team works on short cycles ranging from two to four weeks. At the end of each sprint, a new version of the project is delivered to the client to make the recipe.
• With Kanban, it is more the continuous improvement that is put forward, the developments are not fixed and can be subject to changes throughout the project.

Even if the two methods are different, they do not really oppose and are generally used in parallel because if we look good, they are complementary. It is quite possible to use, and this is often the case, to use Kaban (with his table and limited task lists) on short Scrum development cycles.

In any case, no project management method will be completely adapted, each case being unique. You have to be pragmatic and take the best of each world, the objective being to have at your disposal tools that work and that advance the project and the teams.