1. Day 8
ELC 347/BUS 348/PSA 347

2. Agenda Questions? IP part 1 Late
IP Part 2 Due Oct 10 (or maybe Oct 14)
Group work days  Oct 3
Assignment 3 Due
Due September 30 prior to class
Assignment 4 Posted
Read Case Study 4.3, Problems with John (page 130)  and 5.4, Classic Case: The Ford Edsel . (page 167). Complete and upload the answers to the Questions at the end of each case study. In addition, complete the MS Project Exercise Project Outline-Remodeling an Appliance on page 171 of the text. Upload a MS project file (*.mpp) Due Oct 7
Exam 1 on Oct 7
Chaps 1-5 Open Book Open Notes 80 min.
Scope Management

3. Chapter 5
Scope Management

4. Chapter 5 Learning Objectives
After 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.

5. 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 reporting
2) Scope statement 5) Control systems
3) Work authorization 6) Project closeout

6. 1) Conceptual Development
The process that addresses project objectives by finding the best ways to meet them.
Key steps in information development:
Problem/need statement
Information gathering
Constraints
Alternative analysis
Project objectives

7. Problem Statements Successful conceptual development requires:
Reduction of overall project complexity
Goals and objects are clearly stated
Reference points are provided
Complete understanding of the problem

8. 2) Statement of Work (SOW)
A SOW is a detailed narrative description of the work required for a project.
Effective SOWs contain
Introduction and background
Technical description
Timeline and milestones
Client expectations

9. Statement of Work Components
Background
Objectives
Scope
Task or Requirements
Selection Criteria
Deliverables or Delivery Schedule
Security
Place of Performance
Period of Performance
Statement of work.docx

10. Scope Statement Process
Establish the project goal criteria
cost
schedule
performance
deliverables
review and approval gates
Develop the management plan for the project
Establish a work breakdown structure
Create a scope baseline

11. Goal Setting With and Without Work Breakdown Structures (WBS)
Figure 5.2
Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall

12. 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 objectives
Offers a logical structure
Establishes a method of control
Communicates project status
Improves communication
Demonstrates control structure

13. Example WBS Making a PBJ Gather materials Assembly Consumption
Get 2 slices of bread
Get peanut butter
Get jelly
Get butter knife
Assembly
Using knife spread 1/8” layer of peanut butter on one side of one slice of bread
Using knife spread 1/8” layer of jelly on one side of the other slice of bread
Place two slices of bread together with peanut butter in contact with jelly
Consumption
Bite off a chunk of PBJ
Chew
Swallow

14. Defining a Project Work Package
Work package forms lowest level in WBS.
Work package has a deliverable result.
Work package has one owner.
Work package may be considered by its owner as a project in itself.
A work package may include several milestones.
A work package should fit organizational procedures and culture.
The optimal size of a work package may be expressed in terms on labor hours, calendar time, cost, reporting period, and risks.

15. Work Breakdown Structure and Codes
1.0
1.2
1.3
1.4
1.2.1
1.2.2
1.2.3
1.3.1
1.3.2
The project is the overall project under development
Deliverables are major project components
Sub-deliverables are supporting deliverables
Work Packages are individual project activities

16. Sample WBS in MS Project 2010
PBJ.mpp
Figure 5.7

17. Sample WBS in ProjectLibre

18. Organizational Breakdown Structure
Organizational Breakdown Structure (OBS) allows
Work definition
Owner assignment of work packages
Budget assignment to departments
OBS links cost, activity & responsibility

19. Intersection of the WBS and OBS
Figure 5.8
Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall

20. Cost Account Rollup Using OBS
Figure 5.10
Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall

21. Responsibility Assignment Matrix
Figure 5.11

22. 3) Work Authorization The formal “go ahead” to begin work
Follows the scope management steps of:
scope definition
planning documents
management plans
contractual documents

23. Contractual Documentation
Most contracts contain:
Requirements
Valid consideration
Contracted terms
Contracts range from:
Lump Sum
Cost Plus
also called
“Turnkey”

24. 4) Scope Reporting
determines what types of information reported, who receives copies, when, and how information is acquired and disseminated.
Typical project reports contain
Cost status
Schedule status
Technical performance

26. 5) Types of Control Systems
Configuration
Design
Trend monitoring
Document
Acquisition
Specification
templates\Project Exception report.doc
templates\Technology Project Assessment xls

27. 6) Project Closeout The job is not over until the paperwork is done…
Closeout documentation is used to:
Resolve disputes
Train project managers
Facilitate auditing
Closeout documentation includes:
Historical records
Post project analysis
Financial closeout

28. Reasons Why (IT) Projects Fail
Politics
Naïve promises
Naïve optimism of youth
Startup mentality of fledging entrepreneurial companies
“Marine Corps” 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

29. Using MS project 2010 (and ProjectLibre)
Many of the required functions/reports in Project management are part of MS project 2010
Industry wide acceptance
Do not use Wizard till you are comfortable with MS project
File  New  Blank Project
Enter Project and all
Deliverables
Sub deliverables
Work packages
Indent using arrows to show decomposition
Template
Actual project
More on MS Project as we progress through course

30. Summary
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.

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