1 LOGO

By Hosam Dahb

Scope Management

Scope Management

• Collect Requirements• Define Scope• Create WBS• Verify Scope• Control Scope

Processes used to identify all the work required and only the work required to successfully complete the project

2

5. Scope Management ProcessesInitiation Planning Executing Controlling

5.1 Collect Requirements

5.2 Define Scope

5.3 Create WBS

5.4 Verify Scope

5.5 Control Scope

3

5.1 Collect Requirements

• Collect Requirements is the process of defining and documenting stakeholders’ needs to meet the project objectives.

• Collecting requirements is defining and managing customer expectations.

• Requirements become the foundation of the WBS. Cost, schedule, and quality planning are all built upon these requirements.

4

5.1 Collect Requirements

5

Inputs Tools And Techniques Output

1.Project charter2.Stakeholder

register

1. Interviews2. Focus groups3. Facilitated workshops4. Group creativity techniques5. Group decision making

techniques6. Questionnaires and surveys7. Observations8. Prototypes

1. Requirements documentation

2. Requirements management plan

3. Requirements Traceability Matrix

Collect Requirements Data Flow Diagram

6

5.2 Define Scope

• Define Scope is the process of developing a detailed description of the project and product.

• The preparation of a detailed project scope statement is critical to project success and builds upon the major deliverables, assumptions, and constraints that are documented during project initiation.

7

5.2 Define Scope

8

Inputs Tools And Techniques Output

1. Project charter2. Requirements

documentation3. Organizational

process Assets

1. Expert judgment2. Product analysis3. Alternatives identification4. Facilitated workshops

1. Project scope statement

2. Project document updates

Define Scope Data Flow Diagram

9

5.3 Create WBSWork Breakdown Structure

• Create WBS is the process of subdividing project deliverables and project work into smaller, more manageable components.

• The WBS is a deliverable-oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project objectives and create the required deliverables.

10

5.3 Create WBS

11

Inputs Tools And Techniques

Output

1. Project scope statement2. Requirements documentation3. Organizational process

assets

1. Decomposition 1. WBS2. WBS dictionary3. Scope baseline4. Project document

updates

Create WBS Data Flow Diagram

12

5.4 Verify Scope• Verify Scope is the process of formalizing

acceptance of the completed project deliverables. This includes reviewing deliverables with the customer or sponsor to ensure that they are completed satisfactorily

• scope verification is primarily concerned with acceptance of the deliverables while Quality control is primarily concerned with correctness of the deliverables and meeting the quality requirements specified for the deliverables. 13

5.4 Verify Scope

14

Inputs Tools And Techniques

Output

1. Project management plan2. Requirements documentation3. Requirements traceability

matrix4. Validated deliverables

1. Inspection 1. Accepted deliverables

2. Change requests3. Project document

updates

Verify Scope Data Flow Diagram

15

5.5 Control Scope• Control Scope is the process of monitoring the

status of the project and product scope and managing changes to the scope baseline.

• Uncontrolled changes are often referred to as project scope creep.

16

5.5 Control Scope

17

Inputs Tools And Techniques

Output

1. Project management plan2. Work performance information3. Requirements documentation4. Requirements traceability matrix5. Organizational process assets

1. Variance analysis 1. Accepted deliverables

2. Change requests3. Project document

updates

Control Scope Data Flow Diagram

18

19

Exam Question

• List all the Scope Management Processes Inputs, Tools & Techniques and Outputs and draw all the related diagrams

• What is the scope management and how the scope change can impacts Time, Quality and cost constraints?