1. Demand management—eliminate the source of all diseases in software development.
In summarizing the products we have done before, especially the unsuccessful products, we can always find some of the reasons; among these reasons, it is not difficult to find. There are not a few problems caused by the reasonable management of requirements, so there will be a situation similar to “the staff is not clear about what to do, but they have been busy developing.” In the end, there will be “the product developed is actually not The cup of the product that the user needs!
Demand is the root of the product, and the quality of demand work has the greatest impact on the product. The source of product development, if the direction is wrong at the beginning, the next work will be wrong and further away from the “good product”, so we first grasp the source and carry out the product development process in an orderly manner.
How can we manage our needs in a reasonable and orderly manner? It is necessary to establish a complete demand management mechanism to manage the entire life process of demand from generation to extinction (demand birth, old age, sickness and death), rationally and effectively allocate the company’s limited human and material resources, and do the most cost-effective things.
2. Demand practice-the way to solve the problem
The practice of demand management mainly includes four processes: demand collection, demand analysis, demand screening, and demand processing.
2.1 Demand collection collects
the needs of different users through a variety of forms, the usual forms are: user interviews, questionnaires, test results, data analysis, etc.; users include: end users, marketers, editors, testers, leaders, etc. . 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 for the products are extensively recorded.
2.2 Demand analysis
In the demand analysis stage, analyze the demand, determine its basic attributes, and what commercial value will it bring to the product after doing it? Increase in the number of users? The cost of personnel, time, etc. required to achieve this requirement is used to finally calculate the cost-effectiveness of the requirement; in this process, the requirement is mainly evaluated in all aspects to clarify the purpose and the value created.
For some requirements such as bugs or small functional changes, no detailed analysis is done. Generally, after the modification is confirmed, it is directly transferred to the demand processing.
2.3 Requirement Screening
The work at this stage is to deal with the requirements based on the status quo, mainly to solve-do it or not? How much do you do? When will it be done? The
form of requirements review is mainly launched in the morning meeting of the team, and leaders are invited to participate. Team members include page designers, front-end engineers, programmers, testers and other roles;
through a review, multiple requirements are packaged, Sort out the demand points required for a version (or sub-project);
form a document for the packaged demand points, submit them for review by the leader, and enter the development cycle after confirmation;
2.4 demand processing The
determined version (or sub-project) For development, the development process is mainly involved here. For details, please refer to the relevant development specifications.
3. Demand collection-Everyone’s participation in
Demand collection is the most important for the entire demand management process. It is the data basis for deciding what to do. Demand collection is not the work before product design, but a continuous process; it is not a product person. It is a matter for all personnel; different personnel and different roles can raise questions about their areas of expertise and different concerns. In the requirements collection stage, we are not afraid of discovering absurd requirements, but afraid of missing them. Reasonable demand…
