Experience from the project manager for years

Everyone has different life experiences, but most of them are life experiences. I also have a lot of life experiences like other people, so I don't talk about life experience here. Because it's very common, and it's mostly similar. Today, I am here to share with you over the years work experience, people often say that life experience is precious, hard work experience, we have worked, we all have their own work experience, but what I want to describe today is a learning computer network students to work, engaged in a completely different professional direction development. I have been mainly engaged in the medical software system for several years, I will not say more, I would like to share my years of experience in the project manager, I hope to be useful to everyone.

First, before the implementation of the project. First find out if the project has a contract, and has been signed, because some sales staff in order to win the list first agreed to implement the project and then sign. Such projects do not have a price and range, the latter may incur cost overruns, time is overdue, resulting in the customer has no basis for acceptance of the project. This will be a serious image of the company's interests and personal performance (must)

Second, the project entry into the preliminary investigation. In the traditional computer industry is very common (medical software needs medical equipment, computers, servers, printers and so on), the preliminary research is to the project cycle of a projected calculation, but also to determine the project milestone. The Internet industry may not need it. (selectable)

Thirdly, the project scope programme submits and determines the signature. The project plan involves the detailed scope of the contract content. The advantage of this is that customers cannot add project-wide content without adding additional project implementations. will not exceed the project cycle. Must

Four, the project implementation process to submit daily, weekly, and weekly meeting (conditional daily meeting), and the next week to complete the content of the plan. Finally, a written document or e-mail is sent to all project stakeholders. The purpose of this is to: 1, inform the customer and the Project stakeholder project progress level. 2, in the implementation process to immediately meet the issue of the notice (mainly customers need to cooperate or need to provide hardware, etc. can not allow the project to continue the problem) in the project compensation issues have evidence, will not lead to the implementation of the construction party passive situation. Must

Five, the project implementation of various coding tests, unit testing, system testing, integration testing, and so on, the completion of this link will bring great benefits to the project on-line process. Avoid problems such as system downtime, obvious bugs, and system performance on project line. In this way, customers will have great dissatisfaction with the project or cause the customer to incur economic losses, etc., will affect the project on-line, promotion, acceptance and so on. Serious will lead to economic compensation, project extension, Project Rotten tail, lifting projects and so on. Must

Six, the project acceptance, this link is the end of the entire project cycle. The process is generally based on the contract acceptance requirements or project on-line use situation to reasonably propose project acceptance. First of all, the project acceptance request, the customer leader will generally according to the current project implementation of the situation to formulate the project acceptance time, and organize the acceptance team for on-site use acceptance. The project manager must arrange the acceptance documents in the agreed-upon time, and print and bind them into books and take them to the acceptance site. In the site acceptance process encountered small problems to be dealt with in a flexible way or first agreed that the customer will immediately dispose of, can not let the acceptance team to stare at the small problem, the best project manager on-site demonstration to collect the group to see, so that can quickly guide the acceptance team to go down. In a word, to this critical moment can not let the system appear obvious small problems, as long as the signature acceptance. Some of the acceptance team members may not meet the project requirements for a small problem, but do not affect the entire project, can be treated as a legacy after the project acceptance. Must

VII, project handover after acceptance. This link customers are concerned, because the project after the acceptance of the money, customers are worried about after-sales service quality problems. At the time of acceptance may meet the customer to ask the question, generally provide customers with after-sales service telephone and other contact methods, which is a balance of customer service quality assurance and customer psychology. The company will also take the company's project handover process. Complete implementation of the project (required)

Problems encountered during the implementation of the project:

1, the implementation of the project in the process of jam, sorting out the problem of the existence of the jam or the problem occurs in a party B, and then submitted to the project stakeholders or the relevant superior leadership, so that will not passively accept the project risk. It also does not cause project managers to be passive as a result of a project jam, but also to carry out other project implementations. will not cause the project manager performance to appear the lower question.

2, the majority of customers are very co-operation, but always meet your unexpected customers, this kind of customer generally performance (or request too much too fine, need to have, beyond the scope of the contract) (or in the use of a year is not willing to accept, want to continue to use, anyway the project implementation party did not get money. Each time the project manager puts forward the acceptance, the customer will ask a lot of questions and needs. After the disposal of the batch, another batch. At this point, positive representations should be made on the basis of the scope of the contract and the project scope confirmation programme, which requires a prior contract and project validation programme, as it has signature confirmation evidence. Finally, this customer will be asked to take out such a demand I will sign the acceptance, this time it can be issued by the customer written documents, and signed to confirm that the need to deal with the acceptance after processing. After the final problem processing completed on-site demonstration acceptance (this is the next choice, but for such customers can only be in the next book)

The above is my 5 years of project experience, not the best experience, but also the experience of the work of the results, I hope everyone has help thank you!

Experience from the project manager for years