Project management-project phase division

A project goes through a series of stages from the beginning to the end. Effectively dividing these stages is crucial to progress control, cost control, quality management, and function control. Generally, large and medium-sized software development companies have their own division of stages, and the tasks to be completed in different stages are also different. This article briefly describes the various development processes from the perspective of R & D.
(1) phase0: Feedback from market personnel on the project development stage.
There is no obvious time period for this phase, which is the project initiation phase. Relevant personnel should provide the product's main feature and market prospects. The company's management, marketing department, and product department hold the P0 meeting, and the resolution is passed, specifying the full leader of the product: Product Manager. The project is officially started.
(2) phase1: planning stage.
The product manager defines the time period, cost, and function scope of each stage of the product.
Output: progress and cost report
Completion: Call the System Department staff and R & D department director to hold the PR1 (Phase Review) meeting. After the meeting is approved, the System Department staff should be designated and the time should be allocated to notify the R & D department and Test Department preparation staff to enter the project at the scheduled time.
(3) phase2: requirement design stage.
System Designers complete requirement Design
Output: requirements documents the interaction interfaces between Subsystems Required by each subsystem must clearly indicate the functional points to be completed
Completion: convene system designers, R & D personnel, and testers to hold the PR2 meeting. The meeting passed to the phase3 stage
(4) phase3: development stage.
The product manager allocates time for R & D personnel. System development stage (including three sub-stages: Design Stage D1, encoding Stage D2, and internal test Stage D3)
D1 stage:
Output: Responsible for the system design of the module.
Completion: the R & D Director convenes relevant personnel to hold the DR1 (Development Review) meeting
D2 stage:
Output: Code
Finished: no obvious events
D3 stage:
Input: unit test report (must contain clear function points, clear inputs, outputs, and test results)
Complete: design documents, source code, installation files/packaging files, Test Documents, installation instructions, relase notes, and other documents are submitted to the specified version management tool and sent to relevant personnel.
The product manager calls relevant personnel to hold a Pr3 meeting to confirm the Function Point completion status, code volume statistics, development simulation tools, public modules, and other additional development results, and notifies the IT department to mark the current version.
(5) phase4: test phase.
The product manager allocates time for testers. The tester tests the function, stability, and performance of the current version based on the requirements of the system designer. In some cases, this stage may be divided into laboratory testing and field testing.
Output: Test Report, bug stored in Bug Management System
Complete: Notify the IT department to mark the current version as the official release version.
(6) phase5: maintenance phase.
The product manager arranges appropriate time for technical support and R & D personnel. The official version is submitted to the on-site implementation department.
(7) phase6: end stage.
The product has been eliminated by the market, maintenance is terminated, all relevant personnel are withdrawn, all documents and codes are frozen, and destroyed after a certain period of time.
Common tools include clearcase, SVN, CVS, and sourcesafe ClearQuest. Open-source bug management tools are not listed.