Work Breakdown Structure Use and Demo

2

SCOPE

TIME COST

Concepts of Project Management

When a project has a WBS its like having the Scope on steroids.

3

The Planning Process and the WBS

Project Charter

Scope

Scope Definition

WBS

WBS Outline

Task Definition & Logic

Work Duration

Location

Special Skills

GenericResources Pool DescripSkill Requirements

Resource Assignment

Leveling

WBS

4

The Planning Process and the WBS

Project

Segment

Assembly A1

SubAssyA11

DesignA12

SubAssyA12

SubAssyA13

Assembly A2

Segment

CS Component B1

TestA12

BuildA12

DesignA2

TestA2

BuildA2

DesignB1

TestB1

CodeB1

DesignA1

DesignB1

BuildA1

BuildA2

DesignA2

TestA2

TestA1

TestB1

CodeB1

≈

≈

≈

≈

WBS

NetworkDiagram

5

The WBS as defined by PMI

A deliverable-oriented hierarchical decomposition of the work to be

executed by the project team to accomplish the project objectives

and create the required deliverables. Each descending level

represents an increasingly detailed definition of the project

work.*

The WBS as defined by PMI

* A guide to the Project Management Body of Knowledge 3rd edition.

Project Management Institute (PMI). Page 379

What the heck is that?

6

Work Package vs. Task vs. Activity

They are all the same for this demo. They are the bottom level of the WBS.

Their description contains a verb and a noun.

They normally have a unique identifier.

They identify specific work to be performed.

They normally have a duration.

They are a source for risk.

They are a deliverable

They consume resources

7

Functions & Benefits of a WBS

1. Identifies ALL work to be accomplished on the project.

2. A breakdown of the project into specific work packages.

3. Describes ALL work to be accomplished on the project.

4. A mechanism to roll-up items to a parent level.

5. Accounts for ALL work to be accomplished on the project.

6. Helps to identify all project deliverables. No “I forgots”.

7. Represents ALL work to be accomplished on the project.

8. Supports activity estimates.

8

Basic Attributes of a WBS

• A systematic breakdown of the project objective(s) in a hierarchical format.

• The top level is the project objective and deliverable.

• The next level defines the major segments of the planned objective and deliverables.

• Upper and mid-levels define a decomposition of the major segments into components.

• Lower levels define the work to be accomplished to create each lower level product.

• The lowest level is defined as the work package.

9

WBS Demo

P h ase 1 P h ase 2 P h ase 3

T h e P rod u ct

10

WBS Diagram(s)

S e gm en t A

A sse m b B 1 A sse m b B 2 A sse m b B 3

S e gm en t B

W o rk W o rk

A sse m b C 1

W o rk W o rk

S u b -A ssm bC 2 .1

W o rk W o rk

S u b -A ssm bC 2 .2

A sse m b C 2

S e gm en t C

P ro jec t, E nd -p ro d u cto r S ys tem

11

WBS Diagram(s)

1.1Select

Designer

1.2CreatePlans

1.3Select

Contractor

1.0Kitchen Design

2.1Purchase

Sink

2.2Purchase

Lights

2.0Purchase Appliance

3.1Tear Out

3.2Change Walls

3.3Install NewCabinets

3.4Install Floor

3.5Finish &Clean Up

3.0Walls & Cabinets

4.1WireKitchen

4.2InstallLights

4.0Rewire

5.1InstallPiping

5.2InstallSink

5.3Install

Dishwasher

5.0Kitchen

Plumbing

6.0Eat!

RemodelKitchen Project

12

WBS Diagram(s)

Start Finish

A B C

D E F

This is NOT a Work Breakdown Structure!

13

WBS Diagram(s)

This is a Work Breakdown Structure!

1 .1 1 .2 1 .3

P ro du c t1 P ro du c t2

3 .1 .1 3 .1 .2 3 .1 .3 3 .1 .4

3 .1 3 .2 3 .3

P ro du c t3

4 .1

4 .2 .1 4 .2 .2 4 .2 .3

4 .2

