Most software teams still use a waterfall process for development projects.
Illustration多数的软件开发团队仍然在开发项目中使用瀑布型的开发过程。
Metrics like these are difficult to collect in a traditional waterfall process.
像这些量度在传统的瀑布过程中是很难收集的。
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)，而软件开发的过程不能！
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)，而软件开发的过程不能！
应用推荐