Business Requirement survey preparation

Business Requirement survey preparation

Cheng Xiaoxu

[Reserved copyright, reprinted]

This document summarizes the practical work experience in the software development, project management, and consulting and design fields in customer interviews and demand research. It is an internal document for internal training.

1. Overall requirement survey process 1.1 requirement stage work process 1.2 requirement survey process 2 Experience Exchange prepared in the preliminary stage 2.1 internal project Information Communication

The full communication of project conditions is an important basis for project demand research and preparation.Market front-end personnel should conduct formal organization requirements research personnel to explain the project overview, and send the preliminary project information to the technical personnel of the project team as much as possible: including customer relationship, project background, industry development, construction objectives, project owner, demand unit or department. Instead of saying one or two sentences, "if you want to investigate your requirements and start development ".

2.2 demand survey outline

The Demand Survey outline is a key element for the success or failure of the Demand Survey.A qualified demand survey outline has been prepared, and half of the demand interview and survey work has been completed. If the design of the Demand Survey outline is unreasonable, the demand survey and interview activities will be carried out in a rush, it is often unable to meet the expected goal of collecting project requirements, which also leaves a serious risk for the subsequent work of the project.

The content of the Demand Survey outline should be as comprehensive as possible based on actual needs, not just the business aspect; at the same time, it should ensure that the respondent should not be delayed too much time.The Demand Survey outline usually involves the current situation of business management (including the overall business framework, business processes, participants, and statistical reports) status Quo of IT systems (including system name, system vendor, construction time, supporting business, system maintenance, system interface, functional architecture, network deployment, and hardware equipment configuration), business requirements (including management requirements, business support requirements, system construction/transformation requirements, system performance indicators requirements, etc.), documentation (including: reports, workbooks, policy documents, standards, standards, data formats, interface protocol documents, and communication protocol documents ).

2.3 customer interview plan drafting

If the project is complex and involves a large number of departments or personnel, it is best to develop a customer interview plan, with the customer agreed on the specific time of the on-site interview, general issues, etc. When preparing an interview plan, be sure to obtain the consent of the customer's leaders to obtain the support from the leaders. It is best to arrange the interview schedule directly by the customer's project owner/leader; the specific interview time should be communicated, negotiated, and determined at a formal meeting where all stakeholders are present, try to avoid individual appointment of interview time with each interviewee afterwards (this makes it difficult to coordinate the time of each party and disrupt the overall plan ).

2.4 customer interview agenda

The customer interview Agenda refers to the outline of the customer interview content, time, and communication topics for specific customer communication and communication activities, and prepares the customer interview agenda, it aims to explain the form, process, content and time of customer interviews.The customer interview agenda is similar to the meeting agenda in the content and diagram.The customer interview agenda is not a required material before the customer interview, but it is recommended that you make a rough arrangement to help the interviewer sort out and unify the interview ideas. This is especially effective for the case of group interviews with multiple interviewees, this effectively ensures that respondents in each group accept the same interview.

2.5 survey outline review

Based on the specific situations of demand research, the project team submits the survey outline and organizes internal project members and project market owners for brief discussion and review. The survey outline review can be effectiveImprove the content and scope of the survey, clarify the key points of the interview, and remind Relevant Precautions. The review process can increase the importance of preparations for the demand survey outline and ensure the feasibility and effectiveness of project demand survey implementation to a certain extent.

3 survey outline experience example 3.1 business demand survey example 3.2 IT system function status survey example 3.3 It system interface status survey example 3.4 IT system hardware status survey example 3.4.1 host device 3.4.2 storage device 3.4.3 Network device