Upload
doxuyen
View
219
Download
0
Embed Size (px)
Citation preview
Lecture 5
Scope Management
By : Prof. Lili Saghafi
Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall 1
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
Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall
� 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
Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall
Scope management is the function of
controlling a project in terms of its goals
and objectives and consists of:
1) Conceptual development 4) Scope reporting
2) Scope statement 5) Control systems
3) Work authorization 6) Project closeout
05-03
Conceptual Development
The process that addresses project objectives by finding the best ways to meet them.
Key steps in information development:
Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall
Key steps in information development:
�Problem/need statement
�Information gathering
�Constraints
�Alternative analysis
�Project objectives
05-04
Problem Statements
Successful conceptual development requires:
�Reduction of overall project complexity
Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall
�
�Goals and objects are clearly stated
�Reference 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 contain
Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall
Effective SOWs contain
1. Introduction and background
2. Technical description
3. Timeline and milestones
4. Client expectations
05-06
Statement of Work Components
� Background
� Objectives
� Scope
Task or Requirements
Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall
� Task or Requirements
� Selection Criteria
� Deliverables or Delivery Schedule
� Security
� Place of Performance
� Period of Performance
05-07
Scope Statement Process
1. Establish the project goal criteria
a) cost
b) schedule
c) performance
Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall
c) performance
d) deliverables
e) review and approval gates
2. Develop the management plan for the project
3. Establish a work breakdown structure
4. Create a scope baseline
05-08
Goal Setting With and Without
Work Breakdown Structures (WBS)Figure 5.2
05-9Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall
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?
Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall
What does WBS accomplish?
�Echoes project objectives
�Offers a logical structure
�Establishes a method of control
�Communicates project status
�Improves communication
�Demonstrates control structure
05-10
Work Breakdown Structure and Codes1.0
1.2 1.3 1.4
1.2.1 1.3.1Deliverables are major project components
The project is the overall project under development
Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall
Work Packages are individual project activities
1.2.2
1.2.3
1.3.2
1.2.3.1
1.2.3.2
components
Sub-deliverables are supporting deliverables
05-11
PROJECT
Sample WBS in MS Project 2010
Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall 05-12Figure 5.7
Defining a Work Package
Lowest level in WBS
Deliverable result
One owner
Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall
One owner
Miniature projects
Milestones
Fits organization
Trackable
05-13
Organizational Breakdown Structure
Organizational Breakdown Structure (OBS) allows
� Work definition
� Owner assignment of work packages
Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall
� Budget assignment to departments
OBS links cost, activity & responsibility
05-14
PROJECT
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
PROJECT
Responsibility Assignment Matrix
Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall 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
Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall
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
PROJECT
Work Authorization
The formal “go ahead” to begin work
Follows the scope management steps of:
Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall
Follows the scope management steps of:
1. scope definition
2. planning documents
3. management plans
4. contractual documents
05-19
PROJECT
Contractual Documentation
Most contracts contain:
Requirements
Valid consideration
Contracted terms
Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall
Contracted 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.
Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall
Typical project reports contain
1. Cost status
2. Schedule status
3. Technical performance
05-21
Reasons Why Projects Fail
� Politics� Naïve promises� Naïve optimism of youth� Startup mentality of fledging ( become capable of fly)
entrepreneurial companies
Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall
entrepreneurial companies� “Marine Corps” ( soldiers ) mentality� Intensive competition caused by globalization� Intense competition caused by appearance of new
technologies� Intense pressure caused by unexpected government
regulations� Unexpected and/or unplanned crises
05-22
Types of Control Systems
o Configuration
o Design
o Trend monitoring
Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall
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 disputes
Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall
Resolve disputes
Train project managers
Facilitate auditing
Closeout documentation includes:
Historical records
Post project analysis
Financial closeout
05-24
Summary
1. Understand the importance of scope management for project success.
2. Understand the significance of developing a scope statement.
Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall
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