1 / 43

Work Breakdown Structure: Definition, Relationships, and Best Practices

Understand the concept of Work Breakdown Structure (WBS), its definition, relationships, and approaches to developing it effectively. Learn about hierarchical structure, task interdependency, milestones, and more.

olgae
Download Presentation

Work Breakdown Structure: Definition, Relationships, and Best Practices

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Work Breakdown Structure (WBS) Farrokh Alemi, Ph.D. Lee Baliton

  2. Why break up? • Improve work management • Understand resource and time constraints • Set milestones for progress • See alternative sequencing of components of work

  3. Definition of WBS • Breaks the project scope • Inter-related • Discrete tasks • Hierarchical tree structure

  4. Definition of WBS Clear starts and ends • Breaks the project scope • Inter-related task • Discrete tasks • Hierarchical tree structure

  5. Definition of WBS Four possible relationships • Breaks the project scope • Inter-related • Discrete tasks • Hierarchical tree structure

  6. Definition of WBS Four possible relationships • Breaks the project scope • Inter-related • Discrete tasks • Hierarchical tree structure • Finish to Start: Start second task after first one is finished

  7. Definition of WBS Four possible relationships • Breaks the project scope • Inter-related • Discrete tasks • Hierarchical tree structure • Finish to Start • Start to Start: Start second task same time as first one

  8. Definition of WBS Four possible relationships • Breaks the project scope • Inter-related • Discrete tasks • Hierarchical tree structure • Finish to Start • Start to Start • Finish to Finish: Start second task so both finish at same time

  9. Definition of WBS Four possible relationships • Breaks the project scope • Inter-related • Discrete tasks • Hierarchical tree structure • Finish to Start • Start to Start • Finish to Finish • Start to Finish: Second task cannot finish before first one starts

  10. Definition of WBS Lower level tasks inherit the relationships among higher level tasks • Breaks the project scope • Inter-related task • Discrete tasks • Hierarchical tree structure

  11. Hierarchy of Activities Level 1: The root of the tree is the project name A

  12. Hierarchy of Activities EHR implementation A

  13. Hierarchy of Activities EHR implementation Level 2: Components of the entire project A B C D

  14. Purchase system Train users Configure system Hierarchy of Activities EHR implementation A B C D

  15. Purchase system Train users Configure system Hierarchy of Activities EHR implementation A Level 3: Each level 2 tasks is broken into its subcomponents B C D E F

  16. Hierarchy of Activities EHR implementation A Purchase system B C D Train users Configure system E F Purchase training material Detail employees

  17. E Purchase training material Hierarchy of Activities EHR implementation A Purchase system B C D Train users Configure system F Detail employees

  18. E Purchase training material Hierarchy of Activities EHR implementation A Purchase system B C D Train users Configure system F Detail employees

  19. A D C E B Hierarchy of Activities EHR implementation F Detail employees Train users Purchase training material Configure system Purchase system

  20. Approaches to Developing Work Breakdown • Guidelines • Analogy • Bottom up • Mind mapping

  21. Approaches to Developing Work Breakdown • Guidelines • Analogy • Bottom up • Mind mapping

  22. Approaches to Developing Work Breakdown • Guidelines • Analogy • Bottom up • Mind mapping

  23. A D C E B Hierarchy of Activities EHR implementation F Detail employees Train users Purchase training material Configure system Purchase system

  24. EHR implementation A Train users D F Detail employees Purchase training material C Configure system E Purchase system B Hierarchy of Activities

  25. Approaches to Developing Work Breakdown • Guidelines • Analogy • Bottom up • Mind mapping

  26. Task • Mutually exclusive • Exhaustive

  27. EHR implementation A D Train users C Configure system B Purchase system Task • Mutually exclusive • Exhaustive Purchase of systems and organizing training may not be mutually exclusive if the purchase includes training

  28. Task • Mutually exclusive • Exhaustive

  29. Breadth .vs. Depth • Focus on breadth • Let details emerge • Progressive elaboration • Creativity

  30. Breadth .vs. Depth • Focus on breadth • Let details emerge • Progressive elaboration • Creativity

  31. EHR implementation A Train (detail)users D C Configure system Purchase system B Numbering Convention 1.1.2 Purchase training material E

  32. EHR implementation A Train (detail)users D C Configure system Purchase system B Numbering Convention 1.1.2 Purchase training material E

  33. EHR implementation A Train (detail)users D C Configure system Purchase system B Numbering Convention 1.1.2 Purchase training material E

  34. EHR implementation A Train (detail)users D C Configure system Purchase system B Numbering Convention 1.1.2 Purchase training material E

  35. Work Breakdown Is Not … • We need to clarify some common mistakes …

  36. A Task Is … • Not a goal

  37. A Task Is … • Not a goal • Not a process

  38. Work Breakdown Is … • Not an exhaustive list of work

  39. Work Breakdown Is … • Not an exhaustive list of work • Not a chronology

  40. Work Breakdown Is … • Not an exhaustive list of work • Not a chronology • Not an organization structure

  41. Work Breakdown Is … • Not an exhaustive list of work • Not a chronology • Not an organization structure • Not to be changed often

  42. Good Work Breakdowns • Easy to understand • Corresponds to job descriptions • Not too detailed • Preserve the most important relationships among the tasks • Does not add to length of project

  43. Take Home Message Think Carefully through Work Breakdown Structure

More Related