New demands put forward by customers cannot be accepted blindly

　　In software development, changes in requirements are often encountered problems. The "customer is God" mentality is not acceptable when dealing with changing requirements. The new demands put forward by customers cannot be accepted blindly. It is necessary to think rationally and fully consider the progress of the project and the interests of the company before making a rational choice. When customers put forward new requirements, how to deal with them? And how to better deal with changes in project requirements, what should be paid attention to?

　　In-depth analysis of changes in customer requirements should be made before making decisions.

　　Theoretically, it should evaluate the impact of the changes proposed by the customer on the project, such as cost increase, time consumption, increased risk, etc., and discuss the evaluation results with the customer. If the customer thinks it is acceptable, then Fill out the relevant forms in accordance with the change procedure to implement the change. Otherwise, the change is aborted. Also, who is on the client side who makes the icing on the cake? The person who may propose the change does not have the authority to approve, so the change may not be considered.

　　Communication with customers is to be flexible and clearly point out the pros and cons.

　　Communicate with customers the corresponding time, cost, labor, and risks that will arise from increasing these demands. When putting these resistances in front of customers, you should also stand from the customer's point of view and make a certain affirmation of these icing on the cake. If you can find a small demand that is both bright and relatively easy to achieve to meet customers, then It is easier to reject other demands.

　　Pay attention to the following points when dealing with changes in project requirements

　　(1) the contract system (although there is no legal benefit, but it can restrain customers to a certain extent), let customers know the cost of changing requirements; when contacting customers, you should clarify your attitude, especially It is to make them aware of the costs and risks of random changes in requirements. If the customer thinks that the cost is too high, then there is no need for developers to modify it in time, and go according to the original progress, but still need to record the changes and wait for the next version to modify.

　　(2) Confirm whether the customer accepts the price of the change

　　(3) Report the monthly change record to the leaders of both parties

　　Finally, the implementation consultant should copy the relevant change measures and records to the highest level of both parties for the record at any time, which can take various forms such as briefings, documents, copying, copying, and meetings. Take the initiative and gradually make unreasonable and frequent changes to become embarrassing events that customers are embarrassed to talk about, form a normal project execution atmosphere and good work habits as soon as possible, and also leave a foreshadowing for possible responsibility problems caused by changes.

　　The new demands put forward by customers cannot be accepted blindly. Reasonable treatment of changes in customer needs can not only establish a professional and responsible image for customers. Also be able to benefit as much as possible for your team and the company.

　　This article is reproduced from Tuoyuan Youke: www.toyoke.com