A sense of today: Look at the product manager for outsiders

Today is a special day: a new project of the company has started. Today is the first meeting of this project. Boss Dong took us to the product manager yesterday. Today, the product manager passed the interaction diagram with us and probably knew the project status. This project is not very complex. At least all functional points in the first phase seem simple, mainly displaying some information.

Some outsourced colleagues in this project have introduced how to use wiki to help them better understand the internal development process and specifications of our company, use of data source dictionaries and git. I felt like I was the boss!

But in fact, I am still a bit confused, because I have not done these jobs before, such as checking interfaces and assigning tasks. After Li Ning comes over tomorrow, I will ask him to take me to do something, so that I can have a transition.

When I went to learn Qinqin yesterday, I had a plot with Xiao Chen: the store on the bottom of the disk is worth trying. After I came back today, I had a chat with my sister Dai. She also thought that this could be done, and the profit was still quite high. I think I can do what I like. I have to say that it is more satisfied than going to work. In fact, I have been a turning musician in my life, haha.

This is far away. Let's pull back and talk about the product manager's knowledge points.

Today, I took out the PRD document from the shared document in the Project Group. At first I really didn't know what it meant. Then I tried Google with Baidu and found the following knowledge points:

Market Requirement documents: (full name)Market requirement document, MRD)

Product Requirement document(Product Requirement document, PRD)

Business Requirement document; Description of business requirements. The Product Requirement content document (report), which is based on the business objectives or values, is used by the enterprise leadership as an important basis for decision-making and evaluation before the product is put into R & D.

BRD is the earliest document in the product life cycle. It should have been conceived for a long time. Its content involves market analysis, sales strategy, profit prediction, etc, it is usually a demo document for decision makers to discuss. It is generally short and refined, with no product details.

I will not talk about anything else.

I just want to say that this PRD document is actually very close to the interaction diagram after the BRD document and MRD document, therefore, we need such a PRD document for any product. Although MrD and BRD documents do not have to be available, as a good product manager, we still need to understand the ideas to be expressed in these two documents.

In fact, what I am doing now is very similar to the product manager. The product manager collects user requirements, presents them, and finally implements the application. Now, I want to put the abstract idea of the piano room into reality and make a qualified product, that is, do a good job in the piano room. Therefore, I think it is quite a sense of accomplishment.

Yesterday, I moved from sanlin to the company. I felt very convenient: I only needed a few minutes to go to work. I wanted to come back and live with my colleagues. I could play cards or other entertainment programs if I had something to do, i'm really happy to have it.

So if you want to play it, let me know in advance. A warm welcome !!!