On the scope management of XX Information System construction project
Summary
I. Introduction to the background of the project
Basic situation of the project
Current status of implementation
My role in the project and the content of my work
Second, the scope of the project for the management of the main work
Third, carefully develop scope management plan
Prepare the scope management plan according to the regulations and the preliminary scope of the project;
Set up a project Working group composed of party A, party B and supervisor, and established every Monday working regular meeting system.
Iv. developing the scope of the project definition
According to the project charter, the preliminary scope specification, the project scope management plan, the preparation of the project Detail scope statement;
The project objectives, project requirements, work boundaries, final deliverables, delivery standards, progress milestones, configuration management requirements, and project specifications are defined.
V. Preparation of project WBS and WBS dictionaries
Based on the above-mentioned project management plan and detailed scope specification, the project work breakdown structure is prepared with the project final delivery target as the first layer, and the work is decomposed and refined until the work package (decomposition by week).
Vi. organizing the project scope review meeting to confirm the scope of the project
To convene a project Working group meeting, please party a project leader, the supervisor of the project detailed scope of the previous preparation of the specification and related work breakdown structure, etc. were determined.
Seven, do the project scope control
In the process of the whole project, through regular or occasional inspection and management review of the implementation of the project, formed a periodic performance report. When a scope change occurs, the first is to confirm whether the scope changes have occurred, through the project team meeting, to analyze the cause of the change, please party A and the design party to confirm the change. Then revise the project scope Management plan and the detailed scope specification. At the same time, the place where the changes are made is enforced.
Viii. project experience and lessons learned
There is also a lack of clarity on the scope definition
When a change occurs
This article from the "Crooked Don't" blog, declined reprint!
"9.28 Jobs" on the scope management of XX Information System construction project