BRD is the abbreviation of "Business Requirement Description". It is collectively referred to as: Business Requirement Document BRD and MRD. PRD is considered to be the Document specification to be established from the market to the product.
It is the earliest document in the product life cycle. It should have been conceived for a long time. It involves market analysis, sales strategy, profit prediction, and so on. It is usually a demo document for decision makers to discuss, it is generally relatively short and refined, with no product details.
BRD includes: project background, business value, Functional Requirement Description, non-functional requirement description, resource evaluation, risks and countermeasures.
- Detailed description of BRD content
Project Background: Where are we? Why is this project required? What problems can be solved? Some data can be listed to illustrate the necessity of the project.
Commercial Value:Where are we going? The most important point! What is the value of this project? In general, we will also predict the changes in related figures and propose the commercial objectives of this project.
Function Requirement Description: how can we proceed? To achieve the goal, you can describe the packaged requirements in the form of a function list, but it is best to draw the business logical relationship. Of course, we also often use highly technical things, such as deliberately adding some requirements for the boss to cut down, I hope my boss will be embarrassed to cut down what we really want to do after it is cut (commonly known as Li daitao ).
Non-functional requirements: provide important non-functional requirements.
Resource Evaluation:How much is required to achieve the project goal.
Risks and Countermeasures:Possible risks and Countermeasures in the project.
Business Value, resource evaluation, risks and countermeasures are the three most important parts of a BRD. Good BRD should haveInflammatory and guiding. When writing a BRD, we should fully consider the background, knowledge structure, and general method of thinking about the problem of reading a person (usually the boss). Considering how he will respond after reading the BRD, how does he consider it, rather than simply passing a simple message about the results to be expressed, he should plan ahead. To achieve this level, you need to have a deep understanding of the boss, the company's high-end desires, information symmetry in the enterprise, and the high-end desires are decoded correctly. Of course, if the person writing BRD has a great influence on the boss in the company, it will also increase the BRD.