WORK BREAKDOWN STRUCTURE

Unit Name /Number

[Title of the Research Project]

Publish Date]
TABLE OF CONTENTS
INTRODUCTION.................................................................................................................................1
OUTLINE VIEW.................................................................................................................................1
HIERARCHICAL STRUCTURE.............................................................................................................3
TABULAR VIEW................................................................................................................................4
TREE STRUCTURE VIEW...................................................................................................................5
WBS DICTIONARY...........................................................................................................................6
GLOSSARY OF TERMS.......................................................................................................................9
 Work Breakdown Structure
[Title of the Research Project]

INTRODUCTION
The Work Breakdown Structure (WBS) is a view into the project. It is a decomposition of all the
work necessary to complete a project. The Project Manager and project team use the WBS to
develop the project schedule, resource requirements and costs. The objective should be to
capture 100% of the work for the project.

The WBS step helps accomplish the following key objectives:

 Develops an objective, rational view of the amount of work required.
 Helps team grasp the skills required and amount of resources required for the project.
 Provides a clear framework for assigning to individuals a clear task definition and
delegate the responsibility for completion.
 Lays a foundation for analyzing the task dependencies and for isolating and managing
risks
 Lays a foundation for developing a bottom-up estimate for the project schedule
 Allows tradeoffs to be made consciously and with the proper consensus involved.
 It helps to easily communicate the work and processes involved to execute the project.

There are many ways to present the WBS for a project and this template provides many of the
most popular layouts from which to choose. Depending on where the WBS is placed in the
project plan, a different layout may be more suitable. For instance, many Project Managers
include a high level WBS within the project plan, and a more detailed version as an appendix to
the plan.

To save space in this template, WBS examples are developed to the third level only. In most
projects, the approach to the WBS use the 8 to 80 rule, which states that the WBS should be
decomposed down to a work package containing between 8 and 80 hours of work to complete.

The Work Breakdown Structure (WBS) presented in this document represents the work required
to complete [Title of the Research Project].

OUTLINE VIEW
The outline view presents an easy to view and understand layout for the WBS. It is also a good
layout to use when developing the WBS because changes can easily be made, especially since
the Microsoft Word auto numbering feature updates the WBS Code automatically.

1. Widget Management System

1.1 Initiation
1.1.1 Evaluation & Recommendations
1.1.2 Develop Project Charter
1.1.3 Deliverable: Submit Project Charter
1.1.4 Project Sponsor Reviews Project Charter
 Work Breakdown Structure
[Title of the Research Project]

1.1.5 Project Charter Signed/Approved

1.2 Planning
1.2.1 Create Preliminary Scope Statement
1.2.2 Determine Project Team
1.2.3 Project Team Kickoff Meeting
1.2.4 Develop Project Plan
1.2.5 Submit Project Plan
1.2.6 Milestone: Project Plan Approval
1.3 Execution
1.3.1 Project Kickoff Meeting
1.3.2 Verify & Validate User Requirements
1.3.3 Design System
1.3.4 Procure Hardware/Software
1.3.5 Install Development System
1.3.6 Testing Phase
1.3.7 Install Live System
1.3.8 User Training
1.3.9 Go Live
1.4 Control
1.4.1 Project Management
1.4.2 Project Status Meetings
1.4.3 Risk Management
1.4.4 Update Project Management Plan
1.5 Closeout
1.5.1 Audit Procurement
1.5.2 Document Lessons Learned
1.5.3 Update Files/Records
1.5.4 Gain Formal Acceptance
1.5.5 Archive Files/Documents
 Work Breakdown Structure
[Title of the Research Project]

HIERARCHICAL STRUCTURE
The hierarchal structure is similar to the outline view but without indentation. Although this
format is more difficult to read, it may be useful where there are many levels. Indenting each
level may potentially cause the table to be too sizable to fit into a document.

Level WBS Code Element Name

