SAB9#40_Create_WBS (Modified)

Beschreibung

Mindmap am SAB9#40_Create_WBS (Modified), erstellt von Roman Velasquez am 25/02/2016.
Roman Velasquez
Mindmap von Roman Velasquez, aktualisiert more than 1 year ago
Roman Velasquez
Erstellt von Roman Velasquez vor fast 10 Jahre
10
0

Zusammenfassung der Ressource

SAB9#40_Create_WBS (Modified)
  1. Scope Mgmt Plan
    1. Project Scope Statement
      1. Requirements documents
        1. EEFs
          1. ISO/IEC-15288
          2. OPAs
            1. Project Scope Statement
              1. Requirements Documents
                1. Organizational Tool Shows all the Scope of the project Broken down into manageable deliverables
                  1. Is better than a List . A list is just a List
                    1. 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
                      1. 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
                        1. A list usually created by one person , whereas the WBS is created with input form the team and stakeholdes
                        2. Created with input from the team and stakeholders
                          1. Show a complete hierarchy of the project , making it easier to see how one deliverable relates to another
                            1. Decompostion
                              1. Expert Judgment
                                1. WBS
                                  1. 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
                                    1. 2 most common ways of visualizing the work are by deliverable or by phase.
                                      1. Start with a Major Deliverable (Project Name)
                                        1. Then begin breaking down the project into a smaller and smaller pieces (project life cycle)
                                          1. 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)
                                            1. 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
                                              1. Work Package
                                                1. Is the lowest level on a WBS
                                                  1. 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
                                          2. Benefits
                                            1. Helps identify risks
                                              1. Helps to prevent changes
                                                1. Helps to manage stakeholders expectation regarding deliverables
                                                  1. Provide a basis for estimating resources , cost and time
                                                    1. Focuses the teams experience on what needs to be done , resulting in increased quality and a project that is easier to manage
                                                      1. Provide PROOF of the need for resouces , funds and time
                                                        1. Helps with planning the control efforts and establishing acceptance criteria for the deliverables
                                                        2. Can be reused for other proejcts
                                                        3. WBS Dictionary
                                                          1. Describe the shedule miletones , t he acceptance criteria , duration , interdependecies , an other information about t he work packages
                                                          2. Is the Foundation of the project, is a required element in project management
                                                            1. It is Not a corporate organizational chart , it is serve a different function
                                                              1. Should exist for every project
                                                                1. Does NOT show dependencies
                                                                  1. as a Commuinication tool
                                                                    1. 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
                                                                      Zusammenfassung anzeigen Zusammenfassung ausblenden

                                                                      ähnlicher Inhalt