Kanban in Project Management
From apppm
(Difference between revisions)
| Line 1: | Line 1: | ||
Kanban|看板 directly translates to signboard from Japanese. The Kanban system was originally a inventory-control system developed by developed by Taiichi Ohno, an industrial engineer at Toyota to reduce the waste (muda) in the production line and by that improve the manufacturing efficiency. | Kanban|看板 directly translates to signboard from Japanese. The Kanban system was originally a inventory-control system developed by developed by Taiichi Ohno, an industrial engineer at Toyota to reduce the waste (muda) in the production line and by that improve the manufacturing efficiency. | ||
The Kanban system is with some alterations applied as an agile project management tool. The basis of this concept is to have a board with cards attached. Different parts on the board represent several stages of the development that all tasks go through. The cards represent the different tasks in the project, and move from left to right on the board. The board can be set-up and divided however the user like, nonetheless the main concept is always the same and can be summarized by these six points | The Kanban system is with some alterations applied as an agile project management tool. The basis of this concept is to have a board with cards attached. Different parts on the board represent several stages of the development that all tasks go through. The cards represent the different tasks in the project, and move from left to right on the board. The board can be set-up and divided however the user like, nonetheless the main concept is always the same and can be summarized by these six points | ||
| − | Limit WIP (work in process): The board is divided in parts, and each part can only have a set number of tasks, thus this don't need to be the same for every part. This is true for all parts except the “start” and “finished” part, which is always unlimited | + | #Limit WIP (work in process): The board is divided in parts, and each part can only have a set number of tasks, thus this don't need to be the same for every part. This is true for all parts except the “start” and “finished” part, which is always unlimited |
| − | Cards : Each task is represented by a card (post-it note or similar) | + | #Cards : Each task is represented by a card (post-it note or similar) |
| − | Flow: The tasks on the board are moved from left to right between the different parts. The person performing the task is moving the post-it | + | #Flow: The tasks on the board are moved from left to right between the different parts. The person performing the task is moving the post-it |
| − | Team: The team working with the tasks agree on some rules for when a task can be set as finished. | + | #Team: The team working with the tasks agree on some rules for when a task can be set as finished. |
| − | Kaizen (constant improvement) 1: The team working with the Kanban board have to get together on a regular basis to analyze the flow. Focusing on tasks that are stuck on the board | + | #Kaizen (constant improvement) 1: The team working with the Kanban board have to get together on a regular basis to analyze the flow. Focusing on tasks that are stuck on the board |
| − | Kaizen (constant improvement) 2: There is no Kanban police - and if you need to alter your board or break your rules that's ok, but let the rest of your team know. | + | #Kaizen (constant improvement) 2: There is no Kanban police - and if you need to alter your board or break your rules that's ok, but let the rest of your team know. |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
Revision as of 07:47, 8 September 2016
Kanban|看板 directly translates to signboard from Japanese. The Kanban system was originally a inventory-control system developed by developed by Taiichi Ohno, an industrial engineer at Toyota to reduce the waste (muda) in the production line and by that improve the manufacturing efficiency. The Kanban system is with some alterations applied as an agile project management tool. The basis of this concept is to have a board with cards attached. Different parts on the board represent several stages of the development that all tasks go through. The cards represent the different tasks in the project, and move from left to right on the board. The board can be set-up and divided however the user like, nonetheless the main concept is always the same and can be summarized by these six points
- Limit WIP (work in process): The board is divided in parts, and each part can only have a set number of tasks, thus this don't need to be the same for every part. This is true for all parts except the “start” and “finished” part, which is always unlimited
- Cards : Each task is represented by a card (post-it note or similar)
- Flow: The tasks on the board are moved from left to right between the different parts. The person performing the task is moving the post-it
- Team: The team working with the tasks agree on some rules for when a task can be set as finished.
- Kaizen (constant improvement) 1: The team working with the Kanban board have to get together on a regular basis to analyze the flow. Focusing on tasks that are stuck on the board
- Kaizen (constant improvement) 2: There is no Kanban police - and if you need to alter your board or break your rules that's ok, but let the rest of your team know.
