该问题也波及到所有其他的团队，因为各团队要等待后继者为他们完成迭代的工作，或者等待前驱者给予他们工件进行工作。
This problem ripples across all of the other teams as well, as teams wait for successors to finish their work for the iteration, or for predecessors to give them artifacts to work on.
不足为奇，大部分有关这些问题的讨论没有涉及TDD、或者迭代，甚至没涉及回顾，因为障碍来自团队的外部。
Not surprisingly, most of the discussion around these problems did not involve TDD, or iterations, or even retrospectives, because the roadblocks were coming from outside the team.
首先，映射两个框架似乎是微不足道的事——就是分析阶段、里程碑、迭代和工件的问题。
At first, mapping both frameworks seems a trivial task — a matter of analyzing the phases, milestones, iterations, and artifacts.
这些就是在变更计划时遇到的种种问题，它们必须被处理，处理他们更适合使用迭代的方式。
These are the kinds of questions that result in changing plans and therefore must be addressed, preferably in an iterative manner.
找到并修复这些问题，然后要求开发和质量保证测试的人员对最新代码变更进行完整的迭代。
Fixing the found issues then requires a full iteration of late code changes by development and quality assurance testing personnel.
敏捷，尤其是短迭代，可帮助你尽早发现问题。
Agile, and specifically short iterations, help you discover problems early.
这对早期的迭代特别重要，那个时候更容易纠正设计问题。
This is particularly important for earlier iterations, when it is easier to correct design problems.
本文将描述“重叠迭代”的含义以及为什么会首先出现关于该技术的使用的问题。
This article will show what is meant by "overlapping iterations" and why the question of using this technique comes up in the first place.
在一些我所观察的使用OI方法的团队中，需求人员开始接受变更请求或进行会面以澄清第一次迭代需求中的问题。
With a few teams I've observed that used an OI approach, the requirements people began to receive change requests or meeting invitations to help clarify problems with the first iteration requirements.
很多试图采用迭代开发的组织都失败了，因为这些拥护者在面对组织特有的文化问题时没有足够的准备。
Many attempted adoptions of iterative development fail because the advocates do not adequately prepare to face the cultural issues that characterize the organization.
直到关闭了所有问题的用例，我们才允许完成这次迭代。
We did not exit an iteration until we had closed the cases for all issues.
同样，也可以通过在迭代期间锁定集合防止这个问题。
Again, this can be prevented by locking the collection for the duration of iteration.
所有内容都来自于工作说明，我们得到特性列表和用例图，分解问题，然后选择一个用例开始迭代。
All from a statement of work, we can derive the feature list and use case diagrams, break up the problem, and then pick a use case to start to iterate.
我无法想象的是，无论如何，比起L2S和EF开发人员需要在你的OR M下一次迭代中需要面对的问题而言，API的变化要显得更加的重要。
I do not imagine that the API changes would be any more significant than those that L2S and EF developers will face in the next iteration of your ORM anyway.
请注意，在不同的资产注册中拥有相同名称的迭代没有问题。
Notice that it is fine to have iterations with the same name in different asset registries.
本文的第 1部分介绍了两个场景，主要解决如何在流程模型中设计分支和迭代行为这一问题。
Part 1 of this article deals with two scenarios that address the modeling of branching and iterative behavior in business processes.
好，我知道这看起来有点无聊，但是这是我要去以迭代的方式，去解决一个问题采取的，措施的大致结构。
Ok. I know. It looks boring. But it's a structure of the things I want to think about when I go through trying to take a problem and mapping it into a iterative program.
更多的注意力集中在确保该构造的质量以及问题的尽早处理，从而保证迭代的成功。
More attention is spent on these builds to make sure that the quality is not eroding and issues are dealt with early so the success of the iteration isn't jeopardized.
不管用什么手段SCA都不会完工，因为它可延伸到许多企业问题，但是与其等到我们把海蒸干不如去迭代规范。
SCA isn't finished by any means, there are lots of enterprise problems it could be extended to, but it would be better to iterate a specification than wait until we've boiled the ocean.
JSTL 1.2是一个维护版本，它支持统一el并解决了在同一个jsp页面中混用JSF标记和JSTL迭代标记时遇到的问题。
JSTL 1.2 is a maintenance release that supports the unified el and resolves issues that used to arise from trying to mix JSF tags and JSTL iteration tags in the same JSP page.
第 5章介绍了划分问题、递归函数到迭代函数的转换（我可以向您保证，这非常有趣）以及阶乘和斐波纳级数的实现。
Chapter 5 deals with partitioning problems, converting recursive functions to iterative functions (it's fun, I assure you), and more factorial and Fibonacci series implementations.
插图当计划并执行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'?"
作为替代，Sessions提出了一个部分迭代方法作为复杂度问题的解决方案。
Instead Sessions proposes a Partitioned Iterative Approach as a solution to address the complexity problem.
为了回答这个问题，本系列将采取下面的步骤(通常采用迭代的方式完成)从面向对象模型中标识Web服务。
To answer this question, this series will follow several steps, typically performed in an iterative manner, for identifying Web services from your object-oriented models.
敏捷团队负责人(在Scrum中是ScrumMaster或迭代经理)是第一位的问题解决者。
The Agile Team Lead (in Scrum the Scrum Master, or Iteration Manager) is the first line of issue resolution.
我们也发现我们需要在迭代中期进行检验会议，这 样我们可以问这个问题“在这个反复中我们还需要做多少的工作？ 我们将全部做完么？”
We also found that we needed a mid-iteration checkpoint meeting so we could ask the question, "How much more work have we got to do for this iteration and are we going to do it all?"
“Sprint失败，无法交付”：这个问题可能是由于迭代故事导致的，而这又可以回溯到与产品负责人的协作问题。
"Failed Sprints, inability to release" : its possible that problems with the iteration stories have caused this and can be traced back to problems in collaboration with the Product owner.
在前面两个例子里,每一部问题的规模缩小了,不管是迭代的还是递归的，这表明这个问题的复杂性可能是线性的。
In the first two cases, the problem reduced by 1 at each step.
如果您一次只工作在一个迭代上的话，就不存在这个问题了。
If you work on only a single iteration at a time, this is not an issue.
我们指出迭代可以减少风险并避免一次产生所有产物的与生俱来的问题。
We pointed out that iterations reduce risk and avoid the problems inherent in an all-at-once delivery.
应用推荐