Implementación - ACTUALIZACIÓN DEL WORKFLOW DE LOS CRÉDITOS

CAPÍTULO VI ACTUALIZACIÓN DEL WORKFLOW DE LOS CRÉDITOS

6.1 WORKFLOW

6.1.6 Implementación

Figure ‎4-4- Define Scope Process

Source: PMBOK® Guide - Fourth Edition, page 112

1.Project charter 2.Requirements documentation 3.Organizational

process assets

Inputs

1. Expert judgment 2. Product analysis 3. Alternatives

identification 4. Facilitated

workshops Tools &

Techniques

1.Project scope statement 2.Project

document updates

Outputs

Definition

Define Scope is the process of developing a detailed description of the project and product.

Source: PMBOK® Guide – Fourth Edition, page 103

4- Planning Phase

PMP Exam Preparation Course Page 52

Group Discussion ‎4-2- Scope Creep Indicators

Group Discussion 4.2– Scope Creep Indicators

From your perspective, what do you think of the following three statements?

1. Exceeding Customer Expectations 2. Delivering State of the art products

3. Providing low cost items, that may not cost anything free of charge

Your Notes

1. Exceeding Customer Expectations

_________________________________________________________________________

2. Delivering State if the art products

_________________________________________________________________________

3. Providing low cost items, that may not cost anything free of charge _________________________________________________________________________

_________________________________________________________________________

4- Planning Phase

PMP Exam Preparation Course Page 53

4.3.1 Inputs of Define Scope 1- Project charter

2- Requirements documentation 3- Organizational process assets:

4- Policies, procedures, and templates for a project scope statements 5- Project files from previous projects, and

6- Lessons learned from previous phases or project

4.3.2 Tools and Techniques for Define Scope 1- Expert judgment

2- Product analysis

3- Alternatives identification 4- Facilitated workshops

1. Expert judgment

This is the tools of getting the opinion of experts who have had previous experience in similar projects. Experts can be obtained from the following categories:

 Other units within the organization

 Consultants

 Stakeholders including customers or sponsors

 Professional and technical associations

 Industry groups and

 Subject matter experts 2. Product analysis

Each application area has one or more generally accepted methods for translating high-level product descriptions into tangible deliverables.

Product analysis includes techniques such as:

 Product breakdown

 Systems analysis

 Requirements analysis

 System engineering

 Value engineering

 Value analysis.

3. Alternatives identification

Identifying alternatives is a technique used to generate different approaches to execute and perform the work of the project. A variety of general management techniques can be used such as brainstorming, lateral thinking, pair wise comparisons, etc.

4- Planning Phase

PMP Exam Preparation Course Page 54

4.3.3 Outputs of Define Scope 1- Project scope statement 2- Project document updates

1. Project scope statement

This document describes, in detail, the projects deliverables and the work required to create those deliverables.

It also provides a common understanding of the project scope among project stakeholders. The Project Scope Statement may contain explicit scope exclusions that can assist in managing stakeholder expectations. Below are some of the benefits of the project scope statement:

 Help the project team to perform more detailed planning

 Guides the project team’s work

Scope Statement Content

As the details are not always ready from day one of the project, so this document may be compiled progressively over a period of time. The contents of this document include, but not limited to the following:

 Product scope description

 Product acceptance criteria

 Project deliverables

 Work breakdown structure

 Project exclusions

 Project constraints

 Project assumptions

 Project boundaries

 Project resources

 Project milestones

 Project stakeholders

 Project Risks Identifying Constraints

Examples of constraints that may be faced during a project:

 Budget

 Schedule

 People

 Facilities and Equipment

Constraints:

Are known factors, which limit the project team’s options.

Assumptions:

Are factors that, for planning purposes, are considered to be true, real, or certain. They need to be validated during the course of project planning

4- Planning Phase

PMP Exam Preparation Course Page 55

 Fault tolerant objectives

 Portability requirements

 The real world Identifying Assumptions

Assumptions are identified and documented during the planning process as they affect all aspects of planning. They need to be verified to ensure that they are true. In case if it is proven to be false, then re-planning is needed. They always carry a certain degree of risk

Unquantifiable Expectations

Some expectations “requirements” may be difficult to quantify, they need to be quantified as much as possible, and otherwise they become a risk item of unclear requirements. Examples of these are:

 Customer satisfaction

 Company Image

 Community Perception 2. Project Document Updates

As mentioned earlier, the project management team does not always have answers to all planning questions. Facts come up during different times during the project life cycle. This entails changing the project related documents as and when new facts come up. Changes also come due handling authorized change requests. Examples of the documents that will be changed in this process are:

 Stakeholder register

 Requirements documentation

 Requirements traceability matrix.

4- Planning Phase

PMP Exam Preparation Course Page 56

Exercise ‎4-3-Create Scope Statement

Exercise 4.3 – Create Scope Statement

Based on the supplied case study, create the Project Scope Statement that will highlight the minimum project information. Consider this as the business case used in your organization. Include the following information:

1. Project Name 2. Project Manager

3. Business Needs (project justification) 4. Summary of Product Description 5. Deliverables

6. Objectives (cost, schedule, quality measures, other) 7. Project Constraints

8. Project Risks (high level) Note: Use form 9.2 in Appendix 2

Your Notes

_________________________________________________________________________

4- Planning Phase

PMP Exam Preparation Course Page 57

Exercise ‎4-4-Create Project Assumptions

Exercise 4.4 – Create Project Assumptions

Based on the supplied case study and the developed scope statement, create the Project Assumptions List. Include the following information:

1. Area: the area of the assumption, can be technical, financial, business etc.

2. The Assumption that you see true or false and that will be verified later on.

Note: Use form 9.3 in Appendix 2

Your Notes

_________________________________________________________________________

4- Planning Phase

PMP Exam Preparation Course Page 58

In document Sistema OPCISAP, OPCIPRES SA de CV SOFOM ENR. (página 71-76)