看板和scrum_Scrumban如何结合最好的看板和Scrum方法论

看板和scrum

In this post, you will learn some basic facts about Scrumban and how to combine two popular Agile methodologies – Kanban and Scrum to make this hybrid approach perform better.

在本文中，您将学习有关Scrumban的一些基本知识，以及如何结合两种流行的敏捷方法(看板和Scrum)来使这种混合方法的性能更好。

But first, it worth to recollect some fundamental facts about both Agile methods. What is your favorite in the fight Scrum vs Kanban?

但是首先，值得回顾一下有关两种敏捷方法的一些基本事实。 在Scrum与看板的战斗中，您最喜欢什么？

Scrum 101 (Scrum 101)

Scrum was originally designed to help teams maximize their ability to deliver quickly, respond to emerging requirements, and adapt to changes in market conditions.

Scrum最初旨在帮助团队最大化其快速交付，响应新兴需求以及适应市场条件变化的能力。

This Agile framework requires using fixed-length development cycles called sprints. Each sprint usually lasts 1-4 weeks.

这个敏捷框架需要使用称为sprint的固定长度的开发周期。 每个冲刺通常持续1-4周。

A Scrum team is usually small, self-organized and cross-functional. Team members split work into small product increments and prioritize tasks. The product owner chooses all work to be done in a sprint at one time. Then the team completes the work during each sprint.

Scrum团队通常规模较小，自组织且具有跨职能。 团队成员将工作分成小的产品增量并确定任务的优先级。 产品负责人一次选择要在sprint中完成的所有工作。 然后，团队在每个冲刺期间完成工作。

Scrum helps to achieve agility. It implicates frequent feedback and collaborative decision-making principles.

Scrum有助于实现敏捷性。 它牵涉到频繁的反馈和协作决策原则。

看板101 (Kanban 101)

Kanban is a visual workflow management approach for managing the creation of products with an emphasis on continual delivery without teams overburdening. The method has come form manufacturing.

看板是一种可视化的工作流管理方法，用于管理产品的创建，强调持续交付而不会增加团队负担。 该方法来自制造形式。

All work items in Kanban are visualized with cards on a board and lanes that represent process stages. A Kanban board is used to manage the collective work of the team.

看板中的所有工作项目都可以通过板卡和代表过程阶段的通道来可视化。 看板委员会用于管理团队的集体工作。

Kanban-focused teams practice a continuous flow approach (continuously planning, working, reviewing, and measuring the results).

以看板为重点的团队练习一种连续流程方法(不断地计划，工作，审查和衡量结果)。

One of the essential Kanban tools is WIP limits. It helps to minimize chaos and promote focus by explicitly limiting how many items are in process. Kanban teams measure lead time — the average time from when work is requested to when it is finished.

WIP限制是基本的看板工具之一。 通过明确限制正在处理的项目数量，它有助于最大程度地减少混乱并促进关注。 看板团队测量准备时间-从请求工作到完成的平均时间。

Scrum和看板的常见功能 (Common features in Scrum and Kanban)

自我管理的团队 (Self-managed teams)

One of the aspects of Scrum and Kanban success is that development teams direct their own work, guided by the business goals. Both approaches advocate respect for people and allow them to do their best work.

Scrum和看板成功的方面之一是，开发团队在业务目标的指导下指导自己的工作。 两种方法都倡导尊重人，并允许他们尽力而为。

工作包 (Work packages)

Both methods prosper from well-defined user stories that can be accomplished and delivered separately. Scrum leaves the decision about how much to work at the same time to the team. Kanban focuses on limiting the number of items the team has in progress. The main difference is that Scrum measures the levels of teams’ productivity in terms of the team’s speed, Kanban controls for continuous work in progress and limits the number of stories the team will accept to working on at the same time.

两种方法都可以从定义明确的用户案例中获得成功，这些案例可以分别实现和交付。 Scrum由团队决定是否要同时进行多少工作。 看板专注于限制团队正在进行的项目数量。 主要区别在于，Scrum根据团队的速度来衡量团队的生产力水平，看板控制连续进行中的工作，并限制团队同时接受的故事数量。

板结构 (Boards structure)

