Work breakdown structure
- 1. Click to edit Master title style 1 Work Breakdown Structure Presented By: Muhammad Zaid Zulfiqar Submitted To: Sir Javed Larik
- 2. Click to edit Master title style 2 ❑ Work Breakdown Structure 2 It is a technique/process in which the complete project is broken down into small chunks/parts. ▪ Work Breakdown Structure -Defines tasks and assign resources to those tasks. ▪ The WBS is an important tool which helps to keep an overview of the project. PROJECT Small Parts / Chunks
- 3. Click to edit Master title style 3 ❑ Work Breakdown Structure 3 It is the process by which : ▪ Project Manager, all connected functional managers, and all connected staff will work together and analyze all the aspects of the project. Project Work Packages Sub- Tasks Tasks Sub- Projects
- 4. Click to edit Master title style 4 ❑ Level Of Work Breakdown Structure 4 ▪ There is no hard and fast rule and depends on your own choice ▪ 1 or 2 levels can lead to difficulty in integration of activities ▪ Too many levels can make the analysis complex ▪ Then How many levels ?? Some approaches to the no of levels; ✓ Building up the WBS till such time that the work packages available can give a good definition of work content, the cost, time, and resources required. ✓ Using 8/80 rule, Three week / Year Rule etc. Project Sub- Projects Tasks Sub- Tasks Work Packages (Level 1) (Level 5) (Level 4) (Level 3) (Level 2)
- 5. Click to edit Master title style 5 ❑ Types of Work Breakdown Structure 5 1. Product oriented work break down structure: ▪ In product oriented WBS. the project is subdivided into sub- projects based on "product" ▪ The sub-project is again subdivided based on product and so on, till the tiny work packages are obtained. 2. Functionally oriented work break down structure: ▪ In this type the project is broken- down based on functional departments (or Functional tasks) ▪ The project is subdivided into sub- projects based on "Function“ ▪ The sub-project is again subdivided based on functional department and so on, till the tiny work package are obtained.
- 6. Click to edit Master title style 6 ❑ WHY IS IT NEEDED ? 6 ▪ Simplifying the project execution ▪ Accurate and readable project organization. ▪ Accurate assignment of responsibilities to the project team. ▪ Indicates the project milestones and control points. ▪ Helps to estimate the cost, time, and risk. ▪ Illustrate the project scope, so the stakeholders can have a better understanding of the same.
- 7. Click to edit Master title style 7 ❑ MISCONCEPTIONS 7 ▪ A WBS is not an exhaustive list of work. ✓ Comprehensive classification of project scope. ▪ A WBS is ✓ neither a project plan, ✓ a schedule, ✓ nor a chronological listing. ✓ Specifies what will be done, not how or when. ▪ A WBS is not an organizational hierarchy, ✓ It may be used when assigning responsibilities.
- 8. Click to edit Master title style 8 ❑ KEY POINTS 8 ▪ Work breakdown structures are great for developing and validating the scope of a project. ▪ Work breakdown structures are most powerful when shown in a graphic style, like an organization chart. They can also take on the form of a simple outline. ▪ Work breakdown structures allow people from various backgrounds, disciplines, and perspectives to understand the activities being planned. ▪ Simplifying the project execution and defines the total scope of the project ▪ Help to estimate the cost, time, and risk.
- 9. Click to edit Master title style 9 Thank You