Home / BA / Project Scope Management Processes

Project Scope Management Processes

The scope of a project is the clear idea of the work that is required to complete or deliver the requirements of the project successfully. The Project Managers responsibilities is to ensure that the only needed work will be performed and that each of the deliverables can be completed in the given time and budget.

There are six project scope management processes which are mentioned as below:

  1. Planning for Project Scope Management

It is the first process group in scope management. In this phase we want to gather input from all of the stakeholders. Then we will decide and document how we want to define, manage, validate and control the project scope. Once that is done, team members can be allocated tasks and provided them direction to deliver a project in given time and budget.

This plan also includes information on how you will handle uncertain circumstances throughout the project.

There are some inputs, tools and techniques, and outputs for the planning scope management process:

Inputs Tools and Techniques Outputs
Purpose of the project

Business objectives



Project description

Project scope and boundaries

Project deliverables

High-level risks

Stakeholders list

Requirements for the project

Expert judgement


Project scope

Product scope


Out of scope areas

Product acceptance criteria




  1. Collecting Requirements

Once the scope management plan is done, based on its input along with stakeholders’ interview and discussions the requirements management plan is documented. This document contains a set of requirements which include:

  • Functional and non-functional requirements
  • Business requirements
  • Reporting requirements
  • Stakeholders’ requirements
  • Services and quality requirements
  • Project assumptions
  • Project constraints


There are some inputs, tools and techniques, and outputs for collecting requirements:


Inputs Tools and Technique Outputs
Scope management plan

Stakeholder management plan

Stakeholder register

Requirement management plan


Focus groups


Questionnaire and survey


Requirements documentation

Requirements management plan

Requirements traceability matrix


  1. Defining the Project Scope

This process involves the detailed description of the project. The scope is the statement outlines the goals that will be met to achieve a satisfactory output.

So, while gathering the requirements, all the different requirements of the product and service are defined.

The following steps are included while defining the scope:

  • Project goals and objectives
  • Tasks
  • Resources
  • Budget and Time

Once these steps are completed, the constraints of the project need to be clarified. After doing this, the project scope will clear to stakeholders, team members and other senior management members what will and what will not be included in the final product.

There are some inputs, tools and techniques, and outputs for defining the scope process:

Inputs Tools and Techniques Outputs
Scope management plan

Project permission

Requirement documentation

Organizational process assets

Expert judgement

Product analysis

Alternative identification


Project scope statement

Project documents updates


  1. Creating a Work Breakdown Structure (WBS)

Creating the WBS will help us in separating the final deliverables of the project. This is done using a technique called as Decomposition. Based on the project scope statement and requirements management plan the main task is divided into smaller chunks to make the project delivery smooth and easy. This kind of structure is called as work breakdown structure (WBS).

There are some inputs, tools and techniques, and outputs for the creating a work breakdown structure:

Inputs Tools and Techniques Outputs
Project management plan

Requirements documentation

Organization process assets

Expert judgement

Decomposition (Division)


Scope baseline

Project document updates


  1. Validating Scope process

This process occurs at the end of phase. This process focuses mainly on customer acceptance. It is when project customer accepts all the project deliverables. And the customer gives feedback on the work that was performed.

There are some inputs, tools and techniques, and outputs of the validating scope process:

Inputs Tools and Techniques Outputs
Project management plan

Requirements documentation


Validated deliverables


Decision making

Accepted deliverables

Work performance information

Change requests

Project document updates



  1. Controlling Scope process

This is a post-execution process in a project. If any new change request comes up which is beyond the project scope that should come through proper change request. Besides, it is also a performance measurement process where gaps are identified against performance reports by validating it with project requirements. This may change the project plan.

There are some inputs, tools and techniques, and outputs for the controlling scope process:

Inputs Tools and Techniques Outputs
Project management plan

Requirement documentation


Work performance data

Organization process assets

Data analysis

Variance analysis

Work performance information

Change Requests

Project management plan updates

Project document updates

Organization process assets updates

Project scope management defining the required work and ensure that the required work is done within the given timeline. It includes a detailed description process of scope management, control and management. The Project manager needs to get approval on the project scope document. An effective and proper project scope management helps the project manager leads the project successful. So, Scope management is very important while implementing the project and it requires effort, time and patience.

About Sayali Karan Sonawane

Check Also

Explain SRS and Its Key Elements

Introduction: Clear and concise communication is the cornerstone of successful software development projects. Software Requirement …

Leave a Reply

Watch Dragon ball super