Project management software development project management

Preface

For a complete software development team , Product managers should be included , Development , Test the three teams

• Product manager soul , Responsible for requirements and acceptance
• The development team is the main force , Be responsible for product development and realization
• The test team is the guarantee , Be responsible for product quality .

For a complete software project , In addition to the need for product managers , Development , Outside the test , The project manager is also required

• The project manager is the pilot , Be responsible for the whole project .

abbreviation

In the software project system , Some commonly used role names and corresponding Chinese and English abbreviations are as follows , The following roles will be abbreviated .

name	Full name	English abbreviation
project manager	Project Manager	PM
The product manager	Product Manager	PM
Test Engineer	Quality Assurance Engineer	QA
Development Engineer	Research and Development engineer	RD

project manager -PM

Be responsible for the project progress , Coordinate PM,RD,QA Ensure the smooth progress of the project

1. Collect development plans and test plans .
2. Organize regular project meetings every day , And arrange and send project minutes
3. Face the risk allocation positively , Adjust the plan in time , Reduce reinsurance
4. Push bug Repair condition
5. Supervise the testing of testers , Product manager's acceptance, etc
6. Master the project progress

The product manager -PM

Determine product requirements , Determine what is right .

1. Clarify product requirements . Coordinate sales , Customer ,UI, Determine product requirements .
   Only I can figure it out , To make RD,QA I understand
2. Hold requirements review meeting - Output requirements document
3. Participate in regular project meetings . Timely understand the problems of R & D and testing in product requirements logic , To adjust
4. Handle QA The demands put forward bug. See whether to adjust the business logic or lower the priority , This period does not deal with
5. Validation requirements . The development work is over , At the end of the test , The product manager checks whether the actual product meets the requirements
6. Feel whether to release the version . Before release , According to this iteration buglist detailed list , as well as QA Feedback , Decide whether to release the version .

Test team -QA

Be responsible for product quality , Timely feedback various problems found during the test bug And reinsurance

1. Clarify product requirements , Write corresponding test cases
2. Hold a test case review meeting - Want to be a party member and need a second review ,
   QA,RD,PM Need to agree - Output test case documents
3. Participate in regular project meetings , Timely feedback and communicate the problems found during the test bug And reinsurance
4. A functional test
5. Pressure test
6. Customer complaint return visit

R & D team -RD

Product development , Design the product according to the product requirement document , Development , Self test, etc

1. Outline design .

   Document according to requirements , Demand analysis Output outline design , Clarify product requirements , Logic , Frame, etc

2. Organize the development team to review the outline design

3. Detailed design .

   Output detailed design documents according to the outline design documents , Clearly implement the module , Function, etc

4. Organize the development department to conduct detailed design review internally

5. software development . According to detailed design documents , Software development ,

6. Self test . Write self-test cases .

7. Version test . After the self-test passes , Send the test version to QA.

8. Participate in the daily meeting of the project , Keep abreast of products bug And project progress

9. correct QA/PM Relevance of feedback bug.

10. Do a good job of code version management control and version control of release and test version .

Conclusion

The above just lists and sorts out a normal , The role assignment and responsibility division required for an idealized software project , But in real work , Yes RD There are bound to be many problems . For example, lack of PM Or lack of QA etc. , Or the demand is not clear , Or the requirements change too frequently , All these need us to face .

For this reason, as an excellent developer , It also needs to be improved from the following aspects

• communication skills .

  Be good at listening , Do things peacefully , There is no knot that cannot be untied , There is nothing that is not clear .

• Knowledge reserve .

  Good at learning , Keep pace with the times , Continue to expand their technical reserves .

• Share the summary .

  Good at sharing , Summarize and make up for shortcomings . Never underestimate the power of the team , Share the summary , backgammon .

such , Keep a peaceful mind , Maintaining the status quo , knowledge has no limit .