|
m Date maintenance tags and general fixes: build 570:
|
mNo edit summary
|
||
| Line 7: | Line 7: | ||
Kanban is Lean and has been around for 50 years and has shown to be successful. Things are seen as a flow without iterations. Not many rules. It is just a focus on reducing work in progress, strict prioritization and limiting demand after capacity. Besides that you have the normal Lean principles of: |
Kanban is Lean and has been around for 50 years and has shown to be successful. Things are seen as a flow without iterations. Not many rules. It is just a focus on reducing work in progress, strict prioritization and limiting demand after capacity. Besides that you have the normal Lean principles of: |
||
|
* Quality |
||
|
* Just-in-time (decisions and facts just when they are needed) |
||
|
* Short lead-time (quickly from concept to cash), |
||
|
* Kaizen (continuous improvement) |
||
|
* Minimizing waste (everything that is not adding value to the customer) |
||
No meetings if it is not adding value to the customer. Most of those things are fine with Scrum but I can sometimes think Scrum has some waste. Here I will mention some areas where Scrum practices might be waste. |
No meetings if it is not adding value to the customer. Most of those things are fine with Scrum but I can sometimes think Scrum has some waste. Here I will mention some areas where Scrum practices might be waste. |
||
 |
This article uses first-person (I, we) or second-person (you) inappropriately. Please help rewrite it to use a more formal, encyclopedic tone. (November 2010)
|
Kanban is an iterative, incremental methodology for project management often seen in agile software development.
Kanban is based on the principles of Kanban, a concept related to lean and just-in-time (JIT) production. According to Taiichi Ohno, the man credited with developing JIT, Kanban is one means through which JIT is achieved.[1]
Kanban is based on Lean principles and is often seen as a simpler version of Scrum (development). List of software development philosophies Kanban is Lean and has been around for 50 years and has shown to be successful. Things are seen as a flow without iterations. Not many rules. It is just a focus on reducing work in progress, strict prioritization and limiting demand after capacity. Besides that you have the normal Lean principles of:
No meetings if it is not adding value to the customer. Most of those things are fine with Scrum but I can sometimes think Scrum has some waste. Here I will mention some areas where Scrum practices might be waste.
Kanban was intended for management of software development projects. It can be used to run software maintenance teams, or as a general project/program management approach.
Kanban in manufacturing traces its history to the mid-1900s, the birth of lean manufacturing, and the Toyota Production System. In his 1978 book by the same name, Taiichi_Ohno wrote: The two pillars of the Toyota production system are just-in-time and automation with a human touch, or autonomation. The tool used to operate the system is kanban. [Poppendieck07] Mary and Tom Poppendieck, "Implementing Lean Software Development", 2006 Addison-Wesley. Explains Kanban in lean and how it works as a pull process mechanism. Note: Unsure when Kanban was first referenced in terms of specific Agile software development
