The document provides an overview of agile principles and the Scrum framework. It discusses the values of agile like prioritizing customer satisfaction, responding to change, and valuing individuals. The principles behind agile like welcoming changing requirements, frequent delivery of working software, and self-organizing teams are also outlined. Finally, it briefly introduces Scrum roles, ceremonies, and artifacts.

1. Agile 101 Agile Essentials & the Scrum Framework January 23, 2010 Presented by: Vernon Stinebaker ( 史文林 )

2. Rules of the game 游戏规则

3. Objectives/ 目标

4. Vernon Stinebaker ( 史文林）

5. Perficient Inc. 博克软件（杭州）有限公司

6. What is agile? 什么是敏捷？ It is NOT a methodology, process, or framework 它不是一种方法论、过程学或者框架论

7. Values and principles 价值观和原则

8. Values 价值观

9. Individuals and interactions over processes and tools 个体与交互胜于流程和工具

10. Working software over comprehensive documentation 可用的软件胜于冗长的文档

11. Customer collaboration over contract negotiation 客户合作胜于合同谈判

12. Responding to change over following a plan 响应变化胜于遵循计划

13. Principles 原则

14. Principles behind the Agile Manifesto We follow these principles: Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. Business people and developers must work together daily throughout the project. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. Working software is the primary measure of progress.Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. Continuous attention to technical excellence and good design enhances agility. Simplicity--the art of maximizing the amount of work not done--is essential. The best architectures, requirements, and designs emerge from self-organizing teams. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

15. Our highest priority is to satisfy the customer through early and continuous deliver of valuable software . 我们的 最高优先级目标 是通过尽早且 持续 交付有价值的软件 来满足客户。

16. Welcome changing requirements , even late in development. Agile processes harness change for the customer’s competitive advantage. 欢迎不断变化的需求 ，即使在开发的后期。 敏捷过程利用变化为客户带来竞争优势。

17. Delivery working software frequently , from a couple of weeks to a couple of months, with a preference to the shorter timescale. 经常交付可用的软件， 从两个星期到两个月，时隔越短越好。

18. Business people and developers must work together daily throughout the project. 业务人员和开发者最好 每天一起共事直到项目结束。

19. Build projects around motivated individuals . Give them the environment and support they need, and trust them to get the job done. 让被激励的人员来完成项目。 给他们需要的环境和支持， 并且相信他们能够完成任务。

20. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. 开发团队之间以及团队内部 最充分有效的传达信息的方法是 面对面的交流。

21. Working software is the primary measure of progress . 可用的软件是对项目进展最基本的考量。

22. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely . 敏捷过程提倡可持续的开发。 项目发起人、开发者和用户都 应该一直保持恒定的步调。

23. Continuous attention to technical excellence and good design enhances agility. 持续关注技术的优秀和良好的设计能提高敏捷性。

24. Simplicity – the art of maximizing the amount of work not done – is essential. 简单－ 使无需完成的工作最大化的艺术 －是根本的。

25. The best architectures, requirements, and designs emerge from self-organizing teams. 最好的构架、需求和设计的涌现来自自管理团队。

26. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts it behavior accordingly. 每隔一段时间，团队会 在如何才能更有效地工作方面进行 反省 , 然后相应地 调整 他们的行为。

28. Scrum

30. Product owner ScrumMaster Team Roles Sprint planning Sprint review Sprint retrospective Daily scrum meeting Ceremonies Product backlog Sprint backlog Burndown charts Artifacts Thanks to Mountain Goat Software, LLC

31. Product Owner Team ScrumMaster Image available at www.mountaingoatsoftware.com/scrum Thanks to Mountain Goat Software, LLC

32. Done 完成

33. Ready 准备好

34. The Standish Group XP 2002 Conference

35. Self-organized teams 自组织团队 Team

36. reflect/adjust 反省 / 调整

37. Testable 可测试的

38. small steps build on success 在成功基础上的小步提升

39. technical excellence 技术的优秀