Sybex Chapter 03 - Intro

LCS International, Inc.

PMP Review

Chapter 3

Developing the Project

Scope Statement Presented by

David J. Lanners, MBA, PMP

These slides are intended to be used only in settings where each

viewer has an original copy of the Sybex PMP Study Guide book.

LCS International, Inc. PMP Exam Review - (Rev F) Chapter 3 - Slide 2

Reproduced from PMP Project Management Professional Study Guide by permission of Sybex, Inc. ISBN 0-7821-3601-X. ©2005, Sybex, Inc. All rights reserved.


Scope Statement

• Develop Project Management Plan

• Collect Requirements

• Define Scope

• Create WBS

Develop Project Management Plan Develop Project Management Plan is the process of documenting the actions necessary to define, prepare, integrate, and coordinate all subsidiary

plans. The project management plan defines how the project is executed, monitored, controlled, and closed. The project management plan can be

summary level or detailed, and it can be composed of one or more subsidiary plans and other components. The project management plan evolves

through progressive elaboration and updates authorized through the integrated change control process until project closure.

4.2 Project

Management

Integration

To Direct and Manage Project Execution

From Develop Project Charter

Tools & Techniques .1 Expert judgment

Inputs .1 Project charter

.2 Outputs from planning processes

.3 Enterprise environmental factors

.4 Organizational process assets

Outputs .1 Project management plan



Documenting the

Project Management Plan

• Processes you’ll use to perform the project

• Degrees of execution of each of the processes selected for the project

• Tools and techniques to use from each process

• Dependencies and interactions of the processes used to manage the project

• Methods for executing the work of the project to fulfill the objectives

• Methods for monitoring and controlling changes

• Methods to perform configuration management

• Methods for determining & maintaining the validity of performance baselines

• Communication needs of the stakeholders & techniques to fulfill those needs

• Project life cycle

• Project phases for multi-phased projects

• Management reviews of issues and pending decisions



Documenting the


• Subsidiary Plans

• Project scope management plan

• Schedule management plan

• Cost management plan

• Quality management plan

• Process improvement plan

• Staffing management plan

• Communications management plan

• Risk management plan

• Procurement management plan



Documenting the


• Process components to be considered:

• Milestone list

• Resource calendar

• Schedule baseline

• Cost baseline

• Quality baseline

• Risk register





• Define Scope

• Create WBS


Scope Statement

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

directly influenced by the care taken in capturing and managing project and product requirements. Requirements include the quantified and

documented needs and expectations of the sponsor, customer, and other stakeholders. These requirements need to be elicited, analyzed, and

recorded in enough detail to be measured during project execution. Requirements become the foundation of the Work Breakdown Structure.

5.1 Project

Scope

Management

To Define Scope, Control Scope

Tools & Techniques .1 Interviews

.2 Focus groups

.3 Facilitated workshops

.4 Group creativity techniques

.5 Group decision making techniques

.6 Questionnaires and surveys

.7 Observations

.8 Prototypes


.2 Stakeholder register

From Develop Project Charter, Identify Stakeholders

Outputs .1 Requirements documentation

.2 Requirements management plan

.3 Requirements traceability matrix





• Define Scope

• Create WBS


Scope Statement

Define Scope Define Scope is the process of developing a detailed description of the project and product. Preparation of a detailed project scope statement is

critical to project success and builds upon the major deliverables, assumptions, and constraints that were documented during project initiation.

During planning, project scope is defined and described with greater specificity as more information about the project is known. Existing risks,

assumptions, and constraints are analyzed for completeness. Additional risks, assumptions, and constraints are documented as necessary.

5.2 Project

Scope

Management

To Create WBS (Work Breakdown Structure)

From Collect Requirements

Tools & Techniques .1 Expert judgment

.2 Product analysis

.3 Alternatives identification

.4 Facilitated workshops


.2 Requirements documentation


Outputs .1 Project scope statement

.2 Project document updates



Writing the Project

Scope Statement

• Scope Statement Components

• Project objectives

• Product scope description

• Project deliverables

• Project requirements

• Project boundaries

• Product acceptance criteria

• Project constraints

• Project assumptions



Project Objectives

• Objectives are quantifiable criteria used to

measure project success . . .

• Objectives should follow the SMART rule:

• S – Specific

• M – Measurable

• A – Achievable, Attainable or Accurate

• R – Relevant, Realistic, or Result-Oriented

• T – Time-bound, Time-limited, or Tangible



Project Constraints

• Constraints are anything that either restrict

actions or dictate actions of the team.

• Time constraints

• Budget constraints

• Quality constraints

• Schedule constraints

• Technology constraints

• Directive constraints



Documenting the Scope

Management Plan

• The process you’ll use to prepare the project

scope statement

• A process for creating the WBS

• A definition of how the deliverables will be

verified for accuracy and accepted

• A description of the process for controlling

scope change requests





• Define Scope

• Create WBS


Scope Statement

Create WBS Create WBS (Work Breakdown Structure) is the process of subdividing the project deliverables and project work into smaller, more manageable

components. The WBS is a deliverable-oriented hierarchical decomposition of all the work to be executed by the project team to accomplish the

project objectives and create the required deliverables. Planned work is contained within the lowest-level WBS components, which are called

work packages. A work package can be scheduled, cost estimated, monitored, and controlled. The WBS serves as the basis for the activity list.

5.3 Project

Scope

Management

To Define Activities, Verify Scope

From Collect Requirements, Define Scope

Tools & Techniques .1 Decomposition

Inputs .1 Project scope statement

.2 Requirements documentation


Outputs .1 WBS

.2 WBS dictionary

.3 Scope baseline

.4 Project document updates



Constructing the WBS

(First 2 levels)




(First 3 levels)




(Bottom 2 levels)



Unique WBS Identifiers



WBS Dictionary

• Code of accounts identifier

• Statement of work

• Organization responsible for completion

• List of schedule milestones

• Contract information

• Quality requirements for the component

• Relevant technical references



Other Breakdown Structures

• Organizational Breakdown Structure (OBS)

• Bill of Materials (BOM)

• Risk Breakdown Structure (RBS)

• Resource Breakdown Structure (RBS)

Date post:	05-Oct-2021
Category:	Documents
Upload:	others
View:	5 times
Download:	0 times

Sybex Chapter 03 - Intro

Documents