——https://www.zhihu.com/question/19844142
Demand management originates from business needs, starts with demand mining, then demand analysis, demand definition, and demand verification. Week by week.
First, the business needs to explain the reasons for the demand, which may be the goals set by the top level, the adjustment of the work process by the middle level, the unsolvable problems encountered by the grassroots level, the needs of users, changes in the external environment, changes in competitors’ strategies or government policy adjustments.
When clarifying business needs, the requirements personnel first identify the stakeholders, and secondly obtain the requirements/requirements of the stakeholders. The methods that can be used include: industry benchmarking (competing products), business rule analysis (product analysis), brainstorming, focus groups, functional decomposition, root cause analysis, etc.
First, the business needs to explain the reasons for the demand, which may be the goals set by the top level, the adjustment of the work process by the middle level, the unsolvable problems encountered by the grassroots level, the needs of users, changes in the external environment, changes in competitors’ strategies or government policy adjustments.
When clarifying business needs, the requirements personnel first identify the stakeholders, and secondly obtain the requirements/requirements of the stakeholders. The methods that can be used include: industry benchmarking (competing products), business rule analysis (product analysis), brainstorming, focus groups, functional decomposition, root cause analysis, etc.
Second, the goal of the requirements mining phase is to find out the real needs of stakeholders. Unilateral oral descriptions or normative regulations may be far from actual needs. Therefore, demand personnel are required to collect various needs, cross-validate, reasonably derive, and discover the actual needs of users.
Working steps: Confirm the stakeholders, collect the actual situation, integrate various information, and confirm the actual needs. Methods include: interviews, observations, questionnaires, focus groups, brainstorming, usability testing, competitor analysis, data analysis, document analysis, consulting experts, etc.
Third, the requirements analysis stage is to organize the real requirements that have been collected, including two parts, organizing the requirements and prioritizing the requirements.
Organizing requirements uses the same granularity to describe requirements and describe the relationships between requirements. The main methods include: functional decomposition, business rule analysis, data model, process model, scope model, user experience, scenarios and use cases, organization model.
Requirements prioritization provides a valuable reference for scheduling by defining the priority of requirements. Defining dimensions that can be referenced include: time, budget, business value, business and technical risk, implementation difficulty, likelihood of success, norms and policies, relationship to other requirements, agreement with stakeholders, urgency, etc. A class 3/4 priority definition can be used, or a MoSCoW model definition, where M=must S=should C=can W=will.
Fourth, the main work of the requirement definition is to organize the requirement description according to the relevant documents organized in the previous stage. Outputs include: business needs, requirements statement, organized requirements, and requirements prioritization. Requirements description mainly includes: business needs, business requirements and system requirements.
5. Requirement verification includes requirement inspection and requirement confirmation, that is ,
the inspection in the requirement process and the test of the requirement completion.
the inspection in the requirement process and the test of the requirement completion.
From the summary of my work, there are the following points in demand management:
1. Customer needs,
find the core functions and uses of the product from the customer's point of view, analyze the model of customer requirements for the product, and which functions are most concerned and valued, And screen out the real customer needs from the existing data and feedback, instead of simply judging whether the customer wants this thing, likes and hates a certain feature, and why they like and hate it. . . And customers' "suggestions" also need to be analyzed and judged.
1. Customer needs,
find the core functions and uses of the product from the customer's point of view, analyze the model of customer requirements for the product, and which functions are most concerned and valued, And screen out the real customer needs from the existing data and feedback, instead of simply judging whether the customer wants this thing, likes and hates a certain feature, and why they like and hate it. . . And customers' "suggestions" also need to be analyzed and judged.
2. The company's needs,
including the company's business plan, profitability methods, profitability indicators, etc., as well as the company executives and other departments' understanding and requirements of the product interface, function, and process.
3. The needs of other departments
The workload of other departments on the product, the technical threshold, whether the resources are met, etc., as well as the needs of the product project for their own interests.
4. The needs of
the same department The understanding, ideas, and suggestions of the same department on the product, whether it cooperates, and the impact of interests.
All requirements must be repeatedly screened and the real answer can be identified, which can provide a clear direction and method for product design, development and operation. Analysis of needs is to constantly ask why
Requirements tracking matrix is a good thing, can be produced in the requirements analysis stage.