没有合适的资源?快使用搜索试试~ 我知道了~
首页Scrum Guide
Scrum Guide
需积分: 10 53 浏览量
更新于2023-05-22
评论
收藏 525KB PDF 举报
Scrum Guide Scrum is a framework for developing and sustaining complex products. The Scrum Guide contains the official definition of Scrum as authored by Ken Schwaber and Jeff Sutherland.
资源详情
资源评论
资源推荐

The Scrum Guide
The Definitive Guide to Scrum:
The Rules of the Game
July 2011
Developed and sustained by Ken Schwaber and Jeff Sutherland

© 1991-2011 Ken Schwaber and Jeff Sutherland, All Rights Reserved Page | 2
Table of Contents
Purpose of the Scrum Guide ........................................................................................................... 3
Scrum Overview .............................................................................................................................. 3
Scrum Framework ....................................................................................................................... 3
Scrum Theory................................................................................................................................... 4
Scrum ............................................................................................................................................... 5
The Scrum Team .............................................................................................................................. 5
The Product Owner ..................................................................................................................... 5
The Development Team .............................................................................................................. 6
The Scrum Master ....................................................................................................................... 6
Scrum Events ................................................................................................................................... 7
The Sprint .................................................................................................................................... 8
Sprint Planning Meeting .............................................................................................................. 9
Daily Scrum ................................................................................................................................ 10
Sprint Review ............................................................................................................................. 11
Sprint Retrospective .................................................................................................................. 12
Scrum Artifacts .............................................................................................................................. 12
Product Backlog ......................................................................................................................... 12
Sprint Backlog ............................................................................................................................ 14
Increment .................................................................................................................................. 15
Definition of “Done” ...................................................................................................................... 15
Conclusion ..................................................................................................................................... 15
Acknowledgements ....................................................................................................................... 16
People ........................................................................................................................................ 16
History ....................................................................................................................................... 16
Translation ..................................................................................... Error! Bookmark not defined.

© 1991-2011 Ken Schwaber and Jeff Sutherland, All Rights Reserved Page | 3
Purpose of the Scrum Guide
Scrum is a framework for developing and sustaining complex products. This Guide contains the
definition of Scrum. This definition consists of Scrum’s roles, events, artifacts, and the rules that
bind them together. Ken Schwaber and Jeff Sutherland developed Scrum; the Scrum Guide is
written and provided by them. Together, they stand behind the Scrum Guide.
Scrum Overview
Scrum (n): A framework within which people can address complex adaptive problems, while
productively and creatively delivering products of the highest possible value. Scrum is:
Lightweight
Simple to understand
Extremely difficult to master
Scrum is a process framework that has been used to manage complex product development
since the early 1990s. Scrum is not a process or a technique for building products; rather, it is a
framework within which you can employ various processes and techniques. Scrum makes clear
the relative efficacy of your product management and development practices so that you can
improve.
Scrum Framework
The Scrum framework consists of Scrum Teams and their associated roles, events, artifacts, and
rules. Each component within the framework serves a specific purpose and is essential to
Scrum’s success and usage.
Specific strategies for using the Scrum framework vary and are described elsewhere.
The rules of Scrum bind together the events, roles, and artifacts, governing the relationships and
interaction between them. The rules of Scrum are described throughout the body of this
document.

© 1991-2011 Ken Schwaber and Jeff Sutherland, All Rights Reserved Page | 4
Scrum Theory
Scrum is founded on empirical process control theory, or empiricism. Empiricism asserts that
knowledge comes from experience and making decisions based on what is known. Scrum
employs an iterative, incremental approach to optimize predictability and control risk.
Three pillars uphold every implementation of empirical process control: transparency,
inspection, and adaptation.
Transparency
Significant aspects of the process must be visible to those responsible for the outcome.
Transparency requires those aspects be defined by a common standard so observers share a
common understanding of what is being seen.
For example:
A common language referring to the process must be shared by all participants; and,
A common definition of “Done”
1
must be shared by those performing the work and those
accepting the work product.
Inspection
Scrum users must frequently inspect Scrum artifacts and progress toward a goal to detect
undesirable variances. Their inspection should not be so frequent that inspection gets in the way
of the work. Inspections are most beneficial when diligently performed by skilled inspectors at
the point of work.
Adaptation
If an inspector determines that one or more aspects of a process deviate outside acceptable
limits, and that the resulting product will be unacceptable, the process or the material being
processed must be adjusted. An adjustment must be made as soon as possible to minimize
further deviation.
Scrum prescribes four formal opportunities for inspection and adaptation, as described in the
Scrum Events section of this document.
Sprint Planning Meeting
Daily Scrum
Sprint Review Meeting
Sprint Retrospective
1
See “Definition of “Done”, p. 15.
剩余16页未读,继续阅读












安全验证
文档复制为VIP权益,开通VIP直接复制

评论0