SAB9#40_Create_WBS (Modified)

SAB9#40_Create_WBS (Modified)

1. Scope Mgmt Plan

2. Project Scope Statement

3. Requirements documents

4. EEFs

   • ISO/IEC-15288

5. OPAs

6. Project Scope Statement

7. Requirements Documents

8. Organizational Tool Shows all the Scope of the project Broken down into manageable deliverables

9. Is better than a List . A list is just a List

   • A list display information make it easy to overlook some deliverables , WBS chart provides a structure vision for the project and helps to ensure nothing slips through the cracks
   • A list can be cumbersome and does not allow you to clear break down a large project into small enough pieces , WBS you can easily break down the work into work packages and the WBS shows how the work packages are derived
   • A list usually created by one person , whereas the WBS is created with input form the team and stakeholdes

10. Created with input from the team and stakeholders

11. Show a complete hierarchy of the project , making it easier to see how one deliverable relates to another

12. Decompostion

13. Expert Judgment

14. WBS

    • Doesnt Show the order of the work packages or any dependecies between them. Its only goal is to show the work involved in created the product
    • 2 most common ways of visualizing the work are by deliverable or by phase.
    • Start with a Major Deliverable (Project Name)
      • Then begin breaking down the project into a smaller and smaller pieces (project life cycle)
        • Make sure the team has enough information about the work package to get the job done , provide them enough detailed to do the job (such decomposition continues until reaching the level appropriated to manage the project)
          • Each work package has to be compact enough to make it easy to organize , should begin to think about how you are going to estimate the work packages when you are decomposing them
            • Work Package
              • Is the lowest level on a WBS
              • Its a unit of work that you and your team use to organize the stuff youare going to have to do to get the project done
    • Benefits
      • Helps identify risks
      • Helps to prevent changes
      • Helps to manage stakeholders expectation regarding deliverables
      • Provide a basis for estimating resources , cost and time
      • Focuses the teams experience on what needs to be done , resulting in increased quality and a project that is easier to manage
      • Provide PROOF of the need for resouces , funds and time
      • Helps with planning the control efforts and establishing acceptance criteria for the deliverables
    • Can be reused for other proejcts

15. WBS Dictionary

    • Describe the shedule miletones , t he acceptance criteria , duration , interdependecies , an other information about t he work packages

16. Is the Foundation of the project, is a required element in project management

17. It is Not a corporate organizational chart , it is serve a different function

18. Should exist for every project

19. Does NOT show dependencies

20. as a Commuinication tool

21. PREGUNTA DE EXAMEN DEFINICION DE WBS ES: Herramienta de comunicacion orientada a Entregables , Paquete de Trabajo tiene 4 componentes : Nombre de Activadad o prodcto o servicio , fecha de inicio- Fin , un Owner , un fondo asignado si le falta uno de estos componentes se llama planning PAckage

Bilder und Dateien der Mindmap