Before we start the project, we have to have a complete process and rules.
I. Personnel allocation
Project leader (collectively called Project Manager below) 1 people
Candidates: Initially in the development team, with a strong overall ability to act as
Role: Team building, project development Progress monitoring, risk assessment and avoidance, coordination between the various departments of the docking, control the scope of the project, reasonable management of the project changes.
Demand analyst 1 people
Candidate: Early in the development team, strong communication skills.
Role: Analyze the needs of business units and translate them into functional descriptions of the software industry. Track requirements changes and record status throughout the development process. At the same time as part of the development work.
Development Team .
Role: Database design, code writing, unit testing, summary design (considering the staffing problem here, only requires the preparation of the outline design, but not the detailed design, but the code of the comments require detailed), mutual code walk-through.
Note: One must be required to be a major development engineer, responsible for the difficult problem of the breach and pseudo-code writing, by the assistant programmer to complete.
Test team
Role: Write test cases, in-depth requirements, and can make use of any comments or suggestions in the process to promote project growth.
According to the actual situation, our students are grouped and assigned roles, so that each student participates in the project with a fixed role.
Output: Stakeholder list. The attachment is the stakeholder list template.
Stakeholder templates
Two. Work flow
1. Once the requirements of the product manager have been raised, a person (demand analyst) from the development team follows the requirements and outputs the requirements specification. At this point, the project manager integrates human resources to build the project team (output stakeholder list) and leads the team to assist the requirements analyst with documentation.
2. Once the requirements are determined, the project manager brings together the relevant personnel from the project team, evaluates the requirements using the expert method, and outputs the "Project estimate form" To evaluate all the module functions in the project. Project estimates need to be approved by the product manager and the project stakeholders before you can proceed to step 3, otherwise repeat step 1.
3. Project manager prepares "project plan"
4. The development team designs the database, writes the summary design document. The Test team writes the test cases.
5. The project manager organizes the review of design documents and test cases.
6. The development team writes the code. Test team to test.
7. The project Manager organizes weekly project week meetings, outputs "meeting minutes", "Risk Management", "Problem management", "Change Management". and monitor the project flow. Every 2 weeks the Product Manager participates in a feedback test.
8. Development Team Integration module.
9. Test team for integration testing.
10. User participation in user testing.
11. Project manager to carry out the project summary.
The above process, with reference to the CMMI3 model for cropping, if the question is welcome to throw bricks (smiley).
After the completion of the division of labor, the next thing we need to do is to let the students develop the habit of teamwork and start discussion. Divided into 2 groups began to complete the project, group discussion, and arrange for the meeting minutes.
Original blog, without permission, please do not reprint.
Double Valley Talent Financial Management (1)