About the Internet operating period product review

Evaluation system is an important means of Internet product management, the evaluation system runs through the strategic planning of product management, product design, technology realization, product operation, product marketing and other links. It can be said that efficient evaluation system is a company's product management capacity of an important measure. Simply enumerate some of the value of the review system:

~ ~ ~ Through the evaluation system can help stakeholders to achieve the goal of product building a consistent understanding;

~ ~ ~ Through the evaluation system can be product planning, product demand, technical solutions, operating plans, marketing programs and other quality checks to improve product quality;

~ ~ ~ Through the evaluation system can be in the process of product planning and construction of key points, risk points, etc. to check, reduce the risk of project implementation

~ ~ ~ Through the evaluation system can effectively improve the ability of the personnel;

~ ~ ~ through the evaluation system to check the scheme to ensure that the system product architecture, architectural design of the spirit of consistent implementation

Although the product review is so important, it seems that no company's assessment system is efficient, and everyone complains about the myriad evils of the review system, whether the review meeting or the performance has changed into a form, or a major faction of the PK Convention. On the review system, in a variety of software engineering books and methodologies are involved, here is not the focus of the discussion review System general guidelines (such as product review that matter), here mainly discuss a platform-type products in the operation of how to pass the review system to check.

1. Construction period Project VS. Operation Period Project

For products such as the payment platform, open platform, the product platform concept of the Internet products (product platform), its construction phase of the product project management and the operating period of the product project management faced with different challenges.

The emphasis on these product platforms, mainly for many Internet products, the main logic is the front end of the site, so these sites are relatively easy to review, only to adopt a prototype-driven approach. But for these platform products, not simply a simple web page development work, the most complex logic of these systems is generally the backend business rules, business logic, and these are not a prototype can be explained clearly.

1), Construction period project characteristics

~ ~ ~ Project cycle is relatively long, such as more than 1 months

~ ~ ~ Project resources are relatively abundant, can be operated as a separate project team

Project management can adopt traditional project management methods or agile project management

~ ~ ~ ~ ~ Project preparation is relatively sufficient, such as product documentation is relatively complete, complete prototype, complete project plan, project discussion/demand Seminar, market research/competitor product analysis, etc.

~ ~ ~ Project is relatively independent, subject to other projects less constrained

2), operating period project characteristics

~ ~ ~ ~ period is shorter, most of 2 weeks below

Limited resources, project team members may also be concurrent maintenance of other products

Because with the expansion of the company's business, familiar with the product and technical structure of the staff is always scarce, these people are generally responsible for a number of key new projects, must be in the work to help new people familiar with the system

Project management typically employs agile project management methods such as scrum, XP, and even reduced agile development

The project preparation is not very abundant, and can not be prepared enough to do

~ ~ ~ The project needs to be optimized and reconstructed on the basis of existing products, and it cannot affect the existing system. For the operation of products, product architecture, system architecture is in a bit of change out of control, deformation, there must be a mechanism to control these factors

This paper focuses on the product review and technical review methods in the operating period.

2. The principle of product review during Operation period

No matter the urgent project must do product review, technical review

~ ~ ~ Review must remain agile

~ ~ ~ The form of the review is not important, the review!= meeting, the form of review can be formally reviewed, can also be informal review. The core of the review is the need for people familiar with the system, the ability to check the scheme

~ ~ ~ The purpose of the review is not to find the best solution, but under the constraints of existing resources the most reasonable scheme

~ ~ ~ No perfect evaluation system, the key in the practice of continuous optimization evaluation system, the establishment of a suitable company for their own assessment system and follow-up measures

3, the Operation period product review method

For the operating period of the product review, there is no best practice program for reference, each company has its own real business situation, different business models have different methods of assessment. It can be said that the operating period of the product evaluation is a balanced art, must be balanced management of normative, agile, business reality requirements. But overall, the approach core of the product review in the operating period is the same: continuous improvement on the basis of teamwork.

~ ~ ~ ~ ~ Operating period of the review system needs the operating period of product development process support. A simplified process for product development in the operating period (as opposed to the product development process in the construction period) should be developed to ensure the continuous optimization of the product review system by collecting and exposing the evaluation system from other process links. For example, through the quality testing, operation, sales, marketing and other aspects of feedback, found that the evaluation system failure of the project, into the case library, continuous optimization of research and development processes, evaluation system

~ ~ ~ Establish the hard standard that must be reviewed, and refine it into quantifiable checklist form (simple first rule)

For example, the development time of more than 1 weeks or less than 1 weeks, but involving the focus of business modules must be reviewed. The reason for the use of the duration and impact of the 1-cut method rather than the use of interface to assess whether the need for review, mainly to avoid too many human factors leading to a mere formality of the review system.

For less than 1 weeks and does not involve the key business model changes, the owner from the line of judgment.

~ ~ ~ Review must have stakeholder participation, can not simply let the product personnel, technical personnel evaluation. For example: The product plan must have the technical personnel, the operation personnel, the finance personnel and so on, the technical solution must have the product personnel, the architect, the business expert and so on. Stakeholders who participate in the review have the right to return the proposal to redo. Of course, there is another big topic involved: teamwork, if a team can't build trust, then the perfect system will become PK.

~ ~ ~ Reviewers do not need to do a comprehensive review, only the requirements of key points, key business rules, risk points of the program to do a review to ensure the efficiency of the review. The results of the review need to be documented in the relevant process form.

~ ~ ~ Set up a review case database, regular (monthly) Review case library, continuous optimization evaluation system. Review the case summary to the matter rather than to the person, does not let the reviewer have must to the result overall responsibility burden.

The implementation of a system does not lie in how perfect the system initially defines, but whether the system can be continuously optimized. Continuous optimization/continuous improvement/continuous refinement is one of the core secrets of various management methods that are well known and effective. But it is also the hardest to implement, especially when it comes to managing fashionable buzzwords, which are too new and too high, and we all expect a silver bullet to solve all the problems.