克服采用迭代开发的挑战的学习。
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.
作为向迭代开发转换的第一步，在需求和设计阶段考虑一个或者更多的功能原型。
As a first step toward iterative development, consider one or more functional prototypes during the requirements and design phases.
本文描述了在你采用迭代开发时可能遭遇的文化上的挑战，以及如何应对这些挑战的建议。
This article presents the cultural challenges you might encounter on your journey to adopting iterative development and suggests how to address those challenges.
在迭代开发周期中，持续的验证是一个好的方法，在每一个迭代开发早期的原型是被鼓励的。
In an iterative development lifecycle, continuous experimentation is viewed as a good thing, and early prototyping is encouraged in each development iteration.
作者应用最佳实践--用例驱动开发，关注架构、持续测试和迭代开发--来抵销一些项目风险。
To their credit, the authors applied best practices -- use-case driven development, focusing on architecture, frequent testing, and iterative development -- to offset many of these project risks.
该系列文章中包含的项目交换文件，允许您在准备好应用程序进行迭代开发之前，先熟悉环境配置。
A project interchange file is included with this article series will to allow you to become familiar with the environment configuration before your application is ready for iterative development.
服务版本控制还允许对服务进行迭代开发，并能基于业务功能需求进行持续的改进和增强。
Service versioning also allows for iterative development of a service and its continuous improvement and enhancement based on business function requirements.
当转换成为迭代开发过程的一部分时，甚至很可能在转换执行之后，输入和输出工件都将由人工更新。
When the transformation becomes part of an iterative development process, it is likely that even after a transformation is executed, the artifacts, both input and output, will be manually updated.
在迭代开发中，这类似于随着我们不断地了解我们的项目和客户的需求，用一个可选特性来替代另一个。
In iterative development, this is much like substituting one optional feature for another as we continually learn about our project and our customer needs.
多数采用迭代开发方法的项目声称改进过程带来的主要结果之一是质量的提高，这也就是意料之中的了。
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.
当使用RUP中具体化的迭代开发方法时，项目经理保留着一个按照出现和影响可能性排列的风险列表。
When using the iterative development approach embodied in RUP, the project manager maintains a list of risks sorted by likelihood of occurrence and impact.
很多试图采用迭代开发的组织都失败了，因为这些拥护者在面对组织特有的文化问题时没有足够的准备。
Many attempted adoptions of iterative development fail because the advocates do not adequately prepare to face the cultural issues that characterize the organization.
在迭代开发生命周期中，根据目前的情况或需要对需求的修改不只是可接受的，而且也是实际被期望的。
In an iterative development lifecycle, modification to requirements based on the current situation or need is not only acceptable, it's actually expected.
迭代开发方法典型地将架构师作为项目的开发点，辅助开发团队完成需求阶段，并进行早期的少量编码。
Iterative development methods typically place architects at the beginning of a project, partnering with development teams through requirements and early bits of coding.
我们已经发现，当您将迭代开发与及早的风险减少和及早的价值创造的谨慎平衡相结合时，它是最有效的。
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.
在用MDA工具包开发能够参与到迭代开发流程中的转换时，需要注意一下设计和实现过程中的所有单元。
Developing transformations with the MDA Toolkit that participate in an iterative development process requires some attention to all elements in the design and implementation.
在许多客户合约中，早期开发阶段涉及多个原型版本，需要与应用程序所有者在迭代开发周期中进行协作。
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.
迭代开发就意味着在每次迭代的最后，系统就可以工作，从而系统行为、架构和设计的规格就可以得到验证。
Iterative development means that the specifications for behavior, architecture, and design are reviewed in the light of what actually worked on the last iteration.
传统的项目管理需要的团队成员是涉及面窄的专家，迭代开发在专家还可以有较宽泛的技能集时工作得最好。
Traditional project management required team members who were narrow specialists; iterative development works best when specialists can also have a broader skill set.
迭代开发是一种软件开发方法，能够通过需求和开发项目的连续改进让一个解决方案实现预期目标。
Iterative development is a software development approach that enables the convergence of a solution with the desired goals through successive refinements of requirements and development artifacts.
理解个体如何看待文化将使你洞察你在处理的组织的类型，并因此确定在你采用迭代开发时哪些行为需要改变。
Understanding how individuals view the culture gives you insight into the type of organization you are dealing with and therefore what behavior needs to change as you adopt iterative development.
在软件工程课程中，为了驱动迭代开发，每一支团队必须在每一个周五演示运转的软件，而不仅仅是出席讲座。
In order to drive home iterative development in software engineering, each team must demonstrate working software each Friday rather than attending a lecture.
团队完成迭代开发后，将计算描述点，并查看此前的迭代开发的数据，将呈现一幅如图3所示的图片。
As the team completes iterations, tallies up the story points, and looks at the data of previous iterations, a picture such as the one in Figure 3 begins to emerge.
构建可复用的服务需要创造性的头脑风暴，解决冲突，设计整合，直到到达一个逻辑点，可以进行你的迭代开发。
Building reusable services require creative brainstorming, conflict resolution, design synthesis, and arriving at a logical point that will be used to deliver your iteration.
迭代开发强调了在业务需求变更、尽早测试，以及在原型化阶段更深层次的让客户参与进来方面进行持续的结合。
Iterative development emphasizes continuous alignment with changing business requirements, early testing, and deep client involvement in prototyping and beyond.
它还可以适用于特定的实践，例如迭代开发(软件开发与交付敏捷方法的中心)，它还需要您去考虑所有的元素。
It can also be applied to specific practices, such as iterative development (at the heart of an agile approach to software development and delivery), which also requires you to consider all elements.
集成的生命周期环境启用或促进了介绍的许多其他的实践，包括迭代开发、简单和相关的度量标准，及灵活的架构。
Many of the other practices described are enabled or facilitated by integrated lifecycle environments, including iterative development, simple and relevant metrics, and flexible architectures.
这些结果被表现为与贯穿系统定义、分析、设计、构建和测试的迭代开发周期的开发进展一样的单独视图中的构件。
These results are represented as artifacts in the individual views as development progresses through iterative cycles of system definition, analysis, design, construction, and test.
如果团队提前完成了工作，它始终可以重新返回发行版计划安排，并挑选额外一些可以在迭代开发内部完成的工作项。
If the team finishes work ahead of schedule, it can always go back to the release backlog and pick some additional work items that can be completed inside the iteration.
应用推荐