软件开发方法和开发模型_传统的软件开发方法

软件开发方法和开发模型

Traditionally, Waterfall project teams face three constraints: Time, Cost, and Scope. They were unable to change any of these things once their project started.

传统上， Waterfall项目团队面临三个约束：时间，成本和范围。 项目启动后，他们将无法更改其中的任何内容。

The problem is, during the course of a project, the business environment changes around you. This means, by the time you are done, what you built is no longer valuable. This isn't anyone's fault. Business needs are changing more rapidly than ever. Project requirements are shifting just as quickly to keep up.

问题是，在项目进行过程中，您周围的业务环境会发生变化。 这意味着，当您完成工作时，所构建的内容将不再有价值。 这不是任何人的错。 业务需求的变化比以往任何时候都快。 项目需求的变化速度跟得上。

In the traditional approach, first the client requirements are documented in details, architecture of the software is planned and conceptualised and then the work starts to produce the end product.

在传统方法中，首先详细记录客户需求，规划和概念化软件的体系结构，然后开始生产最终产品。

用Scrum解决项目问题 (Solve Project Problems with Scrum )

Teams were doomed to failure on every project until the Agile manifesto came along. Then we shifted our focus away from constraining all three project's elements, and decided to make one of them flexible.

在敏捷宣言出现之前，团队在每个项目上注定要失败。 然后，我们将重点从约束所有三个项目要素转移到其他方面，并决定使其中三个要素具有灵活性。

Agile is a broad umbrella of many methodologies that follow the same principles. Scrum is one of them. Scrum took it a step further by creating a framework to help teams stay focus and protect them from distractions. Essential to Scrum are two key roles, the Product Owner and the Scrum Master.

敏捷是遵循相同原理的许多方法的广泛保护 。 Scrum就是其中之一。 Scrum通过创建一个框架来帮助团队保持专注并保护他们免受干扰，从而进一步向前迈进了一步。 对Scrum至关重要的是两个关键角色，产品负责人和Scrum主管。

In Scrum Framework, the client is constantly involved during the course of development, reviewing bits and pieces created, time and over. The cost of testing a product is less when it is being tested in parts separately. It is easier to test and produces more robust product.

在Scrum Framework中，客户端在开发过程中一直参与其中，不断地检查创建的点点滴滴。 如果分别对零件进行测试，则测试产品的成本会更低。 它更易于测试并生产出更坚固的产品。

翻译自: https://www.studytonight.com/scrum-framework/traditional-approach

软件开发方法和开发模型