Some practices, like strict code ownership or a waterfall process, can play against refactoring.
某些实践例如严格的代码所有权或瀑布过程，可能会与重构背道而驰。
A key challenge in transitioning from a waterfall process to an agile process is bridging the terminology.
从瀑布流程过渡到敏捷流程时，一个重要挑战就是要衔接术语。
Imagine my surprise when over half of the teams admitted that they followed a fairly straightforward waterfall process!
想象一下，当超过半数的团队承认他们遵循一个相当简单的瀑布过程时我的惊讶之情！
The Internet world is much faster-paced than the database product world, and I was frustrated by our slow, waterfall process.
互联网世界比数据库产品变化快得多，我对缓慢、瀑布型的过程感到沮丧。
Because the development team operated within a rigid, waterfall process, they could not adopt all aspects of agile development.
因为开发团队依照严格瀑布式流程而运作，所以他们不能全方面采用敏捷开发。
Jason estimated that under traditional waterfall process implementing ERP they spent no more than 5-10% on client value added activities.
Jason估计在传统的瀑布流程下实施ERP，他们在增加客户价值的活动上花的时间不超过5- 10%。
These phases are essentially the same for all styles of practices, including the waterfall process, the Rational Unifies process, OpenUp, and an agile approach.
这些阶段对于所有形式的操作都是相同的，包括瀑布过程、Rational统一过程(Rational UnifiesProcess, RUP)、OpenUp以及所有敏捷方法。
My main objection to comparing the two is that the building process can be a totally predictable waterfall process (see Figure 1), while a software development process can't!
对于将这二者进行类比，我主要的异议在于，建造房屋的过程可以是完全可预知的瀑布式的过程(参见图1)，而软件开发的过程不能！
This is not different than the traditional waterfall approach to managing scope, though likely it will be a leaner process.
尽管它可能是一个更简洁的流程，实际上这种做法与传统的管理范围的瀑布方式并无不同。
However, that runs counter to the thinking behind the waterfall approach: Many design teams would view modifying the design after Stage 1 as a failure of their initial design or requirements process.
然而，使用瀑布型开发方法的执行与想象是相反的：很多设计团队把在阶段1之后的修改设计视为他们的最初设计或者需求过程的失败。
Defining a strict sequence, as in a waterfall model, is just as much a process as defining a semi-ordered sequence of iterations in parallel work.
定义一个严格的序列，比如在瀑布模型中，与在并行工作中定义一个半排序的迭代序列是基本相同的。
This contribution extends beyond, for instance, demanding delivery of something testable earlier — or executing a standard battery of tests earlier — than in a traditional, waterfall-driven process.
该贡献远远地扩展了，例如，要求更早地测试交付内容——或者更早地执行一组标准的测试——比传统的瀑布驱动过程中。
Often, organizations investigating IBM Rational solutions have many varying process/methodologies in-house that are all serial or "waterfall" in nature.
通常，调研IBMRational解决方案的组织有很多种不同的过程或方法，它们内部都是顺序的或者自然瀑布型的。
The existing architecture was fixed to a serial — what IBM Rational might call "waterfall" — development process.
现有的架构是固定在一个串行的——IBMRational可能会称之为“瀑布式”——开发过程上。
Now we even see some product maintenance teams utilizing Kanban systems in a waterfall-like process model.
我们甚至可以看到一些产品维护团队在类似瀑布过程模型中使用看板系统。
Figure 6: Estimation in waterfall and iterative process lifecycles.
图6：瀑布和迭代生命周期中的评估。
Once upon a time, testing was the final phase of a waterfall-style release plan, undertaken at the end of the software development process.
以前，测试是瀑布式发布计划的最终阶段，在软件开发过程最后进行。
As the project moved into the waterfall qualify phase — in which the development team needed to handle a constant stream of testing defects — the team's scrum process ended.
当项目进展到瀑布验证阶段——在此阶段中开发团队需要处理持续的一串流程来测试缺陷——团队的scrum流程就结束了。
Presently the main software process models are waterfall model, V-Shape model, incremental model, spiral model, rapid prototype model and parallel model.
目前的软件过程模型主要有线性模型、V模型、增量模型、螺旋模型、原型模型和并行网络模型。
This system adopts waterfall method function menu and browse data edit menu. The data flow and work flow are designed according to practical work process.
该系统采用瀑布式功能选单和全屏幕数据选单，数据流程、工作流程完全根据实际工作过程设计。
Using a traditional waterfall-oriented process leads to a cycle of write all the requirements, analyze the requirements, design a solution, code the solution, and then finally test it.
传统的、面向瀑布的方法会导致以下循环：记录所有的需求、分析这些需求、设计解决方案、编写解决方案代码、最后测试它。
Using a traditional waterfall-oriented process leads to a cycle of write all the requirements, analyze the requirements, design a solution, code the solution, and then finally test it.
传统的、面向瀑布的方法会导致以下循环：记录所有的需求、分析这些需求、设计解决方案、编写解决方案代码、最后测试它。
应用推荐