这可能是一个传统的瀑布式方法。
混合使用敏捷式与瀑布式方法。
这是典型的瀑布式方法。
瀑布式方法是其中第一个这样被定义的系统开发过程。
The Waterfall methodology was one of the first such defined system development processes.
瀑布式方法在每个交付阶段的最初和结束时强调客户交互。
The waterfall approach also stressed client interaction at the beginning and end of each phase of delivery.
ADDIE模型有不同的版本，但是，在本质上，它是一个瀑布式方法。
There are different versions of the ADDIE model, but, in spirit, it is a waterfall method.
但正如这种瀑布式方法在编写软件时是失败的一样，在电影制作时这种方法也会失败。
But just as the waterfall approach fails when we're writing software, it would fail in making a movie as well.
虽然瀑布式方法管理了未定义过程的使用，但是，它的线性特点成为它的最大问题。
Although the waterfall approach mandates the use of undefined processes, its linear nature has been its largest problem.
如果该团队使用传统的瀑布式方法，如图1所示，则需要花两到三个月的时间来详细记录所有的需求。
If the team were to use a traditional waterfall-style method, as shown in Figure 1, it would take two to three months to record all the requirements in detail.
这种方法的好处就是相对于传统的瀑布式方法来说，用户会在更晚的时候才被要求提交需求。
The good news about this approach is that users are asked to commit to requirements much later than in a conventional waterfall approach.
下面的图片使用瀑布式方法、螺旋型方法或迭代过程中的任何一种方法来描述当前开发环境。
The following graph demonstrates the current development environment, using any of the Waterfall, Spiral or Iterative processes.
图2所示的敏捷方法产生应用程序工作版本的速度比瀑布式方法仅产生应用程序设计的速度还快。
The agile method depicted in Figure 2 produced a working version of the application faster than the waterfall-style method was able to produce just the application design.
以及这些对于预算意味着什么？可以对敏捷开发作出这些重要的评估，但是这种思考方式与您在瀑布式方法中的思考方式不同。
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.
请记住，需要对项目活动进行迭代；传统的瀑布式系统开发方法的风险经常要高得多，特别对于大型的复杂项目更是如此。
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.
瀑布式开发方法可以很好地工作。
避免瀑布式开发方法。
后来，美国国防部意识到瀑布方法是行不通的，并最终于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.
应用推荐