scope management 05-01. copyright © 2013 pearson education, inc. publishing as prentice hall...

Chapter 5Scope Management

05-01

Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall

Chapter 5 Learning ObjectivesAfter completing this chapter, students will be able to:Understand the importance of scope management for

project success.Understand the significance of developing a scope

statement.Construct a Work Breakdown Structure for a project.Develop a Responsibility Assignment Matrix for a

project.Describe the roles of changes and configuration

management in assessing project scope.

05-02


Project Scope

Project scope is everything about a project – work content as well as expected outcomes.

Scope management is the function of controlling a project in terms of its goals and objectives and consists of:

1) Conceptual development 4) Scope reporting2) Scope statement 5) Control

systems3) Work authorization 6) Project closeout

05-03


Conceptual DevelopmentThe process that addresses project

objectives by finding the best ways to meet them.

Key steps in information development:Problem/need statementInformation gatheringConstraintsAlternative analysisProject objectives

05-04


Problem StatementsSuccessful conceptual development

requires:

Reduction of overall project complexity

Goals and objects are clearly statedReference points are provided

Complete understanding of the problem 05-05


Statement of Work (SOW)A SOW is a detailed narrative description of

the work required for a project.

Effective SOWs contain1. Introduction and background2. Technical description3. Timeline and milestones4. Client expectations

05-06


Statement of Work ComponentsBackgroundObjectivesScopeTask or RequirementsSelection CriteriaDeliverables or Delivery ScheduleSecurityPlace of PerformancePeriod of Performance

05-07


Scope Statement Process1. Establish the project goal criteria

a) costb) schedulec) performanced) deliverablese) review and approval gates

2. Develop the management plan for the project

3. Establish a work breakdown structure4. Create a scope baseline

05-08

05-9

Goal Setting With and Without Work Breakdown Structures (WBS)

Figure 5.2



Work Breakdown Structure (WBS)A process that sets a project’s scope by breaking

down its overall mission into a cohesive set of synchronous, increasingly specific tasks.

What does WBS accomplish?Echoes project objectivesOffers a logical structureEstablishes a method of controlCommunicates project statusImproves communicationDemonstrates control structure

05-10


Work Breakdown Structure and Codes

Work Packages are individual project activities

1.0

1.2 1.3 1.4

1.2.1

1.2.2

1.2.3

1.3.1

1.3.2

1.2.3.1

1.2.3.2

Deliverables are major project components

Sub-deliverables are supporting deliverables

The project is the overall project under development

05-11


Sample WBS in MS Project 2010

05-12Figure 5.7


Defining a Work PackageLowest level in WBS

Deliverable result

One owner

Miniature projects

Milestones

Fits organization

Trackable

05-13


Organizational Breakdown StructureOrganizational Breakdown Structure (OBS)

allowsWork definitionOwner assignment of work packagesBudget assignment to departments

OBS links cost, activity & responsibility

05-14

Intersection of the WBS and OBS

05-15Figure 5.8Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall

Cost Account Rollup Using OBS

05-16Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Figure 5.10


Responsibility Assignment Matrix

05-17Figure 5.11


Defining a Project Work Package1. Work package forms lowest level in WBS.2. Work package has a deliverable result.3. Work package has one owner.4. Work package may be considered by its owner

as a project in itself.5. A work package may include several milestones.6. A work package should fit organizational

procedures and culture.7. The optimal size of a work package may be

expressed in terms on labor hours, calendar time, cost, reporting period, and risks.

05-18


Work Authorization

The formal “go ahead” to begin work

Follows the scope management steps of:1. scope definition2. planning documents3. management plans4. contractual documents

05-19


Contractual DocumentationMost contracts contain:

RequirementsValid considerationContracted terms

Contracts range from:

Lump Sum Cost Plusalso called “Turnkey”

05-20


Scope Reporting

determines what types of information reported, who receives copies, when, and how information is acquired and disseminated.

Typical project reports contain1. Cost status2. Schedule status3. Technical performance

05-21


Reasons Why Projects FailPoliticsNaïve promisesNaïve optimism of youthStartup mentality of fledging entrepreneurial

companies“Marine Corps” mentalityIntensive competition caused by globalizationIntense competition caused by appearance of new

technologiesIntense pressure caused by unexpected government

regulationsUnexpected and/or unplanned crises

05-22


Types of Control Systems

o Configuration

o Design

o Trend monitoring

o Document

o Acquisition

o Specification

05-23


Project Closeout

The job is not over until the paperwork is done…

Closeout documentation is used to:Resolve disputesTrain project managersFacilitate auditing

Closeout documentation includes:Historical recordsPost project analysisFinancial closeout

05-24


Summary1. Understand the importance of scope

management for project success.2. Understand the significance of developing a

scope statement.3. Construct a Work Breakdown Structure for a

project.4. Develop a Responsibility Assignment Matrix

for a project.5. Describe the roles of changes and

configuration management in assessing project scope.

05-25

scope management 05-01. copyright © 2013 pearson education, inc. publishing as prentice hall...

Documents