Kanban is not a software development lifecycle methodology or an

approach to project management. It requires that some process is

already in place so that Kanban can be applied to incrementally
change the underlying process.

 Single card Kanban systems

In a single-card Kanban system, parts are produced and bought

according to a daily schedule, and deliveries to the user are controlled
by a withdrawal Kanban.

In effect, the single-card system is a push system for production

coupled with a pull system for delivery to the point of use. Single-card
Kanban controls deliveries very tightly, so that the using work centre
never has more than a container or two of parts and the stock point
serving the work centre is eliminated.

Single-card systems work well in companies in which it is relatively

easy to associate the required quantity and timing of component
parts with the schedule of end products. These are usually companies
with a relatively small range of end products, or products which are
not subject to rapid, unexpected changes in demand levels.

Advantages:
1. Start with what you do now. The Kanban method does not dictate
specific processes. Kanban can be used to examine existing
processes, but radical changes don’t need to be made immediately.
 2. Agree to pursue incremental change. By its nature, the Kanban
method supports continuous small changes to whatever current system
is in place. Wide-ranging, radical changes are discouraged because they
are inevitably met with resistance.
3. Respect current process, roles, responsibilities and titles. Kanban
doesn’t prohibit or mandate change and recognizes that the present
state of organizations have value. Kanban-style incremental change
creates broader implementation support because small corrections are
more palatable than complete alterations to process.
4. Encourage acts of leadership at all levels. Kaizen, or a mindset of
continual improvement by everyone in the organization, is supported.
The concept is that great ideas can be generated from anyone on the
team, not just management.
5. Limit work in progress (WIP). This is a cornerstone of Kanban.
Limiting WIP forces the team to focus on a limited number of tasks and
work to completion. This spotlights where work is being obstructed in the
delivery pipeline before a situation becomes critical.
6. Manage flow. Based on the data gathered on cycle time and other
agreed upon metrics, and using information about the current state of
work on the board, Kanban helps visually track and manage tasks to
deliver maximum value.