我们推荐您在每个迭代的末尾投入两个小时，开一个非正式的过程改进会议或回顾。
We recommend that you invest two hours at the end of each iteration in order to hold an informal process improvement meeting or retrospective.
我们用来指导这个过程的机制就是在每个迭代结束时进行一小时回顾会议。
One mechanism we employ to guide this process is one-hour retrospective sessions that take place at the end of each iteration.
特别是，软件团队采纳了下面的敏捷实践：迭代周期为两周的短迭代，客户参与，数据测量，角色分配和每两周的回顾会议。
Specifically, the software team adopted the following agile practices: short two-week iterations, customer involvement, measurements, role assignments, and bi-weekly retrospective sessions.
这包括发布计划、迭代计划、迭代kickoff会议、需求收集，每个迭代末尾的UAT (user accessence Test)以及项目回顾。
This includes release planning, iteration planning, iteration kickoff, requirements gathering, UAT at the end of an iteration and project retrospectives at the end of each iteration.
在迭代规划会议时留出头一到两小时用于回顾上一次迭代。
Reserve the first hour or two of your iteration planning session for a retrospective on the previous iteration.
为了尽可能地挖掘他们的潜力，回顾会议选取在每两周迭代开发周期结束时进行，同时为了保证生产效率，每次会议时间控制在一小时。
To exhaust their potential, retrospective sessions take place at the end of each two-week iteration and are limited to one hour to ensure productivity.
保持Scrum中在小团队中有意义的部份：每日站立会议、短迭代、检讨、回顾、burndown。
Keep just the parts of Scrum that make sense in a smaller group: daily standups, short sprints, reviews, retrospectives, visible project burndowns.
保持Scrum中在小团队中有意义的部份：每日站立会议、短迭代、检讨、回顾、burndown。
Keep just the parts of Scrum that make sense in a smaller group: daily standups, short sprints, reviews, retrospectives, visible project burndowns.
应用推荐