Understanding and awareness of project management

Understanding and understanding of project management

Everyone generally has a certain understanding of the concept of project management. Let me talk about my understanding of project management. The following is my collection and understanding of project management for your reference. I hope it can help friends in need.

1. Selection of team members

Be careful in selecting personnel and try to select the right people. When selecting team members, you should focus on their teamwork ability, coding readability, and ability. factors such as the degree of compatibility with the project.

2. Determination of project vision

In the early stage of the project, the project manager needs to negotiate with senior management and customers to set the long-term goals of the project (i.e. the purpose of the project, the overall functions to be achieved, etc.) , The long-term goal does not need to be too long or too thin, but it must be there. A good long-term goal is like a lighthouse in the sea, which can prevent the project team from losing its way during the project process.

3. Project plan

The project plan is one of the most important documents of the project and needs to be formulated by the project manager based on the actual situation. It should be noted that the project plan is not determined once and never finalized. The project plan is a step-by-step process from coarse to fine, from large to small, and needs to be continuously refined and adjusted throughout the project cycle.

4. Requirements stage

According to the direction of the company, the requirements are collected by the personnel responsible for the requirements. After the requirements personnel define the requirements and form a document, the project team members then design. As a project manager, you must participate in this process as early as possible. The earlier the intervention, the better. The requirements collection process can be carried out in a model where the requirements personnel are the mainstay and the project manager is the supplement. The requirements personnel are responsible for collecting requirements and writing documents in the form of demand use cases. , the project manager reviews and organizes the requirements review. Only after the requirements review is passed, the requirements collection process can be completed in stages.

5. Project framework selection and construction

After the requirements are determined, if the customer does not have clear requirements, the project manager needs to determine the framework and technology to be used for the project. Sometimes this process can be completed by the project manager and the technical backbone of the project team.

6. Design stage

The project manager and technical backbone will work together to complete the overall design of the project and undergo design review. Then the design of each sub-module can be assigned to specific members for design, Reviewed by the project manager and technical backbone; it can also be completed by the project manager and technical backbone regardless of the distinction, but the design document must be completed by only one person (the project manager is usually the best candidate), one can maintain the document writing style Secondly, it can ensure that there is someone in the project team who is familiar with the detailed design of the entire project and can control it as a whole. Thirdly, it can save project members' time and allow them to focus on implementation.

7. Implementation phase

After entering the implementation phase, the main aspects that the project manager needs to control include code quality control, progress control, etc. Code quality can be achieved through code spot checks, review, and formulation Controlled by means such as code check-in rules, progress can be controlled by checking the schedule. It should be noted that the project manager must be ready to help project members solve problems encountered, including technical and non-technical aspects.

8. Testing phase

After the requirements document is determined, it is necessary to negotiate with the test group, who will prepare test cases and submit the approximate test time. Each subsequent review (such as design review) must ensure that someone from the test team participates, because testers and QA personnel can better detect review problems.

9. Implementation

After entering the implementation stage, the project will encounter more problems, many of which are not technical, but customer management systems and customer site environment. aspect.

Since project members are tired after a long period of development and there are many problems during the implementation phase, the morale and mood of project members are prone to instability. At this time, the project manager needs to take control, stabilize the mood of project members, and improve Improve morale and communicate more with customers to solve problems found.

10. Technical testing

If the project is of a type that has not been done before, technical testing is required to verify whether the selected technology is feasible. Issues that need to be paid attention to during technical testing Technical tests must simulate the actual environment of the end user and cannot be tested in the development environment.

11. Check-in control and progress control

The project manager must ensure that there is an appropriate time period every day to check the quality of the code checked in by project members (including functional correctness and Standardization, etc.) and the completion of tasks, and problems must be solved in a timely manner.

12. Task allocation

Task allocation should be small rather than large. Generally speaking, the allocation cycle can be one week. When assigning tasks to members, they need to be affirmed by the members and cannot be rigid. 'Assign tasks. You can refer to the XP task allocation method.

13. Positioning issues

