How to look right: product requirements documentation and product requirements

In fact, when it was still in Beijing, it was once written an article called "Correct writing http://www.aliyun.com/zixun/aggregation/8193.html" > Product Requirements Document (PRD) was later reproduced countless, Now think of it as just staying in the skill level, or through this article, you can get a quick documentation routine.

Because there are still a lot of new people asked me to ask for product requirements documents, they would like to see a typical product requirements document should be what kind of, I directly refused, I will generally say: "Please think more." I understand that: looking at the document itself is meaningless, especially the product requirements of the document, in fact, is the product of demand. As a product is like you use a mobile phone today, look at the phone's instructions, you already know what this product looks like, but why do this, how to do? What to do first, what to do after, you still do not know!

So from the product requirements, the document itself does not have a process of derivation. This is back to a problem, many product managers are not aware of the new person, how to do the demand, how to write the requirements of the document differences. In their subconscious, anyway, the company is required to have product requirements documents such a carrier to express their ideas, so it is natural to learn to write the requirements of the document, you have mastered how to do the needs of the same process.

This sounds a bit around the mouth, but my point of view is: the process of thinking and doing is separate. One is the process, one is because of the product of the process, it is likely that in many cases the product itself may not have much meaning. But from the superficial point of view, the document has no sense of logic, there is no sense of hierarchy, the wording is clear, clear is a realm.

A lot of times we write a program to do ppt, a lot of people write something is completely different. The purpose of the PPT is: Simple, headline, there is a view, there is no shortage of holes. The reason for this example is actually the same. Write the product requirements of the document itself is actually more: the process of product demand derivation. Because there is the process of derivation, and then there is the result of the deduction. Very smooth Zhang, the product manager of the new entry of friends, you also have: "Product derivation" process?

The process of product derivation is: What to do, why to do so, who to do, how to do, step by step how to do, and finally make what, the most what to do so, do not make that. The process of writing requirements documents is actually the process of processing requirements, so do you want to understand these points? Many companies want to do a product, may be high-level is to want a thing, but in the process of implementation because the superior and the understanding of different, so in the process of implementation more or less biased. So in this process, answer the above several essential questions, will correct you to do the thought of the demand, will not make a detour.

Product Manager This group is a very strange group, their subjectivity is very strong, like the product according to their own interests and preferences to do, so come to a result itself is not difficult. Because the result is likely to be the result of a product manager's subjective liking, but if you get a result from the process, this time you will have a different understanding of the outcome than the process and the result itself.

Combined with today's theme: "How the media correctly look: Product requirements documents and product requirements", product requirements documents can be no fixed format, we do not want the product requirements of the document how to imagine how. Write product requirements documents, is to do a product manager of a basic ability to write a sense of how the sense of the level, how to write the clarity and understanding, there is a certain difference. But in essence, whether it's Excel, Word, rose, or TXT, it's secondary.

Purpose: To give you the needs of the people, know what your logic is, let you do with the programmer very clearly know what the requirements are, to your test staff to know your details on it. Later also facilitate the version upgrade, know you a version, a version of what needs, changed what needs, delete what know the demand can. So the document itself is this, one is to inform, the other is to archive.

But product demand is the core of the essence of things, only you want to understand what to do, how to do, who to do, step-by-step derivation of the process is reasonable, whether to convince themselves, to convince others, this is the most fundamental. With this to do to ensure product demand in the process of documentation, will be structured, clear structure. So when a lot of friends have been asking me how to write the document, please think about it: which aspects should I deal with this requirement, how to cut the dimension of the demand? What is the priority of the requirement? What is the core and key to the whole product? What is the icing on the cake? What is dispensable? What is the main line of demand? ...... Wait a minute

Only if you want to understand these, will be the turn of the product requirements, the stage of documentation. This time, we review the "right to write product requirements document (PRD)", through a number of small thinking way to organize the skills of writing documents, found that all is so smooth. Finally also loyal advice everyone: to learn to write requirements documents, please first learn how to analyze the needs of the beginning. Life is the same, from the nature of the look, so we feel will be different.

The author of this article: Fejer

Release Date: 2010-08-15

Article links: How to look right: product requirements documentation and product requirements