0
0
This model began to be used in the 1930s. As an example, let’s take the development of a social network.
The customer needs to create a social network. He formed a detailed terms of reference. The developers offered to first create basic functions in the form of a page with personal information and chat. After that testing will be done on real users.
The customer evaluates the product and makes a decision about its release. If the customer and users are satisfied with the result, the further work is done in parts.
Developers simultaneously organize the functionality to download photos, exchange documents, listen to music and other operations, which are previously agreed with the customer. Step by step the product becomes more and more perfect, becoming more and more similar to the formed reference.
Advantages:
- No need for a large material investment at the initial stage. The customer only needs to pay for the development of the basic functionality. After that he receives the product and can release it. The decision to continue the development will be based on the feedback from real customers.
- The possibility of timely feedback for rapid updating of the terms of reference. Thanks to this approach the probability of getting an unclaimed product is minimized.
- A lower cost of error. If any problems in the architecture are identified, they can be fixed at a lower cost compared to the previous two models.
Disadvantages:
- Each of the development teams is involved in creating separate features. This can lead to uncoordinated implementation of the PP interface. To avoid this situation, the final result should be precisely defined at the stage of discussing the terms of reference.
- Programmers may slow down the process of creating the product by postponing the configuration of main functions and excessively focusing on small details. Thus, it is necessary to focus on managing software development. For this reason, the project manager needs to exercise strict control over the actions of each team.
This model is best suited when working with projects for which the terms of reference is formed in the early stages, and the software itself should soon be released on the market.
