Project Scope Management

Project Scope Management

Scope of the project: it is required by the project to achieve the project goal and to deliver specially crafted products and services.

Two reasons for the spread of demand: 1. The project team never knows the scope of the project. What the project should do and what the project should not do. 2. Many Information System Project Teams have never used any effective methods and processes to control changes in scope.

Product Scope and project scope

The product scope refers to the functions that information system products or services should contain.

Project scope refers to the work that can be done to deliver information system projects.

Project Scope Management consists of five processes: scope planning, scope definition, creation of work breakdown structure, scope validation, and scope control.

I. Preparation of the project scope plan

The project scope management plan describes how the project team manages the project scope.

Input: Project Charter, preliminary scope statement, assets in the organizational process, environment and organizational factors, and project management plan.

Output: Project Scope Management Plan.

Technology: product analysis, identification of optional solutions, expert judgment

Range Definition

Scope definition is to define the scope of the project, that is, to prepare the scope management plan defined in the phase according to the scope plan, and adopt a certain method to gradually obtain the precise scope of the project.

Scope boundary: the most important task of scope definition is to define the scope boundary of the project in detail. The scope boundary is the boundary between the work that should be done and the work that does not need to be done.

Deliverables: The scope of the project needs to define the main deliverables of the project, and all the major work required should be listed in the deliverables, rather than the necessary work.

If the deliverables of a project are not carefully defined, the consumption of budget, progress, and resources will be greatly affected.

Input: Project Charter, scope management plan, organizational process assets, and approval change application.

Output: Project Scope Statement (detailed) and scope management plan (updated)

Create a work breakdown structure

Input: Project Scope Statement (detailed) and Project Management Plan

Output: WBS and WBS dictionary, project management plan (update)

Technology: WBS template, decomposition, WBS coding design

Confirm Scope

It is not easy to confirm the project scope. The project team tends to ask the user to confirm the scope to start the following work as soon as possible, and the user may think that he has not seen anything. How can he confirm it? The project team must have sufficient ability to communicate with users to make users aware that although the scope of the project is confirmed to be formal, it does not mean that the scope of the project is a piece of steel and cannot be modified, changing the scope of a project may change the project time, progress, and resources.

Scope validation mainly determines whether the project's interactive results meet the requirements of stakeholders.

When the stakeholders confirm the scope, they generally need to check several issues:

1. Check whether deliverables are true and verifiable.

2. Whether each delivery result has a clear milestone and whether the milestone has a clear and identifiable event, such as the customer's written consent.

3. Whether there are clear quality standards.

4. whether the review and commitment are clearly expressed.

5. Whether the project scope covers all activities of products or services to be completed, and whether there are any omissions or errors.

6. is the risk of the project scope too high? Can the management level reduce the impact on the project when foreseeable risks occur.

Management LayerThe scope of the project is to focus on the impact of the project scope on the project progress, capital and resources, whether these factors exceed the scope of the organization, and whether they are reasonable in terms of input and output.

CustomerThe main concern is the scope of products and whether deliverables of related projects can be used to complete products or services.

Project management personnelFocus on whether deliverables are sufficient and must be completed, whether time, capital and resources are sufficient, and the main potential risks and solutions to them.

Project Team MemberFocus on the elements involved and responsible elements in the project scope, check whether your work is sufficient through the time series in the scope definition, and whether you have multiple jobs within the project scope, these jobs have conflicts. If the project team members estimate that some deliverables cannot be completed by themselves, they need to give their own opinions.

Input: Scope Management Plan, deliverable, Project Scope statement, WBS, and WBS dictionary.

Output: Confirmed range, WBS, and WBS Dictionary Update

Technology/tool/method: Check

Variable range control