pmp02projectscopemanagement-130907032132-

7/21/2019 pmp02projectscopemanagement-130907032132-

1/62


2/62

Introduction to Project Scope

Plan Scope Management

Collect Requirements

Define Scope

Create WBS

Control Scope

Validate Scope

Agenda

PMP - Project Scope Management 2https://www.facebook.com/waleed.naggar


3/62

Scope refers to all the work involved in creating

the deliverables of the project and the processes

used to create them.

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.

What is Project Scope?



4/62

Product scope: The futures & functions that

characterize the product, service, or result.

Project Scope: The work that needs to be

accomplished to deliver a product, service, or

result with the specified features andfunctions.

Product Scope vs. Project Scope



5/62



6/62

The process of creating a scope managementplan that documents how the project scope

will be defined, validated, and controlled.

It provides guidance and direction on scopewill be managed.

5.1 Plan Scope Management



7/62

Plan Scope Management Data

Flow



8/62

1. Project Management Plan: it defines how the

project is executed, monitored, controlled

and closed. It integrates all plan

components.

2. Project Charter

3. Enterprise Environmental Factors

4. Organizational Process Assets

Plan Scope Management: Inputs



9/62

1. Expert Judgment: knowledgeable and

experiences parties.

2. Meetings.

Plan Scope Management: T & T



10/62

1. Scope Management Plan. It includes:

Process for preparing a detailed project scope

statement.

Process to enable the creation of WBS

Process to establish how the WBS will be

managed

Define formal acceptance criteria ofdeliverables

How change requests will be applied to scope

Plan Scope Management: Output



11/62

2. Requirements Management Plan: describes how

requirements will be analyzed, documented, and

managed. It includes, but not limited to:

How requirements activities will be planned,tracked and reported.

Configuration management activities.

Requirements prioritization process.

Product metrics

Traceability structure

Plan Scope Management: Output (2)



12/62

Which is the BEST description of project scope?

A. All of the features and deliverables your

project will deliver

B. All of the products your project will make

C. All of the people involved in your project

D. All of the work you will do to build theproject deliverables

Quiz



13/62

The process of determining, documenting andmanaging stakeholder needs to meet projectobjectives.

The key benefit is to provide the basis fordefining and managing project scope.

Requirements includes the quantified anddocumented needs and expectations of thesponsor, customer, and other stakeholders.

Requirement must be analyzed and recorded ina clear and detailed way to be measured.

5.2 Collect requirements



14/62

Requirements can be grouped into classifications including:

Business requirements, describe the high-level needs of

the organization as a whole.

Stakeholder requirements, describe needs of astakeholder or stakeholder group.

Solution requirements, describe features, functions and

characteristics of the product, service, or results.

Transition requirements, describe temporary capabilities

such as data conversion & training needs.

5.2 Collect requirements (2)



15/62


CollectR

equirementsData

Flow


16/62

1. Project Scope Management Plan

2. Requirements Management Plan

3. Stakeholder Management Plan

4. Project Charter

5. Stakeholder Register

Collect Requirements: Inputs



17/62

1. Interviews: meeting the stakeholders to ask

prepared and spontaneous question &

recording the responses.

Collect Requirements: T & T (1)



18/62

2. Focus groups: bring together stakeholders

and subject matter experts to learn about

their expectations and attitudes about a

proposed product,service or result.




19/62

3. Facilitated Workshops: Focused session with

key cross-functional stakeholders to define

product requirements.

4. Group Creativity Techniques:

Brainstorming

Nominal Group

Idea/Mind Mapping

Affinity Diagram

Multi-criteria decision analysis




20/62

Mind Map



21/62

Affinity Diagram



22/62

5. Group Decision Making Techniques

Unanimity

Majority

Plurality

Dictatorship

6. Questionnaire and Surveys

7. Observations

8. Prototypes




23/62

9. Benchmarking

10.Context Diagrams

11. Document Analysis




24/62

1. Requirements Document

Business Requirements

Stakeholder requirements Solution requirements

Project requirements

Transition requirements

2. Requirements Traceability Matrix

Collect Requirements: Outputs



25/62

Sample Requirements Traceability Matrix



26/62


27/62

The process of developing a detailed description

of the project and product.

5.3 Define Scope



28/62

Define Scope Data Flow



29/62

1. Scope Management Plan

2. Project charter



Procedures & Templates

Historical Data

Lessons learned from old Projects

Define Scope: Inputs



30/62

1. Expert Judgment

2. Product Analysis

3. Alternatives Identification

4. Facilitated workshops

Define Scope: T & T



31/62

1. Scope Statement: describes projects

deliverables and the work required to create

those deliverables. It includes

Product scope description

DeliverablesAcceptance Criteria

Project Deliverables

Project Exclusion

Project Assumptions

Constraints

