How to reduce software project risks-including customer risks and software provider risks

Introduction:
"Reducing software project risks" is generally a problem that the project manager of the software provider is thinking on his own. This article puts forward some ideas based on "Reducing customer risks together" and "software provider risks.
1. Traditional mode: Write demand analysis, design, programming, testing, and delivery to customers
2. Agile development mode: through multiple iterations
Disadvantages: it is difficult to control the number of iterations, and it is difficult to explain to the customer when the iterations can be completed. The customer is used to the ability of software providers to quickly implement changes in demand, which will cause the customer to not seriously think about the problem.
3. Your own mode:
A) first adopt the agile development model, record the brief requirements, quickly develop a model, and present it to the customer. (Note: This is a demo, not a delivery. In this phase, you do not have to pay the customer first to reduce the customer's risks .)
B) determine whether to implement the project based on the demonstration results. If necessary, perform a detailed requirement analysis. Estimate a relatively large completion time, and provide the project fee per unit time and the total fee of software development. (For example, this project takes six months and requires 20 thousand yuan each month. The total price is 20 thousand/month × 6 months = 0.12 million ). It can also be divided into more careful calculation methods.
C) segment the development time of each requirement and calculate the exact time.