• This forum is the machine-generated translation of www.cad3d.it/forum1 - the Italian design community. Several terms are not translated correctly.

wbs (work breakdown structure) - parte 1a

  • Thread starter Thread starter gfrank
  • Start date Start date

gfrank

Guest
wbs (work breakdown structure), what is it and what are the rules for proper application. here is the procedure to break a project into more detail componentsa project to be developed at the best needs to be analyzed in all its individual stages. Many complex projects involve the execution of numerous activities that, without proper planning and organization, would be difficult to achieve.
to try to make all phases of a project more understandable, we help the wbs (work breakdown structure), also defined as “structured project breakdown“: this is a methodology developed in the United States, useful to structure and define clearly all the activities of a project.cos’è la wbs?wbs is a tool used for analytical breakdown of a project in elementary parts.the purpose is to organize the work in elements more easily manageable and make less complex understanding of the project, in order to communicate to all stakeholders the steps and activities to be carried out to achieve a goal.
wbs, in general, can be applied to any type of project, such as:
  • building contractor
  • building of a building
  • organization of the activities of a construction site
  • design of a building
  • etc.
the wbs fornisce a valid ausilio project manager especially in the definition and organization of the activities of complex projects.
with the tool of the wbs, therefore, the project comes Hierarchically decomposed in components (e.g. Subsidiaries, activity e specific tasks), with an increasing degree of detail, following a approach top-down, starting from macro-areas and then subdividing them into smaller parts.
each level represents always detailed portions of the project.
there is no defined number of levels: the breakdown depends on the complexity of the project. the decomposition ends when in the last hierarchical level you have a degree of detail from:
  • describe uniquely the single work to be carried out
  • to allow the allocation of executive responsibility
how to represent a wbswbs are usually represented in graphic form (shaft structure) or descriptive (Index structure).
so that the wbs carry concrete results it is necessary that it is clearly the objective to reach already in a preliminary phase.
before work starts on each individual activity the breakdown can be progressively redefined.
tree structure
struttura-ad-indice-wbs-1.jpg
index structure
and work package nella wbsthe fundamental goal of the wbs is to identify at the last level the so-called “work package” better defined as work packages.in the work package all the instructions to be carried out to achieve a certain task and task are indicated.
work-package-wbs.jpg
work package (work packages) in a wbs
so that the breakdown can be optimally defined each work package must be:
  • described clearly and concisely
  • differentiated from other work packages
  • foresee the assignment/activity to one person
  • uniquely describe the individual work to be done
in the work package you can locate:
  • all activities (task) and tasks to perform
  • the necessary inputs to carry out the work and achieve the objectives
  • description of expected results
  • the necessary resources identified
  • the start and end dates of the work
  • work outputs (deliverable)
  • the activities that are not included in the project
  • the responsibility of the task
the identification of milestones
le milestone milestone milestone milestone sleep comparisons o Interim objectives that are identified within the project with the aim of monitoring its progress.
some examples may be:
  • the end of testing an electrical system
  • signing a contract
  • the end of testing a water system
  • etc.
the identification of milestone goals can be represented through a gantt diagram:
milestone-diagramma-di-gantt.jpg

rules for the correct creation of a wbs
per la creation of a wbs, whatever the type of project, it is necessary to know a priori the objectives to be pursued, already in a preliminary phase. without proper upstream planning It would be difficult to define the individual activities to be carried out.

the level of decomposition must be able to better define the “work packages” which must be clear and well defined, avoiding duplication in the allocation of tasks.

It is recommended that the project be decomposed in logic by defining a priori the level of disaggregation to be chosen, such as:
  • per fasi: disaggregation takes place according to the various stages leading to the realization of a goal (e.g. design, approval, construction, etc.)
  • per processi: the breakdown is based on the processes leading to the realization of deliverables. is usually used in high standardization jobs (e.g. foundations, walls, roof, etc.)
  • per localizzazione: the decomposition is carried out according to the place of realization (e.g.: construction site roma, construction site milano, etc.)
wbs e la regola del 100%one of the fundamental rules underlying the creation of the wbs is the 100% rule which states:
the wbs must include 100% of the work defined by the project and everything necessary – internal, external and contracted – to the realization of the project, including the management of the project itself.
the rule applies to all levels of the hierarchy: the sum of the work of the “children” levels must be equal to 100% of the work represented by their “father”.
the rule also applies to the level of activity: the work represented by the activities in each work package must give, added, 100% of the work necessary to complete the package.
to better clarify the rule of 100% we see how to apply it to our previous example.
regola100-wbs1_2.jpg

the advantages of wbsAs already seen, using a wbs within a project involves a number of advantages, such as:
  • individuare le liability for each phase of the project
  • describe the activities to be carried out clear and complete avoiding every ambiguity
  • attribuire un task to a specific person or resource avoiding duplication in the assignment of tasks
  • agevolare la communication among the different actors involved in the execution of the project
  • improving understanding of the project by all stakeholders involved
  • improve understanding of the project by external subjects
... continue...

(source: acca biblus-net)
 

Forum statistics

Threads
44,997
Messages
339,767
Members
4
Latest member
ibt

Members online

No members online now.
Back
Top