Address reprint: http://www.woshipm.com/pmd/865302.html
Product Manager is responsible for the product or product line, can not focus only on demand transformation, but also need to focus on the needs of implementation, both hands grasp with both hands.
Many people may not understand the difference between needs analysis and requirements management, generally speaking we are up to requirements gathering and requirements analysis, the most common procedure describes the general said as how to how demand analysis, demand analysis how to, other activities related needs mention is relatively small. Collection and needs analysis are just a part of the demand management process actually needs.
A project to do for a long time, the feeling is always endless, like a "bottomless pit." I want to finish this project as soon as possible, but there are always new needs to be done. In fact, here's a concept of demand management. Project what to do and what not to do, to what extent, are determined by the demand management process.
Demand management is usually demand management lifecycle, from demand to generate demand for the end of the process can be divided into several distinct phases:
Requirements gathering and collation: Based on the direction of business development of existing products, through communication with our customers, questionnaires and collected user views on the products business, and these views were of a process to classify and organize.
This process requires the product to establish a business model concept, in order to be an abstract description. Users often do not understand technical terms, we need to use language to describe the scene of the way as much as possible to be described. For example, the user would like to study financial management, many users may not know "financial management" of the specific meaning, but you ask him "usually is how to manage the surplus funds, bank deposits are turned into still other ways?" He might be easier understand.
Requirements Analysis: around the product core business, the purpose is to find the actual needs to be done, and clearly the implementation of priority needs.
We have said earlier, the key is to identify the needs analysis of the target user groups, all analytical methods should be targeted based on the use of the business itself and the characteristics of the target user. In addition to finding collect back from the demands which have to do real needs, but also the needs of business value based on the evaluation of the implementation of the priority needs.
Requirements definition: According to the results of research needs and requirements analysis to further define the accuracy of product requirements.
More requirements definition process is a demand for an accurate description of the use of scenes from the user point of view, the function of the angle of operational procedures, to make a complete and unambiguous definition of the analysis out of the real needs, so that other staff can accurately understand the needs.
Needs assessment: the process of confirming the need for the parties to reach a unified understanding and consensus, so that demand can promote the realization of landing.
In the process of needs assessment, we must make clear demands of background, values, meaning, rather than purely demand explanations, it helps to understand the needs of all parties.
Requirements Tracking: follow-up demand for design and implementation process to ensure the realization of the demand is not compromised, and keep up with changes in demand.
By comparing the correspondence between requirements definition and follow-up results of the work to establish and maintain a list of requirements traceability to ensure that products developed based on defined requirements.
Demand for change: When the environment changes due to external or internal error caused demand requirements definition needs to be changed, to make changes to management and control, prevent the implementation process as a result of changes in demand can not continue.
From the strict point of view, the definition of good demand is not allowed to change. But no one can guarantee not make mistakes, and the speed of the Internet environment is changing rapidly, the demand for change is not produced a terrible, terrible thing is out of control change, the implementation of the plan will change too much demand as a whole is disrupted.
Each link above demand management will actually occur among the entire life cycle of demand, but many small partners might not pay special attention to practical work, are more concerned about the link needs analysis, and not pay attention to all aspects of the follow-up , although the cause to find a real demand, but there is no way to landing, or no way to commercialization. From the user requirements translate into more demand for products of the first three links from three product needs to become part of the actual product you need.
Earlier we had talked about special requirements gathering, requirements analysis and requirements definition, which is found and converted a key demand, needs assessment, requirements traceability, requirements change is the key demand of landing. Product Manager is responsible for the product or product line, can not focus only on demand transformation, but also need to focus on the needs of implementation, both hands grasp with both hands.
Requirements Tracking is the product manager for the daily work that must be done
Product managers need to follow up on a daily basis to achieve progress in the current iteration needs to ensure that the implementation process needs no mistakes, in general, demand is divided into two tracks:
Forward Tracking: Each needs to check whether scheduled can have a portion corresponding to the subsequent implementation process to ensure that there is no leakage needs to do, and to ensure that achieve the same level of requirements definition and requirements demand. This requires both confirmation and personnel responsible for implementing each subsequent day.
Reverse Trace: According to the results of the existing interaction design draft document, system design documents, test case documentation, check for the reverse it contains all the requirements have been scheduled.
Most test requirements change, product manager needs the ability to control
There are many reasons for changes in demand, not specific expansion here. Product manager needs to do more to change control, we all know that the demand for products, changes harm than good, but there are also good after changed, but a few. Control rule change is relatively simple:
If the requirements change benefits outweigh demerits will be allowed to change, but change must be performed in accordance with procedures defined, so as not to change out of control. If the requirements change brings more harm than good, then reject the change. Demand change control process is the most difficult thing than the "reject the proposed needs of the user change requests." Product manager for flexible control scale changes to realize business value-oriented products, more products from the point of view.
Demand management is a very important job, according to the survey in a number of failed projects, due to the demand caused accounted for a large part of it. Therefore, demand management have a crucial impact on the product can be attained.