First experience Project Management

I just graduated from last year. After graduation, I was engaged in "Software Development". As a girl, it seems to the average person that "development" is very tired and has no future, however, since I joined the company for nearly a year, I feel that development is not as hard as I generally think. Of course, the basic knowledge in the university is not solid enough, it brings a lot of difficulties to the work, but with each difficulty, my knowledge and skills have been greatly improved.

As a female programmer, I have positioned myself as a "Project Management" development. However, as a new employee, there are very few such opportunities, generally, it is a part of a large software or project, so there is little chance to manage the project. Fortunately, it is the next graduation season, A large number of students just graduated from the company for internships. I and another colleague are responsible for the project practice of graduates in our department, it mainly involves "Explaining Tasks", "Personnel Arrangement", "Work iteration Arrangement", and "team formation". It is really a "Project Management" experience ".

When I was doing this, I was reading related books, therefore, the "Project Plan", "Project Management", "project quality", and "project risks" are verified in practice. In general, some guidance is given. However, there are many issues that need to be verified in real projects. You cannot make decisions blindly or rely on your own personal experience.

Taking a very small example, the initial plan for "Project Practice" was 30 days. Later, due to time changes, it was shortened from 30 days to 25 days, since we started to estimate the risk of time, when we learned that the time had changed, we felt we had already considered this part and reviewed the arrangement a little, I think there is no need for change. The practical conclusion is that time changes still lead to a shortage of tasks. (During this period, our department manager also specifically told us that we must carefully review the task as time changes-this is experience !)

Let's talk about the project. The project is a software that provides the same mind map to help people sort out their ideas (similar to Xmand ), the original idea was to implement the same simple and graphical operations as xmand. in the later stage, due to the low level of knowledge and time required by the personnel, an alternative solution was selected, use tables to sort out ideas. The project was finally completed within the specified time. Although some indicators may not be met, the overall goal of personnel training was achieved.

The biggest question in the project is the communication problem. You can seek help from "Great gods" for the technology or anything, but no one can replace "team building.

The most serious and frequent problems in the project are as follows:

(1) If you have a leader, you can do whatever you want. If you have any problem, the leader will take responsibility for it and it has nothing to do with me. If the problem is solved by the leader, it doesn't matter.

(2) I am more introverted. I will do what others say. others' ideas are not the best solutions. If you forget it, do it. Everyone thinks it is feasible.

(3) I don't have a good idea about other people's technologies or ideas. Let me pick up my mind. Anyone who needs help will do it. My technical difficulties can be solved by others' research, while others will be able to handle anything else.

(4) When reporting tasks, the ideal status is better. In this case, the actual execution is delayed. Tasks may fail to be completed every day, and the progress is delayed.

(5) Review the code tomorrow. Today, you can simply organize the code or modify the bug. The task progress will be placed first.

(6) bug1 is easy to change. I changed bug1 and bug1 to another one. As a result, two people did the same thing and the division of labor was unclear. There was no good project configuration management.

(7) I really don't understand this part of the code. I can't write it anymore, so I don't want to find anyone else.

In fact, these problems are all the reasons why a unified mentality is not achieved during team building or task publicizing (target publicizing). If a team is already a brother, there is no shirking of responsibility, everyone is aiming to accomplish tasks with high quality, and the result is certainly not the same. Of course, some methods or systems are required, such as bug modification, and a bug management system is required.

In the later stage, when we talk one by one and communicate with each other at ordinary times, we do have a certain improvement in making sense of each person's problems, and gradually become familiar with each other, the Team has formed a good communication mode and working and learning atmosphere.

Here, we also want to raise some points that we did not do well during the entire project:
(1) failing to Solve the Problem Found early: Some people may expose the problem but some may not, but the problem exists, so the problem should be solved in a timely manner, just like the "bad taste" in programming

(2) failing to establish and communicate with team members as early as possible, and communicating with them as early as possible, can adjust the mentality of team members and the cognition of projects, at the same time, it can better integrate team members

(3) There is no good reward and punishment mechanism.

(4) tasks are delayed due to lack of in-depth understanding of the project and vague requirements.

(5) In the project, the monitoring of tasks in each iteration is not in place, and problems are not promptly stated, or the task or personnel arrangement is not properly estimated and planned.

(6) There is no good time for control. In some special cases, no timely feedback is provided.

Of course, now these problems have been found in the corresponding way or strategies during the project, but they are found late, so there is still a certain delay in the overall task.

This is my first experience with "Project Management". I would like to share with you some suggestions on inaccuracy or errors. I hope you will criticize and correct them.