A Scope Management processes determines what work is required to be done and ensure that the project includes only that work to complete the project.
Why managers need Project Scope Management
- Without determining the project scope, the time or cost that the project will take up cannot be estimated
- Scope management builds control processes to address elements that may alter project during the project life-cycle
- It helps to avoid the challenges that a project might encounter with every growing scope and unruly requirement list.
This stage includes both-
- Managing Project scope
- Managing Product scope
Project Scope Management Process include following activities.
| Process | Project Group | Key deliverables |
|---|
| Planning |
|
| Planning | Required document |
| Planning | Project scope statement |
| Planning | WBS directory, WBS |
| Monitoring and Controlling | Acceptance deliverables |
| Monitoring and Controlling | Change request |
We will see this all process step by step below:-
Plan Scope Management
The Scope Management plan will determine how the scope will be defined, validated and controlled.
| Primary Inputs | Tools and Techniques | Primary Outputs |
|---|
- Preliminary Project Scope Statement
|
|
|
| Meetings | Requirements management plans |
| Expert Jugment | Scope Management Plans |
- Enterprise environmental factors
|
|
|
- Organizational Process Assets
|
|
|
Collect Requirements
During this process managers use various techniques and tools for the collection of the project requirements from the stakeholders. This stage is very important and if done accurately the chances of error during the project will be minimal.
| Primary Inputs | Tools and Techniques | Primary Outputs |
|---|
| Interviews | Requirement documentation |
| Focus groups | Requirement management plan |
| Group creativity techniques | Requirements traceability matrix |
| Facilitated workshops |
|
| surveys and Questionaires |
|
| Prototypes |
|
| Observations |
|
| Group decision-making techniques |
|
Defining Scope Process
This process clearly indicates how the project is supposed to progress and what it cannot do. During this process it is ensured that the project remains on the track by reviewing the supporting documents. The resulting scope will then mention the stakeholder's requirements and expectations.
| Primary Inputs | Tools and Techniques | Primary Outputs |
|---|
| Expert Judgment | Project Scope statement |
- Requirements documentation
| Product analysis | Project document updates |
- Organizational Process Assets
| Alternative identification |
|
| Facilitated workshops |
|
Creating WBS (Work Breakdown Structure)
The WBS enables the project manager and his team to break down a high level project deliverables into a smaller, manageable units of work called work packages.
| Primary Inputs | Tools and Techniques | Primary Outputs |
|---|
| Decomposition | WBS |
- Requirements documentation
|
| WBS dictionary |
- Organizational Process Assets
|
| Scope baseline |
|
| Project document updates |
Validate Scope
The validate scope process involves clients acceptance. It is when the client formally accepts all the project deliverables. At the end of each phase this process occurs. During this process, the client gives their feedback on the work that was performed.
| Primary Inputs | Tools and Techniques | Primary Outputs |
|---|
| Inspection | Acceptance Deliverables |
|
| Change request |
- Requirement Traceability Matrix
|
| Project document updates |
|
|
|
Scope Control
This process or phase involves the monitoring of the project status and managing of the scope changes. Apart from this, it also involves assessing of the additional requirements by the customer or proactively overlooking the project scope.
| Primary Inputs | Tools and Techniques | Primary Outputs |
|---|
| Variance analysis | Work performance measurements |
- Requirements documentation
|
| Change requests |
- Requirement traceability matrix
|
|
|
- Organizational process assets
|
|
|
- Work performance information
|
| Project document updates |
Key points to remember for Scope Management
- To avoid cost overrun and schedule slips, the scope needs to be complete and accurate.
- Scope needs to be clearly defined to avoid unnecessary work and confusion
- Scope document should be shared with all stakeholders to avoid error in design and requirement
- The good practice for Scope Management is that the scope document must remain unaltered for the duration of project
Summary:
The scope management is used for determining how the rest of the scope planning processes will be managed.
The key aspect of this stage
- Project requirement analysis
- Communicate the scope change to all stakeholders
- Roles and responsibilities pertaining to scope
