What
is KANBAN
Kanban is a new technique for managing a software development
process in a highly efficient way. Kanban underpins Toyota's
"just-in-time" (JIT) production system. It is first developed and
used by them. Kanban is a visual signal that’s used to trigger an action. As we
know the word kanban is Japanese.
Roughly translated, it means “card you can see.”
Toyota introduced and refined the use of kanban in a relay system to standardize the flow of parts in their
production lines in the 1950s. Kanban process starts with the customer’s
order and follows production downstream. Because all requests for parts
are pulled from the order, kanban is
sometimes referred to as a "pull" system.
In software development process, it can be thought of as a
pipeline with feature requests entering one end and improved software emerging
from the other end. In simple terms the requirement comes in simple form from
the user and finally comes with a finished product or services or part of
service.
We can divide the input and output as below mentioned category:-
1. Analyze the requirements
2. Develop the code
3. Test it
works.
Simply we make use of a Board generally called the KanaBan Board
which can have the representation as
There are six generally accepted rules for kanban:
1.
Downstream processes may only withdraw items in the precise
amounts specified on the kanban.
2. Upstream processes may only send items downstream in the precise amounts and sequences specified by the kanban.
3. No items are made or moved without a kanban.
4. A kanban must accompany each item at all times.
5. Defects and incorrect amounts are never sent to the next downstream process.
6. The number of kanbans should be monitored carefully to reveal problems and opportunities for improvement.
2. Upstream processes may only send items downstream in the precise amounts and sequences specified by the kanban.
3. No items are made or moved without a kanban.
4. A kanban must accompany each item at all times.
5. Defects and incorrect amounts are never sent to the next downstream process.
6. The number of kanbans should be monitored carefully to reveal problems and opportunities for improvement.
Thanks
Anil Kumar Pandey
Microsoft MVP, Microsoft MCC, DNS MVM
Anil Kumar Pandey
Microsoft MVP, Microsoft MCC, DNS MVM
No comments:
Post a Comment