The product starts with the requirement requirements and starts with the management

Demand is the root of the product, and the need for work has the greatest impact on the product. The source of product development, if the beginning of the wrong direction, the next work will be wrong to add the wrong, away from the "good products" more and more away, so we first grasp the source, orderly development of the product research process.

I. Demand management--eliminating the source of all the ills of software development

In summarizing the products we've done before, especially the unsuccessful products, there are a number of reasons why it is not difficult to find out that there are not many problems caused by the lack of reasonable management needs, so there will be similar "people do not know what to do, but have been busy development" situation, In the end will appear "developed products are not users need products" of the cup!

How can we manage our needs rationally and orderly? We must establish a complete set of requirements management mechanism to manage the whole life process of demand from generation to extinction (demand), rationally and effectively allocate the company's limited manpower and material resources, and do the most cost-effective things.

Demand practice--the way to solve the problem

The practice of demand management mainly includes four processes: Demand collection, demand analysis, demand screening, demand processing.

2.1 Demand Collection

Through a variety of forms of the needs of different users to collect, the usual forms are: User interviews, questionnaires, test results, data analysis, etc., the user has: end users, marketing personnel, editors, testers, leaders and so on. At this stage, the attributes of the requirements are recorded in detail, and the traceable feedback personnel are recorded, and the requirements of different users on the product are extensively recorded.

2.2 Requirements Analysis

In the requirements analysis phase, analyze the requirements, determine their basic attributes, and what business value will be brought to the product after it is done? Increase in user volume? In order to achieve this request to pay the staff, time and other costs, and finally calculate the demand for cost-effective, in the process of the main requirements of the overall evaluation, Define the value of purpose and creation.

For some bugs or functional small changes such as the demand, do not do a detailed analysis, the general determination of changes, directly into demand processing.

2.3 Requirements Screening

This phase of work is combined with the status quo to deal with the needs, mainly to solve-do not do, how much to do?

The requirements of the form of review is mainly in the team morning, invite leadership participation, team members have page designer, front-end engineers, programmers, testers and other roles;

Through a review, a number of requirements for packaging, sorting out a version (or sub-project) required for the demand point;

To form a document for the packaged demand point, and submit it to the leader for review, confirm and enter the development cycle;

2.4 Demand Processing

The development of the requirement point of the established version (or sub project), which mainly involves the development process, the details refer to the relevant development specifications.

Iii. collection of needs-participation by all

Demand collection for the entire requirements management process is the most important, decide what to do the data base, the demand collection is not the product design before the work, but a process through the always; it is not a matter of product personnel, but of all personnel;

Different people, different roles, can put forward their own expertise in the field of problems, different points of concern, in the demand acquisition stage, we are not afraid to find out what absurd needs, but to be afraid of missing reasonable needs ...