ENGINEERING

PROJECT MANAGEMENT

Brig (R) Dr Masood Raza

DEPARTMENT OF ENGINEERING MANAGEMENT
Work Breakdown Structure
(WBS)
Work Breakdown Structure (WBS)
 Work Breakdown Structure (WBS)

• A WBS is a deliverable-oriented grouping of the

work involved in a project that defines the total
scope of the project
• WBS is a foundation document that provides the
basis for planning and managing project
schedules, costs, resources, and changes
 Work Breakdown Structure (WBS)

• Decomposition is subdividing project

deliverables into smaller pieces
– A work package is a task at the lowest level of
the WBS
– Tasks on a WBS represent work that needs to
be done to complete the project, not
specifications (e.g., type of server)
 Work Breakdown Structure (WBS)

• The project scope statement and project management

plan are the primary inputs for creating a WBS
• The outputs include the WBS itself, the WBS
dictionary, a scope baseline and updates to the project
scope statement and scope management plan
• The WBS is often depicted as a task-oriented family
tree of activities
– The WBS can be organized around project products,
project phases or using the project management
process groups
Project: Functions, Activities and Tasks
f1:Function
p:Project
f2:Function

a1:Activity a2:Activity a3:Activity

a2.1:Activity a2.2:Activity a2.3:Activity

t1:Task t2:Task t3:Task t4:Task

 Tasks

• Smallest unit of work subject to management

• Small enough for adequate planning and tracking
• Large enough to avoid micro management
• Finding the appropriate task size is problematic

• Tasks must be decomposed into sizes that allow

monitoring
 Activities

• Major unit of work with precise dates

• Consists of smaller activities or tasks
• Culminates in project milestone
 The Work Package

• It is a bottom-level or “atomic” activity in the

WBS
• Represents a task or group of tasks whose costs
will be tracked and estimated together

Work Package
 Deliverables and Milestones

• Deliverables
– Tangible, verifiable work products
– Reports, presentations, prototypes, etc.
• Milestones
– Significant events or achievements
– Acceptance of deliverables or phase completion
– Cruxes (proof of concepts)
– Quality control
– Keeps team focused
 Approaches to Developing WBS

• Using guidelines: Some organizations provide guidelines

for preparing WBSs
• The analogy approach: Review WBSs of similar projects
and tailor to your project
• The top-down approach: Start with the largest items of
the project and break them down
• The bottom-up approach: Start with the detailed tasks
and roll them up
• Mind-mapping approach: Write down tasks in a non-
linear format and then create the WBS structure
 Why Use a WBS?

To document all work that must be done to

develop and deliver the system in a
satisfactory manner

WBS
 Is This Necessary?

WBS serves to consolidate information from

many sources into one place and into an
organized format.

A “table of contents” for the project.

 “Rolling Up” Costs

$301K

$112K $85K $28K $45K $31K

$22K $13K $15K $38K $24K

 WBS Dictionary

• A supplement to the WBS that provides additional

detail for each WBS activity
• Typical contents for a given activity:
– Inputs, Outputs, Performance Goals & Reviews
– Exit or Completion criteria
– Sub-activities that make up this activity
– Detailed description (if a work package)
• Other contents are derived from the process
 ELEPHANT BREAKDOWN STRUCTURE

Tail Legs Body Head

 Sample Partial WBS

Level 1 SOFTWARE
PROJECT

TRAINING USER SOFTWARE SYSTEM PROJECT

MATERIALS DOCUMENTS SYSTEM ANALYSIS MGT

SYSTEM
MODULE 1 MODULE 2 MODULE 3 Level 3
TEST

CODING TEST
 100 % Rule

The next level decomposition of a

WBS element (child level) must
represent 100% of the work
applicable to the next higher
(parent) element.
 Service Project Breakdown

International
Level 1 Conference
Project

Transport- Project
Attendees Facilities Program Displays
ation Management

Spouse
Level 3 Receptions Presentations Tours
Activities

Level 4 Papers Speakers Translators

 Example of WBS: “Holiday”

holiday

travel
booking household
documents

passport tickets choose confirm

resort cat!

insurance
brochures
WBS
Formats of WBS
 Formats of WBS

• Mind-mapping
• Bubble Format
• Tree Diagram/Org-Chart Format
• Indented Outline Format
• Cycling Format
Sample Mind-Mapping Approach
 Bubble format

• Effective for supporting the brainstorming

process
• Not so good for displaying work breakdown
structures to audiences who are not familiar
with the project.
• Use bubble format to develop the WBS, then
turn it into Org-Chart or outline format.
 Bubble Format
Review
Final Report
Review
Draft Report Prepare
Report

Review Write Print

Draft Report Final Report Final Report
 Org-chart format
– Often good for a “bird view” of the project
(executive summaries,...)

– Less effective for displaying large numbers of

activities
 SAMPLE WBS - GARAGE

Level 1 GARAGE
PROJECT

CONSTR. PROJECT
PERMITS/ GROUNDS GARAGE
INSPECTIONS PLANS MGT

FOUNDATION WALLS ROOF UTILITIES ASSEMBLY

DRY WALL/ DOORS/

FRAME DOORS/ ASSEMBLY Level 4
PANELING WINDOW
WINDOWS
S
 Outline format

Easier to read and understand if WBS

contains many activities
 Intranet WBS in Tabular Form
1.0 Concept
1.1 Evaluate current systems
1.2 Define Requirements
1.2.1 Define user requirements
1.2.2 Define content requirements
1.2.3 Define system requirements
1.2.4 Define server owner requirements
1.3 Define specific functionality
1.4 Define risks and risk management approach
1.5 Develop project plan
1.6 Brief Web development team
2.0 Web Site Design
3.0 Web Site Development
4.0 Roll Out
5.0 Support
 Combined format
• In large projects:
– Use a combination of org-chart and outline
formats:
• Display activities in org-chart format,
• Display sub-activities and tasks in outline
format.
Discussion