Understanding

• Responsibility of carrying out this activity lies with project manager or project lead
• Team members could well be included into WBS to assist in the process.
• Domain experts and subject matter experts (SME) are the essential requirements of this procedure. Whether the domain is technology related or business domain.
• Before starting this activity one should see that requirements have been gathered and documented.
• Activities one could perform to carry out breakdown work are
  • Review the complete set of requirements.
    • Typically requirements are documented in a hierarchical fashion. This may help to simplify creating a WBS.
  
  
  • Determine the high-level work items
    
    Example 1-1 A WBS with high-level work items only.

    It is recommended that documenting and tracking problems with technical activities (such as source code, executable code, system data files, databases, specifications, video scripts, network schematic drawings, etc.) to closure be one of the high level work items.

  
  
  • Determine 2nd level tasks
    Brainstorm to break each work item into another level of sub-items. For larger or riskier projects, consider selecting a small group of Subject Matter Experts (SMEs) to aid in the brainstorming activity.
  
  
  Example 1-2 A WBS high-level work items with sub-item
  • Determine lowest level tasks
    Break each work item into smaller and more manageable work items until the level of detail necessary to manage the project has been reached. Use the following guidelines to determine the lowest level of detail desired. During breaking down of work one should see that no task item has a work estimate of more than a 7 man days. If this happens to be the case, breakdown work structure again.
    • Some person (or group for a larger project) can take responsibility for the task, or accomplish the activities involved.
    • A rough estimate of effort (person-days) can be determined for this task.
    • The task can be scheduled. In other words, it’s precedence and calendar duration can be determined.
    • Deliverables for this task can be identified as a means of determining the completion status of the task.
  
  
  Example 1-3 WBS for software engineering work with lowest level work items shaded
  • Capture task
    • Document all identified work items in a document (MPP, etc).
  
  
  • Review task list with project team for final input
  • Capture and document measurements for this procedure
    • Record time required by skill level.
    • Record non-personnel related expenses incurred from this procedure.
    • Record special resources required (i.e. consultants, books, and training.)
• Once you perform the above-mentioned activities you will have list of all identified tasks in your hands. One can go ahead with estimation to calculate the timings.