Product Design Experience (May 3)-product documentation and specifications

I have been sorting out various documents suitable for our team over the past few months. It is a very lightweight document package. This time I am talking about the well-managed mindmanager diagram in five categories:

 

Ø demand management

N function list is an extremely important management method. Here we can understand the importance of team collaboration tools. Now we use office live excel, which is relatively simple.

N product website page map.

 

Ø Project Management

N project kick off PPT.

N Project Task book.

N project daily report.

N project release notification.

N process type: the daily release process and urgent release process are commonly used in the initial stage.

 

Ø business needs

N is mainly brd. At this stage, the team does not need to strictly distinguish BRD from MRD (see "17th"). It is enough to use BRD in a unified manner.

 

Product requirements

N is basically a PRD, which includes the following three parts: General description, UC documentation, and non-functional requirements.

 

Ø requirement category

N interface specifications: The overall page size and font size are color encoded.

N Interaction specifications: for example, the default sorting of the list and the method of text in the list, the product at hand is "left-aligned text, centered time, right-aligned number ". It also includes field validation specifications and system feedback specifications.

N document specifications: such as the Language Style, syntax template, and standard Statement of Common Operations.

 

 ------> Click here

 

 

There are also some technical specifications, such as development specifications, some code rules and function naming rules. If you do not understand them, you will not be involved.

 

Many of my peers on the Internet have discussed how to organize product documents and specifications. My personal feeling is that after product 1.0 is released, before product 2.0 is released. Generally, Internet products will have a long life cycle after 1.0 Release, there is often a buffer period for design work when we do 1.1 and 1.2 (on the one hand, development and testing are busy dealing with online faults, on the other hand, PD needs to collect feedback to determine the next step, Team personnel adjustments will also be made ), therefore, the Product Specification at this time is the work summary of the first generation of products and the first generation of teams. It is most appropriate to improve the efficiency in the future. Of course, this work should also be carried out in an iterative manner, and cannot be achieved overnight without any need.