PROJECT MANAGEMENT

Unit 1 : PMBOK
“Scope Management”

Week : 04

Prepared by: Prof. Augusto

Choy 1
PROJECT
MANAGEMENT
UNIT 1: PROJECT MANAGEMENT BODY OF KNOWLEDGE
“SCOPE MANAGEMENT”
WEEK: 04

2
Prepared by Prof Augusto Choy
UNIT’S LEARNING OUTCOME
•To recognize and understand the structure of the course in
order to develop and learn PM successfully.
•To review and analyze the main concepts related to Project
Management and how to apply them in their profesional
life.

3
Prepared by Prof Augusto Choy
 Unit 1 : INTRODUCTION TO PROJECT MANAGEMENT

SCOPE MANAGEMENT

◦ Reviewing Concepts – Scope Management

◦ The Scope Management Process.

◦ Summary

Source: Heizer, Jay (2020), Operations Management: Sustainability and Supply Chain Management. 12th Ed.

4
Prepared by Prof Augusto Choy
 Topics – Scope Management
1. Scope Management
1. Scope Project and Scope Product
2. Scope Management Processes
3. Work Breakdown Structure as a Fundamental Tool
Reviewing Concepts – Scope Management

6
 Scope Management
 Have you ever asked yourself,
how many times, you have
incorporated additional work to
a Project?

 Scope Management Definition

 It is the processes that ensure that
the Project includes all the work
required, and only the work
required, to complete the Project
successfully.
7
Review Concepts – Scope Management
What is the Scope?
 Project Scope
 Product Scope

 What is a requirement?

 What is a deliverable? Deliverable

8
Activity N° 01

In class, determine a list of at least 30

deliverables for a Wedding Project.
Scope Management Processes
Scope Management Processes
Nª Process Process
Group
01 Plan Scope Management
02 Collect Requirements
Planning
03 Define Scope
04 Create WBS
05 Verify Scope Monitorin
g&
Controllin
06 Control Scope g
Plan Scope Management
 Create Scope Management Plan (scope will be defined,
validated and controlled).
 Provides guidance and direction on how scope will be
managed throughout the project.

 Scope Management Plan

12
Plan Scope Management
 Requirements Management Plan
 Requirement Collection Techniques.
 Formats.
 Requeriment prioritization
Guidelines.
 Attribute Traceability Matrix.
 Requirement Monitoring and Control
process

13
Plan Scope Management

14
Requirement Collection
 Types of Requirements
 Business
 Stakeholder
 Solution
 Functional.
 Non-Functional (Service - Security).

 Transition
 Project Requirements
 Quality Requirements
15
 Requirement Collection
 Types of Requirements
 Cohesive.
 Complete.
 Consistent.

 Correct.
 Feasible.
 Clear.
 Testeable.

16
 Requirement Collection
 How to determine which requirements are
acceptable?
 Business Case.
 Project Charter.
 Scope Statement.
 Project Constraints.

 How to prioritize requirements?

 MoSCoW Technique.

 Timeboxing / Budgeting
17
 Requirement Collection
 Requirement Collection - Techniques
Interviews

Focus Groups

Facilitated Workshops

Group Creativity Techniques

18
 Requirement Collection
 Requirement Collection - Techniques
Group Decision Making
Techniques

Questionnaires & Surveys

Observations

Prototypes

Context Diagram

Document Analysis

19
 Requirement Collection
 Requirements Traceability Matrix
 Document that sets requirement’s atributes
to monitor them.
 Links requirements with general Business
and Project goals.

Requirement 1
Requirement 2
Requirement 3

Requirement n Business and Project Goals

20
 Requirement Collection
 Requirements Traceability Matrix

21
Requirement Collection

22
Activity N° 02
In your group project, determine 15
requirements and classify them in:
Functional, Non-functional, Transition
Management and Business.
Scope Definition

 It is primarily concerned with what

is and what isn’t included in the
Project and its deliverables.

 A detailed Scope, is an important

achivement for the Project.

24
 Scope Definition
 Project Constraints
 These are factors that limit the team’s
options, such as limited resources,
reduced Budget or tight schedules.

25
 Scope Definition
 Project Assumptions

 Are factors or events that you

considered as true or valid in order to
plan your project, but, we should
confirm them in the future.

26
 Scope Definition
 Project Exclusions - Limits
 It represent everything that is not
included in the Project, in other words,
everything that will not be done.

27
 Scope Definition
 Scope Definition Techniques
Expert Judgement

Product Analysis Deliverabl

e

Alternatives Generation

Facilitate Worshops

28
 Scope Definition
 Scope Statement

 Product Scope
 Deliverables
 Product Acceptance Criteria. Scope Statement

 Everything that is not part of the Project –

Exclusions / Limits.
 Constraints.
 Assumptions.

29
 Scope Definition

30
 Create WBS
 Create WBS – Work Breakdown Structure
 Its acronyms in Spanish is EDT (Estructura de
Descomposición de Trabajo).
 The WBS breaks the Project into smaller and more
manageable parts.
 It is a TOP DOWN decomposition tool.
 It is a deliverable-oriented tool.
 The resulting parts are called “Work Packages”.
 All work not included in the WBS, is not part of the
