I. Demand analysis

1. Demand Review:

Time: After the product design is completed and before entering the formal development process, organizer: Product Design (PM); Objective: To unify everyone's understanding of the product, find product design defects in time, and reduce the frequency of subsequent modification requirements as much as possible; Participants: back-end development, front-end development, interaction design, visual design; Source of demand (if possible) form: meetingCopy the code

2. Demand analysis

Analyze key functions, application scenarios, etc. Basically in the requirements review and analysis stage on the overall implementation of the project has a basic design; Have a clear understanding of the difficulty of the implementation of core functions, and do technical research in advance when the scheme is not clear; On the one hand, a more accurate schedule can be given; On the other hand, it avoids the difficult solutions encountered in the real development, and it is very awkward to start all over againCopy the code

Second, such as visual and interaction design (very important, can not get interaction will not be scheduled)

That being said, the usual schedule can’t wait for the delivery of visual interaction (front-end 😭 ah);

At this stage, it is generally necessary to give the project schedule (give yourself more time to fill the pit).

Iii. Project development (Project completion is basically consistent with visual design and interaction design)

Four, reserve sufficient self-test time (test function and style)

V. Front and back end joint tuning (tuning interface function and field limitation); Often need to change the interface logic, and even add the interface to cause the front-end need to modify the corresponding verification or function; Time must be

Vi. Visual and interactive acceptance

Good development and self-testing; Visual and interactive acceptance is easy; Just set aside a day or twoCopy the code

Seven: product acceptance;

Product acceptance is very important, often they predict things with the design of the thing is inconsistent; The product design logic may even need to be modified for practical use; You need to reserve some time for the modificationCopy the code

Viii. Test submission: The product can be submitted for test only after the above steps are completed;

Ensure the test quality (the test cycle will be long, and the bugs need to be timely modified during the test, and even the bugs that affect the business logic need to be repaired within one to two hours)Copy the code

Ix. Online interface regression (online interface function regression is required after the backend goes online)

X. Preparation before launching new projects

1. Resource application;

2. Sandbox deployment testing (simulating real online deployment testing is required)

3. Online deployment test (after QA delivers, it needs to conduct update iterative test to ensure the completeness and availability of the project).