What is Scrum Team? - Scrum Guide

如何用Scrum框架开始敏捷开发

敏捷开发的原则之一是让团队成员定期讨论如何提高效率,然后相应地调整他们的行为。Scrum整合了一个正式的过程来帮助团队做到这一点。每天的会议使团队能够反思在接下来的24小时内要做的工作,并根据预期或遇到的障碍改变他们的方法。敏捷的另一个原则是认识到最好的工作来自于自我指导的团队。Scrum master在这方面发挥了作用。它们给予团队完成工作所需的东西,以及设定自己路线的自由。然后,他们充当服务型领导,指导团队解决问题、实现目标和解决冲突。

Continue reading

什么是敏捷项目管理?实施敏捷方法的好处

敏捷的工作原理是将项目分解为用户功能的一小部分,对它们进行优先级排序,然后以 2-4 周的周期持续交付它们,称为迭代或冲刺。团队以短周期运作,旨在持续改进,只开发用户想要的东西。工作目标由团队在每个周期开始之前定义。如果客户对该功能有任何疑问,该团队会直接与客户沟通。客户的优先级由产品负责人分析并反馈给团队,让他们继续处理最高优先级的项目。团队估计在一个迭代中工作需要多少时间,以及如何完成工作。

Continue reading

Scrum: 把事件时间盒是什么意思?

Time boxes allocate a fixed maximum unit of time for activities. That unit of time is called a time frame. The goal of time frames is to define and limit the amount of time dedicated to activities. Time frames are a common feature of many project management approaches, because they focus the team on the task at hand by providing a clear definition of completion. (时间盒为活动分配固定的最大时间单位。那个时间单位称为时间框。时间框的目标是定义和限制专用于活动的时间量。时间框是许多项目管理方法的共同特征,因为时间框通过提供明确的完成定义,使团队专注于完成手头的任务。)

Continue reading

Scrum: 什么是持续 集成 / 交付 / 部署?

“Continuous Integration”, “Continuous Delivery” and “Continuous Deployment”, are referred as an integral part of agile development. These approaches shares the same prefix ‘Continuous’, which suggests and allows integrating the increment (shippable software) as well as to deploy the outcome concurrently without the delay involved in traditional sequential development. (“持续集成”、“持续交付”和“持续部署”是敏捷开发不可或缺的一部分。这些方法共享相同的前缀“continuous”,这表明并允许集成增量(可交付软件)以及在不延迟传统顺序开发的情况下并行部署结果。)

Continue reading

Scrum: 产品Backlog改进是什么?

Product Backlog refinement is the act of adding detail, estimates and order to items in the Product Backlog. Ongoing Product Backlog Refinement is needed within each Sprint to refine items to be ready for future Sprints. When the backlog items are refined to the suitable level of granularity, they fit to be implemented within one Sprint. (产品积压优化是向产品积压中的项目添加细节、估计和顺序的操作。在每个sprint中,需要不断改进产品待办事项列表,以便为将来的sprint做好准备。当积压工作项被细化到合适的粒度级别时,它们适合在一个sprint中实现。)

Continue reading

Scrum: Sprint Retropective 会议是什么?

The Sprint Retrospective occurs after the Sprint Review and prior to the next Sprint Planning. This is at most a three-hour meeting for one-month Sprints. The retrospective session is basically an “improvement” meeting held to find ways and means to identify potential pitfalls, past mistakes, and seek out new ways to avoid those mistakes. (sprint审查发生在sprint回顾之后和下一个sprint计划之前。这最多是一个月Sprint的三小时会议。回顾旨在找出找出潜在的陷阱、过去的错误,并寻求避免这些错误的新方法。)

Continue reading