One, the client interface
More is to support sales work

Two, the requirements analysis
Before signing a contract, need intensive project manager, as far as possible complete to collect customer needs, accurate analysis of customer needs, form system features list, repeatedly confirmed with customers,

Three, sign a contract
Contract is signed, must be based on a system function list, in order to project requirements for delineating boundaries,

Four, system design
Based on the system function of the collection and the list of requirements, system design, by product manager
Project manager at this time also to make a systematic function, deeply contoured to issue the minimum scope,

Five, the system development
1, the development plan:
Framed a phase of the smallest scope * 1) * (very important) : can be run through the whole process of the main function module, the perception of function module and judgment is very important,
2) written development plan scheduling: minimum first development function elaboration to each function point (the more accurate the more detailed, the better), and then according to the staff scheduling
3) after the issue of minimum scope is coming, later to the development of the icing on the cake and optimization
4) third party interfaces, requires the opening of the account, must give priority to coordinate communication

2, project management
1) every Monday morning meeting, determine the development task this week, clearly must be completed this week, finish work overtime
2) every morning meeting, determine the development task, clear must be completed in the day, finish work overtime,
3) every day before coming off work regular meeting, the project manager in person on the day of the task completion, judge whether the overtime
4) before coming off work meeting on Friday, this week review task progress and result to determine whether a weekend overtime

Six, test
1, the smoke test: smoke test is very important, if you don't through smoke test, equivalent to project failure
Project manager write about test report

2, the official test
Assured through smoke test first, then an official test, test each tiny function point,

3, the test phase of the project management
1) according to mention BUG measurement condition, specify the final launch time,
2) project managers and project members every day together every BUG, the BUG must change after that day, finish work overtime,
3) * test code repository, developing code repository must be independent deployment, strict separation, code to avoid confusion,

Seven, acceptance
1, internal acceptance: need a project manager for inspection after testing the system function, at this time, depending on the project size, big project main function point inspection, small projects all function points is best able to cover all,
2, customer acceptance: communicate with customers, to submit inspection report, if the customer treat online function to, right now, this time will be sufficient communication, be directed to the customer, if the function of the development is indeed there is a deviation, can discuss in the next iteration process,

Eight, online
1, launched the emergency response plan: list of possible problems, causing the key function of a system crash, individually designed contingency plans, in case of emergency,
2, the official launch of the project: report to the superior leadership launched, the like to like, the punishment punishment,
3, project checking, summarizes the problems in the process of the project