Define Scope: Outputs (1)



32/62


Elements of

Project

Charter and

Scope

Statement


33/62

2. Project Documents Updates: may include,

but not limited to:

Stakeholder register

Requirements Documents

Requirements Traceability Matrix

Define Scope: Outputs (2)



34/62

Why would you consider the scope statement so importantin your project management methodology?

A. Mandatory to consult the plan before accepting change.

B. Project managers must document any changes before

approving or declining them.

C. The project scope serves as a reference for all future

project decisions.

D. The scope statement is the base of WBS creation

Quiz



35/62

Subdividing the project deliverables and

project work into smaller and more

manageable components.

The work breakdown structure is a

deliverable-oriented hierarchicaldecomposition of project work.

5.4 Create WBS



36/62

Create

WBSDataFlow



37/62

Sample WBS



38/62

Sample WBS



39/62


40/62

1. Scope Management Plan

2. Project Scope Statement


4. Enterprise Environmental Factors


Create WBS: Inputs



41/62

1. Decomposition: The subdivision of project

deliverables into smaller, more manageable

components. The work package level is the

lowest level in the WBS, and is the point at

which the cost an activity durations can be

reliably estimated and managed. The level of

detail for work packages will vary with the sizeand complexity of the project.

2. Expert Judgment

Create WBS: T & T



42/62

1. Scope Baseline

Project Scope Statement

WBS

WBS Dictionary

2. Project Documents updates

Create WBS: Outputs



43/62

WBS Dictionary may include (but not limited to) Code of Account Identifier

Description of work

Assumptions and Constraints

Schedule Milestone

Resource required

Cost Estimate

Acceptance criteria Quality Requirements

Create WBS: Outputs (2)



44/62

Control

Accounts,

Work

Packages

and

Activities



45/62

A work breakdown structure numbering system allowsproject staff to:

A. Systematically estimate costs of work breakdown

structure elements.

B. Provide project justification

C. Identify the level at which individual elements are

found

D. Use it in project management software

Quiz



46/62

Which of the following documents contain detailed

descriptions of work packages?

A. Work breakdown structure (WBS) dictionaryB. Activity list

C. Preliminary project scope statement

D. Project scope management plan

Quiz



47/62

The work breakdown structure can best be thought of

as an effective aid for ___________ communication

A. Team

B. PMO

C. Customer

D. Stakeholders

Quiz



48/62

Formalizing acceptance of the completed

project deliverables.

Includes reviewing deliverables with the client

and obtaining formal acceptance of deliverables.

Scope verification is concerned with acceptance

of deliverables while quality control is

concerned with correctness of the deliverables

and meeting quality requirements.

5.5 Validate Scope



49/62

Validate Scope: Data Flow Diagram



50/62

1. Project Management Plan

2. Requirements Documentation

3. Requirements Traceability Matrix

4. Validated Deliverables

5. Work Performance Data

Validate Scope: Inputs



51/62

1. Inspection: measuring, examining, and

validating to determine whether work and

deliverables meet requirements and productacceptance criteria. Inspections may be called

reviews, audits, and walkthroughs.

2. Group Decision Making Techniques

Validate Scope: T & T



52/62

1. Accepted Deliverables

2. Change Requests

3. Work Performance Information

4. Project Document Updates

Validate Scope: Outputs



53/62


54/62

Monitoring the status of the project &

products scope

Managing changes to scope baseline

Ensure all requested changes and

recommended corrective or preventive actions

are processed through the Perform Integrated

Change Control process. Uncontrolled changes are often referred to as

project scope creep.

5.6 Control Scope



55/62

Control

ScopeData

Flow



56/62

1. Project Management Plan

Scope baseline

Scope management plan

Change management plan

Configuration management plan

Requirements management plan

2. Requirements Documentation

Control Scope: Inputs (1)



57/62


58/62

1. Variance Analysis

Analyze performance measurements to assess

the variation from the baseline scope. Analysis

should determine the cause and degree of

variance.

Control Scope: T & T



59/62

1. Work Performance Information

2. Change Requests

3. Project Management Plan Updates

4. Project Document Updates

5. Organizational Process Asset Updates

Control Scope: Outputs



60/62

During a project team meeting, a team member suggestsan enhancement to the scope that is beyond the scope of

the project charter. The project manager points out that

the team needs to concentrate on completing all the work

and only the work required. This is an example of:

A. Change management process.

B. scope management.

C. quality analysis.D. scope decomposition.

Quiz



61/62

Which of the following is the KEY attribute of scope

validation?

A. More complete project scope management plan

B. Customer acceptance of project deliverables

C. Improved schedule estimates

D. An improved project management informationsystem.

Quiz



62/62

[email protected]

pmp02projectscopemanagement-130907032132-

Documents

Transcript of pmp02projectscopemanagement-130907032132-