Information System Project Manager--47 Sub-thesis--Scope management

16 was lucky to have tested the information System Project manager, the thesis actually prepared 4 articles. The exam I wrote is the scope of management, paper 47 points, the following is the paper.

Because the test is written on the back, I can only guarantee the approximate content, I am the back of this article. Here the knowledge in order to record (long time did not come here to write articles), of course, also to share.

Scope Management

Summary

 

in August 2014, I participated in the XX Bank Call center System project as project manager. The project invested a total of 8 million yuan, the construction period of 1 years, through the construction of the project to achieve the bank based on the call center system customer service, business consulting and acceptance, outbound marketing and other services, and achieve the physical branch of the business diversion, reduce the overall business pressure, Improved the service capability and productivity of the bank's Customer service center. The project in August 2015 through the owner's acceptance, won the praise of the owners. Based on the author's practice, this paper discusses the scope management of the information System project construction process, mainly from the following aspects: scope planning, scope definition, creating WBS work breakdown structure, scope confirmation, scope control.

Body

 

in August 2014, I participated in the XX Bank Call center System project as project manager. The project invested a total of 8 million yuan, the construction period of 1 years, through the construction of the project to achieve the bank based on the call center system customer service, business consulting and acceptance, outbound marketing and other services, and achieve the physical branch of the business diversion, reduce the overall business pressure, Improved the service capability and productivity of the bank's Customer service center. The system is a system integration project, mainly including the call center platform, Web service system two subsystems. The platform uses the Avaya platform, the Web Service system database adopts DB2, the application server uses WebSphere, the development language uses Java. The project in August 2015 through the owner's acceptance, won the praise of the owners.

The project is characterized by a wide range of stakeholders, and I am a project manager focused on project scope management. In order to ensure the continuous progress and orderly development of the project, I strengthen the scope management of the project from scope planning, scope definition, WBS work breakdown structure, scope validation, scope control.

 

first, do the scope planning

defining and managing project scope is critical to the success of the entire project, and the low level of scope management is one of the important factors that lead to project failure. As a project manager, I give full attention to the development of the scope management plan, including how to define the scope of the project, how to develop a detailed scope specification, how to compile WBS work breakdown structure, how to confirm the scope and how to control the scope. By developing a project scope management plan, it not only provides guidance for the determination of all the work done, but also effectively prevents the scope from spreading. The development of a practical scope management plan is the guarantee of successful implementation of the project, which lays the foundation for the other management of the project. In formulating the scope management plan, I first looked for the company to organize the process assets, to find out the template of the scope management plan, combined with the experience of the company's previous projects, worked out a preliminary plan, and then convened the relevant stakeholders to review the plan, and finally completed a detailed, scientific scope management plan.
II,   scope definition
  A successful project should only do all the work required to successfully complete the project, in order to achieve this, you need to define a clear project scope in the early stages of the project. In the early stages of the project, I led my team, stationed at the customer site for discussion, reviewed their business manuals, visited the business operations on site, and conducted business exchanges. As the project involves a lot of stakeholders, we have different expectations of the project, the customer needs are not clearly described. In response to this situation, I have used the prototype method based on my previous experience. Through the design of a demo, with an intuitive demonstration, so that customers more convenient to tap their own needs, and gradually clear demand. In our unremitting efforts, finally completed the scope of the definition of work. Then I organized the relevant stakeholders held a seminar, the objectives of the project, the scope of the discussion, and eventually formed a detailed scope of the statement, the two sides signed the confirmation.
Iii. Create WBS work breakdown Structure

based on the project scope specification, my team and I began to decompose the project scope to form the WBS for the project. During the decomposition process, I decomposed according to the following principles. 1, to maintain the integrity of the project at all levels, to avoid missing the necessary components. 2, a unit of work only belongs to an upper unit, avoiding cross-dependent. 3, the same level of work units should be of the same nature. 4, the work unit should be able to separate different responsibilities and different work content, for each work package in the project, I have designated the only person in charge, so as to facilitate a clear definition of each person's work interface and responsibility, to prevent the occurrence of unclear responsibility, shifting situation. 5, to facilitate project management planning and control of the need for management, I based on the actual need to control the level of detail, after referring to the views of team members, determine the level of decomposition of the work package. 6, the WBS is encoded, and the organization chart and the cost control of the control account integration, easy to manage the project later. Finally, the WBS dictionary is made, and the work package is given a specific attribute description.