Project.
 It must comply with the 100% rule.

31
 Create WBS
 WBS – Phases

32
 Create WBS
 WBS – Main Deliverables

33
 Create WBS
 WBS – Example - 1
EDT - ESTRUCTURA DE DESCOMPOSICIÓN DE PROYECTO
PROYECTO SISTEMA DE GESTIÓN DE SOLICITUDES

1 4 6 7
2 3 5
Adminis. Organiz. Pruebas y Implementación y Documentos de
Análisis Diseño Capacitaciones
Proyecto Certificación Despliegue Soporte

1.1 2.1 5.1 6.1

3.1 4.1 7.1
Documento - Especificación Plan de Plan de
DERCAS Plan de Pruebas Instructivo
Roles / Respons. Funcional Capacitaciones Despliegue

1.2 5.1.1
3.1.1 4.1.1 6.2
Cronogr. de Cronograma, 7.2
2.2 Prototipos Pruebas Unit. Plan de Soporte
Reunion Seg. Manual de
Análisis de Flujos sedes, medio. Funcional /
Proy. - Ctrl. Procesos
Técnico
Cambios
3.1.2 4.1.2
5.1.2.
Doc. Campos / Pruebas 6.3 7.3
2.3 Presentación
1.3 Eventos Integr. Plan de Manual de
Cronograma de Reportes y
Comunicación a Usuario del
Ausencias Métricas
Usuarios Sistema
Proyecto 5.1.2.
4.2 Casos
Informe de Prácticos
2.4 Pruebas 6.4
1.4 Cronograma de Informe de
Indicadores de Reuniones de Identificación de
Proy (SPI - CPI) Análisis 5.2 Mejoras
4.3 Informe de Identif.
Plan de Mejoras
Certificación 6.5
Esquema de
Certif. - Pase a
PRD
4.3.1
Test Scripts

4.3.2
Cronogr. / Rol
de Certificador

4.3
Resultados
Certificación

34
 Create WBS
 WBS – Example- 2

35
Create WBS
 WBS – Example - 3
PROJECT
IPCPSMMOR

1.0 2.0 3.0 4.0 5.0

INITIATION PLANNING EXECUTION MONITORING AND CLOSING
PHASE PHASE PHASE CONTROL PHASE PHASE

2.1 4.1 5.1

1.1 Project 3.1Estudio de
Project Plan Informacion Project Final
Charter Mercado
Management Checklist

1.2 Scope 2.2 3.2 Bases 4.2 verificar 5.2 Lecciones

Statement ETMs Elaboradas avance Aprendidas
semana
2.3
1.3 5.3 Acta de
Elaboracion 3.3 4.3
Project Aceptacion
de Convocatoria Status Project
Organizational Y cierre
Cronograma
Char
4.4 5.4 Informe
1.4 3.4Buena Pro Learned Final del
Draft Lesson Proyecto
Schedule
5.5 Acta de
3.5 Contrato
Conformidad
Firmado
Del Servicio

3.6 Implementation

3.7
Capacitacion

36
 Create WBS
 Tips to Create a Project WBS and Decomposition
 First level is compounded by Project Phases,
Main Deliverables or Subprojects.
 It can be based on WBS from similar projects
 “Work Package”
 It should be realistic and an estimation must be
done.
 It should not be divided into smaller pieces.
 It can be estimated in terms of time and cost, in
order to complete it.
 It could be outsourced or put under contract.

37
 Create WBS
 Relation about WBS with other Project Components

t N
c l Di etw
o je ro Activity List a g or
r t ra k
P on m
C

Risk
Staffing
Management WBS

Bu n
d ge io
a t
t in m
g Scheduling
sti
E

38
Activity N° 03

In your group project, create the WBS.

Tip: Define the first level and after that the
deliverables for each section
 Create WBS
 WBS Dictionary
 Details scope related to ‘Work Package’.
 Integrates information that is coming from Planning of
the rest of Knowledge Management Areas
 There are 2 versions: Simplified Dictionary, and
Completed Dictionary.
EDT - ESTRUCTURA DE DESCOMPOSICIÓN DE PROYECTO
PROYECTO SISTEMA DE GESTIÓN DE SOLICITUDES

1 4 6 7
2 3 5
Adminis. Organiz. Pruebas y Implementación y Documentos de
Análisis Diseño Capacitaciones
Proyecto Certificación Despliegue Soporte

1.1 2.1 5.1 6.1

3.1 4.1 7.1
Documento - Especificación Plan de Plan de
DERCAS Plan de Pruebas Instructivo
Roles / Respons. Funcional Capacitaciones Despliegue

