How to realize the communication and confirmation of business informatization demand list and the approval and confirmation of demand change?

On February 6th, information should be transmitted and confirmed through formal meetings, emails and other mechanisms. Single-line communication should be avoided in the process of information transmission, and relevant project stakeholders should ensure that they understand and master the content of demand communication.

Communication is the main channel and means to obtain information system projects. Through communication, we can understand and master the customer's requirements and expectations for the project, and provide necessary delivery content guarantee and quality evaluation basis for the implementation of the project construction. However, due to the strong customization of information system projects, if effective requirements cannot be obtained in the communication process, the projects will often fail, so we should attach great importance to the communication management of information system projects.

First of all, there must be a detailed communication management plan. According to the characteristics of information system projects, identify and analyze all project stakeholders and their communication methods, formulate targeted communication strategies and communication plans, and communicate with project stakeholders in the process of project construction according to the communication plans. The main contents of communication plan include: scheduled communication time, communication goal, communication content, actual communication time, communication result, etc.

Secondly, we should be familiar with and master the background and business knowledge related to the project. Information system project is the informationization and digitization of customer business content. In this process, the customer's business operations and business processes need to be transformed into operational software systems. If we can't accurately understand the customer's business operations and business processes, it will be difficult for the software system to meet the customer's requirements. In addition, being familiar with and mastering the background and business knowledge related to the project, and communicating with it by using customer professional terms can not only improve the efficiency and quality of communication, but also win the understanding and trust of customers quickly.

Third, we should establish the necessary communication and feedback mechanism. Any communication is a two-way and one-way information transmission, which often leads to misunderstanding or omission of requirements. In addition, due to the different communication methods of project stakeholders, there will be many uncertainties in the description of requirements. Therefore, after each communication, it is necessary to understand and analyze the project requirements, and feed back the understanding and analysis results to relevant customers for review and confirmation, so as to form a consistent understanding of the project requirements.

Fourthly, we should master and use certain communication skills. Everyone's communication skills are different, especially when facing customers with weak communication skills, it is very necessary to use appropriate communication skills to guide customers to accurately describe their needs and expectations. Common requirements guidance technologies include "scenario description", "problem guidance" and "business experience and observation".

Fifth, establish an efficient information transmission mechanism. In the modern network environment, the means of information transmission are diversified, but each has its own advantages and disadvantages. For the communication and confirmation of project requirements, formal meetings, emails and other mechanisms should be adopted to transmit and confirm information, and single-line contact should be avoided when transmitting information, so that relevant project stakeholders must understand and master the content and results of requirements communication.