What is a Work Breakdown Structure?

Kenny Hirschmann
Kenny HirschmannSenior Learning Designer um Columbia University
Managing a project can be daunting.
With so many variables,
it's easy to get
overwhelmed.
Where do I begin?
When building a hou se
you start with the foundation.
What is a Work Breakdown Structure?
A Work Breakdown Structure (WBS)
is the foundation
of a project plan. 
                        1


         1.1            1.2                1.3


            1.1.1             1.2.1              1.3.1


                                 1.2.1.1
            1.1.2                                1.3.2

                              1.2.2
Work Breakdown Structure (WBS)




As defined by the Guide to the Project Management Body of Knowledge
What benefits does it provide?
What is a Work Breakdown Structure?
2. Facilitates delegation by creating…




                          …small chunks of work.	
  
3. Simplifies cost estimation, scheduling and risk analysis.
How do I get started?
you need to gather all relevant information.  
First	
     This includes a statement of work, task
            analysis, schedule of deliverables,
milestones, project scope statement, problem analysis,
design documentation or other relevant
documentation.
Welcome to Practicum University




We will take you through the process of
developing a Work Breakdown Structure for a
new program in Dog Whispering that we are
creating this year.
 The team at PU has gathered all of their
documentation and the leadership team is
now ready to start working on a plan to
develop the program.
There are many tools you can use to create the WBS like
mind-mapping tools, Powerpoint or Word. We will use the
industry standard diagramming software, Microsoft Visio
with the WBS Modeler Add-in.
Start with the first level that represents the whole project.  
This should be numbered 1.0.
The second level will vary depending on whether the WBS is
Product-based or  Process-based.
A Product-based WBS is broken down into a series of deliverables
in the second level.  These deliverables should capture 100% of
the project scope.
A Process-based WBS is broken down into a series of phases in
the second level.  Each phase may or may not have a deliverable,
but all major project phases should be included.
An example of a process-based WBS might be to use the stages
of ADDIE as the 5 major phases of the second level.
For the purposes of our example we will use a product-based
WBS.  Development of the new program can be broken down into
these stages: Needs Analysis, Curriculum Proposal, Course
Development Plan, Accreditation Package, Implementation, and
Evaluation Plan.
At this point we enter a stage of the process
called decomposition to further break the work
down in to smaller and more manageable
chunks of work, called Work Packages.
What is a Work Breakdown Structure?
A general rule that you might want to use is
called the 8/80 rule.  No work package should
be less than 8 hours of work, or more than 80
hours of work.
The process of decomposition can be done by an individual, or by
the whole team.  It all depends on what makes sense for your
project. Still, two minds are usually better than one!
But you don't necessarily need to reinvent the wheel!
If you've already completed a similar project, you may already
have a template you can follow for decomposition.  Perhaps PU
has already followed this process for other programs.
It is critical that you and your team try to account for every task
that is necessary to complete the project.  Mistakes here will only
cost the project more time and perhaps more money later.
Once	
  the	
  WBS	
  has	
  been	
  completed	
  it	
  might	
  be	
  necessary	
  to	
  build	
  a	
  
WBS	
  Dic:onary.	
  	
  The	
  WBS	
  Dic:onary	
  is	
  a	
  document	
  that	
  describes	
  
each	
  work	
  package	
  in	
  detail.
Here is the completed WBS for PU's Dog Whispering program.
Now that you've broken the project down into manageable
chunks of work, you can more easily estimate time, cost and
staffing for the project. By estimating the amount of time each
work package "should" take, as well as the role assigned to that
task, you can estimate the cost of that task.
You can develop a table that shows each of these fields in
sequence, but there's another way to visualize this information.
The Gantt Chart.
The power of the Gantt Chart is that it is a simple and clear way
to not only show the length of time of each task, but also
visualize task dependencies.
A	
  Task	
  Dependency	
  is	
  
the	
  rela:onship	
  in	
  
which	
  a	
  task	
  relies	
  on	
     Task	
  #1	
  
the	
  comple:on	
  (or	
  
par:al	
  comple:on)	
  of	
  
another	
  task	
  or	
  tasks	
  
before	
  it	
  can	
  begin.
                                         Task	
  #2	
  




                                         Task	
  #3	
  
Task dependencies
determine the total
length of time for each
stage in the project,
                             Task	
  #1	
  
and thus the overall
timeline of the project.  
Therefore, the Gantt
Chart is a tool that
can help us determine
                             Task	
  #2	
  
the overall timeline for
a project.



                             Task	
  #3	
  
