Product Review.

Is there a time when the product review is interrupted by a high-level, stating clearly that this product is inconsistent with the direction of business development and cannot be implemented? Are some people nodded when explaining the product? Whether the product review is too intense often forget some of the comments collected ...

believe that similar to the above situation in your products have also encountered, product review as a product to check the important link, the importance of product review is self-evident. What exactly is the product review?

Review, as the name suggests, is a step in reviewing and approving project plans, product changes, and work progress evaluations.

Product review in the product process occupies a very important link, is the product molding, product quality, product progress and other aspects of the detection and evaluation process.

Importance of review:
1. Demand is the most important development of an input, a good start is half the success! Therefore, the quality of product requirements to a large extent determines the quality of products.
2. Product risk is often the biggest risk in the software development process, to reduce the risk of the demand phase, we need to do a good job review.
3. Product review do not have the consequences:
1 Requirements Change
2 product target is not clear
3 The product cycle is not planned
4 product function can not be realized
Lead to difficult or frequent changes in follow-up work.
4, Product Manager: "Do not know the truth, only the body in this mountain," the demand is their own written, easy to be fixed thinking restrictions, so, need a pair of eyes have not seen this need to check, what is the problem.
Different levels of product requirements:
Target demand: Defines the goals that the entire product needs to achieve;
Functional Requirements: Define the tasks that the entire product must accomplish;--middle-level attention
Operational requirements: Defines the specific human-computer interaction that completes each task;
In doing product review, should be based on different levels of product requirements, different assessment.

So how do you do the product review?

Recommendation One: Hierarchical review
We know that user needs can be layered, in general can be divided into the following levels:
Target demand: Defines the goals that the entire product needs to achieve;
Functional Requirements: Defines the tasks that the entire product must complete;
Operational requirements: Defines the specific human-computer interaction that completes each task;
The target demand is the enterprise's senior management's attention, the functional demand is the enterprise's middle-level management personnel's concern, the operational demand is the enterprise's concrete operator's attention. For different levels of demand, its description of the form is different, participation in the review of the staff is also a difference. If the specific operators to review the target demand, may easily lead to "foolish, lost watermelon" phenomenon, if the senior managers also to review those operational requirements, is undoubtedly a waste of resources situation.

Recommendation II: Combination of formal and informal reviews
Formal review means the form of a review meeting, organize a number of experts (can be different types of product managers, but also for the product-related departments of the responsible), the product involved people together, and define the role and responsibilities of the reviewers, the product of the formal meeting review. And the informal review does not have such a strict form of organization (that is, the so-called brainstorming method), and generally do not need to gather people together to review, but through e-mail and even online chat and other forms of demand assessment. Each of the 2 forms has advantages and disadvantages, but often informal reviews are more efficient than formal reviews and are more likely to identify problems. Therefore, in the review, should be more flexible use of these 2 ways.

Recommendation III: Phased review
Should be in the process of product formation in a phased review, phased review can be the original need for large-scale review split into small scale of the review, reducing the risk of product rework, improve the quality of the review. For example, in the formation of the target product demand after a review, in the formation of the system's initial summary of the product to conduct a review, when the summary of the product divided into several parts, each part of the review, and ultimately the overall needs of the review. This approach to the evaluation of the understanding of the staff and product managers to organize the review of the continuous inertia of higher requirements.

Recommendation IV: Carefully selected reviewers
Product reviews may involve people who are top management, middle management, potential users, developers, testers, interactions, UI vision, and more. In these people, because of the different positions, the view of the same question is not the same, some of the views are related to the objectives of the product, some are not very related, different views may form a complementary relationship. In order to ensure the quality and efficiency of product review, it is necessary to select reviewers carefully. The first step is to make sure that the different types of people are involved, otherwise it is likely to miss out on important needs. Second, in different types of people to choose those who are really related to the system, the system has enough knowledge of the people involved, it is likely to reduce the efficiency of the review or ultimately impractical to modify the scope of the system.

Recommendation five: Make the most of the demand matrix
The requirements matrix is a good review tool, product managers need to list requirements, through the functional needs of the explanation, as well as related to personnel and the implementation stage, the importance of dividing, so that more people understand the product requirements, as well as the people involved, understand the needs of the product impact, whether there is independence, Product Requirements for product function iterations. List Detailed product requirements and express them directly to the reviewers.

Recommendation Six: Establish a standard review process
Formal product review will need to establish a formal product review process, according to the activities defined in the process of the normative review process. For example, in the review process definition may specify the entry conditions for review, review the information to be submitted, the staff responsibilities of each review meeting, the specific steps of the review, the criteria for passing the review and so on. Through the review process execution may avoid some people to the product problem quarrel scene appears, lets all personnel position the product appraisal domain, the personnel professional.

Recommendation seven: After the review of the follow-up work
After the review, it is necessary to evaluate the issues raised by the reviewers to determine which issues are to be rectified and which can not be corrected, and to give sufficient objective justification and evidence. When identifying the issues that need to be corrected, make a written request for change, enter the management process of the change, and ensure that the change is carried out and reviewed after the change is completed. Not after the review, not to track the problem, and can not guarantee the implementation of the results of the review, so that the early assessment of the efforts in vain.

Recommendation VIII: Full preparation for review
The quality of the review depends to a large extent on the preparation activities prior to the review meeting. The common problem is that the requirements document was not sent to the review meeting before the review meeting, and no more time was left for the reviewers to read the requirements document. What's more, there are no entry conditions to perform requirements review, there are a large number of low-level errors in the review document or communication before the review, there are directional errors in the document, which results in low efficiency and poor quality of the review. For the preparation of the review, a checklist should also be defined to implement each preparatory work against the checklist before review.

Product review needs to face a lot of problems, the preparation of the review will allow you to do the product review process, do a good job of evaluation of the collection of opinions, the quality of the product "".

This is the afternoon with the company's related personnel Taobao Project review after the summary, of course, in the product beta version of the product will be reviewed, when more is to allow users to conduct product review. Product review is so little, the reaction is product manager of product flow and product direction of understanding, at the same time, to other relevant personnel psychological a bottom, let more people understand what you do, why to do so, and how to do, what people to do, how better to do, give everyone a successful signal transmission -The product will surely succeed.

Source: http://www.537520.com/?p=622