瀑布式开发方法可以很好地工作。
避免瀑布式开发方法。
瀑布式开发经常失败的一个原因是，他不能够处理变更。
One of the reasons that waterfall development so often fails is that it's unable to handle change.
许多敏捷团队的失败正是由于缺乏高层支持，最终不得不重回瀑布式开发。
Many agile teams have failed precisely because of the lack of executive support and have gone back to waterfall.
迭代式增量开发为业务提供了超越传统的瀑布式开发方案所提供的更多的优点。
Iterative and incremental development offers businesses many benefits above and beyond those proffered by the more traditional, waterfall development approaches.
我同时与多个团队一起工作，其中有使用传统瀑布式开发的，有使用敏捷的，还有创建电子表格的。
I'm working with multiple teams, one of which is using classic waterfall, another is Agile, and yet another is creating spreadsheets.
请记住，需要对项目活动进行迭代；传统的瀑布式系统开发方法的风险经常要高得多，特别对于大型的复杂项目更是如此。
Keep in mind that the project activities need to be iterative; the traditional waterfall approach to system development is prone to much higher risk, especially for large and complex projects.
瀑布式的开发过程有很少的灵活性，并且不会为你提供高风险的很多早期警告。
Waterfall development processes are much less flexible and don't provide as many early warnings of high risk.
对于将这二者进行类比，我主要的异议在于，建造房屋的过程可以是完全可预知的瀑布式的过程(参见图1)，而软件开发的过程不能！
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!
以前，测试是瀑布式发布计划的最终阶段，在软件开发过程最后进行。
Once upon a time, testing was the final phase of a waterfall-style release plan, undertaken at the end of the software development process.
“瀑布”式开发和缺少服务版本控制。
此瀑布式项目的整合开发流程包含以下阶段。
The integrated development process for this waterfall project included these phases.
现有的架构是固定在一个串行的——IBMRational可能会称之为“瀑布式”——开发过程上。
The existing architecture was fixed to a serial — what IBM Rational might call "waterfall" — development process.
我们开始了第一个会议，目的是讨论迭代和和增量的软件开发优于顺序(“瀑布式”)开发的力量。
We came to the first meeting intending to discuss the strengths of iterative and incremental software development over sequential (" waterfall ") development.
因为开发团队依照严格瀑布式流程而运作，所以他们不能全方面采用敏捷开发。
Because the development team operated within a rigid, waterfall process, they could not adopt all aspects of agile development.
因为每个公司都有各自的开发模式(瀑布式或者敏捷)，应用程序必须拥有足够的灵活性以满足不同的团队。
Since every company practices their own style of development (waterfall or agile), the application has to be flexible to meet the needs of different teams.
以及这些对于预算意味着什么？可以对敏捷开发作出这些重要的评估，但是这种思考方式与您在瀑布式方法中的思考方式不同。
These important types of assessments can be made with agile development, but it’s a different way of thinking than you might be used to with waterfall methodologies.
本文介绍了开发团队如何在较大型的瀑布式项目中成功地实现敏捷开发。
This article describes how that development team was able to successfully implement agile development within a larger waterfall project.
瀑布式方法是其中第一个这样被定义的系统开发过程。
The Waterfall methodology was one of the first such defined system development processes.
瀑布式需求，迭代式解决方案开发
下面的图片使用瀑布式方法、螺旋型方法或迭代过程中的任何一种方法来描述当前开发环境。
The following graph demonstrates the current development environment, using any of the Waterfall, Spiral or Iterative processes.
文章通过对数据仓库技术以及传统瀑布式软件开发模型的分析，提出了数据仓库开发的螺旋式开发模型。
This paper presents a new spiral development model based on data warehouse through analyzing the data warehouse technique and traditional software development model of waterfall.
后来，美国国防部意识到瀑布方法是行不通的，并最终于1994年发布了取代DOD-STD - 2167的标准MIL - STD - 498，支持迭代式开发。
Eventually, the DOD realized that the Waterfall method was not working and in 1994 replaced DOD-STD-2167 with MIL-STD-498, which supports iterative development.
后来，美国国防部意识到瀑布方法是行不通的，并最终于1994年发布了取代DOD-STD - 2167的标准MIL - STD - 498，支持迭代式开发。
Eventually, the DOD realized that the Waterfall method was not working and in 1994 replaced DOD-STD-2167 with MIL-STD-498, which supports iterative development.
应用推荐