Kanban is a method that enables teams to visualize their work. By doing so, they handle better bottlenecks, waste, and chaos because people benefit from the power of visual information.
It dates back to the first half of the 20th century when Taiich Ohno applied it in Toyota Production System (TPS). After that, many other fields, especially software and product development, applied the Kanban logic.
You can design a Kanban-based process following five principles:
- Visualize your workflow using a Kanban board and cards.
- Limit the amount of work in process (WIP) to avoid multitasking.
- Manage the flow of work and monitor performance. Implement necessary improvements, and fix problems as they occur.
- Set the rules and guidelines of your flow.
- Improve continuously and collaboratively.
You can mix Kanban with Agile and Lean. Since Kanban is a method to manage workflow, any practices that can be thought of as steps or conditions of completing steps fit with Kanban.
From Reactive Planning Model to Natural Planning Model
Until some point, the project was manageable, but after some feature requests and bug reports, it became unfeasible. In addition, almost every bug fix or feature implementation broke other "uncorrelated" parts of the application. That slowed us down a lot because our client and his customers were using the software, and we had to rush to fix the new bugs (yes, we didn't have testing at that time).