Standard process documentation for all phases of the Internet product

1. Demand phase

A, demand generation. There are three channels of demand generation:

One, UI (user interface) Designer or PD (product Desiger products planning) to study the needs of the market, put forward demand, should obtain market planning or market research staff approval;

Second, the business unit put forward demand, including general manager, research Department, Content editorial Office, customer service Department, exhibition Industry Department, marketing department and other departments.

Third, UI or PD research users, put forward requirements. This step needs to provide user habits reports, experience goals, user interviews, research, traffic statistics, etc. as a basis, not imagined.

All requirements need to go through PD. Without the demand of PD, the technical department has the right to refuse to develop or be responsible for the demand. Even if planning and design are not required, it should be submitted to PD for filing.

B, MRD (market Requirements document).

The MRD needs to articulate the purpose and objectives of the product's needs, and identify what new products, programs, and services can be successful in the market or in the interior, and what success they want to achieve. The MRD explains "what" and "why", but do not write "how" (i.e. do not include flowcharts and prototype diagrams).

When the demand for a product is high priority (that is, the project is approved), the demand side must provide the MRD documentation. The priority, weight and suitability of the product requirements shall be determined by the project Implementation Committee, and the daily requirements shall be determined by the head of the Committee and non-conventional requirements will be met. Individual minor modifications do not even require PRD and can be communicated directly by PD to the technical department.

C, requirements review. When PD receives explicit demand, it should carefully analyze the real intentions of the demand side. Sometimes the idea of the demand side is not necessarily correct, and some are suddenly not feasible, PD needs to be judged, and when that happens, PD has the right to propose its own solution, including the denial of demand. The responsibility is borne by PD because of the conflict of demand and the duplication of development due to errors in judgment. When a dispute occurs, the PM (product manager) coordinates the resolution. When PD finishes the requirements review, it is necessary to inform the demand party of the time required to complete the PRD, the estimated difficulty of product development and the completion period. This step must be.

2. Planning stage

A, PRD (product requirement document request documentation). PRD focuses on the product function and performance of the description, relative to the MRD in the same content, to be more detailed, and quantified. PRD generally include flowcharts, prototype drawings, etc., using use cases and other means to accurately explain. If the MRD is not available, the PRD needs to be explained to the target. PRD is the step that must be passed, which is done by PD or the UI. PRD need to be numbered, please refer to the "Requirements code" form for the number sequence.

B, expert review. The meeting of the PRD, the General project manager and PM is required to participate in the meeting of the demand side, the consultant in the relevant field (i.e., experienced person), PD or UI. If the project is large, the general manager should be invited. The meeting must have a moderator and a memo (memo) or PRD update instructions after the session. After the expert review, PD out the design results of the program, the demand side signature confirmation. After the programmer receives the PRD scenario, it needs to assess the approximate time to complete the development and the task breakdown schedule. When GUI scheme is needed as auxiliary judgment, it needs to be made explicit.

C, interactive demo. The ID (Interaction Designer interaction Designer) makes an interactive design based on PRD, which reproduces the user interaction process and internally reviews it with the PD and UI. PM participates, as appropriate. (Because the company does not have an ID, this step is done by PD with art, visual designers, verbal communication)

D, visual interface. Designed by the art (visual designer) page style, layout, key interface, etc., by the PD, UI, ID for internal GUI (graphical User interface Graphical user interface) review. After the GUI scheme is passed, the page maker begins to cut the page and write the HTML.

3. Development stage

A, background code. Before coding, programmers should design, design, and conduct internal discussions and reviews, inviting consultants to participate, depending on their system needs. If the programmer has any questions or does not understand the document, it is necessary to communicate with PD to understand its true meaning and not to change the PRD and GUI scheme without any reason. There are functions that need to be adjusted, and programmers need to work with PD and the demand side to complete the negotiations. Changes shall be issued in the document, by the demand side, technical manager, PM signed after the effective.

B, Alpha (alpha initial) test. In the development team, the test method is also more, black box, white box, pressure, stress and so on. This phase should be completed more than 80% of the demand development, testing to PRD prevail. After the test is complete, collect feedback, fix bugs, and optimize the process. Developer presence.

C, Beta (Beta second) test. Selectively ask some end-user to actually use, will find the problem feedback, the developer to make final changes to the system, and then prepare to release the final product. Beta test developers are not present. Product estimate development time, to complete beta test prevail.

D, product release. After beta testing, PD verifies the product. If the product and planning program is relatively large, the right to not accept products, responsibility by the development department. The product release date is set as a milestone to assess the efficiency of the entire project.

4. Calibration Stage

A, release tracking. After the product is on-line, PD or market researcher collects the user operation data, detects each feedback channel, filters the data, issues the user test report, and verifies whether the product improvement achieves the expected goal. The project should be specially issued report, non-project changes need to be reflected in the data analysis report.

Standard process documentation for all phases of the Internet product