WBS vs schedule RRS feed

  • Question

  • Hi,

    What is the best way to create and maintain WBS and schedule?

    A) In Project create the WBS, then copy the tasks into a schedule. Throughout the project duration you maintain the WBS and the Project plan separately.

    B) In Project create the WBS, once it's finished it is converted into a schedule. The WBS no longer exists, only the plan is mantained.

    C) Another approach is better. Please let me know.

    Tuesday, July 21, 2020 12:44 AM


  • Alzbeta K,

    As far as I'm concerned the WBS and schedule go together, they are not separate entities. The schedule should be a logical sequence of tasks leading up to a final result. The structure of the plan may take various forms depending on how the organization tracks costs. For example, the plan work may be broken into functional groups (e.g. concept, design, build, test, etc.), by discipline (e.g. hardware, software, electrical, mechanical, etc.), or in some other fashion that fits with the organizational/project structure.

    Keep in mind that Project will automatically generate a WBS in the WBS field as the plan is created however, that field is also user-definable.

    Also understand that not all plans need a WBS. A WBS is used primarily to dovetail with an organizations costing [financial] structure to facilitate formal tracking of project costs but cost tracking may be tracked in other ways (e.g. custom cost code structure) that doesn't fit easily into a formal WBS structure.

    It all depends on how your organization needs/wants to track plan costs and that method may vary by project (e.g. internal projects may be by discipline while a contract plan may be by function).

    Hopefully others will check in with their ideas.


    Tuesday, July 21, 2020 2:31 AM