本文讲的是瀑布方法，瀑布方法是用于编程开发的基本方法，在传统软件工程中有详细的定义。在瀑布方法中，开发过程将以一种逻辑的方式从项目的开始流动，也就是从需求收集到项目的结束(Paulck, 2002)。另一方面，敏捷方法是对传统方法的一种替代，在传统方法中，方法是增量式和迭代式的，而不是逻辑级联形式。Scrum是一种最流行的敏捷形式，在这种形式中，定义了具有更多会议的小型团队，以便向团队引入敏捷性(Schwaber, 1997)。本篇英国哈德斯菲尔德大学论文代写文章由英国论文人EducationRen教育网整理，供大家参考阅读。
The waterfall methodology is the basic methodology used for programming development and defined in detail in traditional software engineering. In the waterfall methodology, the processes of development will flow in a logical manner from the beginning of the project, which is the requirements gathering to the end of the project (Paulck, 2002). The agile methodology on the other hand is an alternative to this traditional methodology where the approach is more incremental and iterative rather than the logical cascade form. Scrum is a most popular agile form where smaller teams with more meetings are defined in order introduce agility to the teams (Schwaber, 1997).Change Management: Agile has better change management compared to waterfall. So it can be said that better backward scalability exists in Agile. In Agile methodology, a more flexible iterative approach is being used, where it is necessary for all the aspects of the project to be done in a logical consecutive fashion (Syed-Abdullah et al, 2006). They can be done in an iterative form and quite parallel. With this form of an empirical structure, it becomes easier to structure change into the projects quite easily.
On the other hand, in the case of the waterfall methodology, backward scalability is a little difficult, and the implementation of the previous stage cannot be reversed that easily (Sandler, 2010). Changes in scope management would take time and sometimes it would be necessary to start development from scratch and in some cases development might have to be postponed to the next roll out of the project. The many dependencies that exist in a project should not stop the progress of the project, so better backward scalability adds advantages to the project (Bricaud, 2012). However, having too much changes in the project even as the project is ongoing might delay project indefinitely. Also too many dependent change modifications might lead to difficulty in final integration testing stage and production. Sometimes it is alright to wait for the next roll out to incorporate the changes.The second important characteristic that is observed in the case of agile methodology is that of the continuous team interaction (Ilieva, et al., 2004). Continuous team interaction observed in the form of different team involvement, and structured team communication leads to the individuals of development to interact better.