2

I'm fairly new to this. I'm trying to build a WBS for communications equipment installation. This requires things like licenses, electrical conduit, parts ordering, and outsourcing to other organizations. It seems that a deliverable oriented WBS would be best for the project, but once I get to the 3rd layer, it seems natural to the components of the deliverable into the tasks necessary to produce the components. Would a WBS that mixes types in this way work well, or will I run into problems when converting this to a network and project schedule?

1

A product oriented WBS would have products on top, broken down to its manageable sized components, and then activities below it. I define the work package to be the lowest level of product; the activities below it enable size estimation. You should not have any issues scheduling a WBS such as this.

| improve this answer | |
  • Is it any problem that some of my lowest level boxes are a mix of tasks and products? – Frank Mar 3 at 19:23
  • Not in my opinion – David Espina Mar 4 at 11:37

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.