Maintaining a change management solution is an ongoing, iterative development process.
维护变更管理解决方案是持续进行的、迭代的开发过程。
There are several models for development of the requirements that drive an iterative development project.
对驱动一个迭代式开发项目的需求开发来说存在着数个模型。
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报告和修复之外，还要讨论迭代式开发和特性改进。
As a first step toward iterative development, consider one or more functional prototypes during the requirements and design phases.
作为向迭代开发转换的第一步，在需求和设计阶段考虑一个或者更多的功能原型。
Focus on time-to-value with a shorter, more iterative development lifecycle measured in minutes, days or weeks, not months or years.
强调时效性，使用更加紧凑、迭代性的开发周期，用分钟、天或周而不是年、月来度量。
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对迭代开发提供了一个结构化的方法，它将一个项目划分成为四个阶段：初始阶段、细化阶段、构建阶段和产品化阶段。
The following list describes the features of the culture and environment that our organization needs to build if we hope to adopt iterative development
下面列出一些文化特征，它们描述了如果我们希望采用迭代开发，我们的组织必须构建的文化和环境的一些特征。
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.
在迭代开发生命周期中，根据目前的情况或需要对需求的修改不只是可接受的，而且也是实际被期望的。
This would extend the typical developers' model of iterative development to include the requirements specification of the release and its system testing.
这将扩展典型的迭代式开发模型以包括发行的需求规范及其系统测试。
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.
服务版本控制还允许对服务进行迭代开发，并能基于业务功能需求进行持续的改进和增强。
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.
在软件工程课程中，为了驱动迭代开发，每一支团队必须在每一个周五演示运转的软件，而不仅仅是出席讲座。
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项目中存在复杂性和协调需求，增量式或迭代式的开发实践并不少见。
This article presents the cultural challenges you might encounter on your journey to adopting iterative development and suggests how to address those challenges.
本文描述了在你采用迭代开发时可能遭遇的文化上的挑战，以及如何应对这些挑战的建议。
The compare/merge function for iterative development with WebSphere Business Modeler has been improved to include traceability of business rules and human tasks.
用于使用WebSphereBusiness Modeler进行迭代开发的比较/合并功能已经过改进，现在包括业务规则和人工任务的可跟踪性。
And because agile project management embraces change and iterative development methods, it requires an efficient tool to make design and communication easy and fast.
同时，由于敏捷项目管理热衷于接受变更以及采纳迭代开发方法，因此需要一个有效的工具以更轻松和快捷地进行设计和交流。
Many attempted adoptions of iterative development fail because the advocates do not adequately prepare to face the cultural issues that characterize the organization.
很多试图采用迭代开发的组织都失败了，因为这些拥护者在面对组织特有的文化问题时没有足够的准备。
Traditional project management required team members who were narrow specialists; iterative development works best when specialists can also have a broader skill set.
传统的项目管理需要的团队成员是涉及面窄的专家，迭代开发在专家还可以有较宽泛的技能集时工作得最好。
This article serves as a roadmap that can help you overcome this difficulty and move your team from doing plain iterative development to agile development. The roadmap includes
本文将为您提供一个路线图，帮助克服这些困难并使团队从简单的迭代开发过渡到敏捷开发。
In many customer engagements, the early development phase involves multiple prototype versions where we are involved in an iterative development cycle with the application owner.
在许多客户合约中，早期开发阶段涉及多个原型版本，需要与应用程序所有者在迭代开发周期中进行协作。
应用推荐