Work Breakdown Structure Kathy S. Schwaig. What is a Work Breakdown Structure (WBS)? A WBS is a...

Post on 03-Jan-2016

213 views 0 download

Transcript of Work Breakdown Structure Kathy S. Schwaig. What is a Work Breakdown Structure (WBS)? A WBS is a...

Work Breakdown Structure

Kathy S. Schwaig

What is a Work Breakdown Structure (WBS)?

A WBS is a logical hierarchy of work packages involved in a projectA WBS is an essential tool in the project planning processOnce the project charter has been created, the project must be scoped out in more detail

Purpose of a WBSA WBS helps to define the work required for the project and to break it into manageable pieces called work packages A good WBS can help in the development of schedules, budgets, and resource requirementsThe WBS is a useful tool for identification of activities and assignment of responsibilities

Possible Ways to Organize Work Breakdown Structures

By project phasesBy project componentsBy functional areasBy types of workBy resource types

Work PackagesA work package is a deliverable or product at the lowest level of the WBSAs a general rule, each work package should represent 80 hours (or less) of effortEach work package should have a clearly identified person who is responsible for it This individual should . . .

Be a member of the project teamBe responsible for the successful completion of the work package

Requirements Definition System Development System Testing DocumentationSystem Design

Equipment History Module

Spare Parts Inventory Control Module

Data Dictionary Development

Screen & Report Design

Logic Diagrams Code Development Module Testing

Work Order Control Module

Development & ImplementationMaintenance Management Information System

Example WBS (Inverted Tree Structure)Example WBS (Inverted Tree Structure)

Example WBS(Indented List Format)

Development & Implementation Maintenance Management Information SystemRequirements DefinitionSystem DesignSystem Development

Equipment History ModuleWork Order Control Module

Data Dictionary DevelopmentScreen & Report DesignLogic DiagramsCode Development

Module TestingSpare Parts Inventory Control Module

System TestingDocumentationImplementation

Identifying Activities

Look for any time-consuming element with identifiable beginning and ending pointsActivities are at the lowest level of the WBSMost activities should produce an identifiable deliverableLong-duration activities (>1 month) should be sub-divided

Guidelines for Developing a WBS

Develop WBS from the top down; not bottom upDon’t exceed about 5 levels in a WBSIdentify work package manager for each WBS itemCheck to make sure that the WBS is consistent with the project charter