Summary of a project management exchange meeting

This Monday, I attended a new project management meeting. The boss of our company took the lead. It was rare for the boss to take time out of his busy schedule to organize the project management exchange meeting. This article is my work record. The following content is applicable only in a certain environment.

I will not elaborate on the experiences of various project owners. I will record the summary of my experiences with several project owners:

1. When creating a new project, we should pay attention to the establishment of the boundary of the bidding project. What do customers need? Analyze existing requirements and provide solutions. The requirement analysis should be confirmed with the customer, and the project cannot be started without confirmation. To address this problem, I had a deep feeling about the project I started just a while ago. After I left Shanxi, I took over the project again for the first time. Due to lack of experience, as well as the Relationship customers that are subjective to the boss, the cost of the project that they are responsible for exceeds the expectation, I don't think the boundary is very effective because of the overspending of our project. At the same time, the construction content should be clarified in the contract signed with the customer, and the business vocabulary must be clear and unambiguous.

2. The customer's demands should be balanced, reasonable demands should be given to the customer's reasonable solutions, and reasonable suggestions should be put forward for unreasonable demands.

3. In the development stage, the team members should have clear work tasks, which requires the project owner to be clear before assigning the tasks, and avoid throwing unclear work items to the team members.

4. In terms of communication, the environment is different, and the regions are different. The stakeholders may be different, and the communication methods and methods may be different. Communication is not the most important, but it must be constantly strengthened and improved.

5. The project must be managed in a timely manner. For example, to go to the customer's site, make an appointment with Party, inform them of your schedule, who is needed for each arrangement, and the departure time.

6. process management, document writing, and key documents (such as software testing documents ).

7. The acceptance phase is not just this phase. All users should pay special attention to the output of the customer. The acceptance reports of several current documents will not work in this phase, professional acceptance reports should be prepared and presented to Party.

At last, the boss stressed a particularly important point, that is, the employees of these projects are equal to those of Party A. At least we cannot be psychologically afraid of customers.