The Scrum Guide（Scrum指南）.pdf

The Scrum Guide™ The Definitive Guide to Scrum : The Rules of the Game July 2013 Developed and sustained by Ken Schwaber and Jeff Sutherland Table of Contents Purpose of the Scrum Guide3 Definition of Scrum3 Scrum Theory 3 The Scrum Team 4 The Product Owner 5 The Development Team 5 The Scrum Master 6 Scrum Events 7 The Sprint 7 Sprint Planning 8 Daily Scrum 10 Sprint Review 11 Sprint Retrospective 12 Scrum Artifacts 12 Product Backlog 12 Sprint Backlog 14 Increment 15 Artifact Transparency 15 Definition of “Done” 15 End Note 16 Acknowledgements 16 People 16 History 16 ©2014 Scrum.Org and ScrumInc. Offered for license under the Attribution Share-Alike license of Creative Commons, accessible at /licenses/by-sa/4.0/legalcode and also described in summary form at /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 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. 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 complex product development since the early