Anticlue

The scope control process has two key parts. First, it controls changes to a project’s scope. Secondly it assure that all scope changes are process by the described Integrated Change Control Process. A scope change is any alteration affecting the agreed-upon project scope detailed within the Work Breakdown Structure. Scope Control is a part of the Monitoring and Controlling Process Group.
Project Manager need to evaluate the effect a proposed change can have on a project. Before beginning to analyze the proposed change, the following inputs are needed:

• Project Scope Statement – The Project Scope Statement is the document capturing the project scope including the major deliverables.
• Work Breakdown Structure – The WBS details the scope of the project and the project scope baseline. The WBS is used to determine which work packages could be affected by the change.
• WBS dictionary – The WBS Dictionary defines the statement of work, milestones, and a unique identifier for each component. The WBS dictionary also helps to define the project's scope baseline and is analyzed to determine how a proposed change affects deliverables.
• Project Scope Management Plan – The Project Scope Management Plan describes how the scope will be controlled and how changes to the project scope will be managed. The scope stability section indicates the anticipated variation to scope.
• Performance reports - Performance reports provide information on project status, completed deliverables, and work progress. Unsatisfactory project performance can lead to requests to reduce scope or to perform corrective actions.
• Approved change requests – Approved change requests are requests used within the Scope Control process to expand or reduce the project scope. Only changes processed according to the agreed procedures are authorized and implemented. These changes often impact cost, time, and quality.
• Work performance information – Work performance information provides information on the status of changes to the project scope including the status of deliverables and implementation status for change requests, corrective actions, preventive actions, and defect repairs.

Since the need for change is going to occur, there are some tools and techniques that can be utilized to control scope changes. The tools and techniques used in the Scope Control process are:

• Configuration management system - The configuration management system is a subsystem of the project management information system. It is a collection of documented procedures used to identify and document any changes to the characteristics of a product, and to record and report each change and its implementation status. This system also includes a method for validating approved changes.
• Change control system - The change control system is critical because it contains formal procedures that outline how project deliverables and documentation should be managed and changed. The system contains the formal process for submitting, reviewing, tracking, and authorizing proposed changes. The change control system is integrated with the systems in place that control project scope. Often, a change control system is the subset of a configuration management system.
• Variance analysis - To control your project, you need measurements that help you identify whether your project is on the right track. Variance analysis uses information from the project performance reports to assess any possible variations. This technique involves identifying variance—specifically, the difference between what is expected and what is created, and why those differences occurred. Project managers then use this information to decide whether any corrective actions are required.
• Re-planning – Re-planning must be performed when the proposed scope changes are significant enough to affect existing project documents. A change is considered significant if documents left unrevised become useless as the project progresses. If re-planning occurs, affected documents should be modified. This activity usually includes altering the Work Breakdown Structure (WBS) and the WBS dictionary or the Project Scope Statement.

The quickest way to loose control of a project is the occurrence of arbitrary changes. By controlling changes, project managers can get everyone working towards the same goal – delivering the project on time and within budget.

After reviewing the change, the scope control process has resulting outputs. The outputs are:

• Updates to the Project Scope Statement - Once changes have been approved, the Project Scope Statement needs to be updated. The Project Scope Statement is used to assess any future changes in scope.
• Updates to the Work Breakdown Structure (WBS) and WBS dictionary - The Work Breakdown Structure and WBS dictionary need to be in alignment with all other planning documents, reflecting any approved changes in scope. This is because they are used to verify the work results as part of the project.
• Updates to the scope baseline - The scope baseline needs to be updated because it is used in all aspects of project management, including cost estimates and scheduling.
• Requested changes - Part of the Scope Control process involves dealing with changes. The Integrated Change Control process specifies how these should be handled. After changes have been processed, the approved changes will need to be implemented.
• Recommended corrective actions - Some changes occur because of project performance issues. When these types of problems have been identified, corrective actions must be taken to ensure that project work aligns with the project plan.
• Organizational process assets updates - To learn from variances that occur and how they are handled, the project manager should document the reasons behind the variances and corrective actions, and then update the database so that similar problems can be avoided in future projects.
• Project Management Plan updates - When changes affect baseline documents, the Project Management Plan needs to be revised. Changes to the Project Management Plan and related documents should follow the Integrated Change Control process. The affected documents can include cost baselines and schedules.

0 Comments to “The Scope Control Process”

Please share your thoughts and suggestions

Name (required)

Email (required) (will not be published)

Website URL