PRACTICE STADANDAR FOR WORK BREAKDOWN STRUCTURES

PRACTICE STADANDAR FOR WORK BREAKDOWN STRUCTURES

1. DEFINITION

   • COMMON USING TERMS
     • WORK
       • Deliverables that are the result of effort
     • BREAKDOWN
       • Divition in parts
     • STRUCTURE
       • Something arranged
         • in a definite pattern organization
     • OTHER TERMS
     • THE DEFINITION TERMS
       • facilitate understanding
         • of the integral role the WBS plays
           • in project management practice
   • CONCEPT
     • DELIVERABLES
       • Any unique and verifiable product, result, or capability
         • DELIVERABLES ORENTED WBS BENEFITS
           • Better communication
           • More accurate estimation
           • Increased confidence
           • A foundation for the control
     • DESIGN
       • Provides a graphical representatio of the Project scope
     • ORGANIZATIONAL PERSPECTIVE
       • Defined clearly organizational responsabilities
     • MANAGEMENT
       • WBS support effective Project management
     • WBS LEVELS
       • Depend upon the size and complexity
   • CHARACTERISTICS FROM THE DICTIONARY DEFINITION
     • Supports the definition of all work required
       • to achieve an objective
     • illustrate and define the hierarchy of deliverables.
       • organized into ‘‘parent-child’’ relationships.
     • Has an objective or tangible result
   • THE 100% RULE
     • is a core characteric
     • captures ALL deliverable deliverables
     • includes 100% of the work
       • defined by the project scope
   • REPRESENTATION OF WBS
   • EXAMPLE: CONSTRUCTION A BIKE

2. IMPORTANCE

   • INTEGRATION WITH PROJECT MANAGEMENT PROCESSES
     • WBS plays an integral role
       • in other project management processes
   • RELATIONSHIP TO OTHER TOOLS
     • PROJECT MANAGEMENT TOOLS
       • PROYECT CHARTER
         • takes the project charter as its starting point
       • PROJECT SCOPE STATEMENT
         • Describe
       • PROGRAM AND PORTFOLIO WBS
         • Can be used to define scope for projects, programs, and portfolios
       • THE RESOURCE BREAKDOWN STRUCTURE
         • In conjunction with the WBS
           • to define work package assignments.
       • ORGANIZATIONAL BREAKDOWN STRUCTURE
         • Reinforces the guideline
       • WBS DICTIONARY
         • accompanies the WBS and carries critical project information
       • PROJECT SCHEDULE NETWORK DIAGRAM
         • is a sequential arrangement of the work defined by the WBS
         • essential to uncovering project dependencies and risks.
       • PROJECT SCHEDULE
         • The various elements of the WBS
           • are used as starting points
             • for defining the activities
     • WPS DEVELOPMENT TOOLS
       • Promote and enforce
         • the principles of the WBS standard
       • promote
         • Consistency and Repeatability
       • Reduce
         • the development effort
   • WBS INTEGRATION AND USE BY OTHER STANDARS
     • Identifies the WBS as a tool that can be used to develop a program WBS.
     • The Standard for Portfolio Management
     • The Standard for Program Management

3. WBS QUALITY DEFINITION

   • PRINCIPLES
     • PRINCIPLE 1
       • Satisfies all of the requirements for its use in a project
       • Sub Principle 1
         • Describe
           • a set of 16 core characteristics
             • that must be present in every WBS
               • to satisfy project needs
       • Sub Principle 2
         • Define
           • a set of 7 use realated characteristics
             • that can vary
               • from one WBS to another
     • PRINCIPLE 2
       • WBS quality characteristics apply
         • at all levels of scope definition.
           • differ only in
             • the content
             • the scope
   • PROBLEM DIAGNOSTIC CHECK LIST
     • There are abou 7
       • Project problem
         • resulting from WBS keys defects
   • EXAMPLE OF HIGH QUALITY
     • LEVEL 1
       • comprises the full scope of work
         • necessary to produce the bicycle
     • LEVEL 3
       • integration is decomposed
         • into interim deliverables
     • LEVEL 2
       • The first level of decomposition
     • LEVEL 4
       • testing into 3 descpmponent elements
         • Customer test
         • Component test is pre-assembly testing
         • Product test is quality control and pre customer test

4. INTRUDUCTION

   • OBJECTIVES
     • to provide a common ground
       • for understanding the concepts and benefits of the WBS
     • to present a standard application
       • of the WBS as a project management too

Images and files in the map