PMP Summary
PMP Summary
PMP Summary
PMP
Management
Preparation
Professional (PMP)
Welcome Kit
Preparation
Welcome Kit
Day 01
Day
01 Pre-read:
Pre-read:
Project
Management
Project Management
- Introduction,
Introduction,
Initiation
Planning- I-Process
I Process
Initiation &&Planning
Group
Group
Global Registered
Education Provider
| Confidential
Contents
1. INTRODUCTION ........................................................................................................................ 2
2. PROJECT MANAGEMENT - INTRODUCTION ................................................................................... 3
PMBOK Guide ....................................................................................................................... 3
Project & Project Management.................................................................................................. 4
Constraints in a Project ............................................................................................................ 5
Project Managements Relationships .......................................................................................... 5
EEF, OPA & PMO ..................................................................................................................... 6
Role of a Project Manager ........................................................................................................ 6
3. INITIATING PROCESS GROUP ...................................................................................................... 7
Develop Project Charter ........................................................................................................... 8
Identify Stakeholders ............................................................................................................... 8
4. PLANNING PROCESS GROUP - I.................................................................................................... 9
Develop Project Management Plan............................................................................................. 9
Plan Scope Management ........................................................................................................ 10
Collect Requirements ............................................................................................................. 10
Define Scope ........................................................................................................................ 11
Create WBS.......................................................................................................................... 11
1. INTRODUCTION
CONGRATULATIONs on your first step to become a Project Management Professional (PMP)!
Progressive Ventures welcomes you to the beginning of one of the most exciting professional
expedition. When you reach the PMP certification summit, you would have actually passed an exam
of international repute and recognition. The PMP certification demonstrates your knowledge and
application of project management best practices in the real world.
So, how difficult is this journey?
Well, at Progressive Ventures, we have had the opportunity to engage more than 5000 PMP aspirants
over 7 years. From our experiences, there are ONLY 2 reasons why some of our participants find the
journey challenging - lack of real world understanding of project management and lack of familiarity
with PMBOK1 terminology.
Stay tight! We have good news!
Our PMP success stories demonstrate that it is possible to overcome these 2 challenges. All that you
require is in-depth discussions with real world project practitioners and a focused learning effort of
the PMBOK Guide. Hence, we have designed this 4 day intensive training, by selecting real world
practitioners as faculties and providing 24x7 training aids such as e-learning for your learning support.
So, get ready to absorb some project management concepts!
Day 01 Topics
One the first day, we will explore Chapters 1 to 5 of PMBOK
Develop PMP
Define Scope
Collect Requirements
Create WBS
PMBOK: A Guide to the Project Management Body of Knowledge or popularly known as PMBOK Guide, is recognized as a global
standard for the project management profession. It presents a set of standard terminologies and guidelines for project management. It is
the study reference recommended by Project Management Institute (PMI) for Project Management Professional (PMP) certification.
PMBOK Guide is currently into its 5th edition.
Project Integration
Management
Initiating
Process
Planning
Process
Executing
Process
Monitoring and
Control Process
Closing
Process
Group
Group
Group
Group
Group
Total
Project Scope
Management
Project Time
Management
Project Cost
Management
Project Quality
Management
Project Human
Resources
Management
Project
Communication
Management
Project Risk
Management
Project
Procurement
Management
Total
24
11
4
2
47
Now that we have an idea of the PMBOK guide, lets venture into project!
The temporariness of a project is not just limited to its pre-set start & finish dates. The resources
working on the project and also the opportunity window that exists for the projects products are
temporary as well.
Secondly, the uniqueness of the outcome of the project- this is what differentiates a project from
the repetitive & ongoing nature of operations, even though projects & operations might intersect at
various points in the product life cycle.
[Pause for a moment here and list down few projects and related details that you have been involved
in the last 5 years or more. This will come in handy when you are submitting your experience for
verification to the PMI.]
Now that you have grasped what a project really is, lets discover what Project Management is all
about!
Simply said,
Project Management is the application of the knowledge about the various processes with the
help of distinct project management tools & techniques in real world projects systematically.
As a practitioner, one can use these tools & techniques, in isolation or in combination, which are in
accordance with the compulsions within ones project organization.
Constraints in a Project
We know what a Project is! In addition, what project management means! Still executing a project to
completion is a challenge in many organizations! Is there any reason for this?
Well, the reason is one word CHANGE! As many would agree, we live in a dynamic world; this mainly
affects 3 factors in a project, namely, Scope, Time & Cost. These 3 factors are commonly known in the
project world as Triple Constraints.
Constraints depend on the characteristics specific to the project and the circumstances influencing the
project. In addition to the known Triple constraints, the PMBOK Guide identifies 3 more constraints
- Quality, Resource & Risk. The dynamic nature of inter-dependencies among these constraints is what,
we, as Project Managers need to deal with our team on a day to day basis.
Apart, from these relationships, another important factor that can influence project management is
the organizations structure. Just as how the shape of a container influences the shape of the liquid
it holds, the organizational culture, style & structure influences the performance of the project.
Functional
Weak
Organizational Structure
Matrix Structure
Balanced
Strong
Low to
Moderate to
moderate
High
Low to
Moderate to
moderate
High
Project
Mixed
Manager
Projectized
Little or
None
Little or
None
Functional
Manager
Functional
Manager
Part-time
Part-time
Full-time
Full-time
Full-time
Project Management
Administrative Staff
Part-time
Part-time
Part-time
Full-time
Full-time
Resource Availability
Limited
Limited
High to
almost Total
High to
almost Total
Project
Manager
The Project Management Office (PMO) is an important organizational body that provides a range
of support functions that also includes ownership EEF & OPA. In strong matrix or projectized
organizations, this function is further empowered to actually decide which projects the
organization should undertake, to control the strategic resources and to monitor the performance
at the enterprise level.
Initial scope is defined & initial financial resources are committed and the Project Manager is
selected. He is given the authority to apply organizational resources to the project (within the
Project Charter)
Internal & external stakeholders who will interact/influence the overall outcome of the
project are identified (within the Stakeholder Register)
When the charter is approved, the project becomes officially authorized. Although the project
management team may help write the project charter, approval & funding are external to the projects
boundaries. Initiating processes are revisited at the start of every subsequent phase in a multi-phase
project to validate the decisions made during the original Develop Project Charter &
Identify Stakeholders processes. This helps keep the project focused on the business need, verify the
success criteria and review the influence & objectives of the project stakeholders. A decision is then
made as to whether the project should be continued or not.
Stakeholder/customer buy-in is achieved primarily by involving the customers and other stakeholders
during initiation. This greatly improves the probability of shared ownership, deliverable acceptance
and customer & other stakeholder satisfaction. Initiating processes can be performed by
organizational, program/portfolio processes external to the project. Pre-project activities such as
documenting high level requirements, feasibility of the new undertaking, and clear descriptions of the
project objectives including reasons why a specific project is the best alternative to satisfy the
requirements may all be undertaken prior to the start of a new project with the larger organization.
This pre-project documentation may also include initial project scope statement, deliverables, project
duration, a forecast of the resources for the organizations investment analysis.
Identify Stakeholders
Performing this process involves,
Identifying all people/organizations impacted by the project and documenting relevant
information regarding their interests, involvement, & impact on project success
Project Stakeholders are individuals and/or customers and/or sponsors and/or the performing
organizations and/or the public whose interests may be positively or negatively affected by the
execution/completion of the project.
The stakeholders may be at different levels and possess different authority levels and they may also
exert influence over the project and its deliverables. Hence, it is critical for project success to develop
a strategy by identifying them early on in the project and analyze their levels of interest, expectations,
involvement, importance and influence, so as to maximize positive influences and mitigate negative
impacts. This strategy helps the Project Manager focus on the relationships necessary to ensure
project success and periodically review & adjust the strategy for potential changes.
In Day 01, we will cover 5 out of the 24 processes belonging to the Planning Process Group. These 5
planning processes are from the following 2 knowledge areas namely Integration and Scope.
The Planning Process Group consists of those processes (covering aspects of scope, time, cost, quality,
resources, communication, risk, procurement, & stakeholder) involved in establishing the total scope
of effort, define & refine the objectives & develop the course of action required to attain those
objectives. The primary deliverables of this process group are the project management plan and the
project documents, which undergo lot changes (reflecting the approved change requests) throughout
the project life cycle triggering the need to revisit one or more planning processes or possibly the
initiating processes.
This progressive detailing of the project management plan is often called rolling wave planning,
indicating planning & documentation are iterative & ongoing processes thus improving the precision
with respect to schedule, costs & resource requirements to meet the defined scope. The feedback &
refinement process cannot continue indefinitely & the organizations dictate will decide when the
initial planning ends. But all appropriate stakeholders must be involved while planning & developing
the project management plan & project documents. Important influencers of this exercise are the
nature & environment of the project, established project boundaries and appropriate monitoring &
controlling activities.
10
These plans when integrated together results in the integrated project management plan. This plan
also addresses two more important aspects:
1. It contains 3 baselines, namely the scope baseline, schedule baseline and the cost
performance baseline.
2. This plan should also address how you and your team will tailor the project management
processes so as to make it applicable to your project.
Collect Requirements
The process of determining, documenting, and managing stakeholder needs and requirements
to meet project objectives
Now, we have planned on how to analyze document and manage requirements in the previous
process. This process involves executing the requirements management plan. The key benefit of this
process is that it provides the basis for defining the managing the project scope including the product
scope.
As a project manager, one should encourage active stakeholder involvement during this process.
Since active stakeholder involvement helps in decomposing the needs to requirements, which is the
key to the success of the project!
Requirements documentation and Requirements traceability matrix are the main outputs of this
process. The requirement documentation describes how individual requirements meet the business
need of the project. The requirements traceability matrix is a grid which links product requirements
from their origin to the deliverables that satisfy them.
11
Define Scope
The process of developing a detailed description of the project and product
Now that we have collected the requirements of the project and have understood the business need,
the next step is to create the boundaries by defining which of the requirements is included in or
excluded from the project scope. The main output of this process is the project scope statement. The
project scope statement is the description of the project scope, major deliverables, assumptions, and
constraints
Create WBS
The process of subdividing project deliverables and project work into smaller, more
manageable components
After defining the boundaries for the project in the previous process, we now move on to breaking
down the scope to management units in Create WBS process. The PMBOK Guide describes Work
Breakdown Structure (WBS) as the deliverable oriented hierarchical decomposition of project work.
The planned work contained in the lowest level of WBS component is called work packages. When we
decompose a project scope to work packages using top- down approach or bottom up approach, the
resulting hierarchical structure is referred to as the WBS structure. The WBS dictionary is a document
that provides detailed deliverable, activity and schedule information about each component of the
WBS.
The Project Scope Statement, the WBS and the WBS Dictionary together are known as the Scope
Baseline.
This completes our agenda for Day 01 of PMP preparation training! We will next, explore
the second half of Planning process group on Day 02.
We look forward to discussing your questions/queries in the training!