There are many
different programs that
can help you create a
Gantt Chart including
one of the most widely
used tools for project
planning and
management,
Microsoft Project.
Here is a Gantt Chart produced in Microsoft Project for the Dog
Whisperer program at PU.
What is a Work Breakdown Structure?
To	
  build	
  a	
  project	
  you	
  must	
  start	
  with	
  the	
  founda:on.
1


         1.1                 1.2                1.3


            1.1.1                  1.2.1              1.3.1


                                      1.2.1.1
            1.1.2                                     1.3.2

                                   1.2.2



The foundation of a project is the Work Breakdown Structure.
The Work Breakdown Structure will help you to define the
project's scope, estimate time, cost and staffing, make
delegation of tasks simpler and identify risks.
The	
  process	
  starts	
  by	
  gathering	
  all	
  the	
  necessary	
  informa:on	
  and	
  
your	
  key	
  team	
  members.	
  	
  The	
  more	
  heads,	
  the	
  beHer!
The first two levels of a WBS must encompass 100% of the
project process.
Use the process of decomposition to break the project down to
manageable chunks using the 8/80 rule.
Clarify each work package by creating a WBS Dictionary.
Organize	
  the	
  tasks	
  into	
  a	
  GanH	
  Chart	
  to	
  highlight	
  dependencies	
  and	
  
determine	
  the	
  overall	
  :meline.
What is a Work Breakdown Structure?
Slide	
  2	
  -­‐	
  Scream	
  by	
  Edvard	
  Munch.	
  	
  Retrieved	
  from:	
  hHp://1.bp.blog	
  
spot.com/-­‐JFyqLFg67hU/TaxbHC02ngI/AAAAAAAAADs/	
  
0mIK8c8NJm0/s1600/thescream.jpg	
  

Slide	
  4	
  -­‐	
  Retrieved	
  from:	
  hHp://www.flickr.com/photos	
  
/pgoyeHe/2280685630/	
  

Slide	
  12	
  -­‐	
  Retrieved	
  from:	
  hHp://office.microsof.com/en-­‐us/images/	
  
results.aspx?ex=2&qu=start#ai:MP900422560%7Cmt:0%7C	
  
Slide	
  27	
  -­‐	
  Retrieved	
  from:	
  hHp://i.images.cdn.fotopedia.com/	
  
flickr-­‐3784879602-­‐hd/Tokyo_and_Vicinity/Further_Afield/Edogawa-­‐ku/	
  
Kasai_Rinkai_Park/Diamond_and_Flower_Ferris_Wheel/Ferris_wheel_	
  
and_sunset_croulds_at_Kasai_Rinkai_Park.jpg	
  

Slide	
  32	
  –	
  Hourglass	
  Retrieved	
  from:	
  hHp://images.wikia.com/witcher/	
  
images/3/3a/Hourglass_2.png	
  
Dollar	
  -­‐	
  hHp://www.sparkthemagazine.com/wp-­‐content/uploads/2011/	
  
09/dollar-­‐sign.png	
  
1 von 49

Más contenido relacionado

Was ist angesagt?(20)

Project planning and scheduling techniquesProject planning and scheduling techniques
Project planning and scheduling techniques
Shivangi Saini15.5K views
How to create a work breakdown structure (wbs)How to create a work breakdown structure (wbs)
How to create a work breakdown structure (wbs)
Insaf Ali Soomro PMP252 views
Project planning and project work planProject planning and project work plan
Project planning and project work plan
Ferdinand Importado, CPA, MBA154.8K views
Project planning and planning processProject planning and planning process
Project planning and planning process
Shamim Hossain1.1K views
Earned Value Analysis - EVAEarned Value Analysis - EVA
Earned Value Analysis - EVA
Ahmed Bamasdoos15.6K views
Earned value managementEarned value management
Earned value management
Ashif AR1.5K views
 construction project planing construction project planing
construction project planing
SANJEEV Wazir1.4K views
Ignore Project Scope & WBS At Your Own PerilIgnore Project Scope & WBS At Your Own Peril
Ignore Project Scope & WBS At Your Own Peril
Praveen Malik, PMP2.1K views
 project time management project time management
project time management
Hira Atiq758 views
134 work break break down structure134 work break break down structure
134 work break break down structure
Dr Fereidoun Dejahang2.4K views
Work Breakdown Structures (WBS)Work Breakdown Structures (WBS)
Work Breakdown Structures (WBS)
stakeholdermap2.2K views
Project management planningProject management planning
Project management planning
Alvin Niere11.3K views
Work Breakdown StructureWork Breakdown Structure
Work Breakdown Structure
project management38.2K views
Project schedulingProject scheduling
Project scheduling
Carla Fair-Wright12.9K views
Project cost & controlProject cost & control
Project cost & control
AMARAYYA9.3K views
Earned value analysis (1)Earned value analysis (1)
Earned value analysis (1)
Harshit Mahajan426 views
Project organisation structureProject organisation structure
Project organisation structure
sachin kumar sharma22.5K views

