每隔一次迭代(两周一个迭代)，整个团队(很多人距离很远)会参加联合的迭代计划会议。
Every other 2 week iteration, the entire team travels (many are remote), to meet for the joint iteration planning session.
这些需求会作为进一步的迭代计划和风险管理的基础。
These requirements will serve as the basis for further iteration planning and risk management.
阶段由若干迭代组成——依照基本计划和评价标准的不同序列的活动会致使工件的发布(内部或外部的)。
Phases consist of multiple iterations — distinct sequences of activities with a base-lined plan and valuation criteria resulting in a release of artifacts (internal or external).
设想团队在细化阶段计划两次迭代(e1和e2)，这显然会失败。
Imagine that the team plans for two iterations in Elaboration (E1 and E2), which is fairly typical.
插图当计划并执行RUP项目时，大多数（如果不是全部的话）开发团队会遇到一个有趣的问题：“我们应该让迭代‘重叠’吗？”
When planning and executing a RUP project, most if not all development teams face an interesting question: "Should we allow our iterations to 'overlap'?"
接下来是迭代计划、执行和结束，根据项目的需求，这些步骤可能会重复多次。最后是迭代后计划和发布。
Then we have an iteration plan, execution, and wrap-up which may be repeated over and again depending on the requirement of the project (followed by a post-iteration plan and finally a release).
稳定的团队会倾向于在每个迭代中完成同样数目的这些大小相等的故事，并且管理层也会根据团队已知的能力来制定计划。
A given team would tend to complete about the same number of these equal-sized stories each iteration, and management could make plans based on the team's known capacity.
项目计划期间，很可能会达成应在一系列具有时间限制的迭代中制定产品渐进式要求的协议。
It is most likely that, during project planning, it was agreed that product increments should be developed in a series of time-bound iterations.
项目计划期间，很可能会达成应在一系列具有时间限制的迭代中制定产品渐进式要求的协议。
It is most likely that, during project planning, it was agreed that product increments should be developed in a series of time-bound iterations.
应用推荐