31
Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Day 8 ELC 347/BUS 348/PSA 347

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

Embed Size (px)

Citation preview

Page 1: Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Day 8

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

Day 8

ELC 347/BUS 348/PSA 347

Page 2: Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Day 8

Copyright © 2013 Pearson Education, Inc. Publishing as Prentice HallCh 1 -2

AgendaQuestions? IP part 1 Late IP Part 2 Due Oct 10 (or maybe Oct 14)

Group work days Oct 3Assignment 3 Due

Due September 30 prior to classAssignment 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

Page 3: Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Day 8

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

Chapter 5Scope Management

05-03

Page 4: Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Day 8

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-04

Page 5: Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Day 8

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

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 05-05

Page 6: Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Day 8

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

1) Conceptual DevelopmentThe process that addresses project

objectives by finding the best ways to meet them.

Key steps in information development:

a.Problem/need statementb.Information gatheringc. Constraintsd.Alternative analysise.Project objectives

05-06

Page 7: Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Day 8

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

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-07

Page 8: Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Day 8

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

2) 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-08

Page 9: Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Day 8

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

Statement of Work ComponentsBackgroundObjectivesScopeTask or RequirementsSelection CriteriaDeliverables or Delivery ScheduleSecurityPlace of PerformancePeriod of PerformanceStatement of work.docx

05-09

Page 10: Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Day 8

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

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-010

Page 11: Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Day 8

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

Goal Setting With and Without Work Breakdown Structures (WBS)

Figure 5.2

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

Page 12: Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Day 8

Copyright © 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?Echoes project objectivesOffers a logical structureEstablishes a method of controlCommunicates project statusImproves communicationDemonstrates control structure

05-12

Page 13: Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Day 8

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

Example WBS1. Making a PBJ

1. Gather materials 1. Get 2 slices of bread 2. Get peanut butter 3. Get jelly 4. Get butter knife

2. Assembly 1. Using knife spread 1/8” layer of peanut butter on one side of one slice of

bread2. Using knife spread 1/8” layer of jelly on one side of the other slice of bread3. Place two slices of bread together with peanut butter in contact with jelly

3. Consumption1. Bite off a chunk of PBJ2. Chew 3. Swallow

Page 14: Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Day 8

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

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-14

Page 15: Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Day 8

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

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-15

Page 16: Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Day 8

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

Sample WBS in MS Project 2010

05-16Figure 5.7

PBJ.mpp

Page 17: Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Day 8

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

Sample WBS in ProjectLibre

17

Page 18: Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Day 8

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

Organizational Breakdown StructureOrganizational Breakdown Structure (OBS)

allowsWork definitionOwner assignment of work packagesBudget assignment to departments

OBS links cost, activity & responsibility

05-18

Page 19: Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Day 8

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

Intersection of the WBS and OBS

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

Page 20: Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Day 8

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

Cost Account Rollup Using OBS

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

Page 21: Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Day 8

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

Responsibility Assignment Matrix

05-21Figure 5.11

Page 22: Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Day 8

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

3) 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-22

Page 23: Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Day 8

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

Contractual DocumentationMost contracts contain:

RequirementsValid considerationContracted terms

Contracts range from:

Lump Sum

Cost Plusalso

called “Turnkey”

05-23

Page 24: Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Day 8

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

4) 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-24

Page 26: Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Day 8

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

5) Types of Control Systems

o Configuration

o Design

o Trend monitoring

o Document

o Acquisition

o Specification

05-26

templates\Project Exception report.doctemplates\Technology Project Assessment 1-16-01.xls

Page 27: Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Day 8

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

6) 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-27

Page 28: Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Day 8

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

Reasons Why (IT) 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-28

Page 29: Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Day 8

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

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 ProjectEnter Project and all

DeliverablesSub deliverablesWork packages

Indent using arrows to show decomposition TemplateActual project

More on MS Project as we progress through course

Page 30: Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Day 8

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

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

Page 31: Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Day 8

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