Project Scope Control Management

Revision as of 15:26, 22 February 2019

Abstract

In an ideal world, once a scope has been defined and moved into prototyping and construction, no changes will be made to the requirements or the extent, but in reality, project scope is continuously evolving over the entire lifecycle of the project. Therefore, it is significantly important that the scope identifies all the work that the project will accomplish to achieve its final goal and have a clear and easy scope management process that refers to the set of various processes that ensure a project's scope is accurately defined and mapped. ^[1]. It is essential at the start of the project scope that it consists of sufficient detail to determine the purpose of the project with the expected benefits and any constraints such as time and budget. The Project Scope Management (PSM) processes consists of six parts, where control scope is the last part and is the process of monitoring and controlling the status of the product and project scope including managing changes to the scope baseline. ^[1]. The product scope refers to how a product is made while a project scope focusses more on how to deliver the service or product. ^[2]. The advantage of control scope is that it allows the baseline to be maintained throughout the entire project. Without a well-defined project scope, the time and cost of the project cannot be an estimation and obtained due to a lack of communication, which applies that the scope needs to be changed. This immediately affects the cost and disrupts the schedule of the project generating losses. This article focuses on achieving a successful project with the six main aspects of project scope management and including the scope change control and what changes may need to be proceeded to have a great scope. These aspects will be discussed in detail alongside the general guidelines of project scope management.

Introduction

Project Scope Management

Figure 1: Project Scope Management Overview and their tasks, inspired from the PMBOK® Guide ^[2]

1. Plan Scope Management

2. Collect Requirements

3. Define Scope

4. Create Work Breakdown Structure

5. Validate Scope

6. Control Scope

Figure 2: Inputs, tools and techniques, and outputs of the define scope process, with guidance from the PMBOK® Guide ^[2]

Scope Change Control

Figure 2: Inputs, tools and techniques, and outputs of the define scope process, with guidance from the PMBOK® Guide ^[2]

Application of Scope Change

Methodology

Change Request

Limitations

Glossary

References

1. ↑ ^{1.0 1.1} Project Management Institute (2013). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) 5th edition. Page 105
2. ↑ ^{2.0 2.1 2.2 2.3} William R. Duncan. (2013). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) 5th edition. Pennsylvania: Project Management Institute.

Annotated Bibliography