The responsibility of PM's responsibility PM has the following points: 1.PM should be responsible for the success or failure of the software project; 2. PM's objectives in the system specification; 3. Prove with its own experience in the implementation of PM The code implementation is feasible. PM First, we must first familiarize yourself with the user's business process and convert it into a software system process. The software system is just a user's behavior of the user's business, and the software system auxiliary business process runs in a set direction. If business details are water that can flow in four sides, the software system prepared according to user business processes is the pipelines of these water, which helps enterprise managers' management business to run towards the company's needs.
PM needs to control and manage the entire process during the implementation of the software project system. I personally think that from the next six key points: 1. Building a team company as PM is airborne soldiers to RD, as fast as possible and RD combined into a team, and lay a good partnership for the project. 2. Most of the Schedule of Project Schemes is scheduled by RD. In the process of execution, PM should request SD to report the schedule of weekly projects, and pre-discharge progress tables for next week, PM pair The overall progress of the project must have a clear understanding, and the progress may be adjusted in time, and report relevant personnel in time, find the real cause of DELAY, so that the project does not appear out of control. Third, the quality of the software is the software quality of the system to the code quality of SE to the project. In this process, PM should ask QA to issue a test daily, test weekly, and what is the case of the current quality of the project. And need to pay close attention to the control of the software version, the compatibility of the software, and the feedback speed of the software bug, and SE Solution. 4. Control of user needs PM and SD modify the details of the system manual to react to the document, and make SD, SE, QA know all and understand this change to the influence and variation of the relevant part. In the process of code implementation, because user new demand changes current PES, the user's needs are implemented as much as possible, but the system changes minimal. The system has a big impact, and should be changed as a CR after the system is online. V. REVIEW of PIS This is an important part of the code implementation guarantee and PES. Only in the Review Pis process, it can be seen that PM and SD are consistent with the code understanding of the project. 6. Project Acceptance Test PM After receiving the official version of RD submit, test the software to see if it is reached and implemented with user needs. This is a thorough test for the finished product of the entire system, and the PM has a clear understanding when putting the software system in front of the customer. This is just my little experience. If there is something wrong, please correct it.
