16
OM480 Defining the Project Parameters – Work Breakdown Schedule (WBS) (With Material from the Text Authors)

OM480 Defining the Project Parameters – Work Breakdown Schedule (WBS) (With Material from the Text Authors)

  • View
    221

  • Download
    0

Embed Size (px)

Citation preview

OM480

Defining the Project Parameters – Work

Breakdown Schedule (WBS)

(With Material from the Text Authors)

Overview

• Scheduling

• Work Breakdown Structures (WBS)

• Precedence Relationships

• PERT/CPM

• Activity Networks

Scheduling

• Project = Problem scheduled for solution• Requires:

– Planning– Organizing– Coordinating– Directing– Controlling

• gninnalP drawkcaB• Forward organizing, coordinating, directing, and

controlling

Project Management Trade-Offs

Performance

Quality

Cost Time

©

Project Priority Matrix

Constrain

Enhance

Accept

Time Performance Cost

Hierarchical Breakdown of the WBS

1

2

3

4

Project

Deliverable

Subdeliverable

Lowest subdeliverable

Cost account*

Work package

5

Complete project

Major deliverables

Supporting deliverables

Lowest managementresponsibility level

Grouping of work packagesfor monitoring progress andresponsibility

Identifiable work activities

Level Hierarchical breakdown Description

*This breakdown groups work packages by type of work within a deliverable and allows assignment ofresponsibility to an organizational unit. This extra step facilities a system for monitoring project progress

WBS – Key Terms

• Objectives: Logical division of project

– “How much by when”– Tied to specifications

• Tasks: Specific outcomes related to Objective

• Activities: Individual actions within a Task

– A desired result

Input(s) Transformation Output

WBS - Process

• Break down Objectives to Tasks to Activities

• Strive for single input yielding single output

• Measurable by hours to days

• Present in hierarchical methods (trees)

• Rely on “doers” over “experts”

WBS - Precedence

• Sequencing of activities based on relationship(s)

• Categories– Technical Requirements

• Physical movements

– Safety and Efficiency• Separate from technical requirements

– Policy/Preference Decisions• Aesthetics, approvals, other considerations

– Resource Constraints• $, equipment, skills, time

Work Breakdown StructurePersonal computer

prototype

Vendor,software,

applications

Mouse,keyboard,

voice

Diskstorageunits

Microprocessorunit

Moreitems

Floppy HardOptical Internalmemory

unit

BIOS (basicinput/output

system)

ROM RAM I/O File Utilities

Motor Circuitboard

Chassisframe

Read/writehead

WP-1M WP-1 CB WP-1 CF WP-1 RWHWP-2 CB WP-2 CF WP-2 RWHWP-3 CB WP-3 CF WP-3 RWHWP-4 CB WP-4 RWHWP-5 CB WP-5 RWHWP-6 CBWP-7 CB

~ ~ ~ ~ ~

~ ~

~ ~

Work packages

Lowest manageablesubdeliverables

Level1

2

3

4

5

Integration of WBS and OBS

Time

Cost accountnumber

Personal computerprototype

Vendor,software,

applications

Mouse,keyboard,

voice

Diskstorageunits

Microprocessorunit

Moreitems

Floppy HardOptical Internalmemory

unit

BIOS (basicinput/output

system)

ROM RAM I/O File Utilities

Motor Circuitboard

Chassisframe

Read/writehead

~ ~ ~ ~ ~

~ ~

~ ~

Lowest manageablesubdeliverables

Level1

2

3

4

5

1.0

1.2 1.3 1.1 1.4

1.1.1 1.1.2 1.1.31.4.1 1.4.2

1.4.1.1 1.4.1.2 1.4.2.1 1.4.2.2 1.4.2.3

1.1.3.1 1.1.3.2 1.1.3.3 1.1.3.4

Cost 1.1.3.4.1account

Cost Costaccount account

Cost Costaccount account

Costaccount

Costaccount

Work packages WP1.1.3.4.2.1 WP1.1.3.4.2.2 WP1.1.3.4.2.3

Budget byperiod

Production

Design

Test

Purchasing

Software

Manufacturing

Organization

WBS/Work Packages to Network

Circuitboard

Designcost

account

Productioncost

account

Testcost

account

Softwarecost

account

Lowestelement

Organizatio

Units

DesignWP D-1-1 SpecificationsWP D-1-2 Documentation

ProductionWP P-10-1 Proto 1WP P-10-2 Final Proto 2

Test systemsWP T-13-1 Test

SoftwareWP S-22-1 Software preliminaryWP S-22-1 Software final version

BProto 1

5

DFinal

proto 24

ASpecifications

and documentation2

CPreliminary

software3

FFinal

software2

KTest

3

AD-1-1D-1-2

BP-10-1

DP-10-2

FS-22-2

KT-13-1

CS-22-1

Duration and Activities

• Effort is not duration– Time spent in actual “work”

• Duration lasts longer– Elapsed time from activity start to finish

– Imagine “NFL two-minute warning”

• More on specific techniques in Chs 6-8• Realities of Duration Planning

– Deliveries

– Breakdowns/Repairs

– Approvals

PBS for Software Development Project

Responsibility Matrix

Example Responsibility Matrix: Conveyor Belt Project