Kanban: a project management framework
Contents |
Abstract
Over the last decades important new approaches have appeared in operations planning and control of production systems.[1] Kanban is a visual system first developed by Taiichi Ohno for Toyota during the 1940s in Japan. The original aim of this tool was gaining control in processes and make their workflow more manageable. The efficiency of daily activities within industrial processes represents a challenge for every production company. In fact, this tool is not only applicable to production processes, but also to every project taking place in almost every business function (operations, marketing, recruitment, business expansion...). The target of Kanban is achieved by the implementation of certain activities or practices that, if well implemented, will gradually help improving the workflow. Its improvement implies not only a reduction of lead time and a better organization of the activities, but also a reduction of waste, a more value-added approach for the customer and a better predictability for future scenarios. These benefits are crucial in today's market, characterized for experimenting changes and competitiveness in a fast-paced environment.
The aim of this article is to give an approach of this tool analyzing it from its origin and definition, going through its possibilities in its application and stating the advantages and shortcomings that this methodology offers. Also, the relation of this tool with other methodologies such as SCRUM would be presented in order to give a more complete perspective of the topic.
Main Concept
Origin of Kanban
Description of the history of Kanban, explaining its origins within the Toyota production system.
Definition
Definition of the concept from a theoretical point of view.
Agile methodologies
Here I am going to state different important definitions about concepts that are important to understand the context of the Kanban methodology. After the definitions, a short relation of the concepts with project management would be stated. As a further relation of Kanban with Project management will be done in the application section, I will no develop it too much here. These are the definitions to include:
- Agile: group of methodologies used in project management (specially in software development) consisting on an iterative development where solutions and demands are developed through the collaboration of multi-functional teams under an organized and collaborative teamwork philosophy. - Scrum: --- (important to mention as it is another commonly used agile methodology and can be also complemented with Kanban)
The 4 principles
Description of the 4 principles of Kanban.
Application
Methodology
Defining the practices that the tool involves: kanban cards, the framework...
Kanban and Project Management
Kanban and Scrum
DRelation of Kanban with Scrum. I will point the differences between them from the project management point of view.
Advantages
Description of the main advantages of applying this tool, based on the theory and from a project management point of view.
Shortcomings
Description of the main limitations of applying this tool, based on the theory and from a project management point of view.
References
- ↑ R.J. Boucherie, X. Chao and M. Miyazawa, "Arrival first queueing networks with applications in kanban production systems", 2001
Some of the articles and books I will use for references: -ADAPTATION OF FLEXIBLE PROJECTMANAGEMENT MODELS BASED ON SCRUMAND KANBAN TECHNOLOGIES, Popova O. -A Theoretical Framework for Improving Software, Hamzah Alaidaros, Mazni Omar, and Rohaida Romli. Project Monitoring Task of Agile Kanban Method -Overview of Kanban systems, CHUN-CHE HUANG and ANDREW KUSIAK. Made by Guillermo Roig Pitarch (s212754)
