Module 3 Summary: Agile & Scrum第 3 模块总结：敏捷与 Scrum

Congratulations! You have completed this module. At this point in the course, you know:
恭喜！您已完成本模块。到目前为止，您已了解：

• Agile is an iterative software development approach that emphasizes flexibility, interactivity, and transparency by small, cross-functional teams.
  敏捷是一种强调灵活性、互动性和透明度的迭代软件开发方法，由小型跨职能团队执行。
• The Agile Manifesto defines the Agile core values.
  敏捷宣言定义了敏捷的核心价值观。
• Scrum is a methodology based on the Agile philosophy.
  敏捷哲学基础上的敏捷方法。
• Scrum events include sprint planning, daily Scrum meetings, sprints, sprint reviews, and sprint retrospectives.
  敏捷事件包括冲刺计划、每日 Scrum 会议、冲刺、冲刺评审和冲刺回顾。
• Failure to implement Agile across organizations can result in operational bottlenecks.
  组织内未能实施敏捷方法可能导致运营瓶颈。
• Iterative development alone is not Agile unless you are responsive to changes and deliver value frequently.
  迭代开发本身并不等同于敏捷，除非你能对变化做出响应并频繁交付价值。
• Placing existing employees in new roles without proper training will fail because Agile roles necessitate a shift in focus and priorities.
  将现有员工安排到新角色而不进行适当培训将失败，因为敏捷角色需要转变关注点和优先级。
• A Kanban board is a method of tracking plan items to complete, items in the process, and completed items.
  看板是一种跟踪待完成计划项、在过程中的项和已完成项的方法。
• A user story describes a person requesting a function to accomplish a goal.
  用户故事描述了一个人请求一个功能以实现目标。
• Use the acronym INVEST to remember the qualities of a good user story: independent, negotiable, valuable, estimable, small, and testable.
  使用缩写 INVEST 来记住良好用户故事的特性：独立、可协商、有价值、可估计、小、可测试。
• Story points are a metric for estimating the difficulty of implementing a specific user story.
  故事点是对实现特定用户故事难度的衡量指标。
• You can create a sprint plan by transferring stories from the product backlog to the sprint backlog until the team reaches its velocity.
  您可以通过将故事从产品待办事项转移到冲刺待办事项来创建冲刺计划，直到团队达到其速度。
• A sprint review demonstrates the features to implement during the sprint.
  冲刺评审展示了在冲刺期间要实现的功能。
• A sprint retrospective is a time for the scrum master and the development team to reflect on how the sprint went.
  敏捷回顾会是一个敏捷大师和开发团队反思如何进行冲刺的时间。