A WBS (Work Breakdown Structure) is an extremely important document of any project. This document helps customers, management, and project manager in knowing the overall progress of the project. In the absence of WBS, it is not possible to report the project progress like how much work has been done, how much money or time spent for what work, which component or part of the project has more quality issues. Create WBS process defines the WBS of the project, prepares a WBS dictionary that has the unambiguous definition of each WBS element. This is the process where you should baseline your project scope. A WBS is a hierarchical representation of the deliverables. There are many ways to structure a WBS. If you keep milestones at level one of the WBS hierarchy then it is called milestone-driven WBS, similarly, component-driven WBS, phase-driven WBS can be created. What WBS is best suited for your project? It all depends upon your tracking and reporting needs and project organization structures.
WBS रचना (प्रक्रिया सारांश)
This table is based on PMBOK 6th Edition of PMI
- परियोजना प्रबंध योजना ~English
- परियोजना दस्तावेज ~English
- प्रतिष्ठान परवेश के कारक ~English
- संगठनात्मक प्रक्रिया परिसम्पतियां ~English