Project Management guide

FAQ

← Back to FAQ

What is Scope in Project Management?

First off, scope can refer to either product scope or project scope. It's important to know the difference:

  • Product scope is defined as the functions and features that characterize a product or a service.
  • Project scope, on the other hand, is the work that must be done in order to deliver a product according to the product's scope (required functions and features).

Project scope is the common understanding among stakeholders about what goes into a project and what factors define its success. A project's scope is made up of the functionalities or specifications outlined in the requirements.

What is Project Scope in Project Management?

Scope is documented in a scope statement, which is an integral part of any project plan. And what is a scope statement exactly? It's a written document that is used as the basis for project decisions down the line. The scope statement clearly delineates what is in scope (the work required). Everything else is out of scope. What does out of scope mean in project management? Simply put, this is anything that does not fall within the required functionalities and specifications that are documented in the scope statement.

What is Project Scope Management?

According to the PMBOK: "Managing project scope is primarily concerned with defining and controlling what is and is not included in the project.”

What is Involved in Project Scope Management?

Here's where we get down to the process of building that scope statement. The PMBOK recognizes 6 major scope management processes involved in managing and defining a project's parameters. These are:

1. Planning scope management: A scope management plan is created based on input from the project plan, the project charter, and consultation with stakeholders.

2. Collecting requirements: A requirements management plan is created based on the scope management plan plus stakeholder input. Interviews, focus group discussions, surveys, and more will be used to understand requirements. This will all be documented.

3. Defining scope: A project scope statement is produced based on all the requirements documentation plus the project charter and the scope management plan. This definition will be the basis for all project activity.

4. Creating the Work Breakdown Structure: A Work Breakdown Structure (WBS) is built after analyzing the project scope statement and the requirements documentation. The WBS is basically the entire project broken down into individual tasks, and deliverables are clearly defined.

5. Validating scope: Here, deliverables are inspected and reviewed. Either they're accepted as complete or further revisions are requested.

6. Controlling scope: As the project is executed, scope must be controlled. Performance reports are compared against project requirements to see where gaps exist, which may result in changes to the project plan.

Further Reading: