A recruitment consultant will contact you soon.

Kanban VS Scrum

Kanban vs Scrum

Is Kanban in the process of overcoming Scrum?

In recent years, Agile methodology has invaded the world of computer development. In fact, it would be better to talk about Agile METHODS because confusion between Agile and SCRUM has quickly become established in the IT environment.

Waterfall/Scrum/Kanban Benchmarking

Waterfall’s disadvantages

The main disadvantages of the V-cycle are:

Infotel_Kanban vs Scrum_Waterfall visual

  • Delivery of the application version at the end of development which, because of this, means any problems can only be discovered some considerable time later. The debug phase is cumbersome to manage and causal analysis of malfunctions is not necessarily straightforward.
  • The greatest lack of transparency for the client with regard to the project’s progress. The whole application deliverable only gets delivered at the end of the chain, meaning customers must rely on suppliers to manage all their projects’ costs and deadlines.
  • Adapting a V-cycle project to changes in customer requirements (concerning specifications / adding extra functionalities / etc.) is not easy.
  • The waterfall leaves no methodological framework behind (or very little) that can be reused during a future application development. The app’s TMA inherits only a small amount with which to start the application’s day-to-day life.
  • When implementing a major application release’s development, coexistence between the TMA and development teams is not straightforward. Integrating patches from the TMA into the development project is not easy to do either.

Infotel_Scrum Disadvantages

Scrum’s disadvantages

The Scrum solves some waterfall problems, mainly problems of opacity with regard to the customer and the project’s adaptability to customer changes. It simplifies debugging and leaves behind a reusable development plant. However, Scrum is not very relevant when it comes to the methodological framework of TMA and has some difficulties in getting development and predictive maintenance projects to coexist satisfactorily. Scrum ‘imposes’ the almost permanent presence of a client representative in the project team and has difficulty operating without regular client feedback and validation.

Kanban: Waterfall and Scrum inconvenience solutions

Instead of addressing the problem via the process of developing an application (new project / evolution), Kanban approaches the question via the application’s everyday life (the TMA) and then integrates the issues of development into its life management process. As a result, the application’s maintainability and the correction / new development priority rules are natively integrated into Kanban methodology.

Kanban’s major asset when developing a new application is to mechanically leave a viable and robust methodological framework for the application’s everyday operations. The transition between development and TMA is then ‘seamless’.

The integration of a new development project for an application driven in Kanban is facilitated by the prior existence of a TAM team organised to deliver prioritised, staggered tasks, etc. Why set up Scrum if you already have some Kanban? The cost of implementing Kanban is lower than the cost of implementing Scrum for an application already in production and which does not have a methodological framework.

Why and when to use Kanban? The keys to success

Kanban has now been successfully used by many organisations which appreciate its implementation and the way it can improve efficiency. It proves itself to be most efficient in its ability to swiftly produce and deliver tasks. The time between the user request and production start-up becomes very short. Of course, to achieve this level of efficiency, the delivery time (which in many cases does not depend on the development team) must also be very short. Positive feedback is therefore better when an ongoing delivery system is set up, indicating that the more it is developed the more efficient it will be.

Scrum remains well suited for web application development, but is not very comfortable doing maintenance with a hotfix solution. Thanks to its great flexibility of application, Kanban is able to adapt to every kind of situation.

Setting up Kanban can also take a certain time, as much as several months before any real benefits can be seen. It is therefore preferable to choose a very structured method like Scrum for a short-term project with a new team.


There is no perfect formula, so the best solution is to use the best aspects of each method. Kanban specialists chose to adopt a number of items from Scrum methodology some time ago, in order to improve their solution and make Kanban the undisputed champion of development methods (this is the authors’ personal opinion). Kanban can intelligently recover the following Scrum principles:

  • Ritualization of the ‘Daily meeting’ to give the team an overview of the project in hand.
  • Method of assessing the workload of each activity (planning poker).

Infotel_Scrum vs Kanban vs ScrumBan