The project manager must first understand his position and understand that he is a hub. He must play the role of lubricant and handle the issues of all related parties of the project. relation. The project manager does not necessarily have to be the person with the strongest technical and management skills in the project team, but he must be the person in the project team who is best at handling interpersonal relationships. All management problems are ultimately people's problems. Handle people's relationships well. , project management is more than half successful, "Those who can do it, let them do it, those who can't do it, teach them to do it, and those who don't want to do it, urge them to do it."

14. Formulation of project specifications

As a project manager, you are the overall person in charge of the project. Some project basic specifications need to be formulated by the project manager, such as project code specifications (which can be set in the company Modify based on code specifications), project communication mechanism (how often will regular project meetings be held? In what form? How to provide feedback if problems are encountered during the project?), etc.

15. Application of rights

As a project manager, he definitely has more rights in the project than other team members, and has more opportunities to exercise his rights, but the project manager You must use your rights reasonably. Improper exercise of rights can easily harm the team atmosphere and affect the team's combat effectiveness. There are two points to pay attention to when exercising your rights:

(1) Use more influence and less use of the rights granted by the organization. Influence refers to one's normal dealings with others, through one's own work qualifications and Earned by the ability to solve problems, sometimes an ordinary team member may have greater influence than the project manager; and organizationally-empowered rights are granted in the company's articles of association. In the project team, the project manager must have the greatest organizationally-empowered rights. . Using more influence and less organizational-empowered power can help you manage the project team more flexibly, without making people feel domineering or causing resentment. It is more beneficial to unite team members. But don’t hesitate if you encounter a situation where you have to apply organizationally-empowered rights. You must understand that organizationally-empowered rights are a way to solve problems, but their priority is lower than influence.

(2) Don’t underestimate yourself. Some project managers think that they are just doing work. The only difference between them and ordinary project members is that they have to do more work. This is a very wrong understanding. If If you have this understanding, you will not be able to exercise your rights reasonably, and you will not be able to play the role of a hub.

16. Application of monthly evaluation

The company requires the project manager to evaluate the project members to determine the monthly performance salary of the project members. This is equivalent to giving the project manager a hand It is a double-edged sword. Good application can improve team morale, but poor application can not only damage team morale but also increase project costs.

You need to pay attention to the following points during the monthly evaluation:

1) State the evaluation rules in advance. At the beginning of the project, you need to formulate a simple evaluation rule with the team members. When formulating the rules, do not be arbitrary. Listen to your team members' opinions. Rule formulation can consider factors such as attendance, code quality, code specifications, task completion, and whether tools are provided to save the team's time.

2) The evaluation must be reasonable and fair. You cannot give scores based on personal preferences, nor can you give high scores to all students. You must give reasonable scores based on the evaluation rules.

17. Handling overtime situations

Overtime is a last resort and should be used with caution. If you have to work overtime as a last resort, you must make arrangements and apply for overtime first. Through, it is necessary to coordinate overtime dates, determine the tasks that need to be completed during overtime, and check the completion of tasks. In addition, there is a saying about overtime that if a certain milestone of the project is completed through a lot of overtime, then the next milestone will definitely be delayed. I personally think this is very reasonable.

18. Handling business trips

Most of the company’s developers are in Jinan and most of the projects are in Dongying, which requires project members to travel frequently. This is an unchangeable fact, but Prolonged business travel will affect team morale and efficiency, and also increase project costs. This requires the project manager to pay more attention to the impact of business travel on the project, and to reasonably arrange the personnel and period of the business trip. If some team members travel for a long time, they need to pay attention to whether the long business trip will make their "backyard unstable". If If necessary, you can come forward to help solve the problem.

19. Handling of chores of the project team

The project manager is the overall person in charge of the project and the general manager of the project. The project manager must provide good service to the project team and not let daily trivial matters harass the team. Trivial matters that should be blocked for team members must be kept out of the team.

20. Responsibility

The project manager is the overall person in charge of the project, so he must be responsible for the project. When the project can be successfully completed, he must understand that this is the project team The results of cooperation are not accomplished independently. Credit must be shared with the project team. When the project does not succeed smoothly, you must understand that you must be the biggest responsible person. In addition, you must learn to take responsibility for project members. When a project member makes a mistake, as a project manager, you need to learn to accept criticism from the outside and appropriately protect the project member. ;