When demand changes are approaching

I have already arranged a 5.1 trip with my wife last night. I hope you can have a good rest in the US for a few days. But this morning, the customer called and said that the demand had changed, which was a mess.

At the beginning, everyone was a little overwhelmed. After all, this demand change has a big impact on the system, even more depressing to everyone is that this change is a method we previously recommended for them. However, if the customer has seen the software of other companies before, we should not refer to that model for development, we don't know how to use it. Instead, we feel that our suggestions are poor.

But what we are afraid of is this fatal demand change. Everyone is in a strong resistance, and the holiday will take place in the crucial afternoon.

But the complaints are all complaints. The project will be implemented at the beginning of next month, and the scale is relatively large. We can only discuss the solution immediately. There are still a lot of people who are powerful. Everyone puts forward one solution after another, and then supports and denies one after another. In the end, there is a mess, and no one's ideas have been recognized by everyone.

In the past at, the demands of the other party were also clearer during several phone calls. The final solution was that everyone expressed their ideas through the block diagram, after half an hour, everyone patiently listened to others' explanations and analyses, and finally agreed on the same opinions. Now they are in a changed state.

Based on the changes in this demand, I think you need to pay attention to the following points:

(1) it is best to prepare for demand change. During the project establishment process, we have prepared the most basic response to the demand change, software upgrades and maintenance all adopt the automatic update method. Therefore, even if a large change is made, the upgrade and maintenance are transparent to the customer.

(2) In the demand analysis process, all kinds of requirements must be thoroughly understood, and key measures should be made in the case of differences, and signatures should be signed for confirmation. If problems arise in the future, you can find an excuse, or simply say "no ".

(3) Even if the demand changes, do not be afraid. You must calm down and brainstorm to discuss the issue. When the consensus cannot be reached, through detailed explanation and careful listening, we can find the best solution by combining the whiteboard mode when appropriate.

(4) make the final communication with the customer before the writing.

(5) Finally, the most important thing is to carefully test and revise the defects after the revision.