Grass-roots programmers transform to a three-person team for project management

Document directory

• 1. Describe the workflow and method of the three-person team:
• Ii. Summarize the 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 (one-person team): a team of grassroots programmers who have made great efforts in project management

After a person completes a project, the project is a three-person team project in chronological order; one-person project; and the other three-person team project.

The first project was handed over to the branch office only for a rough version. One person's project brought me into contact with the company's water conservancy main business and accumulated the first customer. Another three-person team finished their work at the end of 11 years. After using the three-person team for one year, the customer raised a list of questions in December, fortunately, the two children who worked with me on the project are still there.

1. Describe the workflow and method of the three-person team:

Step 1: The demand research at the beginning of the project requires the technical director to help us with this process. This process is also a place for us to study hard. In this world, we are not afraid of not being good at it, but we are afraid that you will not study it.

Step 2: The technical architecture of the project (this is what we call it) should have an overall idea. After a clear explanation, we should report to your technical director. After all, we are still very young, more advanced guidance is required. The subsequent implementation of the technical architecture should be done by yourself to ensure that your ideas are correctly implemented and as robust, easy to maintain, and scalable as possible. During this period, the summary design document can be compiled.

Step 3: start the project preparation and describe the requirements to the project team according to the outline design. Introduce the technical architecture and schedule (you must also participate in the coding process ).

Step 4: Coding and testing. I think this process is the most important and unordered. Whether the requirements expressed by the program are correct by the team members, the Review of the code written by the team members, the unified style of the UI end, the overall expression, and whether the operations are more customized, in the test phase, individuals must also act as the main force of the test, and test based entirely on their individual abilities. There is no inherent rule to follow. During this period, another important thing is to train new people. After all, you have grown up step by step from the most basic level (some of them are not arrogant ), I hope to pass on the correct software development things I learned before to them, and I will grow as they grow.

Step 5: Project implementation, training, project use, and acceptance. Because it is generally the relationship between customers led by the company, and after several efforts, the customer did not propose too many modifications during the launch, just to ensure smooth acceptance of the project, I took the practice of helping the customer input data (thanks to the customer for preparing the data), so that the software system had a certain amount of actual data, and the acceptance was completed step by step.

Ii. Summarize the advantages and disadvantages.

Advantages:

The pace and method of work described above are generally very happy. I chose a three-person group. I am in the middle. If there is anything we can move down to form a discussion group, internal communication is smooth and timely; at the same time, communication will certainly bring about progress. I have learned a lot from them when I train new people.

Disadvantages:

At that time, as a project manager, I liked the three-person working group model most, satisfying the desire of my project manager and retaining the enthusiasm of my technology, while managing projects, I also actively participated in coding, and I was happy with it. However, after that time, I also felt irrational. As the project owner, serving customers, service companies, and service project team members, it is my main duty to ensure that the project can be successfully completed at a reasonable pace. I should not go deep into a certain point, but lose the overall situation; another major disadvantage is that the current work style seems too casual (although I personally think the three-person team is quite suitable), there is no way to look for any step, for example, once the project staff are lost, it is very likely that the part they are responsible for becomes a place that no one dares to touch; what's more, company leaders do not want to have such casual teams. They prefer teams that can control everything.

Then I will write an article on five project teams, one on seven or eight project teams, and one on 14 and five project teams. I would like to thank you for every project that I grew up.

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