The five-person team behind the transformation of grassroots programmers into project management

Document directory

• I. workflow and method of a five-person team
• Ii. summarize advantages and disadvantages

The articles in these columns only record my personal experiences. The opinions involved in these articles are personal opinions. If not, please give me more advice.

Subsequent article (three-person team): the three-person team who experienced grassroots programmer transformation and Project Management

As the project grows and the number of projects in the company increases, the R & D team working continuously grows. Our group also grows with this wave of growth, due to the strong mobility of the project team members during this period, the situations of five, six, seven, and eight members often alternate. The team at this stage is called a five-person team.

I. workflow and method of a five-person team

Step 1: demand research: After several times of following the technical summary to conduct demand research, coupled with the gradual increase in the software business knowledge of the water conservancy industry, I have already been able to conduct research on certain projects, communicate with customers during the day, summarize the problems of daytime communication at night, and compile the documents (on-site communication records, time, location, participants, and communication matters [separate identified and to be determined projects]).

Step 2: design a summary based on the product of the requirement survey (not too detailed ).

Step 3: Schedule the project according to the time node of the technical contract.

Step 4: The framework is built. Due to the technical accumulation of the previous projects, the framework has been formed and the core remains unchanged. The surrounding items can be customized according to the actual situation of the project.

Step 5: The project kickoff meeting will introduce the entire project to you, express the business functions of the module to you, and arrange work tasks.

Step 5: Write a module style book, a product between the outline design and the detailed design. After the style book is compiled, a unified style book review meeting will be held in the form of full participation.

Step 6: write the code. There is a code specification that standardizes common situations in the coding process of interfaces, classes, methods, variables, and controls. The code is reviewed by mutual check, I conducted a spot check.

Step 7: test. In this phase, the status is still unordered. It only requires a certain amount of manpower, time, and quality.

Step 8: launch and acceptance.

Step 9: Release the upgraded version. The database changes are documented and scripted. Each time the version package is released, the source program is saved and managed.

Ii. summarize advantages and disadvantages

Advantages:

At this time, the team and every process of the project began to develop in an orderly manner. Some work began to adopt a closed-to-work model, such as code Mutual Review. The team began to cultivate backbone in various aspects, requirement Analysis backbone, technical backbone, and testing backbone. A five-person team is a highly efficient team.

Disadvantages:

Because the team building process is relatively short, all aspects of the project still need to be improved. A major weakness is the testing part, which needs to be improved urgently.

Then I will write an article on managing seven or eight project teams (improving each process of the project) and an article on managing 14 or five project teams (group management ). I would like to thank you for every project that I grew up.

The transformation of grassroots programmers into a project management team (7 and 8)