Introduction to Kanban
The concept of Kanban boards traces its origin back to the 1940s when Toyota introduced it on the factory floor. Toyota automotive realized that their production lines were a lot less efficient when compared to their American counterparts. The aim behind introducing this new method of production was to control inventory and improve the speed of delivery while maintaining the highest standards of production quality.
While the concept of Kanban was initially successful on the production line, it slowly started to make its way into other delivery systems.
Kanban for Software Development
In the late 90s and early 2000s, there was a paradigm change happening in software development circles. People began to realise that the traditional top-down approach to building and shipping software was highly inefficient.
There was a new focus of incremental delivery and quick customer validation. The days of having large, perfectly scoped projects was coming to an end.
This is how the concept of Kanban slowly found its way to software development teams. The focus was now on agility and getting features out quickly to be market-tested and validated.
While Kanban is a widely adopted method for software development and delivery today, it still retains its core principles of being a process improvement methodology. Kanban principles can and has continued to be used in all kinds of processes outside software development.
Any Kanban based process revolves around some core concepts and practices.
- Start with existing processes
- Respect current roles, responsibilities and job titles.
- Pursue incremental changes
- Encourage acts of leadership at all levels
- Visualize Workflows
- Restrict Work in Progress
- Manage Flow
- Have explicit process policies
- Implement feedback and improve collaboratively