Q: How did you stumble upon Kanban?
Q：你是怎么发现看板方法的呢？
Use Kanban to Manage Cross-Team workflow.
使用看板来管理跨团队的工作流程。
Figure 3 Properties and Effects of kanban.
图3看板的特性和作用。
Figure 4 Kanban Mechanism of Limiting wip.
图4限定在制品数量的看板机制。
KSSE - Kanban System for Sustaining engineering.
KSSE——持续工程的看板系统。
Figure 8 Portable Agile Kanban (" Kanban-nano ").
图8便携式敏捷看板(“看板nano”)。
Some even have Kanban boards for family activities!
一些人甚至有家庭活动的看板！
It USES a kanban system to pipeline change requests (CRs).
它用一个看板系统来追踪变更请求(Change Request,CRs)。
"Kanban," in Japanese means, loosely translated, 'card or sign'.
“看板”在日语里的大意是“卡片”或者“标志”的意思。
Explains Kanban in TPS and how it works as a pull process mechanism.
解释了TPS中的看板，及看板如何作为“拉”处理机制运作。
It is easy to assume that Kanban is the center of TPS, but it is not.
读者很容易假定看板是整个TPS的中心，但其实并不是。
There is a strict discipline of running Kanban, called "six rules of Kanban"
对于看板的运转有着严格的规定——被称作“看板六准则”
"Speed" - Kanban communicates the timing and the amount of next production.
“速度”——通过看板传达下次生产的时机和数量。
The kanban system also frees us from the constraints of time-boxed iterations.
同样，看板系统使我们可以不受固定迭代周期的限制。
There are different ways to track progress like spreadsheets or Kanban boards.
跟踪进度有不同的方法，例如电子表格或看板。
When scaling Agile to Lean using Kanban, what should one Kanban card represent?
当通过看板从敏捷放大到精益时，一张看板卡应该代表什么东西呢？
They liked this portable small Kanban system very much and named it "Kanban-nano".
他们很喜欢这个便携式小型看板系统，并命名为“看板nano”。
Here, a Kanban system is used in a traditional waterfall development model but with a flow.
在这里，看板系统被用于带有流程的传统瀑布开发模型。
The example "Agile Kanban" in Figure 5 is a work breakdown, and it works well within the team.
图5中“敏捷看板”的例子是一个工作的分解，它在团队内部工作良好。
So the two goals are conflicting, and Kanban can be seen as a strategy to resolve the dilemma.
这样看来这两个目标是相矛盾的，而看板正被看作是解决这个难题的策略。
Customer (Downstream) processes withdraw items in the precise amounts specified on the Kanban.
客户(下游)工序精确按照看板上指示的数量领取产品。
Kanban is newer, and I'm not aware of any teams that are really pursuing SOA under a Kanban model.
看板相对较新，我还不知道有哪个团队真的在看板模型下从事SOA的。
Here, feature Kanban is called feature breakdown structure and feature planning on whiteboard.
在这里，特性看板被称为白板上的特性分解结构和特性计划。
Perfect flow visualization - Kanban Board provides a very clear view on current work in progress.
完美的流可视化 ——看板给当前未完成的工作提供了一个非常清晰的视图。
The example "Sustaining Kanban" in Figure 6 is a feature breakdown and one card represents an MMF.
图6中“持续看板”的例子是一个功能的分解并且一张卡片代表一个MMF。
An Agile team should not switch to Kanban just because an existing process is not working from them.
一个敏捷团队不应该仅仅因为在他们看来现有流程不合适，就切换到看板。
I call this "Lean + Agile Kanban", and it can be combined with "Agile Kanban", as shown the next example.
我叫它为“精益+敏捷看板”，如下一个例子展示的那样它可以与“敏捷看板”相结合。
Looking closely at Kanban Boards, you can find three things expressed on them - time, task, and team.
仔细观察看板图，你会发现上面表达了三项主题——时间、任务和团队。
"Sustaining Kanban" is another type, enabling small-batch maintenance work to flow between several states.
“持续看板”是另一种类型的看板，能够让小批量的维护工作在几个状态之间流转。
Secondly I look around our software development projects and point out examples of Kanban applications.
其次，我将环顾我们的软件开发项目并指出看板应用的例子。
应用推荐