Work Breakdown Structure

Work Breakdown Structure

1. Outputs

   • Proyect document (updates)
     • Requirements documentation
   • Scope baseline
     • Basis for many other processes like budget, risk, activities definition, procurement
     • Monitored, verified, and controlled throughout the project
     • WBS dictionary
     • WBS
     • Approved detailed scope statement
       • Product scope description
       • Project deliverables
       • Product user acceptance criteria
   • WBS Dictionary
     • Supporting Document for WBS
     • Has detailed description of the compnents in the WBS
       • Code of account identifier
       • Description of work
       • Responsible organization
       • List of schedule milestones
       • Associated schedule activities
       • Resources required
       • Cost estimates
       • Quality requirements
       • Acceptance criteria
       • Technical references
       • Contract information
   • WBS
     • Deliverable-oriented hierarchical descomposition od the work
       • Each descending level represents an increasingly detailed definition of the project work
     • Tied up with
       • Control Account
         • Management control point where scope, cost and schedule are integrated and compared
         • May include one or more work packages
     • Work packages
       • Planned work contained within the lowest level WBS components
       • Can be scheduled, cost estimated, monitored and controlled
       • WBS level at which the cost and activity durations for the work can be reliably, estimated and managed
       • Must be associated with only one control account
     • Executed by the project team
       • To acomplish the project objectives and create the required deliverables

2. Inputs

   • Project scope statement
   • Requirements documentation
   • Organizational process assets

3. Definition

   • Process of subdividing project delivverable and proyect work into smaller, more manageable components

4. Scope

   • Tools and techniques
     • Descomposition
       • Subdivision of project deliverables into smoller, more manageable components until the work and deliverables are defined to the work package level