Similar a What is a Work Breakdown Structure?(20)

BhadaniS Microsoft Project Manual TrainingBhadaniS Microsoft Project Manual Training
BhadaniS Microsoft Project Manual Training
BHADANI QUANTITY SURVEYING TRAINING INSTITUTE FOR CIVIL MECHANICAL AND ELECTRICAL ENGINEERS61 views
SEN-22413 -  UNIT - V.pptxSEN-22413 -  UNIT - V.pptx
SEN-22413 - UNIT - V.pptx
FreefireGarena2213 views
Communication 1Communication 1
Communication 1
Ujjwal Joshi1.8K views
Managing Small Projects   IntroductionManaging Small Projects   Introduction
Managing Small Projects Introduction
Peter Tanswell MCom, MSc, PhD2.8K views
Project Implementation.pdfProject Implementation.pdf
Project Implementation.pdf
ssuserc0e4e027 views
MS Project PresentationMS Project Presentation
MS Project Presentation
Khem Singh33.3K views
Pm592 Quiz1Pm592 Quiz1
Pm592 Quiz1
Maritza Peterson2 views
ms-project-presentation.pptxms-project-presentation.pptx
ms-project-presentation.pptx
SunilHotkar24 views
Ms project presentationMs project presentation
Ms project presentation
Khem Singh1.1K views
Lab exercise 6Lab exercise 6
Lab exercise 6
Cesar Castro4.3K views
44259126 ms-project-presentation44259126 ms-project-presentation
44259126 ms-project-presentation
Farrukh Raja2.4K views
Work Break Down StructureWork Break Down Structure
Work Break Down Structure
Somtel748 views
Wbs & Project SchedulingWbs & Project Scheduling
Wbs & Project Scheduling
sslovepk14K views
Pm chapter 5Pm chapter 5
Pm chapter 5
Golam Bitonsir67 views

Último(20)

ChatGPT and AI for Web DevelopersChatGPT and AI for Web Developers
ChatGPT and AI for Web Developers
Maximiliano Firtman161 views
ThroughputThroughput
Throughput
Moisés Armani Ramírez31 views
Web Dev - 1 PPT.pdfWeb Dev - 1 PPT.pdf
Web Dev - 1 PPT.pdf
gdsczhcet49 views

