The skills that the Internet Product manager should have (requirements chapter)

Product manager needs skills, including demand acquisition, demand screening, demand analysis, demand execution, this series of processes is a product manager comprehensive quality test and comprehensive measurement. such as: the knowledge of the requirements of the industry market understanding and experience.

And in the whole process, how we can quickly and efficiently complete the requirements of the project, but also to our more and more high requirements.

First, write the requirements of the eight ideas

1, reasonable to establish a holistic view, grasp the overall framework;

2, reasonable establishment of business model;

3, a reasonable demand for the dismantling of the system;

4, reasonable reservation system expansion;

5, reasonable handling of business flow, information flow, and data flow;

6, reasonable compliance: business Principles (logic) "→ system implementation principle (logic), and then subdivided into-module implementation principle (logic), specific to-interface interaction principle (logic);

7, the reasonable arrangement needs the priority order;

8, reasonable to do the demand is KO off the preparation.

Second, write the needs of 10 points attention

1, writing documents, must not be in the tools, is the idea, but with good tools, will make your needs accelerated;

2, write the document, must first define the process, after defining the interaction prototype, the prototype is only the carrier of the demand interaction;

3, write documents, must be divided into priority before and after the level, the core, the main needs to go first, the other can be slow;

4, write documents, must be based on the development, can not be unrestrained. (Idea stage can be unrestrained);

5, write documents, must standardize, directory, hierarchy are clear, write to others is to see;

6, write the document, must be clear, not in whether to write more, lies in whether to really explain the problem;

7, write documents, must learn the strengths of competitors, you can learn from the good things, absorb the essence;

8, write documents, must be implemented to every detail, the demand is not perfect, the finished product is perfect;

9, to write documents, must see their own, to their own fault, the problem stop in their own;

10, write documents, must pay attention to version management, and do a revision of the work.

Iii. Eight steps to write a requirement

The first step: Demand Analysis (business model, business mechanism, system function, system logic);

The second step: determine the product definition;

Step three: Determine user goals and user tasks;

The fourth step, determine the product specific positioning;

The fifth step, determine the design of product use cases, processes;

The sixth step, determine the design product prototype;

Seventh Step, packaging requirements documentation;

The eighth step, finally determine the product priority (core, Major, expanded);

Iv. the right way to write requirements (reference)

Purpose: Through the tools-the idea of logic, with the details of the rational organization together!

1, familiar with the project occurrence of related business behavior.

The implication is that we are going to do what the project, our project is mainly to do what business, specific business how we through the more appropriate framework, platform to achieve it, support it. In short, the requirements:

For business (objects), business behavior (design), and the beginning of demand,

For example: through the use of case can be very easy, very clear the entire salesman system intuitive, standardized expression, according to the module to build each package, thus the complex business through the case of intuitive display.

2, the business, from the product level dismembered, so that the cobwebs part and the unity of the whole is generally speaking, is the process problem.

The process is logic, you only have to make reasonable, to meet the business situation. A process that conforms to a system implementation (achievable, easy, or stable implementation) will better support the actual business of future business systems and management systems services. Whether it is invoicing, or SAP principles are in fact interlinked.

3, the project items, organized, the directory structure of the specific provisions of good.

With the protection of the main case and process above, it is necessary to make an entry-based planning for the functional aspects of the system. function How to arrange, set more in line with the use of business logic, how to make users easier, intuitive to start, how a good b/s or C/S function interface presented to the foreground.

4, the structure of the front desk layout, reasonable norms of the system off the hazy Hua yarn.

It is well known that developers and users do not know what the function of this place should be, to what the function of this step, data submission failure has any hint, do not use what Help or prompt operation, portal.

Therefore, as a product personnel we have to fully consider the above to these things, for practitioners this is our most basic elements to reflect. Many people say, to conform to the business system, to conform to the use of habits, to meet the browsing or human-machine communication, word of mouth, brand image habits, is always humane to the design of this thing more reasonable, easier to use, more affinity.

5, to wear knitted nets, the need to synthesize, to form the final product requirements document

To do, and then start to do a document, stating the name of the project, the case/l process, directory, the project background, the requirements of the various constraints, the definition of rules, the text of the supplementary explanation clear, at the same time the module of the field, state, should operate. So the page address of the module design is arranged well, a full-color fragrance of the document will be baked out.

Copyright NOTICE: This article for Bo Master original article, without Bo Master permission not reproduced.

The skills that the Internet Product manager should have (requirements chapter)