WORK BREAKDOWN STRUCTURE (WBS) TEMPLATE

This Project WBS Template is free for you to copy and use on your project
and within your organization. We hope that you find this template useful and
welcome your comments. Public distribution of this document is only permitted
from the Project Management Docs official website at
www. P roject M anagement D ocs.com
WORK BREAKDOWN STRUCTURE
(WBS)
<PROJECT NAME>
COMPANY NAME
STREET ADDRESS
CITY, STATE ZIP CODE
DATE
Work Breako!" S#r$%#$re (WBS) Te&'(a#e
!!!)Pro*e%#Ma"a+e&e"#Do%,)%o&
INTRODUCTION
The WBS is a !iew into the project which shows what wor" the project encompasses. #t is a tool
which helps to easily communicate the wor" and processes in!ol!ed to e$ecute the project. The
Project Manager and project team use the WBS to de!elop the project schedule% resource
re&uirements and costs. There are many ways you can present the WBS for your project' this
template pro!ides many of the most popular layouts from which you can choose. Depending on
where in the Project Plan you(re putting the WBS a different layout may be more suitable for
you. )or instance many Project Managers include a high le!el WBS within the project plan% then
a detailed !ersion as an appendi$ to the plan. *ou may find that you prefer one layout for a high
le!el WBS and a different one for a detailed WBS.
#n order to sa!e space in this template we only de!eloped the WBS e$amples down to the third
le!el. #n your project you will want to de!elop them down to a much more detailed le!el using
the + to +, rule -where the WBS is bro"en down to where a wor" pac"age contains between +
and +, hours of wor" to complete..
The Wor" Brea"down Structure presented here represents all the wor" re&uired to complete this
project.
OUTLINE -IEW
The outline !iew presents an easy to !iew and understand layout for the WBS. #t is also a good
layout to use when de!eloping the WBS because you can easily ma"e changes% especially since
the Microsoft Word auto numbering feature updates the WBS /ode automatically.
0. Widget Management System
0.0 #nitiation
0.0.01!aluation 2 3ecommendations
0.0.4De!elop Project /harter
0.0.5Deliverable: Submit Project /harter
0.0.6Project Sponsor 3e!iews Project /harter
0.0.7Project /harter Signed89ppro!ed
0.4 Planning
0.4.0/reate Preliminary Scope Statement
0.4.4Determine Project Team
0.4.5Project Team :ic"off Meeting
0.4.6De!elop Project Plan
0.4.7Submit Project Plan
0.4.;Milestone: Project Plan 9ppro!al
0.5 1$ecution
0.5.0Project :ic"off Meeting
0.5.4<erify 2 <alidate =ser 3e&uirements
0.5.5Design System
0.5.6Procure >ardware8Software
0.5.7#nstall De!elopment System
0
Work Breako!" S#r$%#$re (WBS) Te&'(a#e
!!!)Pro*e%#Ma"a+e&e"#Do%,)%o&
0.5.;Testing Phase
0.5.?#nstall @i!e System
0.5.+=ser Training
0.5.ABo @i!e
0.6 /ontrol
0.6.0Project Management
0.6.4Project Status Meetings
0.6.53is" Management
0.6.6=pdate Project Management Plan
0.7 /loseout
0.7.09udit Procurement
0.7.4Document @essons @earned
0.7.5=pdate )iles83ecords
0.7.6Bain )ormal 9cceptance
0.7.79rchi!e )iles8Documents
.IERARC.ICAL STRUCTURE
The hierarchal structure is similar to the outline !iew but without indentation. 9lthough this
format is more difficult to read% it may be useful where you ha!e many le!els and indenting each
le!el would ma"e the table to large to fit into a document.
4
Work Breako!" S#r$%#$re (WBS) Te&'(a#e
!!!)Pro*e%#Ma"a+e&e"#Do%,)%o&
@e!el WBS /ode 1lement Came
0 0 Widget Management System
4 0.0 #nitiation
5 0.0.0 1!aluation 2 3ecommendations
5 0.0.4 De!elop Project /harter
5 0.0.5 Deli!erable Submit Project /harter
5 0.0.6 Project Sponsor 3e!iews Project /harter
5 0.0.7 Project /harter Signed89ppro!ed
4 0.4 Planning
5 0.4.0 /reate Preliminary Scope Statement
5 0.4.4 Determine Project Team
5 0.4.5 Project Team :ic"off Meeting
5 0.4.6 De!elop Project Plan
5 0.4.7 Submit Project Plan
5 0.4.; Milestone Project Plan 9ppro!al
4 0.5 1$ecution
5 0.5.0 Project :ic"off Meeting
5 0.5.4 <erify 2 <alidate =ser 3e&uirements
5 0.5.5 Design System
5 0.5.6 Procure >ardware8Software
5 0.5.7 #nstall De!elopment System
5 0.5.; Testing Phase
5 0.5.? #nstall @i!e System
5 0.5.+ =ser Training
5 0.5.A Bo @i!e
4 0.6 /ontrol
5 0.6.0 Project Management
5 0.6.4 Project Status Meetings
5 0.6.5 3is" Management
5 0.6.6 =pdate Project Management Plan
4 0.7 /loseout
5 0.7.0 9udit Procurement
5 0.7.4 Document @essons @earned
5 0.7.5 =pdate )iles83ecords
5 0.7.6 Bain )ormal 9cceptance
5 0.7.7 9rchi!e )iles8Documents
TABULAR -IEW
The Tabular <iew is a nicely organized table !iew of the WBS. #t is a good option for
organizations which prefer table formats.
5
Work Breako!" S#r$%#$re (WBS) Te&'(a#e
!!!)Pro*e%#Ma"a+e&e"#Do%,)%o&
Level 1 Level 2 Level 3
0 Widget
Management
System
0.0 #nitiation 0.0.0 1!aluation 2 3ecommendations
0.0.4 De!elop Project /harter
0.0.5 Deli!erable Submit Project /harter
0.0.6 Project Sponsor 3e!iews Project /harter
0.0.7 Project /harter Signed89ppro!ed
0.4 Planning 0.4.0 /reate Preliminary Scope Statement
0.4.4 Determine Project Team
0.4.5 Project Team :ic"off Meeting
0.4.6 De!elop Project Plan
0.4.7 Submit Project Plan
0.4.; Milestone Project Plan 9ppro!al
0.5 1$ecution 0.5.0 Project :ic"off Meeting
0.5.4 <erify 2 <alidate =ser 3e&uirements
0.5.5 Design System
0.5.6 Procure >ardware8Software
0.5.7 #nstall De!elopment System
0.5.; Testing Phase
0.5.? #nstall @i!e System
0.5.+ =ser Training
0.5.A Bo @i!e
0.6 /ontrol 0.6.0 Project Management
0.6.4 Project Status Meetings
0.6.5 3is" Management
0.6.6 =pdate Project Management Plan
0.7 /loseout 0.7.0 9udit Procurement
0.7.4 Document @essons @earned
0.7.5 =pdate )iles83ecords
0.7.6 Bain )ormal 9cceptance
0.7.7 9rchi!e )iles8Documents
TREE STRUCTURE -IEW
The Tree Structure <iew is the most popular format for the WBS. #t presents an easy to
understand !iew into the WBS' howe!er% it is also tric"y to create without an application
specifically designed for creating this organizational chart structure. The Tree Structure below
was created using only Microsoft Word and the Smart9rt graphics option under the insert menu.
6
Work Breako!" S#r$%#$re (WBS) Te&'(a#e
!!!)Pro*e%#Ma"a+e&e"#Do%,)%o&
Widget Mgmt.
System
0
#nitiation
0.0
Planning
0.4
1$ecution
0.5
/ontrol
0.6
/reate Preliminary
Scope Statement
0.4.0
/loseout
0.7
1!aluation 2
3ecommendations
0.0.0
De!elop Project
/harter
0.0.4
Deli!erable
Submit Project
/harter
0.0.5
Project Sponsor
3e!iews Project
/harter
0.0.6
Project /harter
Signed89ppro!ed
0.0.7
Determine Project
Team
0.4.4
Project Team
:ic"off Meeting
0.4.5
De!elop Project
Plan
0.4.6
Submit Project Plan
0.4.7
Milestone Project
Plan 9ppro!ed
0.4.;
Project :ic"off
Meeting
0.5.0
<erify 2 <alidate
=ser 3e&uirements
0.5.4
Design System
0.5.5
Procure
>ardware8Software
0.5.6
#nstall
De!elopment
System
0.5.7
Testing Phase
0.5.;
#nstall @i!e System
0.5.?
=ser Training
0.5.+
Bo @i!e
0.5.A
Project
Management
0.6.0
Project Status
Meetings
0.6.4
3is" Management
0.6.5
=pdate Project
Management Plan
0.6.6
9udit Procurement
0.7.0
Document @essons
@earned
0.7.4
=pdate )iles8
3ecords
0.7.5
Bain )ormal
9cceptance
0.7.6
9rchi!e )iles8
Documents
0.7.7
7
Work Breako!" S#r$%#$re (WBS) Te&'(a#e
!!!)Pro*e%#Ma"a+e&e"#Do%,)%o&
WBS DICTIONARY
The WBS Dictionary contains all the details of the WBS which are necessary to successfully
complete the project. Most importantly it contains a definition of each Wor" Pac"age which can
be thought of as a mini scope statement. 3esources on the project will loo" at the WBS
dictionary to determine the scope of the Wor" Pac"age they(!e been assigned% so it(s important to
be clear when writing the definition. Most WBS dictionaries contain more information than we
show in our sample. These things usually include @e!el of 1ffort% /ost /ontrol Cumbers%
3esource 9ssignments% 3esponsibility 9ssignments D just to name a few.
@e!el WBS
/ode
1lement Came Definition
0 0 Widget Management System 9ll wor" to implement a new widget
management system.
4 0.0 #nitiation The wor" to initiate the project.
5 0.0.0 1!aluation 2 3ecommendations Wor"ing group to e!aluate solution sets
and ma"e recommendations.
5 0.0.4 De!elop Project /harter Project Manager to de!elop the Project
/harter.
5 0.0.5 Deli!erable Submit Project
/harter
Project /harter is deli!ered to the
Project Sponsor.
5 0.0.6 Project Sponsor 3e!iews Project
/harter
Project sponsor re!iews the Project
/harter.
5 0.0.7 Project /harter Signed89ppro!ed The Project Sponsor signs the Project
/harter which authorizes the Project
Manager to mo!e to the Planning
Process.
4 0.4
Planning
The wor" for the planning process for
the project.
5 0.4.0 /reate Preliminary Scope
Statement
Project Manager creates a Preliminary
Scope Statement.
5 0.4.4
Determine Project Team
The Project Manager determines the
project team and re&uests the resources.
5 0.4.5
Project Team :ic"off Meeting
The planning process is officially started
with a project "ic"off meeting which
includes the Project Manager% Project
Team and Project Sponsor -optional..
5 0.4.6
De!elop Project Plan
=nder the direction of the Project
Manager the team de!elops the project
plan.
5 0.4.7
Submit Project Plan
Project Manager submits the project
plan for appro!al.
5 0.4.;
Milestone Project Plan 9ppro!al
The project plan is appro!ed and the
Project Manager has permission to
proceed to e$ecute the project according
to the project plan.
;
Work Breako!" S#r$%#$re (WBS) Te&'(a#e
!!!)Pro*e%#Ma"a+e&e"#Do%,)%o&
@e!el WBS
/ode
1lement Came Definition
4 0.5 1$ecution Wor" in!ol!ed to e$ecute the project.
5 0.5.0
Project :ic"off Meeting
Project Manager conducts a formal "ic"
off meeting with the project team%
project sta"eholders and project
sponsor.
5 0.5.4
<erify 2 <alidate =ser
3e&uirements
The original user re&uirements is
re!iewed by the project manager and
team% then !alidated with the
users8sta"eholders. This is where
additional clarification may be needed.
5 0.5.5
Design System
The technical resources design the new
widget management system.
5 0.5.6
Procure >ardware8Software
The procurement of all hardware%
software and facility needs for the
project.
5 0.5.7
#nstall De!elopment System
Team installs a de!elopment system for
testing and customizations of user
interfaces.
5 0.5.;
Testing Phase
The system is tested with a select set of
users.
5 0.5.?
#nstall @i!e System
The actual system is installed and
configured.
5 0.5.+
=ser Training
9ll users are pro!ided with a four hours
training class. 9dditionally% managers
are pro!ided with an additional two
hours class to co!er ad!anced reporting.
5 0.5.A Bo @i!e System goes li!e with all users.
4 0.6
/ontrol
The wor" in!ol!ed for the control
process of the project.
5 0.6.0
Project Management
E!erall project management for the
project.
5 0.6.4 Project Status Meetings Wee"ly team status meetings.
5 0.6.5
3is" Management
3is" management efforts as defined in
the 3is" Management Plan.
5 0.6.6
=pdate Project Management Plan
Project Manager updates the Project
Management Plan as the project
progresses.
4 0.7 /loseout The wor" to closeDout the project.
5 0.7.0
9udit Procurement
9n audit of all hardware and software
procured for the project% ensures that all
procured products are accounted for and
in the asset management system.
?
Work Breako!" S#r$%#$re (WBS) Te&'(a#e
!!!)Pro*e%#Ma"a+e&e"#Do%,)%o&
@e!el WBS
/ode
1lement Came Definition
5 0.7.4
Document @essons @earned
Project Manager along with the project
team performs a lessons learned
meeting and documents the lessons
learned for the project.
5 0.7.5
=pdate )iles83ecords
9ll files and records are updated to
reflect the widget management system.
5 0.7.6
Bain )ormal 9cceptance
The Project Sponsor formally accepts
the project by signing the acceptance
document included in the project plan.
5 0.7.7
9rchi!e )iles8Documents
9ll project related files and documents
are formally archi!ed.
/LOSSARY O0 TERMS
#t(s important that you pro!ide a glossary of terms as some of the terms are not understood by
persons without a project management bac"ground. )or instance what the PM# Practice
Standard for Work Breakdown Structures refers to as the WBS /ode is commonly referred to as
the WBS number.
@e!el of 1ffort @e!el of 1ffort -@E1. is how much wor" is re&uired to complete a tas".
WBS /ode 9 uni&ue identifier assigned to each element in a Wor" Brea"down Structure
for the purpose of designating the elements hierarchical location within the
WBS.
Wor" Pac"age 9 Wor" Pac"age is a deli!erable or wor" component at the lowest le!el of
its WBS branch.
WBS /omponent 9 component of a WBS which is located at any le!el. #t can be a Wor"
Pac"age or a WBS 1lement as there(s no restriction on what a WBS
/omponent is.
WBS 1lement 9 WBS 1lement is a single WBS component and its associated attributes
located anywhere within a WBS. 9 WBS 1lement can contain wor"% or it
can contain other WBS 1lements or Wor" Pac"ages.
This free WBS Template is brought to you by www.ProjectManagementDocs.com
+