PMP 02 Project Scope Management - PMBOK 5th Edition

Project Scope Management Based on PMBOK 5th Edition

Waleed El-Naggar, MBA, PMP

https://www.facebook.com/waleed.naggar

Introduction to Project Scope

Plan Scope Management

Collect Requirements

Define Scope

Create WBS

Control Scope

Validate Scope

Agenda

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

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?

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 and

functions.

Product Scope vs. Project Scope

The process of creating a scope management plan that documents how the project scope will be defined, validated, and controlled.

It provides guidance and direction on scope will be managed.

5.1 Plan Scope Management

Plan Scope Management Data Flow

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

1. Expert Judgment: knowledgeable and

experiences parties.

2. Meetings.

Plan Scope Management: T & T

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 of

deliverables

How change requests will be applied to scope

Plan Scope Management: Output

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)

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 the

project deliverables

The process of determining, documenting and managing stakeholder needs to meet project objectives.

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

Requirements includes the quantified and documented needs and expectations of the sponsor, customer, and other stakeholders.

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

5.2 Collect requirements

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 a

stakeholder 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)

1. Project Scope Management Plan

2. Requirements Management Plan

3. Stakeholder Management Plan

4. Project Charter

5. Stakeholder Register

Collect Requirements: Inputs

1. Interviews: meeting the stakeholders to ask

prepared and spontaneous question &

recording the responses.

Collect Requirements: T & T (1)

2. Focus groups: bring together stakeholders

and subject matter experts to learn about

their expectations and attitudes about a

proposed product,

service or result.

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

Mind Map

Affinity Diagram

5. Group Decision Making Techniques

Unanimity

Majority

Plurality

Dictatorship

6. Questionnaire and Surveys

7. Observations

8. Prototypes

9. Benchmarking

10.Context Diagrams

11. Document Analysis

1. Requirements Document

Business Requirements

Stakeholder requirements

Solution requirements

Project requirements

Transition requirements

2. Requirements Traceability Matrix

Collect Requirements: Outputs

Sample Requirements Traceability Matrix

The best tool in collecting requirements for a

cross-functional project is:

A. Facilitated Workshops

B. Interviews

C. Surveys

D. Brainstorming

The process of developing a detailed description

of the project and product.

5.3 Define Scope

Define Scope Data Flow

1. Scope Management Plan

2. Project charter

Procedures & Templates

Historical Data

Lessons learned from old Projects

Define Scope: Inputs

1. Expert Judgment

2. Product Analysis

3. Alternatives Identification

4. Facilitated workshops

Define Scope: T & T

1. Scope Statement: describes project’s

deliverables and the work required to create

those deliverables. It includes

Product scope description

Deliverables’ Acceptance Criteria

Project Deliverables

Project Exclusion

Project Assumptions

Constraints

Define Scope: Outputs (1)

Elements of

Project

Charter and

Statement

2. Project Documents Updates: may include,

but not limited to:

Stakeholder register

Requirements Documents

Requirements Traceability Matrix

Define Scope: Outputs (2)

Why would you consider the scope statement so important

in 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

Subdividing the project deliverables and

project work into smaller and more

manageable components.

The work breakdown structure is a

deliverable-oriented hierarchical

decomposition of project work.

5.4 Create WBS

Create WBS Data Flow

Sample WBS

Sample

1. Scope Management Plan

2. Project Scope Statement

4. Enterprise Environmental Factors

Create WBS: Inputs

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 size

and complexity of the project.

2. Expert Judgment

Create WBS: T & T

1. Scope Baseline

Project Scope Statement

WBS Dictionary

2. Project Documents updates

Create WBS: Outputs

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)

Control

Accounts,

Packages

Activities

A work breakdown structure numbering system allows

project staff to:

A. Systematically estimate costs of work breakdown

structure elements.

B. Provide project justification

C. Identify the level at which individual elements are

D. Use it in project management software

Which of the following documents contain detailed

descriptions of work packages?

A. Work breakdown structure (WBS) dictionary

B. Activity list

C. Preliminary project scope statement

D. Project scope management plan

The work breakdown structure can best be thought of

as an effective aid for ___________ communication

A. Team

B. PMO

C. Customer

D. Stakeholders

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

Validate Scope: Data Flow Diagram

1. Project Management Plan

2. Requirements Documentation

4. Validated Deliverables

5. Work Performance Data

Validate Scope: Inputs

1. Inspection: measuring, examining, and

validating to determine whether work and

deliverables meet requirements and product

acceptance criteria. Inspections may be called

reviews, audits, and walkthroughs.

2. Group Decision Making Techniques

Validate Scope: T & T

1. Accepted Deliverables

2. Change Requests

3. Work Performance Information

4. Project Document Updates

Validate Scope: Outputs

Which of the following is an output of scope

verification?

A. WBS template

B. Rework

C. Formal acceptance

D. SOW acceptance

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

Control

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)

4. Work Performance Data

Control Scope: Inputs (2)

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

1. Work Performance Information

2. Change Requests

3. Project Management Plan Updates

4. Project Document Updates

5. Organizational Process Asset Updates

Control Scope: Outputs

During a project team meeting, a team member suggests

an 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.

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 information

system.

waleed_k@aucegypt.edu

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

PMP 02 Project Scope Management - PMBOK 5th Edition

Business

PMP Exam Flashcards presentation 2 of 5 ( PMBOK - 5th Edition - PMI ) Download it in PowerPoint

PMBOK Processes Pmp

Pmp – pmbok 5th edition chapter4 project integration management final

PMBOK Guide 5th Edition and MS Project 2010: A Practical ... · PMBOK Guide 5th Edition and MS Project 2010: A Practical Step-by-Step Approach By Satya Narayan Dash, PMP, CSM, MCP

PMP Exam Flashcards presentation 3 of 5 ( PMBOK - 5th Edition - PMI ) Download it in PowerPoint

PMP 05 Project Quality Management - PMBOK 5th Edition

PMP Exam Prep: Project Integration Management Overview (for PMBOK Guide 5th Edition)

For the PMP® Exam using PMBOK® Guide 5th Edition

5TH EDITION (PMBOK 5) - acculeadsolutions.com€¦ · Get an E Copy of PMBOK 5th edition along with business lunch and coffee on the training days. The PMP recognizes demonstrated

Acerca de PMP - PMBok y PMI

PMP Exam Preparation : PMBOK 5th Question & Answer level 1.0

PP-003-PMP Mock Exams-Based on PMBOK 5th Edition

PMP PMbok 5th CH1 - CH2

Pmp pmbok 5 updates vs pmbok 4

PMP Exam Flashcards presentation 4 of 5 ( PMBOK - 5th Edition - PMI ) Download it in PowerPoint

PMP PMBOK 5TH Ch 6 time management

PMP Cost Formulas & Cost Process Management Overview in plain English (PMBOK 5th Edition). Learn the cost formulas for your PMP test

13-Pmp Professional Responsibility Pmbok v4

PMP Prep Course - Amazon S3 Prep Course 3 About PMP Course ... the PMBOK (5th edition) and presents the ... 13 Project Procurement Management

PMP 08 Project Risk Management - PMBOK 5th Edition