Summary in project management

Original article. If you need to reprint it, please indicate the source.

1.Project member composition:

 

Figure 1. Project Member

 

1.1 among developers, core developers are mainly responsible for System Design and public part development, such as some utility, so that they can be called directly, rather than each developer. Senior development engineers work together with beginners to provide proper guidance for beginners.

1.2 testers are responsible for all tests of the entire project.

1.3 Quality supervision personnel (SQA) regularly reviews the project's outputs at various stages and whether the documents comply with company specifications.

1.4 Configuration Management: SCM is mainly responsible for SVN management and subsequent release.

1.5 DBA is mainly responsible for reviewing whether the developed SQL statements comply with the specifications, have performance problems, and create tables, create indexes, and export data.

(Part-time employees are also involved in other projects, which are only part of their work .)

 

 

2.Project Process:

For the entire project cycle, the phases of each software life cycle and the specific work of each stage are shown in figure 2.

In order to prevent developers from doing nothing during the period from project startup to Requirement Analysis (many developers think that coding is called "there is a job"), during the project startup phase, let the core developers understand the requirements, write the system technical solution, and divide the General modules. When the specific project plan has not been developed, the general module is assigned to the developers so that they can start to write use cases. In this way, when the project manager develops a detailed project plan, the developer has a general understanding of the requirements and can make reasonable suggestions. if the requirements are not clear, they can also be put forward immediately.

The tester reviews the use cases written by the developer to reach an agreement on the development and test requirements. do not disagree with the requirements after the project.

 

 

Figure 2. Project Cycle and project activity

 

3.Some tools used in the project:

3.1 Microsoft Project 2007: used to develop the entire project plan.

3.2 axure RP pro 5.6: used to draw a mock up interface ).

3.3 Jupiter: Install the open-source plug-in eclipse for code review.