Chapter Project Scope Management

Project Scope Management includes the processes required to ensure that the project includes all the work required, and only the work required, to complete the project successfully. Managing the project scope is primarily concerned with defining and controlling what is and is not included in the project. Table 5-1 provides an overview of the Project Scope Management processes, which include the following:

5.1 Collect Requirements—the process of defining and documenting the project and product features and functions needed to fulfill stakeholder's needs and expectations.

5.2 Define Scope—the process of developing a detailed description of the project and product.

5.3 Create Work Breakdown Structure—the process of subdividing project deliverables and project work into smaller, more manageable components.

5.4 Verify Scope—the process of formalizing acceptance of the completed project deliverables.

5.5 Control Scope—the process of monitoring the status of the project and product scope and managing changes.

These processes interact with each other and with the processes in the other Knowledge Areas. Each process can involve effort from one or more persons, based on the needs of the project. Each process occurs at least once in every project and occurs in one or more project phases, if the project is divided into phases. Although the processes are presented here as discrete components with well-defined interfaces, in practice they will overlap and interact in ways not detailed here. Process interactions are discussed in detail in Chapter 3, Project Management Processes. In the project context, the term scope can refer to:

• Product scope. The features and functions that characterize a product, service, or result or

• Project scope. The work that needs to be accomplished to deliver a product, service, or result with the specified features and functions.

This chapter primarily focuses on the processes used to manage the project scope. The processes used to manage project scope as well as the supporting tools and techniques, vary by application area and are usually defined as part of the project life cycle. The approved detailed project scope statement and its associated WBS and WBS dictionary are the scope baseline for the project. This baselined scope is then monitored, verified and controlled throughout the lifecycle of the project.

Table 5-1. Project Scope Management: Inputs, Tools & Techniques, and Outputs

Project Scope Management

5.1 Collect Requirements

1. Inputs

1. Project charter

2. Stakeholder register

2. Tools & Techniques

1. Interviews

2. Focus groups

3. Facilitated workshops

4. Groupcreativitytechniques

5. Group decision making techniques

6. Questionnaires and surveys

7. Observations

8. Prototypes

3. Outputs

1. Stakeholder requirements documentation

2. Requirements management plan

3. Requirements traceability matrix

5.4 Verify Scope

1, Inputs

1. Scope baseline

2. Stakeholder requirements documentation

3. Requirements traceability matrix

4. Validated deliverables

2, Tools & Techniques t. Inspection

3, Outputs

1. Accepted deliverables

2. Change requests

5.3 Define Scope

1. Inputs

1. Project charter

2. Stakeholder requirements documentation

3. Organizational process assets

2. Tools & Techniques

1. Expert judgment

2. Product analysis

3. Alternatives identification

4. Facilitated workshops

3. Outputs

1, Project scope statement

2. Project document updates

5.5 Control Scope

1. Inputs

1. Project management plan

2. Work performance data

3. Stakeholder requirements documentation

4. Requirements traceability matrix

2. Tools & Techniques

1. Variance analysis

2, Replanning

3. Outputs

1 Organizational process assets updates

2. Change requests

3. Project management plan updates

4. Work performance measurements

5.3 Create WBS

1. Inputs

1. Project scope statement

2. Stakeholder requirements documentation

3. Organizational process assets

2. Tools & Techniques 1. Decomposition

3. Outputs

1. Work breakdown structure

2. WBS dictionary

3. Scope baseline

4. Project document updates

Completion of the project scope is measured against the project management plan (Section 4.2). Completion of the product scopc is measured against the product requirements (Section 5.1). The Project Scope Management processes need to be well integrated with the other Knowledge Area processes, so that the work of the project will result in delivery of the specified product scopc.

Was this article helpful?

0 0
Project Management Made Easy

Project Management Made Easy

What you need to know about… Project Management Made Easy! Project management consists of more than just a large building project and can encompass small projects as well. No matter what the size of your project, you need to have some sort of project management. How you manage your project has everything to do with its outcome.

Get My Free Ebook

Post a comment