1 1 Widget Management System
2 1.1 Initiation
3 1.1.1 Evaluation & Recommendations
3 1.1.2 Develop Project Charter
3 1.1.3 Deliverable: Submit Project Charter
3 1.1.4 Project Sponsor Reviews Project Charter
3 1.1.5 Project Charter Signed/Approved
2 1.2 Planning
3 1.2.1 Create Preliminary Scope Statement
3 1.2.2 Determine Project Team
3 1.2.3 Project Team Kickoff Meeting
3 1.2.4 Develop Project Plan
3 1.2.5 Submit Project Plan
3 1.2.6 Milestone: Project Plan Approval
2 1.3 Execution
3 1.3.1 Project Kickoff Meeting
3 1.3.2 Verify & Validate User Requirements
3 1.3.3 Design System
3 1.3.4 Procure Hardware/Software
3 1.3.5 Install Development System
3 1.3.6 Testing Phase
3 1.3.7 Install Live System
3 1.3.8 User Training
3 1.3.9 Go Live
2 1.4 Control
3 1.4.1 Project Management
3 1.4.2 Project Status Meetings
3 1.4.3 Risk Management
3 1.4.4 Update Project Management Plan
2 1.5 Closeout
3 1.5.1 Audit Procurement
3 1.5.2 Document Lessons Learned
3 1.5.3 Update Files/Records
3 1.5.4 Gain Formal Acceptance
3 1.5.5 Archive Files/Documents
 Work Breakdown Structure
[Title of the Research Project]

TABULAR VIEW
The Tabular View is a nicely organized table view of the WBS. It is a good option for
organizations that prefer table formats.

Level 1 Level 2 Level 3

1 Widget 1.1 Initiation 1.1.1 Evaluation & Recommendations
Management 1.1.2 Develop Project Charter
System 1.1.3 Deliverable: Submit Project Charter
1.1.4 Project Sponsor Reviews Project Charter
1.1.5 Project Charter Signed/Approved
1.2 Planning 1.2.1 Create Preliminary Scope Statement
1.2.2 Determine Project Team
1.2.3 Project Team Kickoff Meeting
1.2.4 Develop Project Plan
1.2.5 Submit Project Plan
1.2.6 Milestone: Project Plan Approval
1.3 Execution 1.3.1 Project Kickoff Meeting
1.3.2 Verify & Validate User Requirements
1.3.3 Design System
1.3.4 Procure Hardware/Software
1.3.5 Install Development System
1.3.6 Testing Phase
1.3.7 Install Live System
1.3.8 User Training
1.3.9 Go Live
1.4 Control 1.4.1 Project Management
1.4.2 Project Status Meetings
1.4.3 Risk Management
1.4.4 Update Project Management Plan
1.5 Closeout 1.5.1 Audit Procurement
1.5.2 Document Lessons Learned
1.5.3 Update Files/Records
1.5.4 Gain Formal Acceptance
1.5.5 Archive Files/Documents
 Work Breakdown Structure
[Title of the Research Project]

TREE STRUCTURE VIEW

The Tree Structure View is the most popular format for the WBS. It presents an easy to
understand view into the WBS; however, it is problematic to create without access to an
application specifically designed for creating this organizational chart structure. The Tree
Structure below was created using only Microsoft Word and the SmartArt graphics option under
the insert menu.

Widget Mgmt. System

1

Initiation Planning Execution Control Closeout

1.1 1.2 1.3 1.4 1.5

Evaluation & Create Preliminary

Project Kickoff Meeting Project Management Audit Procurement
Recommendations Scope Statement
1.3.1 1.4.1 1.5.1
1.1.1 1.2.1

Determine Project Verify & Validate User Document Lessons

Develop Project Charter Project Status Meetings
Team Requirements Learned
1.1.2 1.4.2
1.2.2 1.3.2 1.5.2

Deliverable: Submit Project Team Kickoff

Design System Risk Management Update Files/ Records
Project Charter Meeting
1.3.3 1.4.3 1.5.3
1.1.3 1.2.3

Project Sponsor Procure Update Project Gain Formal

Develop Project Plan
Reviews Project Charter Hardware/Software Management Plan Acceptance
1.2.4
1.1.4 1.3.4 1.4.4 1.5.4

Project Charter Install Development Archive Files/

Submit Project Plan
Signed/Approved System Documents
1.2.5
1.1.5 1.3.5 1.5.5

Milestone: Project Plan

Testing Phase
Approved
1.3.6
1.2.6

Install Live System

1.3.7

User Training
1.3.8

Go Live
1.3.9