Work Breakdown Structure [Definition - Example - Template]

Overview:

Work breakdown structure (WBS) is one of the most important documents generated during the project life cycle. It is mandatory to have it at the early stage of project planning as it is part of scope baseline (Project Scope Statement + Work breakdown structure [WBS] + Work breakdown Structure Dictionary [WBS Dictionary]). Usually the WBS document stored in Project management system and it is been updated frequently as part of progressive elaboration. It is part of project planning process and scope management knowledge area. It is an output of “create WBS” process under planning process group. Please note that creation of WBS is a group and team activity which is means that all team members should participate in that activity.

Work breakdown structure (WBS) Definition:

Work breakdown structure is a decomposition of the project into smaller manageable pieces of deliverables. Usually presented as a tree or outline with unique code stamped with each node. The project name is the root of that tree (highest level) and work packages are leaves (Lowest level). Work package is the level that you can start assign your time and cost. You can also start team assignment her at that level by assigning each work package to and individual team member or group.

Work breakdown structure (WBS) Example:

Tree Format:

Outline Format:

1. Build House
  1.1. Main Building
    1.1.1. Building Rooms
      1.1.1.1. Work package
      1.1.1.2. Work package
      1.1.1.3. Work package
   1.1.2. Base & Foundation
 1.2. Yard
   1.2.1. Parking
     1.2.1.1. Electrical door
     1.2.1.2. Entrance

Work Breakdown Structure (WBS) Template:

1. Project Name

  1.1. Major Deliverable (L1)

    1.1.1. Control Account

      1.1.1.1. Work package

      1.1.1.2. Work package

      1.1.1.3. Work package

    1.1.2. Work package

    1.1.3. Work package

    1.1.4. Work package

  1.2. Major Deliverable (L1)

    1.2.1. Major Deliverable (L2)

      1.2.1.1. Control account

      1.2.1.2. Control account

        1.2.1.2.1. Work package

Tips, Hints & Tricks:

• Stop decompositioning when you reach for a deliverable with amount of work equal to around 80 hours. This is called 80's rule of thumb.
• Don't start decomposition of the next level in the hierarchy till you list all deliverables in the current level.
• Start identifying control accounts after you complete your WBS tree. 
• Don't reach to activity level.
• Give a unique code to identify each node in the hierarchy.
• It is not mandatory that all work packages be on the same level. But it is mandatory to be on the leaves.