SAB9#36_37_Planning_Scope & Plan_Scope_Mgmt

Descripción

Mapa Mental sobre SAB9#36_37_Planning_Scope & Plan_Scope_Mgmt, creado por Roberto Vargas Prado el 20/02/2016.
Roberto Vargas Prado
Mapa Mental por Roberto Vargas Prado, actualizado hace más de 1 año
Roberto Vargas Prado
Creado por Roberto Vargas Prado hace alrededor de 8 años
32
0

Resumen del Recurso

SAB9#36_37_Planning_Scope & Plan_Scope_Mgmt
  1. Project Management plan
    1. Since you’re in the process of creating these plans for the other knowledge areas at the same time as this one, there’s a good chance that you can use some of the same ideas in this plan that you’ve uncovered in the process of creating your Time Management plan, your Cost Management plan, or any of the other subsidiary plans.
    2. Project charter
      1. The charter already includes a high-level description of the scope of the project. So it’s a good place to start.
      2. EEFs (Enterprise environmental factors)
        1. Your company’s culture and accepted practices will have a big impact on the way you manage scope on this project too.
        2. OPAs (Organizational process assets)
          1. The Plan Scope Management process is where you lay out your approach to figuring out what work you’ll do and what’s out of scope.
            1. Product Scope
              1. Product scope means the features and functions of the product or service that you and your team are building.
                1. The product scope is all about the final product—its features, components, pieces.
              2. Project scope
                1. Project scope is all of the work that needs to be done to make the product.
                2. Scope creep
                  1. Scope creep means uncontrolled changes that cause the team to do extra work.
                3. Expert judgment
                  1. Meetings
                    1. You might need to hold a meeting with some of the project’s stakeholders to agree on an approach.
                    2. Plan Scope Management
                      1. Here’s where you write down the subsidiary plan for the project management plan that we talked about in the last chapter. You plan out all of the work you’ll do to define your scope, make sure the team is planning to do the right work, and control it.
                        1. Requirements Management plan
                          1. Here’s where you’ll find a description of the approach the team will take to planning, tracking, and reporting on requirements. You’ll use this document to describe the prioritization process for requirements, and how you’ll build a traceability matrix for your requirements as well.
                          2. Scope Management plan
                            1. Here’s where you write down the subsidiary plan for the Project Management plan that we talked about in Chapter 4. You plan out all of the work you’ll do to define your scope, with the right work planned for the team, and control it.
                          3. Collect Requirements
                            1. In this process, you find out all of the stakeholders’ needs and write them down so that you know what to build and your requirements can be measured and tracked.
                            2. Define Scope
                              1. Here’s where you write down a detailed description of the work you’ll do and what you’ll produce.
                              2. Create WBS
                                1. The work breakdown structure (WBS) organizes all of your team’s work into work packages—or discrete pieces of work that team members do—so that you can keep the momentum of the project going from the start.
                                2. Control Scope
                                  1. We already know how important it is to control changes on your project. When scope changes aren’t controlled, it leads to the most frustrating sort of project problems. Luckily, you already know about change control, and now you can use it to manage your project’s scope.
                                  2. Validate Scope
                                    1. Once the work is complete, you need to make sure that what you’re delivering matches what you wrote down in the project scope statement. That way, the team never delivers the wrong product to the customer.
                                    Mostrar resumen completo Ocultar resumen completo

                                    Similar

                                    Creando una Ficha
                                    Diego Santos
                                    Las Matemáticas
                                    María Salinas
                                    ANIMALES
                                    Ulises Yo
                                    Termodinámica
                                    Polett Quiñones
                                    Sistemas del Cuerpo Humano
                                    Diego Santos
                                    Evolución de la Informática
                                    Diego Santos
                                    EL UNIVERSO Y EL SISTEMA SOLAR
                                    ROSA MARIA ARRIAGA
                                    Comunicación Celular
                                    Leonardo Ortega
                                    Guía para Tener Éxito en los Exámenes
                                    Diego Santos
                                    Como realizar un resumen y la importancia de estrategias de comprension lectora en este proceso
                                    Lizbeth Dayann CAMINO MARTINEZ