Kanban in APPPM
(→Abstract) |
|||
| Line 5: | Line 5: | ||
In any successful project, programme or portfolio, the weight of planning and management is vital to deal with the various types of complexities whether seen from technical, time, goal, social, organisational or legal perspectives. When establishing a complexity management plan to treat a time issue, the team should be under the guidance of a schedule, which allows clarification for issues such as when tasks have to be carried out. For this purpose, various methodologies are used, among them the '''Kanban philosophy'''. | In any successful project, programme or portfolio, the weight of planning and management is vital to deal with the various types of complexities whether seen from technical, time, goal, social, organisational or legal perspectives. When establishing a complexity management plan to treat a time issue, the team should be under the guidance of a schedule, which allows clarification for issues such as when tasks have to be carried out. For this purpose, various methodologies are used, among them the '''Kanban philosophy'''. | ||
| − | Kanban, translated to "visual cards" or "billboard" from Japanese, is a scheduling methodology in which you can maximise the productivity of a team by the optimisation of idle time of each process that results in the completion of a unit or project. It was introduced in 1947, by <span class="plainlinks">[https://en.wikipedia.org/wiki/Taiichi_Ohno '''Taiichi Ohno''']</span>, who was an industrial engineer working for <span class="plainlinks">[https://en.wikipedia.org/wiki/Toyota '''Toyota''']</span> and father of the '''Toyota production system'''[https://kanbanzone.com/resources/lean/toyota-production-system/]. It was created to avoid waste, commonly known as '''Muda'''[https://kanbanzone.com/resources/lean/toyota-production-system/muda-mura-muri/] in project management terminology, consequently increasing efficiency in product manufacturing chains. Kanban allows the team to visually target and remove bottlenecks, identified by avoiding these wastes, to reduce queuing times and increase throughput. It was conceived in such a way that its use was directly related to ''' | + | Kanban, translated to "visual cards" or "billboard" from Japanese, is a scheduling methodology in which you can maximise the productivity of a team by the optimisation of idle time of each process that results in the completion of a unit or project. It was introduced in 1947, by <span class="plainlinks">[https://en.wikipedia.org/wiki/Taiichi_Ohno '''Taiichi Ohno''']</span>, who was an industrial engineer working for <span class="plainlinks">[https://en.wikipedia.org/wiki/Toyota '''Toyota''']</span> and father of the '''Toyota production system'''[https://kanbanzone.com/resources/lean/toyota-production-system/]. It was created to avoid waste, commonly known as '''Muda'''[https://kanbanzone.com/resources/lean/toyota-production-system/muda-mura-muri/] in project management terminology, consequently increasing efficiency in product manufacturing chains. Kanban allows the team to visually target and remove bottlenecks, identified by avoiding these wastes, to reduce queuing times and increase throughput. It was conceived in such a way that its use was directly related to <span class="plainlinks">[https://en.wikipedia.org/wiki/Lean_manufacturing '''Lean Manufacturing''']</span> systems and the achievement of <span class="plainlinks">[https://en.wikipedia.org/wiki/Just-in-time_manufacturing'''JIT (just-in-time)''']</span> delivery approach. |
This article will first provide an introduction and context to the concept of the Kanban methodology. This is followed by an explanation of its use and applications. Thirdly and finally, it will address its limitations, establishing its strengths and weaknesses. | This article will first provide an introduction and context to the concept of the Kanban methodology. This is followed by an explanation of its use and applications. Thirdly and finally, it will address its limitations, establishing its strengths and weaknesses. | ||
Revision as of 16:58, 11 February 2021
'draft'
Contents |
Abstract
In any successful project, programme or portfolio, the weight of planning and management is vital to deal with the various types of complexities whether seen from technical, time, goal, social, organisational or legal perspectives. When establishing a complexity management plan to treat a time issue, the team should be under the guidance of a schedule, which allows clarification for issues such as when tasks have to be carried out. For this purpose, various methodologies are used, among them the Kanban philosophy.
Kanban, translated to "visual cards" or "billboard" from Japanese, is a scheduling methodology in which you can maximise the productivity of a team by the optimisation of idle time of each process that results in the completion of a unit or project. It was introduced in 1947, by Taiichi Ohno, who was an industrial engineer working for Toyota and father of the Toyota production system[1]. It was created to avoid waste, commonly known as Muda[2] in project management terminology, consequently increasing efficiency in product manufacturing chains. Kanban allows the team to visually target and remove bottlenecks, identified by avoiding these wastes, to reduce queuing times and increase throughput. It was conceived in such a way that its use was directly related to Lean Manufacturing systems and the achievement of JIT (just-in-time) delivery approach.
This article will first provide an introduction and context to the concept of the Kanban methodology. This is followed by an explanation of its use and applications. Thirdly and finally, it will address its limitations, establishing its strengths and weaknesses.
Kanban and its context
Applications
Limitations
References
