Kanban Board Maps Task to time.
用看板图为团队将任务映射到时间。
This is not the case with Kanban.
有了看板，这不再是问题。
Figure 1 Kanban and Pull production.
图1看板和拉动式生产。
那么，看板到底是什么呢？
Figure 2 Kanban Exchange in the store.
图2仓库中的看板交换。
看板太简单了！
Kanban Board as Main Information radiator.
用看板图作为主要的信息辐射体。
Table 1 Kanban combination of Time and Task
用看板结合时间与任务
A Kanban should accompany each item, every time.
每件产品每时每刻都要与看板相伴。
Figure 1 is an abstract model of a Kanban system.
图1是看板系统的抽象模型。
Not much, since Kanban is a pretty simple system.
其实并没有太多改变，因为看板方法本身就是一种非常简单的系统。
Kanban Empowerment, Trust, Mutual Respect, Team Spirit.
看板授权，信任，相互尊重，团队协作精神。
Off the top of my head, 5 reasons to use Kanban approach.
在我的脑海中，使用看板方式的5个最佳理由是。
So here are two types of Kanban working together in Figure 1.
那么在图1中有两种类型的看板一同工作。
We tested around a bit with Kanban, but never really took off.
我们只是试验了一下但并没有真正用在工作中。
Three viewpoints and Kanban Board as a mapping of Task to time.
概观——三种视角以及用看板图将任务映射到时间。
Since when did my marriage have anything to do with her kanban?
什么时候开始，我结不结婚竟然关系到我妈的招牌？
Q: How long did it take you to get this Kanban process up and going?
Q：你们用了多长时间让这个看板流程运转起来？
Thus, just like any other process, Kanban too has its reasons for adoption.
因此，正如其他任何一种流程，应用看板也有其原因。
We chose Kanban because it was flexible and had a relatively small implementation cost.
我们选择看板方法是因为它灵活而且实施成本相对较低。
As you see, there are several ways to apply the Kanban concept to software development.
如你所见，将看板的概念应用于软件开发有许多方式。
As you see, there are several ways to apply the Kanban concept to software development.
如你所见，将看板的概念应用于软件开发有许多方式。
应用推荐