Ejemplo Wbs

Work Breakdown Structure
Instructions





Work breakdown structures (WBS) are used to define and breakdown all of the work of the project into logical groupings. Work that is not included on the WBS is not considered work of the project. Therefore, all project work must be represented on the WBS.

A WBS is constructed in hierarchical form, much like an organizational chart, with theproject itself at the top. Each level of the WBS represents a further breakdown of the work of the project. For example, level one is the project itself, level two might contain all the deliverables for the project, level three is a further breakdown of those deliverables and level four is the actual task or activity to be performed in order to complete the deliverable.

The first step indeveloping a WBS is to identify all the project deliverables. Hopefully, these are listed in the Scope Statement so you won’t have far to look. Next, begin breaking the deliverables down into smaller deliverables as shown in the examples below and finally into tasks. You know you’re done when you’ve identified all the tasks it will take to complete the deliverable.

Don’t try to go it alone when creatingyour WBS, enlist the help of the project team. Use brainstorming methods to help identify all the tasks needed for each deliverable. One person cannot think of all the tasks needed for a project, except for the smallest of projects, so involve your project team in the identification process. List the deliverables on a white board, one by one, and identify all tasks for each of the deliverablesuntil no one can think of anything more.

Figure 1 (on the next page) shows a sample portion of the WBS for the Implement PMO project. You can see how the levels are broken down into finer levels of detail or activity at each subsequent level of the WBS.








Figure 1 – Sample WBS

[pic]
|Level 4 |Identify templates to |Develop maturity |Develop Knowledge|Develop format for |
| |create |model |Area training |brown bags |
| | |measures | | |
| |Create |Administer |Develop|Develop |
| |templates |survey |Lifecycle |updates and |
| | | |training |refreshers |
| |Write |Compile data |Hold training ||
| |instructions | |classes | |
| |Review |Report data | | |
| |templates | | ||
| |with PAC | | | |

There are no hard and fast rules for how many levels the WBS should have. However they tend to get unwieldy when they exceed five or six levels.

The higher levels of the WBS depict deliverables which are usually described as nouns (person, place orthing). The lower levels and particularly the lowest level are usually activity based and are described using verbs (action words).

Large projects generally have a WBS that is only two or three levels deep. Level one is the main project, level two is sub-projects under the main project, level three is either further sub-projects or a listing of deliverables. Each sub-project manager is then...