Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd
Upload
1K views

Work Breakdown Structure

The document discusses a Work Breakdown Structure (WBS), which is a hierarchical breakdown of the components and subcomponents of a project. A WBS breaks down the total scope of a project into smaller, more manageable elements. It defines the work to be done and is used for planning, estimating costs and schedules, assigning responsibilities, monitoring progress, and controlling changes. The document provides examples of how a WBS can be visually represented and outlines the benefits of using a WBS for project management.

Uploaded by

Kamal Shah
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
1K views

Work Breakdown Structure

The document discusses a Work Breakdown Structure (WBS), which is a hierarchical breakdown of the components and subcomponents of a project. A WBS breaks down the total scope of a project into smaller, more manageable elements. It defines the work to be done and is used for planning, estimating costs and schedules, assigning responsibilities, monitoring progress, and controlling changes. The document provides examples of how a WBS can be visually represented and outlines the benefits of using a WBS for project management.

Uploaded by

Kamal Shah
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 11

R K N

O
W DOW
A K R E
R E T U
B U C
ST R
1
What is a Work Breakdown
Structure (WBS)?
• WBS is a hierarchical listing of the
subcomponents of a project.

• The WBS is an essential tool in the


project planning process

• The WBS is a logical hierarchy that


organizes and breaks down the work that
needs to be accomplished on a project
2
WBS Definition

A deliverable-oriented grouping of project elements


that organizes and defines the total scope of the
project work.

Work not in the WBS is not in scope of the project.

Each descending level represents an increasingly


detailed description of the project elements.

Often used to develop or confirm a common


understanding of project scope.

3
Importance of WBS
•It defines and breaks down the work on a
project into manageable chunks, often called
work packages
•It tells us what activities or tasks have to be
done in order to complete the project
•It serves as the foundation for the
development of schedules, budgets, and
resource requirements
•It serves as a useful tool for identification of
activities and assignment of responsibilities
4
WBS Role
It is the basis for
 Estimating

 Budgeting

 Pricing

 Controlling Costs
 Assigning Responsibility

 Scheduling

 Allocating Resources

 Reporting, Monitoring, and Controlling

5
Basic guidelines
• Work described in a higher level must be the sum of
all the work in the next lower level
• Definitions of work should be usable as
communications tools so results can be compared with
expectations for the work when the project is
implemented
• Work that will be performed by different people
should be clearly differentiated
• WBS should define measurable deliverables for each
work component of the project
• WBS should be flexible enough to allow for changes
6
The most common Work Breakdown
Structure is the six-level indented
structure shown in the figure below.
Level Description

Managerial 1 Total Program


Levels 2 Project
3 Task

4 Subtask
Technical 5 Work Package
Levels 6 Level of Effort

7
What does a WBS look like?
HierarchyExample-W
Diagram BS/How
Format ?
1 MANAGEMENT

Table of Contents Format


1.1 Initiate
1.2 Plan
Project 1.3 Execute
1.4 Control
1.5 Close
Manage Rqmts Design Build Deliver 2 REQUIREMENTS
Construct 2.1 Assess
Plan Assess Engineer Install 2.2 Determine
Execute Determine Specify Test Train 2.3 Analyze
Control Analyze • Validate • 2.4 Propose
Close Propose • Integrate • 2.5 …..
• • • • • 3 DESIGN
• • • 3.1 Engineer
• 3.2 Specify
1. Write First draft of policy. 3.3 ….
List Format

2. Review with team/manager. 3.4 …..


3. Make changes as needed. 4 BUILD
4. File notice w/Secretary of the State 4.1 Construct
(SOS) 45 days before effective date. 4.2 Test
5. Formally review policy analysts and 4.3 Validate
advocates. 4.4 Integrate
6. Make changes as needed. 5 DELIVER
7. Update program manuals and forms 5.1 Install
to reflect changes. 5.2 Train
5.3 …..
8. Submitted to the SOS by 5:00pm the
5.4 …..
day before it is to be effective. 8
9
Benefits of the WBS

Risk and
Contingency
Plans
Estimates
Schedule

WBS
Risk Control

Project
Control Change
Control

Activity List
Communication
Control

Progress
Project Plan Reports 10
THANK YOU…..!!
11

You might also like