Lessons from the field on overcoming the challenges of adopting iterative development.
克服采用迭代开发的挑战的学习。
Iterative development — in other words, "Learning as one proceeds" — represents a thousand years of tradition.
迭代开发——换句话说，从实践中学习“——有着数千年的传统。”
In 2001, Extreme Programming teams adapted retrospectives to fit within an iterative development cycle [2].
在2001年，极限编程团队将回顾纳入迭代周期[2]。
In iterative development cycles, risk management and identification are continuously reviewed in each iteration.
在迭代的开发周期中，风险管理和识别在每次迭代中不断地被检查。
This statistic leads us to ask, "If iterative development is so great, why aren't more organizations using it?"
这个统计让我们不仅要问：如果迭代方法那么好，为什么没有更多的组织采用呢？
We're following an iterative development process - and found out that a length of one week seems to work best for us.
我们一直遵循一个循环的开发流程，并发现以一周为循环周期对我们来说最适用。
In addition to the topics of bug reporting and fixing, I'll also cover iterative development and feature enhancements.
除了bug报告和修复之外，还要讨论迭代式开发和特性改进。
Also, iterative development of each application layer fosters the application of appropriate patterns and best practices.
还有，对每个应用程序层重复的开发可能会包含一些适当的模式及最佳实践。
Let's consider how adoption of iterative development impacts the most common roles involved in a software development project.
让我们来考虑对迭代化开发的采用是如何在软件开发项目中对常规准则发生影响的。
Iterative development is sometimes said to operate on such short time scales that there is no need for planning and estimating.
迭代化的开发有时被认为在很短的时间上执行，以至于不需要进行计划制定或预估。
As a first step toward iterative development, consider one or more functional prototypes during the requirements and design phases.
作为向迭代开发转换的第一步，在需求和设计阶段考虑一个或者更多的功能原型。
Choose this protocol if the intention is to use the source model as a primary engineering artifact in future iterative development.
如果您想使用源模型作为未来重复开发中的主引擎产品的话，那么您就可以选择该协议。
By contrast, a real project, using an iterative development process, requires the team to perform most activities early and often.
与之形成对照，一个运用迭代方法过程的真实的项目，要求开发团队尽早并且经常的完成大部分活动。
Testing is carried out throughout the whole iterative development cycle, each time with a different goal, known as a mission according to RUP.
测试是在整个迭代化开发周期中执行的，每次都有一个不同的目标，依照RUP这是大家都知道的一个任务。
Iterative development, on the other hand, allows projects to proceed by small steps, or increments, to gradually build a more complete system.
而开发迭代允许项目小步进行或增长，逐渐完成整个系统。
But it also has important significance in iterative development environments where any given transformation is likely to be invoked many times.
除此之外，在重复的开发环境(任何转换都可能被多次调用)中，它也具有重要的意义。
Incremental and iterative development across this gap is not trivial, as changes in each side might have significant implications for the other.
在此行业差距之上进行增量式和交互式的开发并不是无关紧要的，因为每一方的变动都有可能对另外一方造成重大影响。
RUP provides a structured approach to iterative development, dividing a project into four phases: Inception, Elaboration, Construction, and Transition.
RUP对迭代开发提供了一个结构化的方法，它将一个项目划分成为四个阶段：初始阶段、细化阶段、构建阶段和产品化阶段。
SAs are usually built by casual programmers using short, iterative development life cycles that often are measured in days or weeks, not months or years.
情景应用程序通常由临时程序员使用较短的迭代开发生命周期构建，该生命周期通常用天或周度量，而不是用月或年度量。
We have found that iterative development is most effective when you combine it with a deliberate balance of early risk reduction and early value creation.
我们已经发现，当您将迭代开发与及早的风险减少和及早的价值创造的谨慎平衡相结合时，它是最有效的。
In an iterative development lifecycle, modification to requirements based on the current situation or need is not only acceptable, it's actually expected.
在迭代开发生命周期中，根据目前的情况或需要对需求的修改不只是可接受的，而且也是实际被期望的。
In iterative development, this is much like substituting one optional feature for another as we continually learn about our project and our customer needs.
在迭代开发中，这类似于随着我们不断地了解我们的项目和客户的需求，用一个可选特性来替代另一个。
When using the iterative development approach embodied in RUP, the project manager maintains a list of risks sorted by likelihood of occurrence and impact.
当使用RUP中具体化的迭代开发方法时，项目经理保留着一个按照出现和影响可能性排列的风险列表。
Service versioning also allows for iterative development of a service and its continuous improvement and enhancement based on business function requirements.
服务版本控制还允许对服务进行迭代开发，并能基于业务功能需求进行持续的改进和增强。
This would extend the typical developers' model of iterative development to include the requirements specification of the release and its system testing.
这将扩展典型的迭代式开发模型以包括发行的需求规范及其系统测试。
It is not a surprise that most projects adopting iterative development claim that an increase in quality is a primary tangible result of the improved process.
多数采用迭代开发方法的项目声称改进过程带来的主要结果之一是质量的提高，这也就是意料之中的了。
In order to drive home iterative development in software engineering, each team must demonstrate working software each Friday rather than attending a lecture.
在软件工程课程中，为了驱动迭代开发，每一支团队必须在每一个周五演示运转的软件，而不仅仅是出席讲座。
In an iterative development lifecycle, continuous experimentation is viewed as a good thing, and early prototyping is encouraged in each development iteration.
在迭代开发周期中，持续的验证是一个好的方法，在每一个迭代开发早期的原型是被鼓励的。
This means that the requirements process needs to be tightly integrated with, and executed to the same timetable of, the iterative development of the solution.
这意味着需求过程需要被紧密的集成，按照与解决方案的迭代式开发同样的时间表运行。
Given the complexity and coordination requirements found in many SOA projects, it is not uncommon to see incremental or iterative development practices in use.
由于许多SOA项目中存在复杂性和协调需求，增量式或迭代式的开发实践并不少见。
应用推荐