Product manager workflow :
①Requirement research
②Design work
③Product research and development (follow up the progress of development, adjust demand)
④Test online (final adjustment)
The skills to be mastered in the early stage of the project :
①Write a product function requirement form (mind map is recommended, other forms can also be used, as long as it can be understood by the development)
②Prototype design (commonly used tools: Axure, ink knife, blue lake, etc. Axure's status is equivalent to PS, ink Knife, Blue Lake, etc. are equivalent to beauty cameras hhh)
③Writing of project requirements documents (it seems that there is no such requirement in the homework, if necessary, you can learn from "Everyone is a Product Manager" and "Jianshu")
Things to do for the product during the project :
①Requirements meeting (a very important link, the requirements must match the actual capabilities of the team, determine whether which functions can be realized, and then modify the logic of the requirements. Of course, some functions that are very important and cannot be deleted must be held firmly Require development to remove hair and implement)
②Roughly determine the development cycle (how long does it take to implement each function? How to complete product development within the specified time, pay attention! There is also time for testing, and give development the opportunity to modify bugs) ③Prototype design (
for Front-end development samples, so that they only need to translate the prototype you made)
④Project development (the back-end does not need your prototype, he can start to lose hair with the functional requirements table you made. Before you make the prototype As for the drawing time, the front-end can learn some technical knowledge, so that you can translate your prototype later. Let everyone move and rush~) ⑤Testing
process (the dawn of victory is coming o( ̄▽̄ )ブ front-end and back-end Connect the interface and start using the applet. Try each function once, and if you find any bugs in the process, let the development clean up)
Some thoughts :
①Don’t be in a hurry to start a project, first think about how to go about your own path (project), that is, how to determine the requirements and functions? When thinking about it, go from rough to specific: How many pieces should it be divided into, what is the content of each piece, and what details does each content contain? Similar to the picture below (this is a simple version made during the summer vacation, and some details are not marked on it, but the general meaning is expressed)
②Prototype design and development in parallel
The prototype does not have to be fully designed, and can be developed while designing. After completing the functional prototype of a branch, you can consider letting the front-end development.
Before the next feature starts, have a friendly tea party within the team. Clarify the goal of the next stage. If during the prototyping process, you find that your previous ideas are unreasonable, then it is time to exchange ideas. All unreasonable places should be eliminated as much as possible before development , otherwise the development fathers will not be easy to coax. I usually communicate frequently, but so far there has been no change in requirements after development (hope this is not a flag.hhhhhhh)