没有合适的资源?快使用搜索试试~ 我知道了~
2017 Scrum指南-最新版
4星 · 超过85%的资源 需积分: 9 24 下载量 30 浏览量
2017-11-24
17:41:54
上传
评论 1
收藏 582KB PDF 举报
温馨提示
试读
19页
2017年12月Scrum发明人jeff与ken对Scrum指南做了修订。
资源推荐
资源详情
资源评论
The Scrum Guide™
The Definitive Guide to Scrum:
The Rules of the Game
November 2017
Developed and sustained by Scrum creators: Ken Schwaber and Jeff Sutherland
©2017 Ken Schwaber and Jeff Sutherland. Offered for license under the Attribution Share-Alike license of Creative
Commons, accessible at http://creativecommons.org/licenses/by-sa/4.0/legalcode and also described in summary form
at http://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.
Page | 2
Table of Contents
Purpose of the Scrum Guide ............................................................................................................ 3
Definition of Scrum .......................................................................................................................... 3
Uses of Scrum ................................................................................................................................... 4
Scrum Theory ................................................................................................................................... 4
Scrum Values .................................................................................................................................... 5
The Scrum Team ............................................................................................................................... 6
The Product Owner ...................................................................................................................... 6
The Development Team ............................................................................................................... 7
The Scrum Master ........................................................................................................................ 7
Scrum Events .................................................................................................................................... 9
The Sprint ..................................................................................................................................... 9
Sprint Planning ........................................................................................................................... 10
Daily Scrum ................................................................................................................................. 12
Sprint Review ............................................................................................................................. 13
Sprint Retrospective ................................................................................................................... 14
Scrum Artifacts ............................................................................................................................... 14
Product Backlog .......................................................................................................................... 15
Sprint Backlog ............................................................................................................................. 16
Increment ................................................................................................................................... 17
Artifact Transparency ..................................................................................................................... 17
Definition of “Done” ................................................................................................................... 18
End Note ......................................................................................................................................... 19
Acknowledgements ........................................................................................................................ 19
People ......................................................................................................................................... 19
History ........................................................................................................................................ 19
©2017 Ken Schwaber and Jeff Sutherland. Offered for license under the Attribution Share-Alike license of Creative
Commons, accessible at http://creativecommons.org/licenses/by-sa/4.0/legalcode and also described in summary form
at http://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.
Page | 3
Purpose of the Scrum Guide
Scrum is a framework for developing, delivering, 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.
Definition of Scrum
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
• Difficult to master
Scrum is a process framework that has been used to manage work on complex products since
the early 1990s. Scrum is not a process, technique, or definitive method. 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 work techniques so that you can
continuously improve the product, the team, and the working environment.
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.
The rules of Scrum bind together the roles, events, and artifacts, governing the relationships and
interaction between them. The rules of Scrum are described throughout the body of this
document.
Specific tactics for using the Scrum framework vary and are described elsewhere.
©2017 Ken Schwaber and Jeff Sutherland. Offered for license under the Attribution Share-Alike license of Creative
Commons, accessible at http://creativecommons.org/licenses/by-sa/4.0/legalcode and also described in summary form
at http://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.
Page | 4
Uses of Scrum
Scrum was initially developed for managing and developing products. Starting in the early
1990s, Scrum has been used extensively, worldwide, to:
1. Research and identify viable markets, technologies, and product capabilities;
2. Develop products and enhancements;
3. Release products and enhancements, as frequently as many times per day;
4. Develop and sustain Cloud (online, secure, on-demand) and other operational
environments for product use; and,
5. Sustain and renew products.
Scrum has been used to develop software, hardware, embedded software, networks of
interacting function, autonomous vehicles, schools, government, marketing, managing the
operation of organizations and almost everything we use in our daily lives, as individuals and
societies.
As technology, market, and environmental complexities and their interactions have rapidly
increased, Scrum’s utility in dealing with complexity is proven daily.
Scrum proved especially effective in iterative and incremental knowledge transfer. Scrum is now
widely used for products, services, and the management of the parent organization.
The essence of Scrum is a small team of people. The individual team is highly flexible and
adaptive. These strengths continue operating in single, several, many, and networks of teams
that develop, release, operate and sustain the work and work products of thousands of people.
They collaborate and interoperate through sophisticated development architectures and target
release environments.
When the words “develop” and “development” are used in the Scrum Guide, they refer to
complex work, such as those types identified above.
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.
剩余18页未读,继续阅读
资源评论
- 咖啡色的思想者2018-03-14要脸不?英文指南Scrum.org随便下载,还要10分?以为是翻译版本。
- qiuhanwow2017-12-23值得推荐的新文章,变化还是挺大的
- priority2017-12-18下载来看看
- lx1678782018-12-13还是不错的,用的挺好的
ShineScrum捷行
- 粉丝: 101
- 资源: 3
上传资源 快速赚钱
- 我的内容管理 展开
- 我的资源 快来上传第一个资源
- 我的收益 登录查看自己的收益
- 我的积分 登录查看自己的积分
- 我的C币 登录后查看C币余额
- 我的收藏
- 我的下载
- 下载帮助
安全验证
文档复制为VIP权益,开通VIP直接复制
信息提交成功