1.2 5.1.1
3.1.1 4.1.1 6.2
Cronogr. de Cronograma, 7.2
2.2 Prototipos Pruebas Unit. Plan de Soporte
Reunion Seg. sedes, medio. Manual de
Análisis de Flujos Funcional /
Proy. - Ctrl. Procesos
Técnico
Cambios
3.1.2 4.1.2
5.1.2.
Doc. Campos / Pruebas 6.3 7.3
2.3 Presentación
1.3 Eventos Integr. Plan de Manual de
Cronograma de Reportes y
Comunicación a Usuario del
Ausencias Métricas
Usuarios Sistema
Proyecto 5.1.2.
4.2 Casos
Informe de Prácticos
2.4 Pruebas 6.4
1.4 Cronograma de Informe de
Indicadores de Reuniones de Identificación de
Proy (SPI - CPI) Análisis 5.2 Mejoras
4.3 Informe de Identif.
Plan de Mejoras
Certificación 6.5
Esquema de
Certif. - Pase a
PRD
4.3.1
Test Scripts

4.3.2
Cronogr. / Rol
de Certificador
WBS Dictionary
4.3
Resultados
Certificación

40
Create WBS
 WBS - Summary
EDT - ESTRUCTURA DE DESCOMPOSICIÓN DE PROYECTO
PROYECTO SISTEMA DE GESTIÓN DE SOLICITUDES

It is a graphical tool that show the

1 4 6 7
2 3 5


Adminis. Organiz. Pruebas y Implementación y Documentos de
Análisis Diseño Capacitaciones
Proyecto Certificación Despliegue Soporte

1.1 2.1 5.1 6.1

3.1 4.1 7.1
Documento - Especificación Plan de Plan de
DERCAS Plan de Pruebas Instructivo
Roles / Respons . Funcional Capacitaciones Despliegue

1.2
5.1.1 6.2
Cronogr. de 3.1.1 4.1.1 7.2
2.2 Cronograma, Plan de Soporte
Reunion Seg . Prototipos Pruebas Unit. Manual de
Análisis de Flujos sedes, medio. Funcional /

hierarchy within the project.

Proy. - Ctrl. Procesos
Técnico
Cambios
3.1.2 4.1.2
5.1.2.
Doc. Campos / Pruebas 6.3 7.3
2.3 Presentación
1.3 Eventos Integr. Plan de Manual de
Cronograma de Reportes y
Comunicación a Usuario del
Ausencias Métricas
Usuarios Sistema
Proyecto 5.1.2.
4.2
Casos
Informe de
Prácticos
2.4 Pruebas 6.4
1.4 Cronograma de Informe de
Indicadores de Reuniones de Identificación de
Proy (SPI - CPI) Análisis 5.2 Mejoras
4.3 Informe de Identif.
Plan de Mejoras
Certificación 6.5
Esquema de
Certif. - Pase a
PRD
4.3.1
Test Scripts

4.3.2
Cronogr. / Rol
de Certificador

4.3
Resultados
Certificación

 It identifies all the work that needs to be

done in the project.

 It is like a framework that provides to

project team understainding in where
their pieces fit into the overall project

 It is a communication tool for

Stakeholders.

41
Create WBS
 WBS - Summary
 It is a very important tool and it is a
Requirement for all types of project.

 Forces you to think through all aspects

of the project.

 It can be reused for other projects.

 It does not show dependencies.

42
Create WBS
 Scope Baseline

Scope Statement

EDT - WBS

WBS Dictionary

43
Create WBS

44
Scope Validation
 It is the process of formalizing
the acceptance of the complete
project deliverables.
 It verifies the Scope process,
actually involves frequent,
planned-in-meetings with the
customer or Sponsor.
 There is a direct relationship between
Scope Verification process and Quality
Control.
45
 Scope Validation
 Relation with Process ‘Quality Control’
DELIVERABLE
COMPLETED PROCESS Deliverable
Not OK
REPROCESS
QUALITY
CONTROL

Deliverable
Checked

DELIVERABLE
APPROVED
PROCESS
SCOPE
Deliverable
VALIDATION Not OK

46
Scope Validation
 Which elements are necessary to get
deliverables approved?

DELIVERABLE Scope
CHECKED Statement
Traceability
Matrix

WBS

WBS
Dictionary

47
Scope Validation

48
Scope Control

 It is the Process of monitoring the

status of the Project and Product
Scope
 Manages changes to the Scope Baseline.

 Uncontrolled changes are often referred to

as Project Scope Creep.

49
 Scope Control
 Techniques
 Variance Analysis
Project Performance is measured against the
Baseline in order to identify the magnitude of
the variance.
It consider determine:
• The Variance root cause.
• The Degree of variance relative to the Scope Baseline.
• Decides whether corrective or preventive actions are required.

50
Scope Control

51
Scope Management
 Summary
 The Scope is divided into Project and
Product Scope.

 It is very important to determine the work

that will not be included in the Project.

 Using WBS should be imperative, and is a

fundamental tool for planning and
communication with stakeholders.

52
Scope Management
 Summary
 Deliverables and Work Packages are named
as a noun.
 Scope Verification is the process that looks
for a formal approval (of deliverables) by the
Client.

 Uncontrolled changes take us to Scope

Creep.

53
 References

Project Management Institute - PMI. (2017). Project

Management Body of Knowledge. (6th ed). Pensilvania:
PA, USA. Book Editor – PMI Publications.
AXELOS, The Stationery Office (editor) (2018)-
Managing Successful Projects with PRINCE2 2017
Edition-TSO

54
Prepared by Prof Augusto Choy
Thank-you