I am looking to find a reference article for construction of WBS for a mega project which has multiple sub-projects. Is there a good article that explains the creation of WBS in detail for such cases? Preferably with explanation of what levels of WBS would be managed by sub-project managers and what level of details would be captured in the main WBS?
It would be good to elaborate a bit more. In general all project and subproject has to follow the scope of work and simple definition of wbs Saving Changes...
Thomas WalentaGlobal Project Economy ExpertHackenheim, Germany
You can look into the practice standard for WBS, free download for members.
It includes examples of WBS containing a set of projects.
Personally, I think the main purpose of a WBS is to communicate the scope to a stakeholder group. Any WBS should fit on one page and have max 8 horizontal elements and be max 6 levels deep.
If you need more detail, create further WBS for work packages in the major WBS. Saving Changes...
Tejas SuraManaging Director| Cubic Turnkey Private LimitedMumbai, Maharashtra, India
I would suggest to work out a WBS of sub-projects to at least 4-5 levels.
The same can be imported into the master WBS and rolled up to get a high-level summary WBS. Saving Changes...
"Humanity has advanced, when it has advanced, not because it has been sober, responsible and cautious, but because it has been playful, rebellious and immature."
