Work breakdown structure
Download as PPTX, PDF2 likes402 views
The document discusses the Work Breakdown Structure (WBS), a method used to efficiently manage complex projects by breaking them into smaller, manageable tasks. It highlights the importance of gaining project charter approval, defining requirements, and forming a core team before implementation. Additionally, it outlines the roles of project managers and stakeholders in creating the WBS and its benefits, such as improved communication, creativity, and risk management.
Work breakdown structure
- 2. Today Our Topic is The WBS is a method for getting a complex, multi-step project done. It’s a way to divide and conquer large projects so you can get things done faster and more efficiently. Work breakdown structure (or WBS) is a hierarchical tree structure that outlines your project and breaks it down into smaller, more manageable portions. You can build a WBS by creating folders and subfolders, and can even go further to divide individual tasks into subtasks. 2
- 3. Mr.Roy is a project Manager This is Mr. Roy 3
- 4. I will implement the work breakdown structure ! 4
- 5. 3 things to be done before doing WBS: Get Project charter’s approval Define the requirements Form the core team 01 02 03 5
- 6. Hi, there! I am Anil I am Ena Hello! I am Labu Meet my team member 6
- 7. WHAT I DO IS !!! 7
- 9. 9
- 10. 10
- 11. Roys team gets a Work breakdown Structure ! 11
- 12. 12
- 14. But remember ! Roy as the project manager Mr.Sen The BOSS !! Has the responsibility to cheak back the WBS 14
- 15. 15
- 16. 1 2 3 4 5 • Overall Project Defination • Identify & Define all deliverable • Highest –level entry corresponds to the overall project deliverable.e.g..,Software development project • Start with high-level outcomes.e.g.,Create user interface • Decompose deliverable • What need to be done to complete the deliverable • Breakdown Activities • Break down to measurable level of detail. • As needed Work Breakdown Structure • 5 level 16
- 17. Who creates the WBS ? •Project Manager •Stakeholders 17
- 18. 1. The increase of communication 2. A field for creativity 3. Focus on end-goals 4. Details organization 5. Possible problems prevention 6. Brainstorming 7. Scheduling issues 8. Risk management 9. Tasks allocation 10. Flexibility for different teams 18
- 19. Goals for WBS • Giving visibility to important work efforts • Giving visibility to risky work efforts • Illustrate the correlation between the activities and deliverables. • Show clear ownership by task leaders 19
- 20. 20
- 21. 21