Keeping the complete history of the wip.
保存WIP的完整历史。
Figure 4 Kanban Mechanism of Limiting wip.
图4限定在制品数量的看板机制。
This table contains information not kept in the wip.
该表包含了未在WIP中保存的信息。
This table contains information not available in the wip.
该表包含了无法在WIP中获得的信息。
Better process control — they keep continuous flow while limiting wip.
更优的工序控制——在限制在制品数量的同时保持连续流通。
Managing the size of the WIP History table
管理WIP历史表的大小
The complete process that extends the WIP capabilities.
扩展WIP功能的完整过程。
In this example, WIP can be limited by defining the size of each area.
在这里例子中，通过设定每一个区域的大小可以限制在制品的数量。
Mining the data in the table containing the complete history of the WIP
挖掘包含WIP完整历史的表中的数据
For each edition maintained in the WIP, its most current status is displayed.
对于维护在WIP中的每个版本，显示的是其最当前的状态。
A record about the editions canceled, even if they have been purged from the WIP.
被取消的版本的记录，即使它们已从WIP中清除。
A WIP of 1 was set for this lane, since we want to discourage the use of this category.
这个泳道的并行任务限制值设为1，因为我们希望少用这个类别。
A record about each edition that is being removed from the WIP, with the time of removal.
正从WIP中被删除的每个版本的有关记录，其中包含了删除的时间。
Specify a schedule for the WIP History process (e.g., Add a Daily schedule for execution).
指定对于WIP History过程的调度（例如，添加每天的执行调度）。
This Kanban Board helps visually signal tasks and limit WIP (tasks actively being worked on).
这样的看板面板有利于可视化地通知任务并限制在制品（处理中的任务）数量。
The right-hand side of this graph explains how it minimizes WIP while sustaining continuous flow.
图表右侧说明了如何在维持连续流通的同时，最大限度地减少在制品。
These records about scheduled editions already executed are deleted from the WIP after execution.
而这些关于已经执行的被调度版本的记录在其执行之后就已从WIP中删除。
Then the WIP administrator defined 2 new schedules for that step: one recurring, and the other a one-time only.
然后，WIP管理员将为该步骤定义2个新的调度：一个重复发生，而另一个则只运行一次。
Kanban support: The planning tools now support Kanban including a story board and Work-In-Progress (WIP) limits.
看板支持：规划工具现在支持看板，包括一个故事版(story board)和在制品(WIP)限制。
The first mechanism only refers to the amount of WIP, but this second refers to the flow, its direction and speed.
第一个机制仅仅涉及到在制品的数量，而第二个则涉及到流程——流程的方向和速度。
Now, the various tables in the WIP History process are being populated and updated automatically on a regular basis.
现在，将定期自动地填充和更新WIP History过程中的各种表。
In other words, the WIP does not maintain a full history of each edition, nor all the statuses that an edition went through.
换言之，WIP不会维护每个版本的全部历史记录和版本经过的所有状态。
Any record being updated in the WIP: i.e., any time the edition record is being updated due to a change in the edition status.
在WIP中更新的记录：即每次由于版本状态更改而更新版本记录时。
The amount of information stored in the WIP can grow quite significantly, especially if the amount of steps run daily is large.
WIP中存储的信息量可能会极快地增长，特别是在每天运行很多步骤的情况下。
"Limits WIP", "Continuous Flow" and "Pull" properties are not attained by the Agile Kanban example by itself, shown in Figure 5.
图5所示的敏捷看板例子本身并没有实现“限制在制品的数量”、“连续流通”和“拉动式”特性。
Since these tables keep growing, the WIP operator needs to periodically remove from these tables the information that is obsolete.
由于这些表持续增长，所以wip操作员需要定期将已废弃的信息从这些表中删除。
Failed editions may be purged safely from the WIP, since there is no data that was filled in the target table for a failed edition.
可以将失败的版本从WIP中安全地清除，因为一个失败版本没有向目标表填充任何数据。
应用推荐