P ro du c t4

P ro je ct

14

WBS Components

• Hierarchy displayed in a tree structure.

• WBS elements forming the units of the tree.

• WBS level number.

• WBS level names.

• WBS number

• Numbering is very useful (3.2.5.1)Numbering is very useful (3.2.5.1)

• WBS dictionary

• A narrative associated with each work package,A narrative associated with each work package,

should include Cost, Resources, Risk & should include Cost, Resources, Risk &

Assumptions.Assumptions.

15

The Project Scope includes:All the work required, and only the work required, to complete the project successfully.

• Project Charter• Strategic Plan• Product Description• Scope Statement• Scope of Work• Supporting Detail• Assumptions• Constraints

Project Scope Foundation of a Comprehensive WBS

Project

Scope

16

Factors To Be Considered

•Each WBS element should represent a single tangible deliverable.

•Each element should represent an aggregation of all subordinate WBS elements listed immediately below it.

Think about These!

17

Factors To Be Considered

•Each subordinate WBS element must belong to only one single parent WBS element.

•The deliverables should be logically decomposed to the level that represents how they will be produced.

Think about These!

18

Factors To Be Considered

•Deliverables must be unique and distinct from their peers, and should be decomposed to the level of detail needed to plan and manage the work to obtain or create them.

Think about This!

19

Factors To Be Considered

•Deliverables should be clearly defined to eliminate duplication of effort within WBS elements, across organizations, or between individuals responsible for completing the work.

Think about This!

20

Factors To Be Considered

•Deliverables should be limited in size and definition for effective control - but not so small as to make cost of control excessive and not so large as to make the item unmanageable or the risk unacceptable.

Think about This!

21

The WBS development process should provide a vehicle for flexibility, particularly when the scope of the project effort may change. When work scope changes do take place, the WBS must be updated.

And This!

Factors To Be Considered

22

• Each entry in the WBS representing subcontracted or externally committed deliverables should directly correspond to matching entries in the subcontractor’s WBS.

• All deliverables are explicitly included in the WBS.

And These!

Factors To Be Considered

23

• All significant reporting items are included and identified in the WBS.

• All WBS elements should be compatible with organizational and accounting structures.

And These!

Factors To Be Considered

24

• A coding scheme for WBS elements that clearly represents the hierarchical structure when viewed in text format should be used.

• Technical input should be obtained from knowledgeable technical subject matter experts, and communicated to and validated by other experts assigned to the project.

And Finally These!

Factors To Be Considered

25

Developing the WBS Around the Scope

• The Scope serves as the framework of the WBS Down to the level where work is defined

• Define the work for each component of Scope Break work down as necessary

• The Scope/WBS interface is an important area for planners, the Project Manager, Systems Engineers and other stakeholders Systems Engineers ensure everything needed is

defined Every Scope item has a place in the WBS

26

The Work Package

The combination of all the Work Packages in the project defines all the work to be accomplished on the project.

Any work that is NOT part of the project should NOT have a Work Package.

Every Work Package has a specific deliverable.

Each Work Package should define all the effort, materials, equipment, risk, quality, cost and duration for the deliverable.

Work Packages are not logically linked in a WBS.

Each Work Package has a unique ID.

They can be used to control change. (Scope creep)

27

The Work Package

Some RULES

Never more than one reporting cycle.

A maximum cost

Maximum labor hours

PERT (Opt. + 4*best est. + Pes) / 6

Team consensus

Past Projects

28

WBS Dictionary

A document that defines and describes the work to be performed in each WBS element.

• Does not need to be lengthy

• Should sufficiently describe the work to be accomplished

• Useful to use a WBS form (Usually minimal information)

• Different forms for different WBS levels

• The work described in each element can be converted into a comprehensive statement of work

29

WBS Dictionary

A document that defines and describes the work to be performed in each WBS element.

•Advantage - The discipline of describing the work in each element in words

• Author is confident it address all the work to be performed

• The total project scope is thereby clearly and comprehensively defined

30

That’s Itfor the WBS Demo