The work package is the lowest level of the WBS, in the creation of the WBS, for the part that can not be decomposed in detail, we take the rolling planning method, that is, the more definite work decomposition in the near future, the long-term ambiguity of the work decomposition, in the subsequent project scope gradually after the breakdown. After the completion of the WBS, I know that it is necessary to obtain a consistent understanding and commitment of the needs of the owners, and that our work is meaningful. So I held a review meeting and invited the relevant stakeholders to participate in the review and confirmation, forming a scope benchmark for the project, which laid the groundwork for subsequent work.

Iv. Scope Confirmation

Scope Confirmation is the process by which the stakeholder formally accepts the completed project scope and achieves acceptance of the project scope by reviewing deliverables and work results. Project validation should always be done throughout the project, and WBS work breakdown structure provides the basis for confirming the scope. At each stage of the project, I organize the customer to check the deliverables and decide whether or not to accept them by determining whether they meet the quality requirements. Each scope confirmation makes the project more successful and reduces the risk of rework due to project outcomes that do not meet customer expectations. The owners are more confident in the success of the project after each confirmation of deliverables, and the satisfaction level is increasing. I personally feel that the most important thing in this process is to make the owners feel that the progress of the project is manageable and that they follow their wishes, so that as the project progresses, the risk becomes less and the customer is naturally satisfied with the project management work. At the same time, the scope of each phase of the project confirmation, also ensure that the project smoothly into the next stage. When confirming the scope with the customer, I pay great attention to obtaining the customer's written confirmation, if cannot pass the confirmation, also must record the detailed reason, in order to seek the solution. In the implementation of the project, as I developed a detailed WBS, and the customer has good communication, so in the scope of the confirmation of progress more smoothly.

v. Scope Control

scope control is the factor that affects the scope changes, ensuring that all changes are handled in accordance with the overall change control process, and that changes are managed in a timely manner when the scope changes actually occur, avoiding the spread of the scope. Changes are unavoidable, and disorderly changes can confuse project management, have a significant impact on project planning, and even lead to project failure. The overall change control of the project is to review all changes, approve or reject the change request. As a project manager, I followed the process of change control strictly, and all the changes have to go through the whole change procedure and be approved by CCB. According to the change control process, the formal change request is first made, and then the overall impact analysis is made on the change request. After approval by CCB, the content of the change should be included in the project management plan. The changes are then notified to the relevant stakeholders. In the early stages of the project, the owners were not aware of the change process and were unwilling to follow the change process, and they wanted their requirements to be unconditionally enforced. After I patiently communicated with the client, explaining the meaning of the overall change, the customer understood that the overall change control was beneficial to both parties, and eventually agreed to establish a change control process and participate actively. This has laid a good foundation for the monitoring of the project by both sides. I think I did a good job, and if I didn't persuade the client to agree to take the overall change control, the risk of the project scope spread would be great. We also have to invest more in our risk response. And now, these risks are greatly reduced.

In addition, I regularly hold status review meetings during the project. Review the scope deviation of the project, analyze the cause and take corrective action against the scope benchmark.

 

through the unremitting efforts of our team, lasted a year, the project finally in August 2015, through the owners of the organization's acceptance, for the user to solve the practical problems, the establishment of high-quality, efficient customer service center, has been the owner of the party's praise, the success of the project benefited from my success in the scope of management. Of course, in this project, there are still some shortcomings, such as: during the implementation of the project, the purchase of the server due to the contractor's problems can not be scheduled delivery caused delays, I as the project manager did not communicate with the contractor in time to confirm delivery arrangements, the primary responsibility for this. However, after my late rectification, and did not have any impact on the project. In the follow-up work and study, I will continue to recharge learning, and peer exchanges, improve their business and management level, and strive for China's information construction to make their own efforts.