-
Notifications
You must be signed in to change notification settings - Fork 7
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #56 from HebeChe/kanban
commit for #21
- Loading branch information
Showing
2 changed files
with
78 additions
and
69 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,109 +1,118 @@ | ||
| --- | ||
| title: Kanban | ||
| templateKey: practice-page | ||
| subtitle: Visualized workflow management method to maximize efficiency and | ||
| become more agile. | ||
| date: 2020-09-15T12:02:15.251Z | ||
| authors: | ||
| - rmarting | ||
| title: 看板 | ||
| type: posts | ||
| date: 2023-05-31T12:02:15.251Z | ||
| author: | ||
| name: 译者-车晓雪 | ||
| link: https://openpracticelibrary.devopschina.org/ | ||
|
|
||
| categories: | ||
| - delivery | ||
| icon: /images/kanban-board.png | ||
| whatIs: >- | ||
| Kanban is a framework used to implement agile software development based in | ||
| the following practices: | ||
| * Visualize the workflow | ||
| * Limit Work in Progress (WIP) | ||
| * Manage flow | ||
| * Make Process Policies Explicit | ||
| * Feedback loops | ||
| Visualization is the key practice of this framework. Each Work Item (Kanban Card) is represented visually on a board (Kanban Board) allowing team members to see the status of every item across the process at any time. This frameworks helps to optimize and maximize the efficiency of the flow. | ||
| description: 看板是可视化的工作流管理方法，可实现效率最大化，同时更加敏捷。 | ||
| resources: | ||
| - name: featured-image | ||
| src: "kanban-board.png" | ||
| - name: featured-image-preview | ||
| src: "kanban-board.png" | ||
| --- | ||
|
|
||
| **Kanban Board** represents the process with a set of columns representing the different step or stages of the flow. Each **Kanban Card** represents a work item (requested or already in progress) containing valuable information about the task and its status (e.g: summary, responsible person, deadline, ...). | ||
| 可视化的价值流管理方法，最大化交付效率，让团队更为敏捷。 | ||
| <!--more--> | ||
|
|
||
| ## 难度 | ||
|
|
||
| **Work In Progress (WIP)** represent the number of work items that a team is currently working on in each stage. This limit frames the capacity of the teams's workflow at any moment and helps to identify bottlenecks. This value will help us to define a stable workflow and then a predictable delivery. | ||
| whyDo: >- | ||
| Kanban applies in situations where work arrives in an unpredictable fashion | ||
| and/or when work items should be deployed as soon as they are ready, rather | ||
| than waiting for other work items. | ||
| > 中等 | ||
| ## 参与者 | ||
| - 开发团队 | ||
| - 产品负责人 | ||
|
|
||
| ## 定义 | ||
| 看板是实现敏捷软件开发的框架，它以下述实践活动为基础： | ||
|
|
||
| This framework helps you to: | ||
| * 可视化工作流 | ||
|
|
||
| * 限制在制品 | ||
|
|
||
| * Visually see work in progress | ||
| * 管理流动 | ||
|
|
||
| * Identify bottlenecks or impediments and take steps to remove them | ||
| * 显示化流程规则 | ||
|
|
||
| * Improve team collaboration | ||
| * 反馈闭环 | ||
|
|
||
| * Increase efficiency and productivity, reducing the time it takes to take a project or user story from start to finish. | ||
| 可视化是这个框架的核心实践。每个工作项（看板卡片）都清晰地展示在看板上（看板墙），从而让团队成员可以在任何时刻看到每一个工作项在全流程中的状态。这个框架有助于优化和最大化流动效率。 | ||
|
|
||
| * Reduce waste | ||
| howTo: >- | ||
| **Who do you need?** | ||
| **看板墙** 展示了价值流动过程，每一栏代表价值流的一个步骤或者阶段。每一个**看板卡片**代表一个工作项（待办或者已经启动中），卡片包含任务、状态等有价值的信息（如：描述，责任人、交期等）。 | ||
|
|
||
| **在制品(WIP)** 指在每个阶段在制品的数量。这个限制决定了在任何时刻团队工作流的能力上限，并帮助团队识别瓶颈。它存在的意义是帮助团队建立一个稳定的工作流，继而达成可预测的交付。 | ||
|
|
||
| Kanban involves the whole team working on software development, delivery and/or deployment, Product Owners and other stakeholders with a knowledge about the process. Also a Facilitator could be useful if the team is new to this framework. | ||
| ## 应用场景 | ||
| 看板适用于团队不定期收到需求的业务场景，而且/或者需求一旦完成期望立即部署，而不是等待其他需求完成后一起部署。 | ||
|
|
||
| 这个框架可以帮助你： | ||
| * 可视化在制品 | ||
|
|
||
| **What do you need?** | ||
| * 识别瓶颈与阻塞，并采取措施解决。 | ||
|
|
||
| * 提升团队协作 | ||
|
|
||
| * A process or workflow defined as a set of step or stages to conclude (develop, deploy, deliver) a work item. | ||
| * 提升效率和生产率，缩短项目或用户的前置时间（从开始到完成的时间周期） | ||
|
|
||
| * Explicit Process Policies: Rules for how the team works and should be developed collaboratively. These rules describe when a work item could be moved from one column to other. | ||
| * 减少浪费 | ||
|
|
||
| * Kanban Board (virtual or physical) divided in a set of columns. Each column (step or stage of the process) is well-know for each member of the team. | ||
| ## 如何操作 | ||
| **你需要谁共同参与?** | ||
|
|
||
| 看板需要参与软件开发、交付、部署的全部成员参与，也需要产品负责人和其他了解该过程的干系人加入。同时，如果团队第一次试用看板框架，建议增加一个辅导员的角色会比较有帮助。 | ||
|
|
||
| * Kanban Card Template: Identifies a work item with a set of properties, values or definitions to describe the task during the process. This template will help us to create the Kanban Cards. | ||
| **你需要做什么准备工作?** | ||
|
|
||
|
|
||
| **What will you get?** | ||
| * 识别完成工作项的一系列步骤或者阶段，这些步骤或阶段的集合被定义为流程或工作流，包括开发、部署、交付等。 | ||
|
|
||
| * 显示化流程规则：建立团队协作的规则，这些规则明确了工作项何时可以从看板的某栏被拉动到下一栏。 | ||
|
|
||
| * 被划分为多栏的看板墙（电子看板或物理看板），团队熟知每栏（代表一个步骤或者阶段）代表的含义。 | ||
|
|
||
| Kanban will provide you a set of metrics to measure your process. These metrics are very usefull to improve your flow and identify points of failure. | ||
| * 看板卡片模板：识别工作项具备的属性、价值或者定义，用于描述流程中的任务。我们将利用这个模板创建看板卡片。 | ||
|
|
||
|
|
||
|
|
||
| * **Lead Time**: Measures how much time a task spends in the Kanban board, since get in and get out. A measure for our customers. | ||
| **你将从中而获得什么？** | ||
|
|
||
| * **Cycle Time**: Measures how much time a task spends going through the process, from when the task started. | ||
| 看板可以提供给你一组过程度量的指标。这些指标对促进流动和识别问题非常有帮助。 | ||
|
|
||
| * **Throughput**: Measures the total amount of work delivered (completed work items). | ||
|
|
||
| * **前置时间**: 度量一个任务从进入看板（接收）到完成(交付)的周期。这是一个面向客户的指标。 | ||
|
|
||
| * **周期时间**: 度量任务从开始处理到完成全流程工作的时间周期。 | ||
|
|
||
| These metrics are connected by the Little's Law: **Cycle Time = WIP / Throughput** | ||
| * **吞吐率**: 统计周期内全部交付的工作项数量（已完成的工作项）。 | ||
|
|
||
| 这些指标与利特尔法则是相息息相关的。（**平均周期时间 = 在制品数量 / 平均吞吐率**） | ||
|
|
||
| **Tips for remote Kanban** | ||
|
|
||
| **远程看板的实践建议** | ||
|
|
||
| * This framework can be applicable in remote teams. | ||
|
|
||
| * Easy to apply if the team can use the same tools for documents and whiteboard. | ||
| * 看板框架是可以用于远程异地团队实践的。 | ||
|
|
||
| * One facilitator shares the primary screen, showing the tool to allow everyone to understan where is the focus. | ||
| * 如果团队使用相同的文档和白板工具，远程看板会更容易实施和使用。 | ||
|
|
||
| * If the tool you are using allows you to see where are the people in the room, it is very helpful to be focused on the same topic. | ||
| mediaGallery: | ||
| - link: https://upload.wikimedia.org/wikipedia/commons/d/d3/Simple-kanban-board-.jpg | ||
| resources: | ||
| - link: https://openpracticelibrary.com/practice/kanban-picture/ | ||
| linkType: web | ||
| description: Kanban Picture | ||
| people: 4+ | ||
| difficulty: moderate | ||
| participants: | ||
| - Development Team | ||
| - Product Owner | ||
| --- | ||
| * 由看板引导员分享屏幕，展示工具看板，让每个人聚焦关键问题。 | ||
|
|
||
| * 如果工具可以支持用户看到每个人在房间的具体位置，那将非常有助于团队聚焦。 | ||
|
|
||
|
|
||
| ## 延伸资源 | ||
| - [看板图片](https://openpracticelibrary.com/practice/kanban-picture/) | ||
|
|
||
| > 原文作者 | ||
|
|
||
|  | ||
|
|
||
| - Roman Martin | ||
| - PUBLISHED SEPTEMBER 15, 2020 | ||
|
|
||
| > 原文链接： <https://openpracticelibrary.com/practice/kanban/> |
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.