迭代也起步于时长为几个小时的迭代计划会议。
An iteration starts with an iteration planning meeting that is a few hours long.
每隔一次迭代(两周一个迭代)，整个团队(很多人距离很远)会参加联合的迭代计划会议。
Every other 2 week iteration, the entire team travels (many are remote), to meet for the joint iteration planning session.
在撰写本文时，我正在协助项目团队准备迭代计划会议，它由四个敏捷团队、超过100人组成，其中包括项目发起人和外部(瀑布)成员。
As of this writing I am facilitating iteration planning sessions with over 100 participants, including sponsors and external (waterfall) members, on 4 agile teams.
在规划会议期间，对于迭代开发计划安排中的每一个用户描述，团队需要分解所有必需的任务，以便对描述进行详细周到的分析。
During the planning meeting, for each user story in the iteration backlog, the team needs to break down all the tasks required for the story to be considered complete.
这包括发布计划、迭代计划、迭代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.
在会议上，团队应当从发行版计划安排中选择它所能承受的尽可能多的高优先级内容项，并将这些内容添加到迭代开发计划安排中。
During this meeting, the team should select as many high-priority items as it can contain from the release backlog and add these to the iteration backlog.
在计划会议时，技术组长就预先将任务、估算和指派等拼装成“迭代计划”，并美其名曰“节省时间”。
Technical Leads will prep "the iteration plan" pre-populating it with tasks, estimates and assignments all in the name of saving time during the planning meeting.
在计划会议时，技术组长就预先将任务、估算和指派等拼装成“迭代计划”，并美其名曰“节省时间”。
Technical Leads will prep "the iteration plan" pre-populating it with tasks, estimates and assignments all in the name of saving time during the planning meeting.
应用推荐