What is a Work Breakdown Structure?

  • 1. Managing a project can be daunting.
  • 2. With so many variables, it's easy to get overwhelmed.
  • 3. Where do I begin?
  • 4. When building a hou se you start with the foundation.
  • 6. A Work Breakdown Structure (WBS) is the foundation of a project plan.  1 1.1 1.2 1.3 1.1.1 1.2.1 1.3.1 1.2.1.1 1.1.2 1.3.2 1.2.2
  • 7. Work Breakdown Structure (WBS) As defined by the Guide to the Project Management Body of Knowledge
  • 8. What benefits does it provide?
  • 10. 2. Facilitates delegation by creating… …small chunks of work.  
  • 11. 3. Simplifies cost estimation, scheduling and risk analysis.
  • 12. How do I get started?
  • 13. you need to gather all relevant information.   First   This includes a statement of work, task analysis, schedule of deliverables, milestones, project scope statement, problem analysis, design documentation or other relevant documentation.
  • 14. Welcome to Practicum University We will take you through the process of developing a Work Breakdown Structure for a new program in Dog Whispering that we are creating this year.
  • 15.  The team at PU has gathered all of their documentation and the leadership team is now ready to start working on a plan to develop the program.
  • 16. There are many tools you can use to create the WBS like mind-mapping tools, Powerpoint or Word. We will use the industry standard diagramming software, Microsoft Visio with the WBS Modeler Add-in.
  • 17. Start with the first level that represents the whole project.   This should be numbered 1.0.
  • 18. The second level will vary depending on whether the WBS is Product-based or  Process-based.
  • 19. A Product-based WBS is broken down into a series of deliverables in the second level.  These deliverables should capture 100% of the project scope.
  • 20. A Process-based WBS is broken down into a series of phases in the second level.  Each phase may or may not have a deliverable, but all major project phases should be included.
  • 21. An example of a process-based WBS might be to use the stages of ADDIE as the 5 major phases of the second level.
  • 22. For the purposes of our example we will use a product-based WBS.  Development of the new program can be broken down into these stages: Needs Analysis, Curriculum Proposal, Course Development Plan, Accreditation Package, Implementation, and Evaluation Plan.
  • 23. At this point we enter a stage of the process called decomposition to further break the work down in to smaller and more manageable chunks of work, called Work Packages.
  • 25. A general rule that you might want to use is called the 8/80 rule.  No work package should be less than 8 hours of work, or more than 80 hours of work.
  • 26. The process of decomposition can be done by an individual, or by the whole team.  It all depends on what makes sense for your project. Still, two minds are usually better than one!
  • 27. But you don't necessarily need to reinvent the wheel!
  • 28. If you've already completed a similar project, you may already have a template you can follow for decomposition.  Perhaps PU has already followed this process for other programs.
  • 29. It is critical that you and your team try to account for every task that is necessary to complete the project.  Mistakes here will only cost the project more time and perhaps more money later.
  • 30. Once  the  WBS  has  been  completed  it  might  be  necessary  to  build  a   WBS  Dic:onary.    The  WBS  Dic:onary  is  a  document  that  describes   each  work  package  in  detail.
  • 31. Here is the completed WBS for PU's Dog Whispering program.
  • 32. Now that you've broken the project down into manageable chunks of work, you can more easily estimate time, cost and staffing for the project. By estimating the amount of time each work package "should" take, as well as the role assigned to that task, you can estimate the cost of that task.
  • 33. You can develop a table that shows each of these fields in sequence, but there's another way to visualize this information. The Gantt Chart.
  • 34. The power of the Gantt Chart is that it is a simple and clear way to not only show the length of time of each task, but also visualize task dependencies.
  • 35. A  Task  Dependency  is   the  rela:onship  in   which  a  task  relies  on   Task  #1   the  comple:on  (or   par:al  comple:on)  of   another  task  or  tasks   before  it  can  begin. Task  #2   Task  #3  
  • 36. Task dependencies determine the total length of time for each stage in the project, Task  #1   and thus the overall timeline of the project.   Therefore, the Gantt Chart is a tool that can help us determine Task  #2   the overall timeline for a project. Task  #3  
  • 37. There are many different programs that can help you create a Gantt Chart including one of the most widely used tools for project planning and management, Microsoft Project.
  • 38. Here is a Gantt Chart produced in Microsoft Project for the Dog Whisperer program at PU.
  • 40. To  build  a  project  you  must  start  with  the  founda:on.
  • 41. 1 1.1 1.2 1.3 1.1.1 1.2.1 1.3.1 1.2.1.1 1.1.2 1.3.2 1.2.2 The foundation of a project is the Work Breakdown Structure.
  • 42. The Work Breakdown Structure will help you to define the project's scope, estimate time, cost and staffing, make delegation of tasks simpler and identify risks.
  • 43. The  process  starts  by  gathering  all  the  necessary  informa:on  and   your  key  team  members.    The  more  heads,  the  beHer!
  • 44. The first two levels of a WBS must encompass 100% of the project process.
  • 45. Use the process of decomposition to break the project down to manageable chunks using the 8/80 rule.
  • 46. Clarify each work package by creating a WBS Dictionary.
  • 47. Organize  the  tasks  into  a  GanH  Chart  to  highlight  dependencies  and   determine  the  overall  :meline.
  • 49. Slide  2  -­‐  Scream  by  Edvard  Munch.    Retrieved  from:  hHp://1.bp.blog   spot.com/-­‐JFyqLFg67hU/TaxbHC02ngI/AAAAAAAAADs/   0mIK8c8NJm0/s1600/thescream.jpg   Slide  4  -­‐  Retrieved  from:  hHp://www.flickr.com/photos   /pgoyeHe/2280685630/   Slide  12  -­‐  Retrieved  from:  hHp://office.microsof.com/en-­‐us/images/   results.aspx?ex=2&qu=start#ai:MP900422560%7Cmt:0%7C   Slide  27  -­‐  Retrieved  from:  hHp://i.images.cdn.fotopedia.com/   flickr-­‐3784879602-­‐hd/Tokyo_and_Vicinity/Further_Afield/Edogawa-­‐ku/   Kasai_Rinkai_Park/Diamond_and_Flower_Ferris_Wheel/Ferris_wheel_   and_sunset_croulds_at_Kasai_Rinkai_Park.jpg   Slide  32  –  Hourglass  Retrieved  from:  hHp://images.wikia.com/witcher/   images/3/3a/Hourglass_2.png   Dollar  -­‐  hHp://www.sparkthemagazine.com/wp-­‐content/uploads/2011/   09/dollar-­‐sign.png