A Kanban board is split into columns and Swimlanes. Every column represents a stage of the workflow. Swimlanes help to separate different types of activities. A typical Kanban board is split into 3 sections that show the state of your tasks: To Do, In Progress and Done.

看板板分为列和泳道。 每列代表工作流程的一个阶段。 泳道有助于区分不同类型的活动。 一个典型的看板分为三个部分，显示您的任务状态：“待办”，“进行中”和“完成”。

The WIP limits feature in Kanban lets you provide more time to the people who are responsible for this stage and allow them to resolve the bottleneck.

看板中的WIP限制功能使您可以为负责此阶段的人员提供更多时间，并让他们解决瓶颈。

A Scrum board is also made up of horizontal (and often vertical) Swimlanes that track the progress of tasks and stories committed to during a Sprint. The typical Scrum board consists of several progressive columns: Stories, To Do, In Progress, Testing and Done. Team members are able to move their work items along the board.

Scrum板还由水平(通常是垂直)的泳道组成，可跟踪Sprint期间完成的任务和故事的进度。 典型的Scrum板包含几个进度栏：“故事”，“待办事项”，“进行中”，“测试”和“完成”。 团队成员能够沿董事会移动他们的工作项目。

结合敏捷世界的最佳实践 (Combining the best practices of both Agile worlds)

The decision about the best methodology should be well-balanced. Many specialists think that you will find Scrum the most obvious choice if you are creating products, and Kanban will suit better if you provide services. However, there is an option to combine them. This solution is Scrumban.

关于最佳方法的决定应保持平衡。 许多专家认为，如果要创建产品，您会发现Scrum是最明显的选择，而如果提供服务，则看板将更适合。 但是，可以选择将它们组合在一起。 此解决方案是Scrumban。

Scrumban定义 (Scrumban definition)

Scrumban is a hybrid Agile development methodology that combines the best practices of Scrum and Kanban. The method was created to meet team needs concerning minimizing the batching of work and adopting a pull-based system.

Scrumban是一种混合敏捷开发方法，结合了Scrum和看板的最佳实践。 该方法的创建是为了满足团队在减少工作分批和采用基于拉式系统方面的需求。

Scrumban method was introduced by a software development enthusiast, Corey Ladas. In his book, Scrumban: Essays on Kanban Systems for Lean Software Development, he claims that Scrumban is aimed to transition a development team from Scrum to Lean or Kanban. Over time, this became an independent methodology.

Scrumban方法是由软件开发爱好者Corey Ladas提出的。 在他的书《 Scrumban：精益软件开发的看板系统文章》中 ，他声称Scrumban旨在将开发团队从Scrum过渡到精益或看板。 随着时间的流逝，这成为一种独立的方法。

Scrum +看板= Scrumban (Scrum + Kanban = Scrumban)

The hybrid of two popular Agile methodologies provides development teams with the flexibility to adapt and change to stakeholders and production requirements without overburdens.

两种流行的敏捷方法的混合为开发团队提供了适应性和适应利益相关者和生产需求的灵活性，而不会造成负担。

Scrumban is a highly versatile approach to workflow management because it provides the structure of Scrum with the visualization and flexibility of Kanban.

Scrumban是一种非常通用的工作流管理方法，因为它为Scrum的结构提供了看板的可视化和灵活性。

Some teams utilize Scrumban as a stepping stone to move from Scrum to Kanban. It makes sense, as the immediate shift to Kanban may be too painful and drastic for many software development teams.

一些团队将Scrumban用作从Scrum转到看板的垫脚石。 这是有道理的，因为对于许多软件开发团队而言，立即转到看板可能会非常痛苦和激烈。

The main objective of Scrumban is to provide teams a soft and healthy way of learning how to practice Continuous Improvement in Kanban without leaving the familiar Scrum structure.

Scrumban的主要目标是在不离开熟悉的Scrum结构的情况下，为团队提供一种柔软健康的方法来学习如何在看板中实践持续改进 。

As the hybrid approach combines the Scrum structure with the flow-based methods of Kanban, it's important to understand what exactly did it take from each system.

由于混合方法将Scrum结构与基于流的看板方法结合在一起，因此重要的是要了解每个系统的确切功能。

Scrumban中整合了哪些Scrum元素？ (What Scrum elements are incorporated into Scrumban?)

