The Scrum Guide The Definitive Guide to Scrum: The Rules of the Game 敏捷指导手册

Ken Schwaber & Jeff Sutherland
The Scrum Guide
The Definitive Guide to Scrum: The Rules of the Game
November 2020 1

Purpose of the Scrum Guide
We developed Scrum in the early 1990s. We wrote the first version of the Scrum Guide in 2010 to help people worldwide understand Scrum. We have evolved the Guide since then through small, functional updates. Together, we stand behind it.

The Scrum Guide contains the definition of Scrum. Each element of the framework serves a specific purpose that is essential to the overall value and results realized with Scrum. Changing the core design or ideas of Scrum, leaving out elements, or not following the rules of Scrum, covers up problems and limits the benefits of Scrum, potentially even rendering it useless.

We follow the growing use of Scrum within an ever-growing complex world. We are humbled to see Scrum being adopted in many domains holding essentially complex work, beyond software product development where Scrum has its roots. As Scrum’s use spreads, developers, researchers, analysts, scientists, and other specialists do the work. We use the word “developers” in Scrum not to exclude, but to simplify. If you get value from Scrum, consider yourself included.

As Scrum is being used, patterns, processes, and insights that fit the Scrum framework as described in this document, may be found, applied and devised. Their description is beyond the purpose of the Scrum Guide because they are context sensitive and differ widely between Scrum uses. Such tactics for using within the Scrum framework vary widely and are described elsewhere.

This publication is offered for license under the Attribution Share-Alike license of Creative Commons, accessible at https://creativecommons.org/licenses/by-sa/4.0/legalcode and also described in summary form at https://creativecommons.org/licenses/by-sa/4.0/. By utilizing this Scrum Guide, you acknowledge and agree that you have read and agree to be bound by the terms of the Attribution Share-Alike license of Creative Commons. 2

Purpose of the Scrum Guide … 1
Scrum Definition … 3
Scrum Theory … 3
Transparency … 3
Inspection … 4
Adaptation … 4
Scrum Values … 4
Scrum Team … 5
Developers … 5
Product Owner … 5
Scrum Master … 6
Scrum Events … 7
The Sprint … 7
Sprint Planning … 8
Daily Scrum … 9
Sprint Review … 9
Sprint Retrospective … 10
Scrum Artifacts… 10
Product Backlog … 10
Commitment: Product Goal … 11
Sprint Backlog … 11
Commitment: Sprint Goal … 11
Increment… 11
Commitment: Definition of Done … 12
End Note … 13
Acknowledgements … 13
People … 13
Scrum Guide History … 13 3

Scrum Definition
Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems.
敏捷是一个轻量级框架，它帮助人们，团队，组织通过高适用性的方案为复杂的项目产生价值
In a nutshell, Scrum requires a Scrum Master to foster an environment where:
简言之，敏捷需要敏捷主管促成这样一个环境：

1. A Product Owner orders the work for a complex problem into a Product Backlog.
   产品经理将解决复杂的问题的工作排列在产品待办事项中
2. The Scrum Team turns a selection of the work into an Increment of value during a Sprint.
   敏捷团队在每个Sprint中，将分配的工作转换为增量价值
3. The Scrum Team and its stakeholders inspect the results and adjust for the next Sprint.
   敏捷团队和干系人检阅开发结果，调整安排下一个Sprint的工作安排
4. Repeat
   重复

Scrum is simple. Try it as is and determine if its philosophy, theory, and structure help to achieve goals and create value. The Scrum framework is purposefully incomplete, only defining the parts required to implement Scrum theory.
敏捷是简单的。

Scrum is built upon by the collective intelligence of the people using it. Rather than provide people with detailed instructions, the rules of Scrum guide their relationships and interactions.

Various processes, techniques and methods can be employed within the framework. Scrum wraps around existing practices or renders them unnecessary.

Scrum makes visible the relative efficacy of current management, environment, and work techniques, so that improvements can be made.

Scrum Theory
Scrum is founded on empiricism and lean thinking. Empiricism asserts that knowledge comes from experience and making decisions based on what is observed. Lean thinking reduces waste and focuses on the essentials.
敏捷是基于经验主义和精益思维。经验注意表知识来自于经验，并且决定是基于观察。精益思维可以减少浪费且专注于要点。

Scrum employs an iterative, incremental approach to optimize predictability and to control risk. Scrum engages groups of people who collectively have all the skills and expertise to do the work and share or acquire such skills as needed.
敏捷采用迭代的增量的方法以最大化预见性和控制风险。敏捷雇佣一群都拥有所有可以完成工作的专业技术和专业能力，可以分享或者获取这些需要的技术。

Scrum combines four formal events for inspection and adaptation within a containing event, the Sprint. These events work because they implement the empirical Scrum pillars of transparency, inspection, and adaptation.
敏捷在一个容器活动中结合了四种用于检阅和调整的活动，即 Sprint。因为这些活动实现了经验敏捷的高透明性，高检阅能力，高适应性。

Transparency
The emergent process and work must be visible to those performing the work as well as those receiving the work. With Scrum, important decisions are based on the perceived state of its three formal artifacts. Artifacts that have low transparency can lead to decisions that diminish value and increase risk. 4
紧急的程序和工作必须对执行工作的人和接收工作的人透明。在敏捷中，重要的决定要基于三个人工制品的可见的状态。透明性差的制品会减少价值，增加风险。

Transparency enables inspection. Inspection without transparency is misleading and wasteful.

Inspection
The Scrum artifacts and the progress toward agreed goals must be inspected frequently and diligently to detect potentially undesirable variances or problems. To help with inspection, Scrum provides cadence in the form of its five events.
向约定的目标进行中的敏捷成品和进度须要被频繁认真地检阅，以发现潜在地不需要的差异或者问题。为了帮助检阅，敏捷让它的五个活动都会有一个整顿间隙。

Inspection enables adaptation. Inspection without adaptation is considered pointless. Scrum events are designed to provoke change.
检阅促使调整。没有调整的检阅是没有意义的。敏捷活动是设计于触发改善。

Adaptation
If any aspects of a process deviate outside acc