Problems caused by changing customer requirements during the project cycle

Recently, I have been busy with customer upgrades and maintenance. Some time ago, I joked that I am not a developer, and I have become an implementation and service personnel;

 

The root cause of the problem is that after the system is delivered to the customer, the customer raises such a problem. We have tried our best to avoid such changes,

 

However, some requirements are just wishful thinking and the customer does not agree. This will inevitably lead to a longer project cycle, and constant modifications will cause system instability.

 

(This happens once. Due to the urgent requirement of the customer, there is not much time for testing after the update, which causes problems for the customer to use ).

 

So now the customer has a big head, but it still needs to be done with a hard head.

 

 

As mentioned above, we are sure to have a lot of complaints, unreasonable project control, unclear demand acquisition, and untimely customer communication;

 

 

However, I personally think that, in the final analysis, it is not the inaccuracy of our needs, but that small enterprises do not know what their systems actually regulate;

 

In the early stage of the project, based on the customer's needs, we made multiple project requirements and communicated with the customer to confirm whether such a function was available. At that time, the customer was confident and confident.

 

This is the case (in fact, they don't know, they need you to make them see if they match, rather than making them in the early stage ).

 

After the delivery is completed, it will be like this: "Can you add this?", "or this is not the case. We actually do this ", "This is a little longer "......

 

 

Now the customer has this misunderstanding and thinks that everything can be controlled by the system (What should you do for your staff? Just quit). In fact, the software only helps you manage it,

 

To standardize your processes, it is to assist in management, rather than using software to serve as the Controller;

 

Therefore, I have encountered many unreasonable requirements in the future. I have explained that these things require human control. They are problems with your enterprise system, and software is not omnipotent;

 

 

This is also an experience that needs to be summarized and improved constantly!