Agenda
0 Instructor Introduction
3 minutes
0 Agenda review
2 minutes
0 Chapter of the week
50 minutes
0 Q&A of chapter
10 minutes
0 Break
10 minutes
0 Exercises
25 minutes
0 Round table
15 minutes
0 Closure
5 minutes
Developing the Project Scope
Statement
2
Content
0 Develop Project Management Plan Process
0 Collect Requirements Process
0 Define Scope Process
0 Create WBS Process
Developing the Project Scope
Statement
Initiation
Planification
Execution
Monitoring
Closing
3
Develop Project Management Plan
0 This process describes, integrates, and coordinates baselines and
subsidiary plans for the processes determined to be used for a
project.
0 According to the PMBOK® Guide, it defines how the project is
executed, how it’s monitored and controlled, and how it’s closed.
It also documents the outputs of the planning group processes.
Developing the Project Scope
Statement
Initiation
Planification
Execution
Monitoring
Closing
4
Develop Project Management Plan
Project Management Plan should include the following elements (but is not limited to them):
0 Processes to be used to perform each phase of the project.
0 The life cycle to be used for the project and for each phase.
0 Tailoring results the project team will define.
0 Methods for executing the work of the project to fulfill the objectives.
0 Change management plan describing methods for monitoring and controlling change.
0 Configuration management.
0 Methods for determining and maintaining the validity of performance baselines.
0 Communication needs of stakeholders and the techniques to fulfill those needs.
0 Management reviews of content, issues, and pending decisions.
0 Subsidiary plans.
0 Other planning documents (e.g. Milestones list, resource calendar, schedule baseline, cost baseline, quality
baseline, Risk register, scope baseline)‫‏‬.
Developing the Project Scope
Statement
Initiation
Planification
Execution
Monitoring
Closing
5
Collect Requirements Process
0 The main purpose of this process is to define and document the
project sponsor, the customer, and the stakeholder’s
expectations and needs for meeting the project objective.
Developing the Project Scope
Statement
Initiation
Planification
Execution
Monitoring
Closing
6
Collect Requirements Process
Requirements Documentation may include at least:
0 Business need for the project and why it was undertaken
0 Project objectives and business objectives the project hopes to fulfill
0 Functional requirements
0 Non-Functional requirements
0 Quality requirements
0 Acceptance Criteria
0 Business rules
0 Organizational areas and outside entities impacted
0 Support and training requirements
0 Assumptions and constrains
0 * Signature of key stakeholders indicating acceptance of the requirements
Developing the Project Scope
Statement
Initiation
Planification
Execution
Monitoring
Closing
7
Define Scope
0 Through this process it’s developed and documented detailed
description of the deliverables of the project and the work
needed to produce those deliverables.
0 This process is progressively elaborated as more detail
becomes known.
Developing the Project Scope
Statement
Initiation
Planification
Execution
Monitoring
Closing
8
Define Scope: tools & techniques
Product Analysis: Is a method for converting
the product description and project
objectives into deliverables and requirements
and might include:
Alternatives Identification: Is a technique
used for discovering different methods or
ways of accomplishing the work of the
project.
• Value analysis
• Functional analysis
• Requirements analysis
• System-engineering techniques
• Systems analysis
• Product breakdown
• Value engineering techniques
• Brainstorming
• Lateral thinking
Developing the Project Scope
Statement
Initiation
Planification
Execution
Monitoring
Closing
9
Define Scope: outputs
0 The purpose of the Project Scope Statement is to provide a common
understanding of the project scope among stakeholders.
0 It should include the following elements:
0
0
0
0
0
0
Product Scope description
Product acceptance criteria
Project deliverables
Project exclusion
Project constrains
Project assumptions
0 Approval requirements are not an official component according to the
PMBOK Guide. It refer to how the objectives, deliverables, documents
and other outcomes of the project will be approved.
Developing the Project Scope
Statement
Initiation
Planification
Execution
Monitoring
Closing
10
Create WBS
0 It’s a deliverable-oriented hierarchical decomposition of the
work to be executed by the project team, to accomplish the
project objectives and create the required deliverables.
Developing the Project Scope
Statement
Initiation
Planification
Execution
Monitoring
Closing
11
Create WBS
Decomposition
1. Identify the
deliverables and
work.
2. Organize the
WBS.
4. Assign
identification
codes.
Developing the Project Scope
Statement
Initiation
Planification
3. Decompose the
WBS components
into lower-level
components.
5. Verify the WBS.
Execution
Monitoring
Closing
12
Create WBS
Decomposition
Project
Phases
Deliverables
Work
Packages
•Output of
Scope
Management
Decomposition
Activities
•Output of
Time
Management
Decomposition
Developing the Project Scope
Statement
Initiation
Planification
Execution
Monitoring
Closing
13
Questions or comments
Elapsed time
55 minutes
14
Break: 10 minutes
Elapsed time
65 minutes
15
Exercises
Elapsed time
75 minutes
16
Round table
Elapsed time
100 minutes
17
Tips for the exam
Elapsed time
115 minutes
18
0 The WBS is created by decomposing large work products into
work packages.
0 The WBS Dictionary is a description of each work package
listed in the WBS.
0 The inputs to WBS creation are the outputs to the Define Scope
and Collect Requirements processes the
Document, and the Project Scope Statement.
Creating the Project Charter
Requirements
19
0 Bibliography:
0 Heldman, Kim. PMP® Project Management Professional Exam
Study Guide. Sybex. Wiley Publishing, Inc. 5th ed. 2009.
0 Project Management Institute, Inc. A guide to the Project
Management Body of Knowledge (PMBOK). 4th ed. 2008.
0 Authors:
0 Iván Guillén Franco, PMP®
0 Luis Catalán, PMP®
0 Roberto Burgos, PMP®
20