pmp exam preparation course: 04 project scope management

www.wizardea.com | [email protected]

B. M. Shahrier Majumder, PMPPMP® Exam Preparation

Project Scope Management


Learning Objectives

Upon completion of this topic you will learn about

– Identify the processes, activities and documentation items for Scope Management

– Describe the elements (and deliverables) for Project Scope Management

– Tools and techniques of the key activities of the scope Management

3


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”

4

• Project Scope and Product Scope may differ

• Scope Management and Requirement Management are not same


Key Activities of Scope Management

Collect Requirements: The process of defining and documenting stakeholder’s needs to meet the project objectives.

Define Scope: The process of developing a detail description of the project and product.

Create WBS: The process of subdividing project deliverables and project work into smaller, more manageable components.

Verify Scope: The process of finalizing acceptance of the complete project deliverables.

Control Scope: The process of monitoring the status of the project and product scope and managing changes of the scope baseline.

5


Collect Requirements | Data Flow Diagram6

Diagram Source | PMBOK 4th Edition


Collect Requirements

Inputs Tools & Techniques Outputs

Project CharterStakeholder Register

InterviewsFocus groupsFacilitated workshopsGroup creativity techniquesGroup decision making techniquesQuestionnaires and surveysPrototypesObservations

Requirement documentRequirement management planRequirement traceability matrix

7

7


Collect Requirements > Inputs

• Project Charter• High-level project requirements and high-level product description of

the project

• Stakeholder Register• Identified stakeholder list

8


Collect Requirements > Tools & Techniques

• Interview• An interview is a formal or informal approach to discover information

from stakeholders by talking with them directly.

• Focus Groups• Focus groups bring together prequalified stakeholders and subject

matter experts to learn about their expectations and attitude about

proposed products, services or results.

• Facilitated Workshops• Requirement workshops are focused sessions that bring key cross-

functional stakeholders together to define product requirements.

9



• Group Creativity Techniques• Brainstorming

• Nominal group technique

• The Delphi technique

• Idea/mind mapping

• Group Decision Making Techniques• Unanimity

• Majority

• Plurality

• Dictatorship

10



• Questionnaires and Surveys• Questionnaires and surveys are written sets of questions design to quickly

accumulate information from a wide number of respondents.

• Observations• Observations provide a direct way of viewing individuals in their environment

and how they perform their jobs or tasks and carry out processes.

• Prototypes• Prototyping is a method of obtaining early feedback on requirements by

providing a working model of the expected product before actually building it.

11


Collect Requirements > Outputs

• Requirements Documentation• Requirements documentation describes how individual requirement meet the business need

for the project.

• Requirements may start out of a high-level and become progressively more detailed as

more is known.

• Requirements must be measurable and testable, traceable, complete, consistent and

acceptable to the key stakeholders.

• Requirements Management Plan• The requirement management plan documents how requirements will be analyzed,

documented and managed through out the project.

• Requirements Traceability Matrix• Requirements traceability matrix is a table that links requirements to their origin and traces

them throughout the project life cycle.

12

Get FR

EE Templates at w

ww

.wizardea.com

http://www.wizardea.com/


Define Scope | Data Flow Diagram



Define Scope


Project charterRequirements documentationOrganizational process assets

Expert judgmentProduct analysisAlternative identificationFacilitated Workshops

Project Scope StatementProject document updates


Define Scope > Tools and Techniques

• Expert Judgment• Expert judgment is provided by any group or individual with specialized

knowledge or training.

• Product Analysis• Product analysis includes techniques such as product breakdown,

system analysis, requirements analysis, system engineering, value

engineering and value analysis.

• Alternatives Identification• Alternative identification is a technique used to generate different

approaches to execute and perform the project.

15


Define Scope > Outputs

• Project Scope StatementThe detail project scope statements includes:

• Product scope description

• Product acceptance criteria

• Project deliverables

• Project exclusions

• Project constraints

• Project assumptions

16

Get FR

EE Templates at w

ww

.wizardea.com

http://www.wizardea.com/


Create WBS

• Work

Commonly used to refer to specific activity, duty, function, or assignment often

being a part or phase or some larger undertaking to achieve an objective.

• Breakdown

Division into parts or categories; separation into simpler substance;

decomposition.

• Structure

Something arranged in a definite pattern of organization .

17


Create WBS

• What are the benefits of creating of WBS?

18


Create WBS

WBS

Staffing

Estimating

Scheduling

Budgeting

Risk Management

NetworkDiagram

Project Control

Activity Lists

19


Create WBS | Data Flow Diagram

20

20



Create WBS


Project Scope StatementRequirements documentationOrganizational process assets

Decomposition WBSWBS dictionaryScope baseline Project documents updates

21

21


Create WBS > Tools & Techniques

• Decomposition• Decomposition is the subdivision of the project deliverables into smaller, more

manageable components until the work and deliverables are defined to the work

package level.

• The work package level is the lowest level of the WBS, it is the point at which the

cost and activity durations for the work can be reliably estimated and managed.

The WBS structure can be created in a number of forms:

• Using phases of the project life cycle

• Using major deliverables

• Using subprojects

22


Create WBS > Outputs

• Work Breakdown Structure:• Phase wise, milestone wise, deliverable wise etc.

• WBS Dictionary:• Code of work package, description of work, responsible organization/person,

duration, effort, milestone, resources required, technical reference etc.

• Scope Baseline:• Approved detailed project scope statement

• Work breakdown structure

• WBS Dictionary

23


Verify Scope | Data Flow Diagram



Verify Scope


Project management plan

Requirements documentation

Requirement traceability matrix

Validated deliverables

Inspection Accepted DeliverablesRequested changesProject documents

updates


Verify Scope > Tools & Techniques

• Inspection:• Inspection includes activities such as measuring, examining, and

verifying to determine whether work and deliverables meet

requirements and product acceptance criteria. Inspections are

sometimes called reviews, product reviews, audits and walkthrough. In

some application areas, these different terms have narrow and specific

meanings.

26


Control Scope | Data Flow Diagram

27

27



Control Scope


Project management plan

Work performance information

Requirement documentation

Requirement traceability matrix

Organizational process assets

Variance analysis Work performance measurements

Organization process assets updates

Change requestProject management

plan updatesProject documentation

updates

28

28


Control Scope > Tools and Techniques

• Variance Analysis• Project performance measurement are used to assess the magnitude

of variation from the original scope baseline.

29


Questions

30

• [[email protected]]

• http://bd.linkedin.com/in/shahrier

pmp exam preparation course: 04 project scope management

Education