Module 2
PM Process Groups
and
Project Integration
Management
OVERVIEW
▹ Process Management Process Groups
▹ Project Management Methodologies
2
▹ Project Integration Management
1.
Project Management
Process Groups
PM Life Cycle
Project Management Process Groups
4
Initiation Process
▹ the stage in which business
identifies a specific problem to 5
solve or an opportunity to cease
and determines what can be done
to address it.
▹ helps to set the vision of what is to
be accomplished.
Initiation Process
▹ Project is authorized and PMs are
selected. 6
Business Project
Need Charter
BUSINESS NEED Exercise:
Context
Participants
Business Need
7
Business Need
- It initiates the PM lifecycle
- Documents the problem,
opportunity or objective that 8
needs to be addressed by the
project
Includes:
1. CONTEXT - Provides a background
on the current state of the
organization for the given problem,
opportunity or objective 9
2. BUSINESS NEED - States the
problem, opportunity, objective the
project would address
Includes:
3. SUPPORTING FACTS - Provides data
and quantitative measure of the current
situation that needs to be resolved.
4. ASSUMPTIONS - Estimates and other 10
supporting information to provide
decision makers for better
understanding
5. APPROVALS - Approvals of the project
sponsors and stakeholders on the
business need
BUSINESS NEED DOCUMENT:
Graduating College
SAMPLES
Will be finishing junior high school in a couple of
Context months.
Parents are asking what I want to do next.
11
Business Need Get a diploma.
People with diploma gets better job opportunities that
those who don’t have one.
Supporting Facts
Education is the only thing my parents could give me
that other’s could not steal.
Assumptions Have the capabilities to enter and support college.
Approvals Parents, yourself.
Project Charter
- This defines what the project is.
- It is a crucial ingredient in
planning the project because it is 12
used throughout the project
lifecycle.
Includes:
1. EXECUTIVE SUMMARY - Provides an
overview to each section included in
the project charter
2. BUSINESS NEED - States the 13
problem, opportunity or objective
the project would address.
3. PROJECT OBJECTIVES - This
describes the ideal solution to
address the business need.
Includes:
3. IMPACT ASSESSMENT - Defines the
specific benefits or consequences of
the project
4. MEASUREMENT OF SUCCESS - Defines 14
the quantitative measures that would
be used to ensure the successful
implementation of the project
5. SCOPE - Defines what is or what is not
included in the project.
Includes:
6. RISKS - Lists the risk the organization
would take when pursuing the project.
7. TIME CONSTRAINTS - Defines time
constraints if applicable. 15
8. STAKEHOLDER AND SPONSOR
APPROVALS - Approvals of the
business sponsors and stakeholders of
the business need
PROJECT CHARTER DOCUMENT: Graduating College
SAMPLES
Executive This shall provide details to getting a college diploma.
Summary
Business Need Get a diploma.
16
Enter a college where I will be able to learn and pass all
Project
the necessary requirements to get a diploma of the
Objectives
course of my choice.
I will be able to learn things that could be used for work
Impact in the future.
Assessment College would require a lot of resources (time, money,
effort) to finish.
PROJECT CHARTER DOCUMENT: Graduating College
SAMPLES
Measurement of Get at least a grade of 1 for all the required subjects of the
Success course of my choosing.
Scope Getting a diploma of an undergraduate course of my choice.
17
Risk of not graduating high school
Risk of not passing any entrance exam
Risks
Risk of not passing all the required subjects
Risk of not having enough resources to finish the course.
Time Constraints Entrance exams are opening next month.
Stakeholder and Parents, yourself
Sponsor Approvals
Planning Process
▹ the stage in which business
identifies how an action or 18
solution will be done, who will be
responsible, when will it be
implemented and where will it
take place.
Planning Process
▹ Planning through progressive
elaboration. 19
Project Work
Management Breakdown
Plan Structure
Project Management Plan
- It defines how a project is going to
be carried out.
- Essential to keeping a project on 20
track.
- The process of identifying all the
work to be done and organizing it
into a manageable plan
Contents:
PROJECT MANAGEMENT PLAN – Defines
the process by which the team would
work in to complete the project.
PROJECT SCOPE, SCHEDULE and COST 21
– Defines the baseline scope, schedule
and cost of the project. These would
may subject to change through the
course of the project.
Contents:
RISK MANAGEMENT PLAN - Describes
the processes and tools that will be used
to track and manage the identification,
planning, assessment, quantification, 22
response, and mitigation strategy for
each risk in the project.
COMMUNICATION MANAGEMENT PLAN –
Describes the process and tools that will
be used for communication through out
the project
Contents:
ISSUE MANAGEMENT PLAN - Describes
the processes and tools that will be used
to track and manage the prioritization,
delegation, status, and resolution of 23
project issues.
CHANGE MANAGEMENT PLAN -
Describes the processes and tools that
will be used to track and manage the
changes to the project, the impact and
approvals required for each change.
Contents:
QUALITY MANAGEMENT PLAN -
Describes the processes and tools that
will be used to track and manage quality
throughout the project. Includes quality 24
assurance and quality control.
REQUIREMENT MANAGEMENT PLAN -
Describes the processes and tools that
will be used to track and manage
product requirements, definition, and
design specifications.
Contents:
RELEASE MANAGEMENT PLAN -
Describes the processes and tools that
will be used to track and manage
multiple product versions that will be 25
implemented as a suite of products in a
release.
COST MANAGEMENT PLAN - Describes
the processes and tools that will be used
to track and manage costs between
budgeted, planned, and actual costs.
Contents:
HUMAN RESOURCE MANAGEMENT PLAN
- Describes the processes and tools that
will be used to track and manage human
resources for the duration of the 26
project. It is also common to list the
roles, requirements, and team members
in this section of the Project Plan.
Contents:
- Others include schedule management
plan, procurement management plan,
configuration management plan,
process improvement plan, and 27
escalation management plan.
Work Breakdown Structure
- It is a deliverable-oriented
hierarchical decomposition of the
work to be executed by the project 28
team to accomplish the project
objectives and create the required
deliverables.
- To establish a common
understanding of project scope
WORK BREAKDOWN STRUCTURE: Graduating College
Get a Diploma
INITIATION PLANNING EXECUTING CLOSING
Get approval List of college Take entrance Graduate
from parents and university exam March 29
Study of
entrance Enter college
exams
Take all
Choose
necessary
course to take
classes
Pass thesis
Executing Process
▹ the stage where work is actually
done. 30
▹ Project management plan is being
executed to keep everyone on
track.
▹ Depend on the methodology
chosen.
Monitoring and
Controlling Process
▹ this is where the project manager
asses the overall performance of 31
the project and makes necessary
adjustments to keep projects in
track to get back on track.
▹ Depend on the methodology
chosen.
Closing Process
▹ the stage in which projects are
officially closed and necessary 32
sign-off and acceptance are
gathered from project owners and
stakeholders.
▹ Usually retrospective happens.
Key Persons of a Project
▹ These are the people that
influences the project. 33
▹ These are defined during
planning.
Key Persons of a Project
KEY PERSONS OF A PROJECT
RESPOSNIBILITIES
Provides leadership to the project
PROJECT
Communicates the vision of the project to the organization
SPONSOR
Provides objective decisions through the project lifecycle
34
Gather and manage necessary resources to complete the
project
PROJECT Understands the necessary skill required for the project
MANAGER
Ensures that the project is on time and on budget
Ensures to maintain a fair environment to participate
PROJECT Have a say on the solution that will be implemented.
STAKEHOLDERS Affected by the implementation. Actual users.
ROLES/RESPOSNIBILITIES
KEY PERSONS
Provides OF A PROJECT
decisions to functionality requirements or
Project Sponsor
disputes of the project
Allocates project members to different project teams Project Manager
Updates project team on deadlines and project
Project Manager
milestones 35
Signs Off on project documentation Project Stakeholders
Does User Acceptance Testing to the acquired system Project Stakeholders
Provides project team with the vision on what the
Project Sponsor
system would be
Reports to management on the progress of the project Project Manager
Insights on the project may affect implementation Project Stakeholders
2.
Project Management
Methodologies
Methods andFrameworks
How to choose?
▹ Cost and budget
▹ Team size 37
▹ Ability to take risks
▹ Flexibility
▹ Timeline
▹ Client and stakeholder collaboration
Activity
Who can do it faster?
[Link]
aF3CZfJm7-BKuJJ2lNo_W2ckcElE/edit?usp=sharing
38
Make a good plan and execute it
▹ Traditional approach to project
management. 39
▹ Tasks are completed in a linear,
sequential manner.
▹ Each stage must be completed
before moving to the next.
Fail fast, fail cheap.
▹ It is a flexible, iterative design and
build process. 40
▹ A series of tasks that are
conceived, executed and adapted
as the situation demands, rather
than a pre-planned process.
▹ Uses iterations.
Enable small, cross-functional, self-managing
team to deliver fast
▹ Is a form of Agile PM.
▹ Has a set of timeboxed events to 41
follow and is managed by a Scrum
Master.
▹ Sprint planning, sprint iteration,
daily stand up, sprint retrospective.
▹ Uses sprints. (1-2 weeks)
Visibility is key
▹ Focused on Lean principles and a
strict process to increase 42
efficiency and quality.
▹ Visualizing the workflow, limiting
work in progress, measuring the
lead time, making process policies
explicit and continually evaluating
improvement opportunities.
Improved visibility
▹ Combination of Scrum and Kanban.
▹ Combines the daily stand up and 43
retrospective of Scrum and the
flexibility of Kanban on filling the
backlog and tasks assigned to the
team.
Streamlining and eliminating
waste
▹ Focused around the theme of
efficiency. 44
▹ It starts by identifying value and
then maximizes it through
continuous improvement by
optimizing the flow of value and
eliminating wastage.
Robust programming
▹ A software development project
management methodology 45
▹ Focuses on defining values and
processes to improve software
quality and ensure responsiveness
to evolving customer requirements.
Any questions? 46
3.
Project Integration
Management
First Knowledge Area
48
Project Integration
Management
▹ The process, where a project
manager receives the authority to 49
track and coordinate all activities
and functions taking place at
different organization levels. It
mainly focuses on ensuring proper
coordination between project
activities. (PMBoK)
Project Integration
Management
▹ What should be implemented with
the aim to create harmony within 50
the project.
▹ Process of evaluating processes,
make trade-offs, and managing
changes.
Project Integration
Management
51
Thank you!
Any questions? 52
Sources
▪ [Link]
structure/#:~:text=A%20Work%20Breakdown%20Structure%20(WBS,and%20create%20the%20required%20delivera
bles.&text=All%20the%20work%20contained%20within,estimated%2C%20scheduled%2C%20and%20budgeted.
▪ [Link]
▪ [Link]
▪ [Link]
▪ [Link]
53
