pmp training project scope management part 1

PMI Project Management

Professional (PMP)® Workshop

Project Scope Management

Part - 1

© 2013 Skillogic Knowledge Solutions. All Rights

Reserved

2

Project Scope Management

Integration

Scope

Time

Cost

Quality

Human Resource

Communications

Risk

Procurement

Stakeholder

© 2013 Skillogic Knowledge Solutions. All Rights Reserved3

Why Project Scope Management?

To ensure that the project includes all the work and only

the work required to complete the project deliverables

To define, monitor, manage or control the in-scope and

out-of-scope requirements

4 © 2013 Skillogic Knowledge Solutions. All Rights Reserved

Product Scope Vs Project Scope

Product Scope

The features and functions that characterize a service, result or

a product

Project Scope

The work performed to deliver a product, service or result.

Project Scope may include product scope.


Project Scope Management : Processes

Plan Scope Management

Collect Requirements

Define Scope

Create WBS

Validate Scope

Control Scope


Plan Scope Management

This is new in PMBOK 5th edition

It is a process of creating a “Scope management plan” which is

a document to know how scope will be defined, validated and

controlled.

It provides guidance and direction on how scope will be

managed throughout the project.


Plan Scope ManagementIn

puts • Project

management plan

• Project charter

• Enterprise environmental factors

• Organizational Process Assets

Too

ls &

Tec

hniq

ues • Expert

Judgment

• Meetings

Ou

tputs • Scope

management plan

• Requirements management plan


Plan Scope Management - Inputs

Project Management Plan

Project Charter

Project Context

High level product description and features

Enterprise Environmental Factors

Organization culture

Infrastructure

Marketplace conditions

Resource administration

Organizational process assets

Policies and Procedures

Historical information

Lessons Learned KB


Plan Scope Management –

Tools & Techniques

Expert Judgment

Collective information from experienced / trained persons or

groups to come up with “scope management plan” which is a

primary output of this process

Meetings

Project manager, project teams, sponsor, selected

stakeholders, etc. Together attend the meeting to come up

with scope management plan


Plan Scope Management - Output

“Scope management plan” is the main output of this process.

It contains the information of how scope will be defined, developed,

monitored, controlled and verified

It is a subsidiary plan or component of “Project Management Plan”

It contains the processes

for preparing a detailed project scope statement

that enables how WBS can be created, maintained and approved

Specifies how formal acceptance of deliverables/completed project

deliverables will be obtained

Process to control how to validate scope


Plan Scope Management - Output

“Requirements management plan” is another output of this

process.

It include the activities such as

how requirement activities can be planned, tracked and

reported

configuration management activities (changes to the product

are handled)

process of prioritizing the requirements

metrics for the product

structure for Traceability matrix


Collect Requirements

It is a process of acquiring, collecting, documenting, and

managing stakeholder needs and expectations/requirements to

meet the project objectives

It provides the basis for defining and managing project scope

(including product scope)


Collect RequirementsIn

puts • Scope management

plan

• Requirements management plan

• Stakeholder management plan

• Project charter

• Stakeholder register

Too

ls &

Tec

hniq

ues

• Interviews

• Focus groups

• Facilitated workshops

• Group creativity techniques

• Group decision making techniques

• Questionnaires and surveys

• Observations

• Prototypes

• Benchmarking

• Context diagrams

• Document analysis

Ou

tputs • Requirements

documentation

• Requirements traceability matrix


Collect Requirements - Inputs

Scope management Plan

Requirements management plan

(The above two are outputs from previous process)

Stakeholder management plan –

Used to understand how stakeholders involve in requirements activities

Used to understand stakeholder communication requirements

Project Charter

Stakeholder register

all the information about stakeholders

major requirements and major expectations that stakeholders have for the

project.


Collect Requirements – Tools & Techniques

Interviews –

formal or informal approach to get information from

stakeholders by talking to them directly

Focus Groups –

Prequalified stakeholders and SMEs share their expectations

of proposed product. A moderator directs the group

interactively

Facilitated workshops –

Focused sessions or workshops with key stakeholders that

also helps to get consensus


Collect Requirements –

Tools & Techniques

Group Creativity Techniques

Brainstorming

Nominal group technique

Idea/mind mapping

Affinity Diagram

Multi-criteria decision analysis

Group Decision-Making Techniques

Unanimity

Majority

Plurality

Dictatorship


Collect Requirements –

Tools & Techniques

Questionnaires and Surveys –

set of written Q’s given to large number of audience

Observations –

viewing directly how the business experts perform the tasks or job, also called as “job

shadowing”

Prototypes –

create a working model of the expected product before actually building it. This helps

in getting early feedback

Benchmarking

Compares actual with planned to provide a basis for measuring performance

Context Diagrams

Visual representation of a business system that covers product scope. It shows how

actors & business system interacts with each other.

Document Analysis

Going through existing documents and analyze the information to get the expectations

/ requirements of the product


Collect Requirements - Output

Requirements documentation includes

Business requirements

Stakeholder requirements

Solution requirements

Functional

Non-functional

Transition requirements

Quality requirements

Requirement assumptions, constraints, and dependencies


Collect Requirements - Output

Requirements Traceability matrix

links the product requirements throughout the project

deliverables and tracks till the end of delivery

Helps to manage the changes to the scope

An example of RTM:



Skillogic Knowledge Solutions

Call Us

@ 901-989-9000

If you are looking for PMP classes in Bangalore visit:

http://in.skillogic.com/pmp-training/pmp-certification-bangalore/

http://in.skillogic.com/pmp-training/pmp-certification-bangalore/

pmp training project scope management part 1

Education