Turn: Internet product development process

Internet product development process

You must make careful deployment and arrangement for a slightly larger Internet product. Otherwise, the project will be messy.
Let's talk about the jobs and software used for development:
Pd (Product Planning): Word, Visio, axure
PM (Product Manager): easymind
ID (Interaction Designer): axure, Photoshop
VD (visual designer): phtoshop, Illustrator
WD (front-end development engineer): Photoshop, Dreamweaver
Dev (backend Development Engineer): Dreamweaver, myeclipse

Let's talk about MRD (Market Requirements document market demand document). MRD should clearly convey the purpose and goal of product requirements, this article describes what new products, solutions, and services can be successful in the market or in the internal market, and what kind of success is expected. MRD describes "what" and "why", but not "how" (that is, do not include flowcharts and prototype diagrams ). When the product needs a high priority (project initiation), the demand side must provide MRD documents. The priority, weight, and project initiation of product requirements are determined by the Project Implementation Committee. The daily requirements are determined by the committee owner, and the non-conventional requirements are determined by the meeting.

The next step is about pd. After receiving the explicit demand, PD should carefully and thoroughly analyze the real intention of the demand side. Sometimes the demand side's ideas are not necessarily correct, and some sudden ideas are not feasible, and the PD needs to make a judgment. In this case, the PD has the right to propose its own solutions, including denying the demand. In case of conflicting requirements or repeated development caused by misjudgment, the responsibility shall be borne by the PD. In the event of a dispute, PM (Product Manager) coordinates and resolves the issue. After the PD completes the demand review, inform the demander of the time required to complete the PRD, the estimated difficulty of product development, and the completion period.

The developer should be responsible for PRD (Product Requirement document product requirement document). PRD focuses on the product features and Performance description, which is more detailed than the same content In MrD, and quantify. PRD generally contains flowcharts, prototype charts, and so on. Use Cases and other means for accurate description. That is to say, the PRD document has already entered the preparation and development stage. At this time, the MRD document should be clear.

Next, we will hold a meeting to discuss the PRD scheme. We should discuss the demand side, consultants in relevant fields (with rich experience), Pd or UI, and keep a record. Next, PD will work out the design result scheme, and the demand side will sign for confirmation. After receiving the PRD plan, the programmer needs to evaluate the approximate development time and task breakdown schedule.

The Interaction Designer (Interaction Designer) makes an interactive design scheme based on the PRD final version to reproduce the user interaction process (the studio generally uses the powerful axure) and reviews it internally with the PD and UI. Based on the situation, PM participants should communicate with the demand side repeatedly until the demand side is satisfied.

Next, VD (visual designer) designs the page style, layout, and key interfaces based on the axure prototype. Communicate with users about the page design.

WD (front-end development engineer) writes HTML, CSS, and JS source code based on the design page cut graph.

The following is the background development stage. Before coding, programmers should conduct outline design, database design, and internal discussion and review based on their system needs. If the programmer has doubts or does not understand the document or prototype, he or she must communicate with the PD and ID to understand the true meaning of the document. He or she shall not modify the determined PRD document scheme without authorization for any reason. Some functions need to be adjusted, and programmers need to negotiate with the PD and the demand side. The change should be documented and approved by the demand side, Technical Manager, and PM. The code written by everyone cannot be completely correct, so you need to test it while developing.
Alpha (alpha initially) test. In the development team, there are many testing methods, such as black box, white box, pressure, and stress. More than 80% of requirements should be developed at this stage. PRD and prototype should be used for testing. After the test is complete, collect feedback, fix bugs, and optimize the process.

Beta (second beta test): selectively ask some end users for actual use, report the problems found, the developers make the final modifications to the system, and then prepare to release the final product. Beta testing developers are not present. The estimated development time of the product is subject to the completion of beta testing.


Some bugs may exist after the product is launched, which requires later maintenance. After the product is stable, the development is completed.

Turn: Internet product development process