Professional Documents
Culture Documents
Project Management Framework: Instructor: Phùng Thanh C Ư NG MSC, PMP
Project Management Framework: Instructor: Phùng Thanh C Ư NG MSC, PMP
• While the advice and information in this book are believed to be true and
accurate at the date of publication, neither the authors nor the editors can
accept any legal responsibility for any errors or omissions that may be
made.
1. Project phase
What is it?
• A collection of logically related project activities that culminates in the completion
of one or more deliverables
• The transition from one phase to another within a project's lifecycle generally
involves some form of technical transfer or handoff. These are also called as phase
gate
Construction: Feasibility-> Planning -> Design -> Production -> Turnover -> Maintenance
What is it?
• A review at the end of a phase in which a decision is made to continue to the next
phase, to continue with modification, or to end a project or program.
• Maybe reffered to by other terms: Phase review, stage gate, kill point, phase
entrance or phase exit.
• Decison made maybe: Go, Hold, Kill, Recycle...
2. Project Lifecycle
What is it?
• The series of phases that a project passes through from its initiation to its closure
• There are many different types of project life cycles, depending on the industry ,
or on the organization’s preferences.
Predictive vs Agile
Predictive
Agile/adaptive
Predictive
Agile/ adaptive
Predictive Agile/adaptive
Process-based Principle-based
Definable work High-uncertainty work
Plan-driven Value-driven
Prescriptive Descriptive
3. Process
A systematic series of activities directed towards causing an end result such that one
or more inputs will be acted upon to create one or more outputs
Monitoring
Initiating Planning Executing and Closing
Controlling
• Small project
IT Project: Requirement -> Design -> Program -> Test -> Implement
• Large Project
4. Integration
5. Scope
6. Schedule
Scope 7. Cost
8. Quality
9. Resource
Quality
10. Communication
11. Risk
12. Procurement
Cost Time
13. Stakeholder
Integration
Stakeholders
Benefit
Management
Pre-Project Work Plan Starting the Project
1. Need assessment
• The needs assessment involves understanding business goals and objectives,
issues, and opportunities and recommending proposals to address them.
• The results of the needs assessment may be summarized in the business case
document.
Technological
advance
Customer Legal
request requirements
Organizational
need Social need
2. Project benefits
management plan
• The document that describes how
and when the benefits of the project
will be delivered
• And describes how the benefits will
be measured
• In some organizations, the business
case and benefits management plan
are maintained at the program level.
What?
The document that:
1. Formally recognizes the existence of
the project. (This means that a
project does not exist without a
project charter.)
2. Gives the authority to Project
Manager to apply organizational
resources to project activities
When?
• Take place on a project/or phase
before it becomes official
Who?
• Project Sponsor and Project Manager,
in collaboration with initiating entity
How?
• Validate project alignment with • The Project Charter is issued by a
organizational strategy and expected sponsor, not the project manager
business value.
• A Project Manager is identified and
• Identify key deliverables, initial
milestones, based on the business assigned as early as in the project as
requirements is feasible, and always prior to the
• Identify high level risks, assumptions, start of planning.
and constraints
• Evaluation of the feasibility of new
products or services within the given
assumptions and/or constraints.
• Propose an implementation strategy
• Obtain project charter approval from
the sponsor
• Inform stakeholders of the approved
project charter
1. Project Charter
• Documents the business need or
demand that the project was initiated
to address and the project
justification
• Provides the description, high-level
requirements of the product, service
or key deliverables of the project.
• Formalize the authority assigned to
the project manager.
• Broad enough so it does not NEED to
change as the project changes
2. Assumption log
• High-level strategic and operational
assumptions and constraints
1. Business Documents
1A. Business Case
• Describe why project is worth doing.
(Project benefits)
• Typically, business case is justified by
business need or cost-benefit analysis
1B. Benefits management
plan
• How desired benefits will be
delivered, and measured
2. Agreements
• A contract is an input to this process,
if the project is being done for an
external customer
• Memorandums of understanding
(MOUs)
• Service level agreements (SLA)
• Letter of agreements
• Letters of intent,
• Verbal agreements, email, or other
written agreements.
What?
• It this process, Project Manager and
Project Team identify all people or
organizations impacted by the project
Why?
• An un-identified key stakeholder can
potentially turn high risk to project.
• Identify the appropriate focus for
engagement of each stakeholder or
group of stakeholders.
When?
• As early as possible, preferably during
initiation and definitely prior to
starting of planning.
• Periodically throughout the project
All Rights Reserved © Professional Management Academy – 2020 www.pma.edu.vn 79
13.1 Identify Stakeholders
3. Classify Stakeholders
• Prioritize the key stakeholders to
ensure the efficient use of effort to
communicate and manage their
expectations.
• There are multiple classification
models
4. Define Management Strategy
• How you will communicate with them
1. Stakeholder Register
• Identification information : Name,
organizational position, location, role
in the project, contact information
• Assessment Information : Major
requirements, main expectations,
potential influence in the project,
phase in the life cycle with the most
interest
• Stakeholder Classification :
internal/external,
supporter/neutral/resistor, etc
www.pma.edu.vn