• Iteration planning at regular intervals that is in sync with reviews and retrospectives.
  定期进行迭代计划，与评论和回顾保持同步。
• Work prioritization that gives teams the best thing to work on next
  确定工作优先级，使团队在接下来的工作中拥有最好的工作
• The decision about how much work can be pulled into the sprint according to the complexity of the work and the length of the sprint.
  根据工作的复杂性和冲刺的长度，可以决定将多少工作拉入冲刺。
• The assurance of the necessary level of analysis before development
  开发之前确保必要的分析水平
• Using the ready queue between Backlog and Doing phases
  在Backlog和Doing阶段之间使用就绪队列

Scrumban中整合了哪些看板元素？ (What Kanban elements are incorporated into Scrumban?)

Kanban improves visualization, adds process improvement, and provides more value metrics to Scrumban. Here are Kanban elements that are used by Scrumban teams:

看板改善了可视化，增加了流程改进，并为Scrumban提供了更多价值指标。 以下是Scrumban团队使用的看板元素：

• Continuous workflow and Pull System.

  连续工作流与拉系统 。

• WIP limits — the explicit limits on how many items are in progress.

  在制品限制 -对正在进行的项目的明确限制。

• Focusing more on Cycle time than Burndown

  更多关注周期时间而不是燃尽时间

• Not clearly specified individual roles
  没有明确指定个人角色
• Short lead times with emphasizing just-in-time analysis and planning.
  缩短交货时间，强调及时分析和计划。
• Using flow diagrams to expose process weaknesses and identify opportunities for improvement.
  使用流程图来揭示过程中的弱点并确定改进的机会。

快速设置Scrumban的优势 (Quick set of Scrumban advantages)

• High quality
  高质量
• Short lead time
  交货时间短
• Fact and decisions just when they are needed (Just-in-time)
  需要时的事实和决策(及时)
• Continuous improvement (Kaizen)
  持续改进(Kaizen)
• Minimizing everything that is not adding value to customers
  最小化不会为客户增加价值的一切
• Process improvement by adding some Scrum values if needed
  通过在必要时添加一些Scrum值来改进流程
• Perfect visualization of a Scrumban board
  完美可视化Scrumban板

Scrumban软件 (Scrumban software)

The right way to pull off Scrumban is to apply a modern project management software that is suited for both Scrum and Kanban development.

实现Scrumban的正确方法是应用适用于Scrum和看板开发的现代项目管理软件。

If this project management tool provides convenient boards and cards, WIP limits, Swimlanes, Lead and Cycle Time, then it can be easily applied to your Scrumban software development.

如果此项目管理工具提供了方便的板卡，WIP限制，泳道，提前期和周期时间，则可以轻松地应用于您的Scrumban软件开发。

摘要 (Summary)

Despite a large number of opponents of mergers and acquisitions, the combination of two Agile methodologies has passed the test of time. The hybrid approach has proven its usefulness and convenience and has demonstrated real strength.

尽管有许多反对并购的公司，但两种敏捷方法的结合已经通过了时间的考验。 混合方法已经证明了其实用性和便利性，并显示出了真正的优势。

Kanban is compatible with Scrum. Adding WIP limits, visualization and other elements to Scrum helps to improve Sprint Commitment effectiveness.

看板与Scrum兼容。 向Scrum添加WIP限制，可视化和其他元素有助于提高Sprint承诺的有效性。

However, it also introduces the WIP limit as a mechanism to catalyze incremental changes. The WIP limit obviates the need for commitment to drive change, reduces any dysfunctional reliance on heroic effort, and improves overall systems thinking when considering potential improvements.

但是，它也引入了WIP限制作为催化增量变化的机制。 WIP限制消除了对推动变革的承诺的需要，减少了任何因英勇努力而导致的功能失调，并改善了在考虑潜在改进时的整体系统思维。

After all, let's define Scrumban as a soft evolution rather than shock treatment. What do you think about it? Have you tried to combine both Agile methodologies? Was this mix effective? Feel free to share your experience below.

毕竟，让我们将Scrumban定义为一种软进化，而不是电击治疗。 你怎么看待这件事？ 您是否尝试过结合两种敏捷方法？ 这种混合有效吗？ 请随时在下面分享您的经验。

翻译自: https://habr.com/en/company/hygger/blog/464325/

看板和scrum