Q 706. Is Kanban more effective than traditional scheduling methods like Gantt charts in Lean projects?

 

Note for website visitors -

• This platform hosts two weekly questions, one on Tuesday and the other on Friday. 
• All previous questions can be found here: https://www.benchmarksixsigma.com/forum/lean-six-sigma-business-excellence-questions/. 
• To participate in the current question, please visit the forum homepage at https://www.benchmarksixsigma.com/forum/.
• The question will be open until Tuesday or Friday at 5 PM Indian Standard Time, depending on the launch day. 
• Responses will not be visible until they are reviewed, and only non-plagiarised answers with less than 5-10% plagiarism will be approved. 
• If you are unsure about plagiarism, please check your answer using a plagiarism checker tool such as https://smallseotools.com/plagiarism-checker/ before submitting. 
• All correct answers shall be published, and the top-rated answer will be displayed first. The author will receive an honorable mention in our Business Excellence dictionary at https://www.benchmarksixsigma.com/forum/business-excellence-dictionary-glossary/ along with the related term.

• Some people seem to be using AI platforms to find forum answers. This is a risky approach as AI responses are error prone as our questions are application-oriented (they are never straightforward). Have a look at this funny example - https://www.benchmarksixsigma.com/forum/topic/39458-using-ai-to-respond-to-forum-questions/

• We also use an AI content detector at https://quillbot.com/ai-content-detector. Only answers with less than 45-50% AI-generated content will be approved.

Kanban is a visual tool used to control, manage and review the flow of work within a process/line/lifecycle of a project/operation through the usage of Kanban cards which would contain details such as status of work, from which station it has come, at what time, quantity, who is supposed to take it up for further processing, etc. It's literal meaning in Japanese is roughly "cards, which you can see". It's purpose is to ensure a pull effect on the work-in-progress(WIP) to ensure that capital tied to WIP is kept at a minimum and the MURA( uneveneness- in this case variation in work flow)  and MURI (overburden-in this case backlog of WIP) are reduced so that MUDA (waste- in this case rejections/rework) is not generated.

 

Gantt charts are also a visual tool which is used for preparing plans of activities within a project as a horizontal bar graph plotted against a timeline. The progress of the project is tracked against the vertical bars using embedded bars or other bars in different color to showcase the amount of work completed against the planned timeline. It is used to visually observe the actual progress of the project against the planned timeline.

 

Both are powerful tools for visually assessing the progress of the work, the effectiveness of one over the other in case of applicability towards LEAN projects depends on the type of project and on the purpose for tracking of the same.

 

Example: -

Suppose, the LEAN project is undertaken aimed towards addressing the losses and leakages occurring through the sub- steps/sub-operations of clear and well defined processes which have been stable over a period of time in order to improve the same or take it to next level of optimization. In such cases Gantt charts wouldn't be able to track the losses but a Kanban system would be able to capture waiting time/quality losses within it's cards and throw up opportunities for improvement. Thereby, making Kanban a better option in this case.

However, the progress of the projects also need to be tracked against a timeline in order to ensure the resources spent on these projects are optimized and benefits are actually obtained. In this case utilization of the Gantt chart makes more sense.

We can say that, though not necessarily always, Kanban is usually more effective for LEAN projects which are : -

1. Which have a well defined setup with lot of variabilities in demands, priorities, interlinked sub-operations, lot of work-in-progress and repetitive operations . In such cases Kanban can help identify and optimize the bottleneck operations. 

2. Where the goal is to identify the gaps in the flow of work, details of losses are to be identified, 

 

And Gantt charts are more effective for LEAN projects which are : -

1. Have set defined timelines for completion, variations within operations are low, lesser no. of parallel & complex activities are involved. In such cases Gantt charts can help identify the operations which is taking more time to complete against the timeline.

2. Where the goal is to identify the gaps in the project timelines and focus is to improve the timelines.

 

Kanban & Gantt charts have their own strength and can be effective in Lean Six Sigma project for different context.

Kanban Board: Kanban board is project management tool which help team to visualize & track the progress of the tasks and manage their work

