敏捷团队管理指南2016.pdf

The Scrum GuideTM The Definitive Guide to Scrum: The Rules of the Game July 2016 Developed and sustained by Ken Schwaber and Jeff Sutherland Table of Contents Purpose of the Scrum Guide3 Definition of Scrum3 Scrum Theory 3 Scrum Values4 The Scrum Team 5 The Product Owner5 The Development Team 6 The Scrum Master6 Scrum Events7 The Sprint8 Sprint Planning 9 Daily Scrum 11 Sprint Review 11 Sprint Retrospective 12 Scrum Artifacts 13 Product Backlog 13 Sprint Backlog 14 Increment 15 Artifact Transparency 15 Definition of “Done” 16 End Note 16 Acknowledgements 17 People 17 History 17 ©2016 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 underst