WBS

Member for

15 years 11 months

WBS is simply similar to a Folders.

[[wysiwyg_imageupload:2093:]]

Member for

18 years 6 months

Mike: For me it is at whatever level you can/should collect costs (data).  It is conceivable, though not practical/realistic, to take a WBS down to the individual craftsman/crew.  In reality, it is the ability of the estimator to estimate to a proscribed level of detail that will determine the granularity of the WBS.  The estimator will collect his quantities in accordance with the existing WBS.  In my world, my little portion of it, the WBS is usually geographic - project, phase, building/structure, craft/discipline, level, quadrant, etc.  The cost accounts should reflect this.  The CBS should map to the WBS.

There is no reason to collect (code) data below the level of the current estimate.  This level will change with project maturity.  The level of the WBS depends on where you are in the project chain/process.

Member for

13 years 4 months

Thanks for the feedback Patrick - much appreciated

Mike

Member for

24 years 9 months

Agree Mike!  The WBS Work Packages are the lowest management level defining a deliverable of some type.  Each Work Package devolves into many schedule activities that define how the work needed to create the deliverable will be accomplished. For more on this see:  http://www.mosaicprojects.com.au/WhitePapers/WP1011_WBS.pdf

The ‘size’ of the work package is less important than it representing a self contained block of work that is assigned to a manager to manage, ether stand alone or as part of a control account.