Features of Kanban Board:

• Visual Representation: Kanban board is effective in  visually manage the work. It helps in understanding the status of task briefly
• Flexibility: It is an Agile tool hence it’s highly adaptive & flexible to changes. Tasks can be added at any point in time, priorities can be changed as per requirements without disturbing the overall flow of the work
• Focus on the flow: This emphasizes on the flow of the work to reduce the bottleneck, which leads to efficient processes

Gantt Chart: It is a kind of bar chart to illustrate the project timelines or schedule

Features of Gantt Chart:

• Detailed Planning: It is an excellent project planning tool. It illustrates the start date, end date of each task or phases and call out the dependencies as well
• Visual representation of timeliness: It helps in clear understanding of project timeline and actual progress can be tracked against the target timelines
• Resource management: It helps in effectively manage the resources to meet the deadline set at the beginning of the project
• Predictability: It helps in anticipating whether the project is going to meet the timelines set earlier and Risks can be identified before hand

Kanban is often more effective due to its flexibilities to adapt changes. It focuses on continuous improvement. This aligns well with the Lean principles and helps in reducing waste and make process more effective and efficient. However, Gantt chart is more effective where timeline management is required, especially where there is clear deadlines and dependencies.

 

Ultimately, the choice between Kanban and Gantt charts depends on the specific needs and nature of your project. Some teams even use a combination of both to leverage the strengths of each method.

The Gantt Chart usually provides basic tracking of the status across various stages but not the detailed aspects of project management.

 

For Example, if we are doing a Business Process Management Lean Project, the real time view of the status, managing change management (integration of Kanban board within Jira), and flagging out constraints or challenges would be of paramount importance. Various visual representation features in Kanban boards like tracking Kaizen Events, elimination of waste, WIP items tracking, collaboration and metric management are essential value adds. 

 

Consider a scenario, where a major change management is required with multiple stakeholders approval and subsequent modelling. The Kanban boards will add immense value in such large scale projects for effective change management.

When it comes to Lean projects, Gantt charts might still have an advantage as they can be used to plan out long-term and structured projects as well as provide a detailed view of the resources and timelines, however, Kanban boards may be more effective when the focus is on flexibility, continuous improvement, and managing workflow efficiency.

 

A comparison between Kanban and Gantt charts is shown in the table below:

 

Feature/Aspect	Kanban	Gantt Chart
Flexibility	Highly flexible; adapts to changes easily in real-time.	Less flexible; focuses on pre-planned schedules and milestones.
Visual Workflow	Displays tasks visually on a board, focusing on WIP and task flow.	Displays tasks in a timeline format, focusing on start/end dates.
Task Prioritization	Tasks are pulled based on priority and availability; flow-based.	Tasks are scheduled in advance with set deadlines; time-based.
Focus on Continuous Improvement	Encourages constant evaluation of processes for optimization.	Less emphasis on ongoing improvement; focuses on following a structured plan.
Real-time Progress Monitoring	Always reflects the current state of tasks; real-time updates.	Requires periodic updates; progress tied to pre-set deadlines.
Managing Uncertainty	Handles uncertainty well by adapting to changing priorities and demands.	Struggles with uncertainty; changes in scope may require rescheduling.
Complexity and Dependencies	Works well for simpler projects with fewer dependencies.	Ideal for projects with multiple dependencies and long-term planning.
Resource Allocation	Focuses on team capacity and flow, not specific resource scheduling.	Provides detailed timelines for resource allocation and scheduling.
Ideal For	Ongoing, incremental work or projects requiring flexibility.	Structured, deadline-driven projects with defined milestones.

  

The above table displays the advantages and disadvantages of Kanban boards and Gantt charts. While Kanban boards might be beneficial when the emphasis is on flexibility, workflow management, and continuous improvement, Gantt charts are can be used while planning large, complex, and structured projects with fixed timelines. Ultimately, the choice between them should be guided by the needs and nature of the project as well as the working style of the team involved.

Akkul Dhand has provided the best answer to this question. The other answers are also a must read.