Customers put forward some rigid requirements, which cannot be verified. How to deal with them

　　When negotiating a software project, if the customer puts forward some hard requirements that cannot be verified, how should we deal with it? For example, if the performance is improved by 80% on the original basis, these requirements cannot be verified, but the customer has strong requirements, and the company has I am eager to get the project. As a project manager, I feel the possible risks and do not have enough time to verify it. What should I do? Many people who have been engaged in project management have expressed their personal suggestions on this issue. If you are interested, take a look below.

　　Suggestion 1: Promise the client to verify, but it can't be verified. First of all, there is a problem with the company where the project manager is located.

　　Suggestion 2: Tell the customer: We need to do sufficient demand research and demand analysis to analyze the function and performance of the current system. Maybe the performance improvement is more than these, but it must be determined according to the results of our final comprehensive analysis. We will work with the customer to determine the acceptance function and performance and related standards in the requirement stage, so as to clearly define the delivery content and quality requirements. The performance needs to be tested in the actual customer environment and data. If the customer can provide the corresponding environment, the corresponding data, and the corresponding support personnel, we will also cooperate with the verification and assist the customer to accept it together.

　　Suggestion 3: For this kind of problem, it means that the customer's demand is not clear. As a project manager, what we should do is to quantify the customer's demand and improve the performance by 80%. Although it is vague, it can be decomposed as a goal. , decompose this goal layer by layer, and decompose it into a quantifiable and verifiable requirement at the end. In this question, the importance of stakeholders and mining customer needs and controlling customer needs is emphasized. (The premise is to convince the company and customers to give you a certain time for verification)

　　Suggestion 4: The first is to refine the requirements, improve the performance by 80%, what performance mainly refers to, what are the main measurement indicators, and see if it can be quantified. Secondly, evaluate whether the user's needs are reasonable and whether it is feasible in terms of benefits. If not, they would rather give up.

　　Recommendation 5: There are two aspects of communication. On the one hand, we need to communicate with customers to refine the requirements. We must understand the reasons behind the requirements and determine what the real requirements are. On the other hand, it is to report to the company, let the company leaders or upper management understand the progress of the project, and formulate a reasonable work plan later, so that the company can understand the project situation and your ideas, so as to obtain company support, including manpower and time. support.

　　In fact, the toughness of the customer and the urgency of the company must have deeper reasons. The project manager needs to understand these deep reasons through multi-faceted communication, so as to solve the problem in a targeted manner and promote the development of the project.

　　The customer has put forward some rigid requirements that cannot be verified. How to deal with this problem? It is necessary to talk to the technical department and ask them to give some professional evaluations, list some performances that can be evaluated and verified, and give a combination of the actual situation of the customer. What the company can do. Communicate and confirm these results with company leaders and customers. If you can reach an agreement, take over, otherwise you can only give up.

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