PMBOK Study Notes PDF

PMP Exam
Based on A Guide to the

PROJECT MANAGEMENT
BODY OF KNOWLEDGE
(PMBOK® GUIDE)
Sixth Edition
Project Management Framework
Project
 Project – a temporary endeavor to create a unique product, service or result

(or enhancement of existing services/products (e.g. v.2 development is a
project) ) — may be collectively termed as deliverable — (vs.
ongoing operations which manage processes in transforming resources into
output) sometimes may involve handing over the deliverable to the operation
teams for continuous operation
 Project drives changes in the organization and often is a means to create
business values and to achieve organizational goals — the net quantifiable
benefit derived from a business endeavor which can be tangible or intangible.
 Projects operate in an environment that may have favorable or unfavorable
impacts on them. Two major categories are:
o Organization Process Assets is a major input in all planning process,
which may be kept at PMO, directly related to project
management, including Processes and Procedures (including
templates (e.g. WBS, schedule network diagrams, etc.), procedures for
issuing work authorizations, guidelines, performance measurements)
and Organizational Knowledge Repositories
o Enterprise Environment Factors (often are constraints) are influences
not under control of the project team that will affect the project, either
intra-organization and extra-organization, e.g. organizational culture,
organization structure, existing human resources, work authorization
system, PMIS, market conditions, legal requirements, technology
 EEF are inputs for all initiating, most planning process, not much
in the executing/controlling process, none in closing process
 Projects often involve more risks and uncertainties than operations and thus
require more planning
 The following factors influence the operation of the organization which may
lead to the need for projects:
o Regulatory/legal/social requirements changes
o Stakeholders needs/requests
o Changes in technology/business
o Improvements, rectification and enhancements to
processes/products/services
Project Management Solutions BD

2
 A project can be subdivided into phases, each phase is a collection of logically
related project activities that result in the completion of deliverable(s).
Towards the end of each phase is a ―Phase Gate‖ which determines whether
the project will go on or not.
 Process – a package of inputs, tools and outputs, there are 49 processes
defined by PMI. Processes are grouped in the PMBOK® Guide into 5 Process
Groups (NOTE: Process groups are not the same as project phases).
 Portfolio > Program > Project
o Program – a group of coordinated projects, taking operations into
account, maybe with common goals, achieving benefits not realized
by running projects individually, if only the client/technologies/resource
are the same, then the projects should be managed individually instead
of a program
o Portfolio – a group of programs and/or projects to achieve
organizational strategic goals within the organization with a view to
maximizing the value to the organization
o Actively coordinating and managing portfolios, programs and projects
through organizational project management (OPM) best position the
organization to achieve strategic business goals.
 Use of portfolio/program/project management to bridge the gap between
organizational strategy and business value realization
Project Management
 Project Management – the application of (all appropriate) knowledge, skills,

tools & techniques and whatsoever to manage project activities with a view to
meet the project requirements and achieve customer satisfaction
 The most important task is to align stakeholder expectations with the
project requirements, around 90% of the PM‘s work is related to
communication with stakeholders
 PMBOK® Guide is a framework/standard but not methodology (agile,
scrum, PRINCE3, etc.) — A framework allows flexibilities while a methodology
would require the use of a predefined system of practices, techniques,
procedures and rules.
o Project management emphasizes tailoring — selecting the appropriate
project management processes, inputs, tools, techniques, outputs and
life cycle phases according to the unique nature of each individual
project.

3
 Competing constraints: time, cost, scope, quality, risk, resources
 Project Management Business Documents
o Project Business Case — documents the economic feasibility vs benefits of
the project and is used for authorization of project management activities.
o Project Benefits Management Plan —describes how and when the benefits
of the deliverables of the project will bring and describes how to measure
the benefits (also including the alignment with organization strategies,
assumptions and risks)
o Project Charter — authorizes the project and names the project manager
o Project Management Plan — how the project will be performed and
managed – documents assumptions & decisions, helps communication
between stakeholders, goals, costs & time scheduling (milestones), project
management system and subsidiary management plans and documents
o Project Success Measures — project success is now more inclined to be
measured by considering the achievement of project objectives as
documented in this document
The Project Management Process Groups
1. Initiating
2. Planning
3. Executing
4. Monitoring and Controlling
5. Closing
 Planning and Executing are iterative. Monitoring and Controlling is exercised

over Planning and Executing.
 A phase is not a process group. The 5 process groups will usually be
included in any single phase.
 The process groups are not to be carried out in sequence as some are iterative
and some are overlapping.
 The PM should identify and choose the most appropriate processes in each
process group to fit in each individual project (tailoring)
 The deliverables from each phase/project are often incremental in nature
meaning the deliverables will be continually refined/enhanced by each
phase/project.

4
Initiating
 align project purposes with stakeholders’ expectations

 assign a project manager
 identify stakeholders and develop the project charter
 document business case (created by an initiator, maybe well before the
initiating process group) and cost-benefit analysis, identify high-level risks,
identify project selection criteria
 early in the process, the staffing, costs and chance of success are low, risk and
stakeholder influence is high
 may be performed at portfolio/program level (i.e. outside the project‘s level of
control)
Planning
 create Project Management Plan [why the project? what to deliver? who
does what? when be accepted? how to execute?], subsidiary documents
(schedule baseline, cost baseline, performance management baseline,
scope baseline (scope statement, WBS, WBS dictionary) and subsidiary
management plans (scope, schedule, budget, quality, human resources [roles
& responsibility, organization chart and staffing management plan include the
staff need, rewards, safety and training need] , stakeholder, requirements,
process improvement, communication, change, risk and procurement) – all are
not finalized until a thorough risk management has been performed, need to
be approved before work begins
 all plan and documents can be formal or informal, generalized or detailed,
depending on needs (tailoring)
 Project Management Plan may be continually updated during the project
with rolling wave planning / progressive elaboration
 obtain approval of the plan from designated stakeholders, changes to the
project management plan and subsidiary documents/plans need formal
procedures described in the change control system
 hold the kick-off meeting
 planning process group is MOST important for project management, with
around 1/2 of all the 49 process in this group
 may need re-planning when significant changes to the baseline is observed in
the executing/monitoring processes

5
Executing
 coordinating human/infrastructure resources in accordance with the project

management plan
 updates and re-baselining the project management plan and subsidiary
management plans when needed
 normal execution, manage contracts, acquire, develop & manager project
team, perform quality assurance and manage stakeholder expectation/
communication
 direct and manage project work
 continuous improvement process (quality assurance)
 use up the largest share of resources here in the Executing process group
Monitoring and Controlling
 measure performance, address change requests, recommend corrective/

preventive measures and rectify defects
 usually performed at regular intervals
 control the quality, inspection and reporting, problem-solving, identify new
risks
 reassess control process
 should there be any internal deviance from the stated plan, the PM should
make corrections (use contingency reserve if necessary)
 monitor and control project work and integrate change control
 make sure only approved changes (through integrated change control) are
incorporated
Closing
 either project finished or cancelled

 final product verification, contract closure, produce the final report (closeout
documentation), obtain formal acceptance, archive, release resources, close
project
 feedback, review and lessons learned (about the process), transition of
deliverables to operation

6
Knowledge Areas
1. Project Integration Management – assemble and combine all the various

parts of the project into a coherent whole
2. Project Scope Management – plan, execute and control the project scope
3. Project Schedule Management (formerly Project Schedule Management) –
plan, execute and control the project schedule
4. Project Cost Management – plan, execute and control the project cost
5. Project Quality Management – plan, execute and control the project quality
6. Project Resource Management (formerly Project Human Resource
Management) – plan, execute and control the project resources including
human, equipment and other physical resources
7. Project Communications Management – plan, execute and control the
project communication (channels, methods, etc.)
8. Project Risk Management – plan, execute and control the project risk control
measures
9. Project Procurement Management – plan, execute and control the project
procurement
10. Project Stakeholder Management – plan, execute and control how to best
dealing with project stakeholders
49 processes of Project Management
The 49 processes of project management are grouped under one of the 5 process
groups/10 knowedge areas listed above and will be discussed in more details next.
3 new processes are added while 1 deleted in PMBOK® Guide 6th edition, resulting
in a total of 49 processes from 47 processes in PMBOK® Guide 5th edition:
 Added processes
o Manage Project Knowledge – in Executing Process Group / Project
Integration Management knowledge area
o Implement Risk Responses – in Executing Process Group / Project Risk
Management knowledge area
o Control Resources – in Monitoring and Controlling Process Group /
Project Resource Management knowledge area
 Deleted process
o Close Procurement – activities now are included in Control
Procurements and Close Project or Phase process

7
 Naming Changed processes
o Perform Quality Assurance → Manage Quality
o Plan Human Resource Management → Plan Resource Management
o Acquire project Team → Acquire Resources
o Develop Project Team → Develop Team
o Manage Project Team → Manage Team
o Control Communications → Monitor Communications
o Control Risks → Monitor Risks
o Plan Stakeholder Management → Plan Stakeholder Engagement
o Control Stakeholder Engagement → Monitor Stakeholder
Engagement
Each project management process is now categorized into:
 used once or at predefined points in the project

 done periodically as needed
 done continuously throughout the project
It is important to understand the differences between PMBOK® Guide 6th edition

and PMBOK® Guide 5th edition (in particular what new things have been added) as
PMI usually emphasizes on these ―new‖ things in the new PMP® Exam 2018.
Project Management Tools and Techniques (T&T)
In the PMBOK® Guide 6th edition, many tools and techniques have been grouped
according to their purpose with a view to better supporting tailoring:
 Data gathering
 Data analysis
 Decision making
 Communication
 Interpersonal and team skills
 Communication skills
Organization System
 The organizational system determines the power, influence, competence,

leadership and political capabilities of the people who can act within the
system. e.g.

8
o Management Elements — general management principles/rules of the
organization, e.g. disciplinary action, division of skills, authorization
model/practices, communication channels
o Organizational Governance Frameworks — framework/processes
describing how authority within the organization is exercised
o Organizational Structure Types
 Organic or Simple
 Virtual
 Project oriented (project manager has the ultimate authority
over the project, team members are often collocated)
 Matrix (Strong, Balanced, Week)
 Functional
 Composite/Hybrid – a combination of different types,
depending on the actual need
 PMO
 Tight Matrix = co-location, nothing to do with the organization type (not
necessarily a matrix org.)
 Functional organizations => the project manager has little authority, often
called project expeditor (no authority) or coordinator (little authority), project
coordination among functional managers
 Matrix organization => multiple bosses and more complex
 Project Management Office (PMO) – standardizes governance, provides
training, shares tools, templates, resources, etc. across all
projects/programs/portfolios
o 3 forms: supportive, controlling and directive (lead the project as PM)
o functions: training, resource coordination, methodology, document
repository, project management oversight, standards, career
management of PMs
o may function as a stakeholder / key decision maker (e.g. to terminate
the projects)
o control shared resources/interdependence across projects at the
enterprise level
o play a decisive role in project governance

9
Role of the Project Manager
 Project Manager: an individual assigned by the organization to lead the team

and is responsible for achieving project objectives
o is the leader of the project irrespective of the authority
o should consider every process to determine if they are needed for
individual projects (tailoring)
o the exact role of project manager is to be tailored to suit the needs of
individual organizations and projects
o may report to the functional manager, program manager, PMO
manager, operation manager, senior management, etc., maybe part-
time or devoted
o identifies and documents conflicts of project objectives with
organization strategy as early as possible
 Skills required of project managers:
o Technical project management — process tailoring, planning,
managing schedule/cost/resources/risk
o Leadership — communication (within team and with stakeholders),
team building, motivation, influencing, coaching, trust building, conflict
management, negotiation
o Strategic and business management — be aware of the high-level
strategies of the organization and effectively implement
decisions/actions that align with strategic goals (Organization Strategy
may be expressed through mission and vision)
 Project Manager must balance the constraints and tradeoffs, effectively
communicate the info (including bad news) to the sponsor for informed
decisions
 Project Manager needs to involve project team members in the planning
process
 Project Manager needs to perform integration at process level, cognitive level
and context level
 Project Team includes Project Manager, project management staff, project
staff, PMO, SME (subject matter experts can be outsourced), customer
representative (with authority), sellers, business partners, etc., maybe virtual
or collocated
 Senior management must be consulted for changes to high-level
constraints
 Leadership vs Management:

10
o Lead: guide through interactive discussion from one point to another
o Manage: direct a person to perform a set of expected behaviour
 Leadership styles:
o Laissez-faire
o Transactional
o Servant leader
o Transformational
o Charismatic
o Interactional
Project Life Cycle vs Project Management Life Cycle vs Product Life Cycle
 Project Life Cycle: includes: initiating, planning and organizing, carrying

out/executing work, closing the project. Project life cycles are independent of
a product life cycle.
 Within a project life cycle, there can be one or more phases of the
development of the product, service, or result (a.k.a. development life cycles)
with the following models:
o Predictive [plan driven/waterfall] – scope, time and cost determined
early in the lifecycle, may also employ rolling wave planning
o Iterative – repeat the phases as understanding of the project increases
until the exit criteria are met, similar to the rolling wave planning, high-
level objectives, either sequential/overlapping phase,
scope/time/resources for each phase may be different
o Incremental – features/scope are added to each incremental cycle
o Adaptive [change driven/agile] – for projects with high levels of
change, risk and/or uncertainty, each iterative is very short (2-4 weeks),
work is decomposed into product backlog, each with a production-
level product, scrum is one of the most effective agile methods,
stakeholders are involved throughout the process, time and resources
are fixed, allow low change cost/keep stakeholder influence high
o Hybrid
 The life cycle chosen must be suitable for the intended deliverable and flexible
enough to deal changes.
 each project phase within the product lifecycle may include all the five
project management process groups

11
 Product life cycle: development > production > adoption & growth >
maturity > decline > end of life
Code of ethics and professional conduct
The Code of Ethics and Professional Conduct help an individual in making wise
decisions, particularly when faced with difficult situations where the individual may
be asked to compromise his or her integrity or values. The Code of Ethics and
Professional Conduct affirms these four values as its foundation.
Responsibility
 in the best interest of the society, public and environment

 accept assignments consistent with skills and fulfill commitments
 accept stretch assignment when the assigner is fully aware of the skill gaps
 own error and make corrections
 uphold laws and regulations
 report illegal/unethical activities substantiated with facts
 ask for direction should the decision is beyond assigned authority
Respect
 show respect to others

 listen and understand others
 conduct in a professional manner, even if not reciprocated
 resolve conflicts directly
 negotiate in good faith
 do not influence others for personal benefits
 respect others rights
Fairness
 transparency in decision making

 be objective
 provide equal access to information, equal opportunities
 disclose any conflict of interests and refrain from making decisions in case of
conflict of interest
 do not deny opportunities base on personal considerations
 do not discriminate
 apply rules without favoritism or prejudice

12
Honesty
 understand the truth and be truthful

 honour commitments
 not to deceive others
 not engage in dishonest behavior for personal gain / at the expense of others
Other Important Project Management Terms
 The Configuration Management Knowledge Bases contain baselines of all

organization standards
 Lessons Learned – focus on the deviances from plan (baseline) to actual
results and how to solve these discrepancies
 The work authorization system (WAS) is a system used during project
integration management to make sure that the right work gets done at the
right time
 PMIS includes configuration system and change control system
 Never accept a change request to trim down one element of the triple
constraint without changing the rest.
 Sponsor – provides resources/support to project, lead the process through
initiation (charter/scope statement) through formally authorized, later
involved in authorizing scope/budget change/review
 Customer – NOT necessarily provide the financial resources, may be external
to the organization, final acceptance of the product
 Business Partners – certification body, training, support, etc.
 Project Statement of Work (SOW): describes the business need, high-level
scope of deliverables and strategic plan of the organization, created by the
sponsor/initiator/buyer
 Project Charter is not a contract
 Project Management Plan is NOT a project schedule
 Project Management System: includes a list of project management processes,
level of implementation (what actions to take in the management processes),
description of tools and techniques, resources, procedures, change control
system [forms with tracking systems, approval levels]

13
 Requirement Traceability Matrix (RTM) – a matrix connecting deliverables to
requirements and their sources (for managing scope)
 Work Breakdown Structure (WBS) – a hierarchal chart of decomposing
deliverables into work packages
 Activity List – a full list of all activities with indication of relationship to the
work packages
 Activity Attributes – further information (duration, start date, end date, etc.)
of all the activities in the list (for scheduling)
 Roles and Responsibilities (RAR) – a document listing all the roles and
description of their responsibilities in the project (often by category)
 Responsibility Assignment Matrix (RAM) – a matrix connecting people to
work packages/activities, e.g. the RACI matrix (responsible, accountable,
consult, inform), usually only one person is accountable for each activity
 Resources Breakdown Structure (RBS) – a hierarchical chart listing all the
resources by categories, e.g. marketing, design, etc.
 Risk Breakdown Structure (RBS) – a hierarchical chart listing all risks by
categories
 Project Management Data and Information
o Work Performance Data – raw data collected
o Work Performance Info – analyzed in context and integrated data,
e.g. some forecasts
o Work Performance Reports – work performance information
compiled in report format
 Sunk costs – money already spent, not to be considered whether to
terminate a project, similar to committed cost (often through contracts)
 Direct costs, indirect (shared) costs, Fixed costs, Variable costs
 Law of diminishing returns – beyond a point, the more input, the less return
 Working capital – assets minus liability, what the company has to invest in
the projects
 Payback period – a time to earn back capital investment
 Benefit-cost ratio (BCR) – an indicator, used in the formal discipline of cost-
benefit analysis, that attempts to summarize the overall value for money of a
project
 Depreciation – straight-line depreciation vs accelerated depreciation (the
amount of depreciation taken each year is higher during the earlier years of an
asset‘s life)
 Under double declining balance, the asset is depreciated twice as fast as
under straight line. Using the example above, 10% of the cost is depreciated

14
each year using a straight line. Doubling the rate would mean that 20% would
be depreciated each year, so the asset would be fully depreciated in 5 years,
rather than 10.
 Under sum-of-the-years-digits, the asset is depreciated faster than the
straight line but not as fast as declining balance. As an example of how this
method works, let‘s say an asset‘s useful life is 5 years. Adding up the digits
would be 5+4+3+2+1 or a total of 15. The first year, 5/15 is expensed; the
next year 4/15 is expensed, and so on. So if the asset‘s cost is $1000, 5/15, or
$333.34 would be expensed the first year, $266.67 the second year, and so on.
 Economic value added – the value of the project brought minus the cost of
project (including opportunity costs) e.g. for a project cost of $100, the
estimated return for 1st year is $5, assuming the same money can be invested
to gain 8% per year, then the EVA is $5 – $100 * 8% = -$3
 Net present value (NPV) – the sum of the present values (PVs) of the individual
cash flows of the same entity
 Present value (PV) – or called present discounted value, is a future amount of
money that has been discounted to reflect its current value, as if it existed
today (i.e. with inflation, etc.)
 Future value (FV) – is the value of an asset at a specific date
 Internal Rate of Return (IRR) – The inherent discount rate or investment yield
rate produced by the project‘s deliverables over a pre-defined period of time.
 Forecast (future) vsStatus Report (current status) vsProgress Report (what
have been done/delivered)
 Journey to Abilene (Abilene’s Paradox) – committee decisions can have a
paradox outcome, the joint decision is not welcome by either party (because
of fear of raising objections)
 when something unusual happens, always refer to the PM Plan/Charter for
instruction on how to proceed; if not found, ask for direction from the
management
 unresolved issues will lead to conflicts

15
Project Integration Management
Project Integration Management encompasses all the process and activities to
identify, define, combine, unify and coordinate all the various project management
processes and activities and manage the interdependencies.
 integration management is required when different project management

processes interact
 tailoring of processes is a very important topic in the PMBOK® Guide 6th
edition with a view to meeting project objectives
 of all the project management activities, communication is the most
important one according to many project managers
 a PM Plan not meeting requirements is a defect
Develop Project Charter
 Inputs: Business Documents (including business case), Agreements, EEF, OPA

 Tools & Techniques: Expert Judgment, Data gathering (including
brainstorming, focus groups, interviews), Interpersonal and team skills
(including conflict management, facilitation, meeting management), Meetings
 Outputs: Project Charter, Assumption log (records all assumptions and
constraints of the project)
 to formally authorize the project and allow the PM to apply organizational

resources
 well-defined project start and project boundaries
 The project charter is a several page document including high-level
information of the project: project background, business case, goals
(S.M.A.R.T. specific, measurable, attainable, realistic, time-bound), who is and
the authority of the project manager, budget, risk, stakeholders, deliverables,
approval criteria, etc.
o the business case contains info to determine whether the project is
justified

16
o agreements are a group of project documents (either a contract (for
external parties), letter of intent, service level agreement, etc. (can be
legally binding or NOT)) that define initial intentions of the project
o a charter is NOT a contract because there is no consideration
 signed off by the sponsor (the one who supply the money/resources)
 PMO may provide the expert judgment
Develop Project Management Plan
 Inputs: Project Charter, Outputs from other processes, EEF, OPA

 Tools & Techniques: Expert Judgement, Data gathering, Interpersonal and
team skills, Meetings
 Outputs: Project Management Plan
 the project management plan is a formal written document on how the

project is executed, monitored and closed, including all subsidiary
management plans (scope, requirements, change, configuration, schedule,
cost, quality, process improvement, human resource, communication, risk,
procurement) and documents (cost baseline, schedule baseline, scope
baseline, performance measurement baseline, cost estimate, schedule,
responsibility for each deliverable, staff requirements) and some additional
documents/plans (selected PM processes and level of implementation)
o the contents to be tailored by the PM (tailoring) to suit each project
o the PM plan may be progressively elaborated in iterative phases (as
outputs from other processes), this must be the final process/iteration
to consolidate the PM Plan
o created by PM, signed off by destined KEY stakeholders (e.g. can be
the project sponsor, project team, project manager)
o when the project management plan is baselined (i.e. validated and then
signed off by key stakeholders), it is subject to formal change
control and is used as a basis for comparison to the actual plan
o after baselining, the senior management must be consulted if these
high level constraints are to be altered (whether to use the
management reserves)

17
 the PM Plan can be re-baselined if significant changes are seen (scope
change, internal changes/variances (for the project execution), external
factors)
o needed to be approved by sponsors/stakeholders/senior management,
must understand the underlying reasons first (built-in costs is not
usually a legitimate reason)
 cost baseline (specific time-phased budget), schedule baseline (-> knows
when to spend money), scope baseline (includes scope statement, WBS, WBS
dictionary): whether preventive/corrective/defect repair actions are needed
 the performance measurement baseline (PMB) is an approved scope-
schedule-cost plan for the project work (to be used in earned value
management), this includes contingency reserve but excludes
management reserves
 configuration management (works with change control management plan),
document all change versions of project deliverables and completed project
components, PMIS includes: Configuration Management System (contains
the updated deliverable/project specifications and processes) and Change
Control System (contains formal documents for tracking changes)
o configuration management system contains the most updated
version of project documents
 Kick-off Meeting: at beginning of the project/phase, participants including
project team+stakeholders, element including project review, responsibility
assignment matrix, participation of stakeholders, escalation path, frequency of
meetings
Direct and Manage Project Work
 Inputs: Project Management Plan, Project documents (including change log,

Lessons learned register, risk register, project schedule, project
communications, etc.), Approved change requests, EEF, OPA
 Tools & Techniques: Expert Judgement, Project management information
system, Meetings
 Outputs: Deliverables, Work performance data, Issue log, Change
requests, Project management plan updates, Project documents updates, OPA
updates

18
 The Direct and Manage Project Work process creates project deliverables,
acquire/assign/train staff, manage vendors, collect data for reports, document
lessons learned
o most of the project time to be spent here
 the PM implements approved process improvement plans and changes,
change requests include corrective actions, preventive actions, defect repair
and updates (all considered to be change requests)
 if the PM discovers a defect, he/she should instruct the team to make defect
repair during this process (need change request but may be approved by the
PM only (if stipulated in PM Plan for minor changes))
 approved change requests – approved in the perform integrated change
control, may include preventive, corrective and defect repair actions
o change requests may arise as a result of implementing approved
change requests
 a work authorization system (part of EEF) defines approval levels needed to
issue work authorization (to allocate the work) and is used to prevent scope
creep as formal approval must be sought before work begins
 Stakeholder risk tolerance is part of EEF
 Face-to-face meeting is considered to be most effective
 The PM Plan itself can be considered as a deliverable
Manage Project Knowledge
 Inputs: Project Management Plan, Project documents, Deliverables, EEF, OPA

 Tools & Techniques: Expert Judgement, Knowledge Management, Information
Management, Interpersonal and team skills
 Outputs:Lessons learned register, Project management plan updates,
OPA updates
 This newly added Manage Project Knowledge process is involved in

documenting and using knowledge learnt from the project to achieve the
project objectives and the whole organization to learn from the experiences.
 Documenting lessons learned from the project is a recurring process during
the life cycle of the project.

19
 The lessons learned register is a new output (first mentioned the PMBOK®
Guide) which records challenges, problems and successes throughout the
project
Monitor and Control Project Work
 Inputs: Project Management Plan, Project documents, Work performance

information, Agreements, EEF, OPA
 Tools & Techniques: Expert Judgement, Data Analysis, Decision Making,
Meetings
 Outputs: Work performance reports, Change requests, Project management
plan updates, Project documents updates
 corrective and preventive actions usually don‘t affect the baseline, only affect
the performance against the baseline
 defect repair: considered as rework, deliverable not accepted, either rework
or scrap, strongly advise defect prevention to defect repair
 the work performance info is fed from all other control processes (e.g. control
schedule, control stakeholder engagement, control communications, control
costs, control quality, etc.)
 Data Analysis Techniques include:
o Alternatives analysis
o Cost-benefit analysis
o Earned value analysis
o Root cause analysis
o Trend analysis – forecasts future performance based on past
performance
o Variance analysis – analyzes the differences (or variances) between
planned and actual performance
 Decision Making is a technique to achieve a decision e.g. by voting.

20
Perform Integrated Change Control
 Inputs: Project Management Plan, Project documents, Work performance

reports, Change requests, EEF, OPA
 Tools & Techniques: Expert Judgement, Change control tools, Data Analysis,
Decision Making, Meetings
 Outputs: Approved change requests, Project management plan updates,
Project documents updates
 changes in the project arise as a result of missed requirements, views of

stakeholders, poorly designed WBS, misunderstanding, inadequate risk
assessment
o the PM should influence the factors that cause project change
 life cycle of a change request:
1. identify needs
2. assess the impact, response and alternatives
3. create the change request
4. meet with stakeholders
5. obtain approval from CCB (change control board) or PM as defined in
roles and responsibility document/PM Plan
 customers/sponsors may need to approve certain decisions by
CCB (if they are not part of CCB)
6. request more funding if needed
the whole process must be documented in the change log (which is a project
document)
changes need to be tracked using a change management system, also affect
configuration management system
o configuration control: changes to deliverables and processes
o change control: identify/document/approve changes
configuration management activities: configuration identification,
configuration status accounting, configuration verification/audit to ensure the latest
configuration is adopted and delivered
communicate the resolutions (approve or reject) to change requests to
stakeholders

21
Close Project or Phase
 Inputs: Project charter, Project Management Plan, Project documents,

Accepted deliverables, Business documents, Agreements, Procurement
documents, OPA
 Tools & Techniques: Expert Judgement, Data Analysis, Meetings
 Outputs: Project documents updates, Final product, service or results
transition, Final report, OPA updates
 must ensure all procurements are closed before formal closure of the
project/phase, all procurement documentation must be collected, indexed and
filed
 obtain formal approval to close out the project/phase (administrative
closure)
o obtain approval and deliver the deliverables (maybe with training)
o formal sign off by designated stakeholders/customer
 finish and archive documentation, lessons learnt and update to organizational
process asset
 if the contract comes with a warranty, make sure that changes during the
project are evaluated against the origin clauses, ensure alignment of the
warranty and changes
 to close a project as neatly and permanently possible
 for multi-phase projects, this process will be performed once for every phase
end and once for the whole project (5 times for project with 4 phases)
 The final report is a summary of the project performance, including:
o Summary level description of the project or phase
o Scope objectives
o Quality objectives
o Cost objectives
o Summary of the validation information for the final product, service or
result
o Schedule objectives
o Summary of how the final product, service, or result achieved the
business needs
o Summary of any risks or issues encountered on the project and how
they were addressed
 litigation can be further pursued after the closure

22
Project Scope Management
 The project manager would need to ensure the inclusion of all and only the
work required to complete the project successfully (to achieve project
objectives to deliver business values).
 The primary aim of scope management to define the exact scope of work and
to prevent scope creep (additional requirements added without any proper
control) or gold-plating (added by the project team with a view to impressing
stakeholders).
 Product Scope – requirements needed to be fulfilled to create the product,
assessed against the product requirements and WBS
 Scope Baseline: scope statement + WBS + WBS dictionary
o WBS includes only the deliverables/outcomes/results (not actions)
 Project Scope – activities and processes needed to be performed to deliver
the product scope, assessed against the scope baseline (scope statement,
WBS and WBS dictionary), e.g. including testing & quality assurance, assessed
against the Project Management Plan
o The completion of project scope is measured against the project
management plan whereas the completion of product scope is
measured against the product requirements/WBS
Plan Scope Management
 Inputs: Project Charter, Project Management Plan, EEF, OPA

 Outputs: Scope Management Plan, Requirements Management Plan
 ScopeManagement Plan (will form part of the Project Management Plan):

how the scope will be defined, validated and controlled
o includes how to prevent scope creep, how to handle change requests,
escalation path for disagreement on scope elements between
stakeholders, processes for creating scope statement, WBS, processing
CR, how the deliverables will be accepted
 RequirementsManagement Plan: how the requirements will be managed,
documented and analyzed

23
o includes how to process requirements, address missed requirements,
configuration management, prioritize requirements, metrics (and
rationale) for defining the product, define the traceability structure (in
RTM), authorization level for approving new requirements
o [important] the requirement management plan is the primary means
to understand and manage stakeholder expectations
Collect Requirements
 Inputs: Project Charter, Project Management Plan, Project Documents,

Business Documents, Agreements, EEF, OPA
 Tools & Techniques: Expert Judgement, Data Gathering, Data Analysis, Decision
Making, Data Representation, Interpersonal and Team Skills, Content Diagram,
Prototypes
 Outputs: Requirements Documentation, Requirements Traceability Matrix
 Requirement: a condition/capability that must be met /possessed by a

deliverable to satisfy a contract/standard/etc., including
quantified/documented needs, wants, expectation of the
sponsor/stakeholder/customer
o Business requirements – support business objectives of the company
o Stakeholder requirements
o Solution requirements – functional (product behavior)
and nonfunctional requirements (reliability, security, performance,
safety, etc.)
o Transitional requirements : temporary capability including data
conversion/tracking/training
o Project requirements : actions/processes/conditions the project needs
to met
o Quality requirements : quality criteria defined by stakeholders
 Requirements Collection Tools
o Data Gathering
 Brainstorming
 Interviews
 Focus groups
 Questionnaires and surveys
 Benchmarking

24
o Data Analysis
 Document analysis
o Data Representation
 Affinity Diagram: for identifying a large number of ideas by
grouping similar ideas together
 Mind Mapping: to generate ideas with the process of
backtracking
 Requirements Traceability Matrix tracks requirements from origins to
deliverables, including source of requirements and completion status,
effective to prevent gold plating (also work with work authorization system)
 Requirement documentation needs to be unambiguous, traceable, compete,
consistent and acceptable to key stakeholders and is approved by the
customer and other stakeholders
Define Scope
 Inputs: Project Charter, Project Management Plan, Project Documents, EEF,

OPA
 Tools & Techniques: Expert Judgement, Data Analysis, Decision Making,
Interpersonal and Team Skills, Product Analysis
 Outputs: Project Scope Statement, Project Documents Updates
 to define both the project& product scope in details, outlines what WILL and
what WILL NOT be included in the deliverables, including details of
constraints and assumptions
o vs project charter which includes only high-level descriptions
 may provide alternatives if the budget and schedule could not meet
management‘s expectations
 Product analysis includes techniques such as:
o product breakdown
o systems analysis
o requirements analysis
o systems engineering
o value engineering – a part of product analysis technique (Value
Engineering (value analysis, value management, value methodology)
with a view to finding alternatives to constraints to improve
product/reduce cost without sacrificing the scope)

25
o value analysis
 Project Scope Statement includes objectives, (project and product) scope,
requirements, boundaries, deliverables, acceptance criteria, constraints,
assumptions, milestones, cost estimation, specifications, configuration
management requirements, approval requirements, etc.
o the scope statement is usually progressively elaborated throughout the
project
Create WBS
 Inputs: Project Management Plan, Project Documents, EEF, OPA

 Tools & Techniques: Expert Judgement, Decomposition
 Outputs: Scope Baseline, Project Documents Updates
 the WBS must be created for every project (if you take on a running project
without WBS, you must stop the project immediately and prepare the WBS
first)
o WBS is a structured hierarchy created by the organization/stakeholders,
can be in an organization chart or table form, based on the project
deliverables (not tasks needed)
o WBS is a decomposition tool to break down work into lowest level
manageable (time and cost can be estimated, work package can be
assigned to a team member) work packages, e.g. by phase or major
deliverables
o the work packages are broken down enough to delegate to a staff, usu.
8 – 80 hours work and different work packages can be at different
levels of decompositions
o WBS does not show dependencies between work packages, but a WBS
dictionary does (WBS dictionary clarifies WBS by adding additional
information)
o WBS includes 100% of scope (100% rule)
o can be a template in OPA
 a higher level above a work package is ‗control account‗ (control point where
scope, cost and schedule are compared to earn value for performance
measurement)
o a work package can have only ONE control account
 code of accounts: a numbering system to identify WBS components

26
 chart of accounts: a list of all account names and numbers
o 1.1 for the 2nd level, 1.1.1 for the 3rd level
 the major deliverables should always be defined in terms of how the project
will actually be organized, for a project with phases, the decomposition
should begin with the phase first
 Scope Baseline, an output from Create WBS, includes:
o WBS (Work Breakdown Structure)
o WBS Dictionary
o Scope Statement
o Scope Management Plan
 Scope Baseline is to be created by the project team
Validate Scope
 Inputs: Project Management Plan, Project Documents, Verified Deliverables,

Work Performance Data
 Tools & Techniques: Inspection, Decision Making
 Outputs: Accepted Deliverables, Work Performance Information, Change
Requests, Project Documents Updates
 the purpose of this process is to gain formal acceptance of deliverables

fromcustomer/stakeholders (e.g. obtain customer sign off, requirements
validations, etc.) near the end of project/phase/each deliverable, e.g. user
acceptance test
o change requests may be an output as stakeholders may request
changes to the deliverables
o if no formal sign off is received as stipulated, the Project Manager
needs to follow the pre-defined process in PM plan, e.g. escalation to
management
 work performance data tells how the deliverables were created, work
performance data includes non-conformance and compliance data
 Validate Scope is often preceded by Control Quality Process to give the
verified deliverable as input to this process, verified deliverables is fed from
the control quality process
o vs Control Quality: the process of monitoring/recording results of
executing quality activities to assess performance and recommend
necessary changes, e.g. unit testing -> high quality vs low quality

27
 need to perform even in case of early termination/cancellation of the
project to save any usable deliverables for other projects
Control Scope
 Inputs: Project Management Plan, Project Documents, Work Performance

Data, OPA
 Tools & Techniques: Data Analysis
 Outputs: Work Performance Information, Change Requests, Project
Management Plan Updates, Project Documents Updates
 Control Scope is performed when assessing additional requirements by the

customer or the project manager proactively overlooking the project scope
o to prevent unnecessary changes (either internally or externally
requested) to the project
 measure the work product against the scope baseline to ensure the project
stays on track proactively, may need preventive, corrective actions or defect
repair
 a well documented and enforced change control process is required
 the customer has the ultimate authority to change scope while the senior
management can make use of management reserves
o i.e. in general, disagreement should be resolved in favour of the
customer
 Data Analysis includes:
o variance analysis – method to compare planned (baseline) and actual
work and determine the causes/actions e.g. update baseline (keep the
variance) or preventive/corrective actions, both need CR
o trend analysis
 work performance info – scope variance, causes, recommended action
 may end up updating some of the inputs – requirements documentation &
requirement traceability matrix & lessons learnt in OPA

28
Project Schedule Management
 The project manager is required to create a detailed schedule plan to describe
how and when the project/team will deliver the products, services and results
as defined in the project scope in the project management plan
 The project schedule will later be used as a tool for communication (for
managing stakeholder expectations) and performance assessment/reporting
Plan Schedule Management

 Outputs: Schedule Management Plan
 defines policies, procedures and documentation for managing and controlling

project schedule
o including scheduling methodology, tools, level of accuracy, control
thresholds (limit beyond which preventive/corrective actions needed),
rules of performance measurement (e.g. earned value)
 lead and lags are NOT considered as schedule constraints
 Data analysis would include:
o choosing the scheduling methodology (or a combination 9f various
methods)c
o determining the detail level of the schedule and how often the
schedule needs to be reviewed and updated
o the duration of waves for rolling wave planning, etc.
Define Activities
 Inputs: Project Management Plan, EEF, OPA

 Tools & Techniques: Expert Judgement, Decomposition, Rolling Wave
Planning, Meetings
 Outputs: Activity List, Activity Attributes, Milestone List, Change Requests,
Project Management Plan Updates

29
 the scope baseline (as part of the Project Mangement Plan) is used here as it
represents the approved (stable) scope
 further decompose work packages into activities for more detailed and
accurate estimations
o ‗activities‘ is the PMI terminology for ‗tasks‘ and ‗work efforts‘
o activity is more related to the actual work/process to produce the
deliverables
o activity types: level of efforts (support, measured in time period),
discrete efforts or apportioned effort (in direct proportion to another
discrete effort)
 activities have durations while milestones do not (zero duration)
 changes requests are listed as a possible output because progressive
elaboration of deliverables into activities (using rolling wave planning) may
allow us to discover work that was not initially included as part of the project
baselines — need to update the project baselines
Sequence Activities

 Tools & Techniques: Precedence Diagramming Method, Dependency
Determination and Integration, Leads and Lags, Project Management
Information System
 Outputs: Project Schedule Network Diagrams, Project Documents Updates
 Precedence Diagramming Method (PDM) to diagram dependencies
o Network Diagramming Tools are software tools that graphically

represent activity sequences
o network diagrams: shows dependencies, duration, workflow,
help identifying critical paths
 precedence relationships (also known as ‗activity on node (AON)‗

approach):
o finish-to-start (the majority, accounts for about 95% of all precedence
relationships)
o start-to-start
o finish-to-finish

30
o start-to-finish (least)
 Activity on Arrow (AOA) or Arrow Diagramming Method (ADM) activities
are represented as arrows, dashed arrows represent dummy activities
(duration: 0) that shows dependencies
 Graphical Evaluation and Review Technique (GERT) allows for conditional
branching and loops
 Network Dependency Types (to be determined during Sequence Activities
Process):
o Mandatory Dependency (hard logic): A must be completed before B
begins/ technical dependencies may not be hard
o Discretionary Dependency (preferred, soft logic): sequence preferred
by the organization, may be removed should fast-tracking is required
o External Dependency: dependency required by external organization
o Internal Dependency: precedence relationship usually within the
project team‘s control
 Milestones: the completion of a key deliverable/a phase of the project, as
checkpoints/summary for progress, often used in funding vendor activities
o Milestone list is part of i) project plan, ii) project scope statement, iii)
WBS dictionary
 Leads: begin successor activity before end of predecessor, for schedule
compression (fast-tracking) (negative lags)
 Lags: imposed delay to successor activity, e.g. wait 2 weeks for concrete to
cure (FS +14 days)
 Network Diagram Setup: 7-box method, usually using software tools or 5-box
method
 if the ES and LS are identical, the activity is on the critical path
 The Project Management Information System provides the scheduling
software to allow planning the activities with logical relationships, leads, lags,
etc.
Estimate Activity Durations

 Tools & Techniques: Expert Judgement, Analogous Estimating, Parametric
Estimating, Three-point Estimating, Bottom-up Estimating, Data Analysis,
Decision Making, Meetings
 Outputs: Duration Estimates, Basis of Estimates, Project Documents Updates

31
 consults SME (subject matter experts, i.e. the one carrying out the actual work)
to come with the estimation, not on the PM‘s own
 Different Estimating Tools and Techniques:
o Analogous Estimating: based on previous activity of similar nature (a form
of expert judgement), used when little is known or very similar scope,
works well when project is small, NOT ACCURATE
o Parametric Estimating: based on some parameters, e.g. the time for
producing 1000 component based on that for 1 component * 1000, use an
algorithm based on historical data, accuracy depends on the parameters
selected, can be used on [a portion of / the entire] project
o One-Point Estimating: based on expert judgement, but highly unreliable
o Three-Point Estimating: best (optimistic), most likely (realistic), worst
(pessimistic) cases, Triangular Distribution vs PERT (Project Evaluation
and Review Techniques, Beta Distribution, weighted average using
statistical methods [most likely * 4 – 95% confidence level with 2 sigma]),
triangular distribution (non-weighted average of three data points),
uncertainties are accounted for
o In real-world applications, the PERT estimate is processed using Monte
Carlo analysis, tie specific confidence factors to the PERT estimate
o Bottom-Up Estimating: a detailed estimate by decomposing the tasks
(lower-level components of the WBS) and aggregating the estimates based
on reliable historical values, most accurate but time-consuming
o Heuristics: use rule of thumb for estimating
 standard deviation (sigma value, deviation from mean, to specify the
precision of measurement): 1 sigma: 68%, 2 sigma 95%, 3 sigma 99.7%, 6
sigma 99.99%
 accuracy is the conformance to the target value
 contingency reserve: for known unknowns, owned by PM, may be updated,
part of schedule baseline
 management reserve: for unknown unknowns, owned by management,
included in overall schedule requirements
 update to documents: the basis of estimates, assumptions and contingencies
 activity duration estimate may be in a range, don’t include lags
 Data Analysis tools and technique may include:
o Reserve analysis

32
 Duration Estimates are the quantitative assessments of the likely durations
that are required to complete the activities, phases or a project (maybe in the
form of a range).
 Basis of Estimates provide the detail to support duration estimate process
(e.g. the basis of the estimate, assumptions, constraints, ranges of possible
estimates, confidence levels of the final estimate, individual project risks
influencing this estimate, etc.)
Develop Schedule
 Inputs: Project Management Plan, Project Documents, Agreements, EEF, OPA

 Tools & Techniques: Schedule Network Analysis, Critical Path Method,
Resource Optimization, Data Analysis, Lead and Lags,Schedule
Compression, Project Management Information System, Agile Release
Planning
 Outputs: Schedule Baseline, Project Schedule, Schedule Data, Project
Calendars, Change Requests, Project Managment Plan Updates, Project
Documents Updates
 the schedule baseline is the approved and signed version of project schedule
that is incorporated into the PM plan
 the project schedule is calendar-based taking into accounts
holidays/resource availability/vacations
o vs the time estimate (work effort/level of effort) just describes the
man hours/man days
 the Schedule Data includes schedule milestones, schedule activities, activities
attributes, and documentation of all assumptions and constraints, alternative
schedules and scheduling of contingency reserves
 Slack/Float
o Slack/Float: activities that can be delayed without impacting the
schedule
o Free slack/float: time an activity can be delayed without delaying the
Early Start of the successor
o Total slack/float: time an activity can be delayed from early start
without delaying the project end date (scheduling flexibility), can be
negative, 0 (on the critical path) or positive
o Project Float: without affecting another project

33
o Negative float: problem with schedule, need schedule rework
o Project slack/float: time the project can be delayed without delaying
another project
 Early Start (ES) – earliest time to start the activity
 Late Start (LS) – latest time to start without impacting the late
finish
 Early Finish (EF) – earliest time to end the activity
 Late Finish (LF) – latest time to finish without impacting
successor activity
 Slack/Float = LS – ES or LF – EF
 The float is the highest single value along the critical path, NOT
the sum of them
 Critical Path: the longest path that amount to shortest possible completion
time (usually zero floats, activities with mandatory dependency with finish-to-
start relationship), can have more than 1 critical paths (more risks), critical
paths may change (keep an eye on near-critical paths)
o activities on the critical path are called critical activities
o Path with negative float = behind schedule, need compression to
eliminate negative float
 Forward Pass: compute the early start
 Backward Pass: compute the late start
 Fast Tracking: allow overlapping of activities or activities in parallel, included
risks/resource overloading
 Crashing: shorten the activities by adding resources, may result in team
burnout
 Agreements are added as an input (in PMBOK® Guide 6th Edition) as these
contain details of how the sellers/vendors will perform the project work to
meet contractual commitments. Works from external parties will have a direct
impact on the project schedule.
 Agile Release Planning, also added as an input, provides a high-level
summary timeline of the release schedule (typically within 3-6 months) based
on the product roadmap and the product vision for the product releases
(based on business goals, dependencies, etc.)
o determines the number of iterations or sprints required in a release
o allows the product owner and team to decide how much time needed
 Scheduling Techniques
o Critical Path Method (CPM) – compute the forward and backward
pass to determine the critical path and float

34
o Critical Chain Method (CCM) – deal with scarce resources and
uncertainties, keep the resources levelly loaded by chaining all activities
and grouping the contingency and put at the end as project buffer, for
activities running in parallel, the contingency is called feeding buffer
(expect 50% of activities to overrun)
o The buffer is determined by assessing the number of uncertainties,
human factors, etc.
 Resource Optimization Techniques
o Resource leveling is used to adjust the variation in resource loading to
stabilize the number of resources working each time and to avoid
burnout, may need to extend the schedule in CPM
o Resource smoothing is to adjust resource requirements so as not to
exceed predetermined resource limits, but only optimized within the
float boundaries
 Data Analysis Tools
o What if analysis: to address feasibility/possibility of meeting project
schedule, useful in creating contingency plan
o Monte Carlo: run thousands of times to obtain the distribution using a
set of random variables (stochastic variables), use a combination of
PERT estimate and triangular distributions as endpoint estimates to
create the model to eliminate schedule risks, the graph is an ‘S’ curve
 Network Diagram: bar charts with logical connections
 Hammock activities: higher-level summary activities between milestones
 Milestone Charts: show only major deliverables/events on the timeline
 data date (status date, as-of date): the date on which the data is recorded
 the Project Calendars identify working days
Control Schedule

Data, OPA
 Tools & Techniques: Data Analysis, Critical Path Method, Project Management
Information System, Resource Optimization, Lead and Lags, Schedule
Compression
 Outputs: Work Performance Information, Schedule Forecasts, Change
Requests, Project Managment Plan Updates, Project Documents Updates

35
 measure result, make adjustments to the project work plan (if needed)
through resource optimization, lead and lags or schedule compression, and
adjust metrics
 Data analysis includes:
o Iteration burndown chart
o Performance reviews
o Trend analysis
o Variance analysis
o What-if scenario analysis
 Change requests generated are to be assessed in the Perform Integrated
Control Process

36
Project Cost Management
 important cost management/calculation terms:
o sunk cost – cost already incurred in the past and cannot be recovered,
do not consider any more
o opportunity cost – difference in value between one path vs alternative
(= 100% of the value of next best alternative)
o value analysis/ engineering – cost reduction without affecting the scope
o Benefit-Cost Analysis (BCA) / Cost-Benefit Analysis (CBA) – determine
feasibility, bigger benefit/cost ratio (BCR)
o Payback Period – the length of time to recover the investment
o Return on Investment (ROI) – the efficiency of investment = (Gain-
Cost)/Cost
o Time Value of Money – Present Value (PV) = value / (1+interest
rate)*year, Future Value (FV) = value * (1+interest rate)*year
o Net Present Value (NPV) = PV of cash inflows – PV of cash
outflows (cost)
o funding for the project: self-fund, funding with equity, funding with
debts
o discount rate – rate used to calculate the present value of expected
yearly benefits and costs
Plan Cost Management

 Outputs: Cost Management Plan
 The Cost Management Plan establishes

o level of accuracy and level of precision
o unit of measurement
o WBS procedure links (to control account (CA))
o control threshold
o earned value rules of performance, reporting, funding and processes
 Life cycle costing = total cost of ownership: production cost, running and
maintenance cost, etc.
 Data analysis techniques include:

37
o alternatives analysis — strategic funding options, ways to acquire
project resources
Estimate Costs

 Tools & Techniques: Expert Judgement, Analogous Estimating, Parametric
Estimating, Bottom-up Estimating, Three-point Estimating, Data Analysis,
Project Management Information System, Decision Making
 Outputs: Cost Estimates, Basis of Estimates, Project Document Updates
 look for ways to reduce cost

 ensure the subject matter experts (SME) to deliver the estimates (which is
much more accurate)
 cost estimate to be based on WBS
 Cost Types
o Variable costs – costs change with the amount of work, e.g. hourly
consultants
o Fixed costs – costs that are constant, e.g. equipment leases
o Direct costs – directly attributed to the project
o Indirect costs – shared costs like AC, lighting, etc.
 Data Analysis Techniques
o Reserve analysis
o Cost of quality – cost of conformance and non-conformance
 Cost Estimate Tools
o Analogous Estimating (Top Down Estimate) — compare to a similar
project in the past (an estimating heuristic/rule of thumb)
o Parametric Estimating — use a parameter and repetitive units of
identical work
o Bottom-up Estimating — detailed estimates of each individual activity
from historical data, more accurate and time-consuming
o Three-point Estimating — taking into accounts of the pessimistic,
optimistic and most likely estimates
 Activity Cost Estimates may include indirect cost and contingency reserves
 usually to be expressed in a range of values

38
 Basis of Estimates – detailed analysis on how the cost estimate was derived
(assumptions, constraints, possible range (+/-15%), confidence level of final
estimate)
Determine Budget
 Inputs: Project Management Plan, Project Documents, Business Documents

(business case, benefits management plan), Agreements, EEF, OPA
 Tools & Techniques: Expert Judgement, Cost Aggregation, Data Analysis,
Historical Relationships, Funding Limit Reconciliation, Financing
 Outputs: Cost Baseline, Project Funding Requirements, Project Document
Updates
 Budget is more about when to spend money

 Historical Relationships – analogous/parametric estimation
 Data Analysis =>Reserve Analysis – addresses Management Reserve
(unknown unknowns) and Contingency Reserve (known risks) [not included
in calculation of earned value managment]
 Funding Limit Reconciliation – addresses variance between funding limit
(e.g. monthly or yearly limit) and planned expenditure, may require
rescheduling of work to level of the rate of expenditure
 Value Engineering – to improve quality/shorten schedule without affecting
the scope
 Project Budget = Cost baseline (the approved time-phased budget) +
Management Reserve
 when management reserve is used during project execution, the amount is
added to the cost baseline
 S-curve: total project expenditure over project lifecycle
 Financing: acquiring funding for projects, may source from internal and/or
external sources
Control Costs
 Inputs: Project Management Plan, Project Documents, Project Funding

Requirements, Work Performance Data, OPA
 Tools & Techniques: Expert Judgement, Data Analysis, To-complete
Performance Index, Project Management Information System

39
 Outputs: Work Performance Information, Cost Forecasts, Change Requests,
Project Management Plan Updates, Project Document Updates
 Check against the Project Funding Requirements

o controlling costs including informing stakeholders of all approved
changes and their costs
o perform Control Cost more often during execution where money is
spent fastest
 Data analysis techniques:
o Variance analysis — including schedule variance (SV), cost variance
(CV), schedule performance index (SPI), and cost performance index
(CPI) to check against the baseline for any variance
o Trend analysis
o Reserve analysis
 Earned Value Calculation
o Estimate at Complete:
 new estimate required (original flawed)
 no BAC variance
 CPI will continue
 sub-standard cost/schedule will continue
o TCPI (To-complete Performance Index):
 >1 not enough funding remain (over budget)
 <1 more fund available than needed (under budget)
 SPI at end of project must be 1
 SPI is NOT telling much information about whether the project is on schedule
as the Critical Path must also be investigated to get a meaningful picture

40
EVM Concepts with Examples
Earned value management (EVM) is used to assess the schedule and cost
performance of a project — with EVM, the project manager will know exactly
whether the project is:
 ahead of / on / behind schedule

 under / on / over budget
Earned value management (EVM) bases on the concept that i) work completed will
deliver value and ii) the value delivered equals the budget put into the work. The
value gained can be assessed along the progression of the project. In reality, earned
value management is very complicated as value usually cannot simply be assessed
based on the percentage of completion.
Good news here: PMI has simplified PMP® EVM calculation to very “ideal” situations!
You will just need to know the following to get your PMP® EVM questions correct.
Basic EVM Formulas
To speak more clearly how the value is to be managed, a number of terms are
defined in EVM (explained with the example of building 10 houses each has a value of
US$1000 expected to be completed in 10 weeks in proportion):
 Planned Value (PV) — The budgeted value of the work completed so

far at a specific date
example: at end of week 4, altogether 4 houses should be completed, the PV is
US$4000
 Earned Value (EV) — The actual value of the work completed so far at a
specific date (refer to the ―Notes on Earned Value Measurement‖ section
below)
example: by end of week 4, only 3 houses are completed, the EV is US$3000
 Actual Cost (AC) — The total expenditure for the work so far at a
specific date
example: by end of week 4, US$4000 was spend, the AC is US$4000
EVM is based on monitoring these three aspects along the project in order to
reveal the health of the project with the following indices:

41
 Schedule Variance (SV) — difference between PV and EV, to tell whether the
project work is ahead of / on / behind schedule
o SV = EV – PV
If the project is behind schedule the SV will be negative (i.e. achieved less
than what planned)
If the project is on schedule the SV = 0
If the project is ahead of schedule the SV will be positive (i.e. achieved
more than what planned)
o example: by end of week 4, the SV = EV – PV = US$3000 – US$4000 = -
US$1000 (behind schedule)
 Schedule Performance Index (SPI) — ratio between EV and PV, to reflect
whether the project work is ahead of / on / behind schedule in relative terms
o SPI = EV/PV
If the project is behind schedule the SPI < 1 (i.e. achieved less than what
planned)
If the project is on schedule the SPI = 1
If the project is ahead of schedule the SPI > 1 (i.e. achieved more than
what planned)
o example: by end of week 4, the SPI = EV/PV = US$3000/US$4000 =
0.75 (behind schedule)
 Cost Variance (CV) — difference between PV and AC, to tell whether the
project work is under / on / over budget
o CV = EV – AC
If the project is over budget the CV will be negative (i.e. achieved less
than spent)
If the project is on budget the CV = 0
If the project is under budget the CV will be positive (i.e. achieved
more than spent)
o example: by end of week 4, the CV = EV – AC = US$3000 – US$4000 = -
US$1000 (over budget)
 Cost Performance Index (CPI) — ratio between EV and AC, to reflect
whether the project work is under / on / over budget in relative terms
o CPI = EV/AC
If the project is over budget the CPI < 1 (i.e. achieved less than spent)
If the project is on budget the CPI = 1
If the project is under budget the CPI > 1 (i.e. achieved more than spent)
o example: by end of week 4, the CPI = EV/AC = US$3000/US$4000 =
0.75 (over budget)

42
Note: Both SV and SPI / CV and CPI give similar information on schedule / budget
but the indices will give more insights into the actual performance with a meaning
comparison.
From my experience, the most difficult process of solving EVM problems for PMP®
Exams is to identify the PV, EV and AC from the wordy calculation questions. Then
you will just have to recall the correct formula to substitute the values into to get the
answer — the question will usually ask you directly about the actual indices to get.
Advanced EVM Formulas
 Budget at Completion (BAC) — also known as the project/work budget, that

is the total amount of money originally planned to spend on the project/work
o example: the BAC for the housing project = US$1000 x 10 = US$10000
 Estimate at completion (EAC) — as the project goes on, there may be
variations into the actual final cost from the planned final cost, EAC is a way to
project/estimate the planned cost at project finish based on the currently
available data
o The following formulas can be used to calculate EAC based on which
information and conditions given in the question:
 EAC = BAC/CPI
If we believe the project will continue to spend at the same rate up
to now
 The delay is caused by reasons which is likely to continue
(e.g. labour with less skilled than expected)
 example: the EAC for the housing project = US$10000 /
0.75 = US$13333
 EAC = AC + (BAC-EV)
If we believe that future expenditures will occur at the original
forecasted amount (no more delays of the same kind in future)
 The delay might be caused by some unforeseen reasons
(e.g. typhoon) which is not likely to happen again
 example: the EAC for the housing project = US$4000 +
(US$10000 – $3000) = US$11000
 EAC = AC + [(BAC-EV)/(SPI*CPI)]
If we believe that both current cost and current schedule
performance will impact future cost performance

43
 The performance of the project will continue with sub-
prime standards (over budget and behind schedule)
 This formula is less likely to be used for the PMP® Exam
 example: the EAC for the housing project = US$4000 +
[(US$10000 – $3000)/(0.75*0.75)] = US$16444
 EAC = AC + New Estimate
If we believe the original conditions and assumptions are wrong
 Will not be tested as there is nothing to calculate
 Variance at Completion (VAC) — the variance at completion, i.e. the
difference between the new estimate at completion and original
planned value
o VAC = BAC – EAC
If we forecast the project will be over budget, VAC will be negative
If we forecast the project will be under budget, VAC will be positive
o example: the VAC for the housing project = US$10000 – US$13333 (just
take the 1st EAC as an example only) = -US$3333
 To Complete Performance Index (TCPI) — the efficiency needed to finish
the project on budget, it is the ratio between budgeted cost of work
remaining and money remaining
o TCPI = (BAC-EV)/(BAC-AC)
Use this equation if the project is required to finish within BAC
 example: the TCPI for the housing project at end of week 4 =
(US$10000 – US$3000) / (US$10000 – US$4000) = 1.167
o TCPI = (BAC-EV)/(EAC-AC)
Use this equation if the project is required to finish within new EAC
 example: the TCPI for the housing project at end of week 4 with
new EAC US$13333 = (US$10000 – US$3000) / (US$13333 –
US$4000) = 0.75

44
EVM Charts
In common practices, EVM will also involve plotting the values on a graph in order to
help stakeholders concerned to visualize the progress and the health of the
project. More often than not you will find the EV, AC and PV plotted on a graph and
you will be asked on the interpretation of the graph.
Insights to be gained from the chart:
 If EV line is below PV, the project is behind schedule; if EV is above PV, the
project is ahead of schedule.
 If AC line is below EV, the project is within budget; if AC is above EV, the
project is over budget.
Below is an example of the EVM charts you would be likely to encounter in your
PMP® Exam — solid lines represent actual figures while dotted lines represent
forecasted figures:
Judging from the chart above, we can infer that the project is currently
over budget and behind schedule.

45
Earned Value Management (EVM) Formulas
Name Formula Interpretation
(Abbreviation)
Schedule
SPI = EV/PV < 1 behind
Performance schedule
Index (SPI) EV = Earned Value = 1 on schedule
PV = Planned Value > 1 ahead of
schedule
Cost < 1 Over budget
CPI = EV/AC
Performance = 1 On budget
Index (CPI) EV = Earned Value > 1 Under budget
AC = Actual Cost
sometimes the term
„cumulative CPI‟
would be shown,
which actually is the
CPI up to that
moment
Schedule
SV = EV – PV < 0 Behind
Variance (SV) schedule
EV = Earned Value = 0 On schedule
PV = Planned Value > 0 Ahead of
schedule
Cost Variance
CV = EV – AC <0 Over budget
(CV) =0 On budget
EV = Earned Value > 0 Within budget
AC = Actual Cost
Estimate at
EAC = AC + New ETC if the original
Completion estimate is based on
(EAC) if original AC = Actual Cost wrong
is flawed New ETC = New Estimate to data/assumptions or
Completion circumstances have
changed
Estimate at
EAC = AC + BAC – EV the variance is
Completion caused by a one-
(EAC) if BAC AC = Actual Cost time event and is not
remains the same BAC = Budget at completion likely to happen
EV = Earned Value again

46
Estimate at
EAC = BAC/CPI if the CPI would
Completion remain the same till
(EAC) if CPI BAC = Budget at completion end of project, i.e.
remains the same CPI = Cost performance index the original
estimation is not
accurate
Estimate at
EAC = AC + [(BAC - use when the
Completion question gives all the
(EAC) if EV)/(CPI*SPI)] values (AC, BAC, EV,
substandard CPI and SPI),
performance AC = Actual Cost otherwise, this
continues BAC = Budget at completion formula is not likely
EV = Earned Value to be used
CPI = Cost Performance Index
SPI = Schedule Performance Index
To-Complete
TCPI = (BAC – EV)/ <1 Under budget
Performance =1 On budget
Index (TCPI) (BAC – AC) >1 Over budget
BAC = Budget at completion

EV = Earned value
AC = Actual Cost
TCPI = Remaining Work

/Remaining Funds
BAC = Budget at completion
EV = Earned value
CPI = Cost performance index
Estimate to
ETC = EAC -AC
Completion
EAC = Estimate at Completion
AC = Actual Cost
Variance at
VAC = BAC – EAC <0 Over budget
Completion =0 On budget
BAC = Budget at completion > 0 Under budget
EAC = Estimate at Completion

47
Project Quality Management
 Quality: the degree to which a set of inherent characteristics fulfills
requirements, decrease rework/costs, increase productivity/stakeholder
satisfaction
 everyone in the organization is responsible for the quality (project team for
destined parts while PM for project quality), the project manager is
ultimately responsible for the project quality
 The project manager is required to perform continuous improvement activities
(quality assurance), verify quality before completion of deliverables (control
quality)
 prevention over inspection
 continuous improvement to ensure quality (quality assurance) — Quality
Management processes are so focused on reviewing every deliverable – not
just the final product, but all of the components, designs and specifications
too.
 some costs of quality will be borne by the organization (organization quality
policy, e.g. quality audit, ISO accreditation)
 Quality Management Concepts
o Crosby Zero Defects: identify processes to remove defects, quality is built
in to the processes
o Juran Fitness for Use: does the product/service meet customer‘s need? i)
Grade, ii) Quality conformance, iii) Reliability/maintainability, iv) Safety, v)
Actual Use
o W. Edwards Deming: 85% of quality problem is managers‘ responsibility,
develop ―System of Profound Knowledge‖ [system = components working
together to achieve an aim] i) Appreciation for system, ii) Knowledge
about variation (special cause vs common cause) , iii) Theory of
Knowledge (built up by prediction/observation/adjustment) , iv)
Psychology
o Six Sigma: achieve 3.4/1 mil defect level (99.999%) using DMAIC (Define,
Measure, Analyze, Implement, Control) or [Design for Six Sigma]
DMADV (Define, Measure, Analyze, Design, Validate) approach, refine the
process to get rid of human error and outside influences with precise
measurements, variations are random in nature
o Just In Time: eliminate build up of inventory

48
o Total Quality Management (TQM): ISO 8402 all members to center on
quality to drive customer satisfaction , refine the process of producing
the product
o Kaizen改善: implement consistent and incremental improvement, to
reduce costs, cycle time, drive customer satisfaction using PDCA (Plan Do
Check Act)
o The Plan-Do-Check-Act cycle is a way of making small improvements
and testing their impact before you make a change to the process as a
whole. It comes from W. Edwards Deming‘s work in process improvement,
which popularized the cycle that was originally invented by Walter
Shewhart in the 1930s.
o Capability Maturity Model Integration (CMMI): improve overall
software quality (design, development and deployment)
o ISO9000: ensures the defined processes are performed in accordance to
the plan
 Important Terms:
o outliers are singular measurements outside the control limits
o Grade (fit for use or not) vsQuality (conformance to stated requirements)
o Accuracy (correctness) vsPrecision (consistence, how closely conforms to
target, standard deviation is a measure of precision, smaller standard
deviation higher precision)
o under control: the process is predictable and repeatable
Plan Quality Management
 Inputs: Project Charter, Project Management Plan, Project Documents

(assumption log, requirements traceability matrix, risk register, stakeholder
register), EEF, OPA
Making, Data Representation, Test and Inspection Planning, Meetings
 Outputs: Quality Management Plan, Quality Metrics, Project Management Plan
Updates, Project Documents Updates
 quality policy (either organizational or just for the project), methods and
procedures to meet the objectives and satisfy customer‘s needs
o including identifying the quality requirements and document how to
achieve

49
o The goal is to refine the process so that human errors and outside
influences no longer exist, and any remaining variations are completely
random
 Quality Metrics: function points, MTBF (mean time between failure), MTTR
(mean time to repair)
 Data Gathering Tools:
o Benchmarking: compare to past activities/standard/competition
o Brainstorming
o Interviews
 Data Analysis tools:
o Cost-benefit Analysis: cost of implementing quality requirements
against benefits
o Cost of Quality:
 Cost of Quality is the total cost of quality efforts throughout the
product‘s lifecycle
 cost of conformance + cost of non-conformance: cost of
conformance (prevention cost, appraisal cost) vs cost of non-
conformance (failure cost [internal/external])
 lowest quality cost is prevention, highest quality cost (poor
quality) is rework and defect repair (as high as 5000 times the
cost for carrying out unit testing), lost reputation and sales,
failure cost may be internal/external (found by customer)
 Warranty claims are external cost of quality —
internal/external is reference to the project (not the
organization)
o Cause-and-effect / Ishikawa / Fishbone Diagram: for identifying the
cause
o Flowchart: (e.g. SIPOC diagram) for identifying failing process steps
and process improvement opportunities
o Check Sheets (tally sheets): collecting data/documenting steps for
defeat analysis
o Histograms: does not consider the influence of time on the variation
that exits within a distribution
o Pareto Chart: based on 80/20 principle, a prioritization tool to identify
critical issues in descending order of frequency, sort of a histogram
o Statistical Process Control (SPC) Chart: determine if a process is
stable/predictable using statistical sampling (assessed by
accuracy[conformance] and precision[standard deviation]), identity the

50
internally computed control limits (UCL/LCL) and specification limits
(USL/LSL) by the customer/PM
o run chart is similar to control chart, but without the control
 usually +-3sigma i.e. a range of 6 sigma
 a form of time series
 if a process is within control limit but beyond specification
limit, the process is experiencing common cause variation
(random) that cannot be corrected by the system, management
help is needed (special cause can be tackled but NOT common
cause)
o Stability Analysis / Zone Test: rule of seven (7 consecutive on either
side of the mean = out of control), rule of six (six consecutive with a
trend = out of control), rule of ten (10 as a saw-tooth pattern around
the mean), rule of one (1 point beyond control limit) [signal in the
noise]
o Scatter Diagram: for trending, a form of regression analysis
 Data Representation tools:
o Flowcharts
o Logical data model
o Matrix Diagrams: House of Quality (HOQ) used in Quality Function
Deployment (QFD) (method to transform user demands [VOC] into
design quality)
o Mind mapping
 Test and Inspection Planning
o used to determine how to test or inspect the product, deliverable, or
service to meet the stakeholders‘ needs and expectations
 alpha/beta releases
 inspections
 field tests
 Other quality tools:
o Design of Experiments (DOE): change several factors at a time for
each experiment, to determine testing approaches and their impact
on cost of quality
o Loss Function: a financial measure of the user‘s dissatisfaction with
product performance
o Kano Model: differentiate features as satisfy, delight or dissatisfy
o Marginal Analysis: cost-benefit analysis

51
o Force Field Analysis (FFA): reviews any proposed action with proactive
and opposing forces
o Process Improvement Plan: process boundaries, configuration, process
metrics/efficiencies, targets for improved performance
o Quality Checklists: checklist to verify a series of steps have been
performed
o Marginal Analysis: ROI of quality measures
Manage Quality
 Inputs: Project Management Plan, Project Documents, OPA

 Tools & Techniques: Data Gathering, Data Analysis, Decision Making, Data
Representation, Audits, Design for X (DfX), Problem Solving, Quality
Improvement Methods
 Outputs: Quality Report, Test and Evaluation Documents, Change Requests,
Project Management Plan Updates, Project Documents Updates
 Manage Quality is in the Executing Process Group

o ensures the quality standards are being followed, to ensure unfinished
works would meet the quality requirements
o by quality assurance department or sponsor/customer not actively
involved in the project
o primarily concerned with overall process improvement for activities
and processes (rather than the deliverable)
o utilize the data collected in Control Quality Process
 Data Analysis tools:
o Document analysis
o Process analysis — to identify opportunities for process improvements
 Data Representation tools:
o Affinity Diagrams: like a mind-mapping diagram, organize thoughts
on how to solve problems
o Cause and Effect Diagrams
o Flowcharts
o Histograms
o Matrix Diagrams: e.g. ‗house of quality‘ in QFD

52
o Scatter Diagrams
 Design for X(Design for Excellence, DfX)
o a set of technical guidelines that may be applied during the design
phase of a product to optimize specific aspects of the design
o may be able to improve the final characteristics of the product (in
aspects like cost reduction, quality improvement, better performance
and customer satisfaction)
 Quality Audit: to verify quality of processes, to seek improvement, identify
best practices, reduce overall cost of quality, confirm implementation of
approved changes, need quality documentation
 Quality Review: to review the quality management plan
 change requests are mostly procedural changes
 Quality Improvement Methods are used to analyze and evaluate opportunities
for improvements:
o Plan-Do-Check-Act
o Six Sigma
 Quality Reports
o can be graphical, numerical or qualitative
o to provide information to help take corrective actions to fulfil project
quality expectations
o includes quality management issues escalated by the team;
recommendations for process, project and product improvements;
corrective action recommendations (can be rework, defect, bug repair,
inspection, etc.), summary findings
 Test and Evaluation Documents
o used to evaluate the achievement of quality objectives
o may include checklists and detailed requirements traceability matrices
Control Quality
 Inputs: Project Management Plan, Project Documents, Approved Change

Requests, Deliverables, Work Performance Data, EEF, OPA
 Tools & Techniques: Data Gathering, Data Analysis, Inspection, Testing/product
Evaluations, Data Representation, Meetings
 Outputs: Quality Control Measurements, Verified Deliverables, Work
Performance Information, Change Requests, Project Management Plan
Updates, Project Documents Updates

53
 verify the deliverables against customer‘s specifications to ensure customer
satisfaction
 validate the changes against the original approved change requests
 conditional probability (events somewhat related) vs statistical independence
(events not interrelated) vsmutual exclusivity
 statistical sampling for control quality
 variable (continuous) data: measurements, can do maths on e.g. average
 attribute (discrete) data: yes/no, no.123, just an identifier, can‘t do maths on
 QC includes the PM process (lesson learnt, budget, scope)
 tolerance (spec limits, deliverables acceptable) vs control limits (process
acceptable)
 if within control limit but outside tolerance: rework the process to give better
precision
 all control and execution processes may generate lesson learned
 Data Analysis Techniques:
 Testing/Product Evaluations
o an organized investigation to provide objective information about the
quality of the product/service in accordance with project requirements

54
Project Resource Management
 Important: Sexism, racism or other discrimination should never be tolerated,
no matter what the circumstances. You must separate your team from
discriminatory practices, even if those practices are normal in the country
where you‘re working <= This is required for the PMI and PMP® Exam
Plan Resource Management

OPA
 Tools & Techniques: Expert Judgement, Data Representation, Organization
Theory, Meetings
 Outputs: Resource Management Plan, Team Charter, Project Documents
Update
 The Resource Management Plan is to organize and lead the project team as
well as other resources
o include roles and responsibilities (identify resources that can take up
the responsibilities) as documented (ownership of deliverables) in RAM
in the form of RACI chart (matrix) or in a chart/text form, org charts –
an organizational breakdown structure (OBS) and staffing
management plan – staff acquisition, release, resource calendar,
resource histogram, training, rewards, compliance & safety
requirements
 networking is useful in understanding skills of individuals and the political and
interpersonal factors within the organization
 Data Representation techniques:
o Hierarchical-type charts
 Work breakdown structures (WBS)
 Organizational breakdown structure (OBS) — the OBS displays
organizational relationships and then uses them for assigning
work to resources in a project (WBS); the org chart also indicates
the reporting structure of the project
 Resource breakdown structure (RBS)
 RACI chart

55
o Assignment matrix
o Text-oriented formats
 The Team Charter is the document documenting team values, agreements
and operating guidelines to create a favourable culture for the project team
members.
What is a RACI chart / RACI matrix or RACI graph?
 The four letters of RACI stands for:

o Responsible – Which project member is responsible for carrying out
the execution of the task?
o Accountable – The Project member who is held accountable for the
tasks and be given the authority to make decisions? In general, there
should only be 1 member accountable for the project task.
o Consulted – The stakeholders that should be consulted for the work or
be included in the decision making (to be engaged in two-way
communication).
o Informed – Who should be informed of the decisions or progress of
the work by means of email updates, progress reports, etc. (one-way
communication)?
 The RACI chart is a tool for tracking the tools for tracking the roles and
responsibilities of project members for specific project tasks during project
execution.
 While there can be an unlimited number of members responsible for the
execution of a project task, there should only be one member accountable
for the same task. Fixing the accountability to a single person will allow the
project team members to know which person to go to should they need to
know the progress or details of the task. This can also avoid the false
assumption that the other person (if there are more than one accountable)
accountable for the task has taken care of the task but in the end, no one has
looked after the task.
 The member responsible and accountable can be the same for small tasks.
 Below is an example of the RACI chart for a website project:
Project Graphic Copywriter Coder

Manager Designer
Logo Design A R C
Web Copy C AR

56
Web Coding A C R
Estimate Activity Resources

 Tools & Techniques: Expert Judgement, Bottom-up Estimating, Analogous
Estimating, Parametric Estimating, Data Analysis, Project Management
Information System, Meetings
 Outputs: Resource Requirements, Basics of Estimates, Resource Breakdown
Structure (RBS), Project Documents Update
 as a planning process
 closely related to Estimate Cost Process (in Project Cost Management
knowledge area)
 Data Analysis includes:
o Various levels of resource capability or skills
o Different sizes or types of machines
o Different tools (manual versus automated)
o Make-rent-or-buy decisions
 resource calendar spells out the availability of resources (internal/external)
during the project period
 matches human resources to activities (as human resources will affect
duration)
 effort (man day, work week, etc.) vs duration vstime lapsed (total time
needed, including holidays, time off)
 ―alternative analysis‖ includes make-or-buy decisions, different tools, different
skills, etc.
 Resource Requirements (formerly Activity Resource Requirements) details the
types and amounts of resources required for each activity in a work package.
 The basis of estimates include methods, assumptions, constraints, the range of
estimates, confidence levels, risks, etc.
Acquire Resources

57
 Tools & Techniques: Decision Making, Interpersonal and Team Skills, Pre-
assignment, Virtual Teams
 Outputs: Physical Resource Assignments, Project TeamAssignments,
Resource Calendars, Change Requests, Project Management Plan
Updates, Project Documents Updates, EEF Updates, OPA Updates
 to acquire team members/facilities/equipment/materials and other resources

necessary to complete the project work
 pre-assignment is the selection of certain team members/resources in
advance
 halo effect: a cognitive bias (if he is good at one thing, he will be good at
everything)
 Physical Resource Assignments
o documents the physical resource assignments including material,
equipment, supplies, locations, and other physical resources that will be
used during the project
 Project Team Assignments
o documents team assignments including who the team members are
and their roles and responsibilities
 Resource Calendars
o identifies the working days/shifts/holidays for each resource included in
the assignment
Develop Team

 Tools & Techniques: Colocation, Virtual Teams, Communication Technology,
Interpersonal and Team Skills, Recognition and Rewards, Training, Individual
and Team Assessments, Meetings
 Outputs: Team Performance Assessments, Change Requests, Project
Management Plan Updates, Project Documents Updates, EEF Updates, OPA
Updates
 enhancing and improving overall team performance

58
 offer feedback, support, engage team members, manage conflicts, facilitate
cooperation
 Colocation is considered the most effective and productive, should be
arranged if allowed
 training cost can be set within the project budget or supported by the
organization
 Communication Technology includes:
o Shared portal
o Video conferencing
o Audio conferencing
o Email/chat
 Individual and Team Assessment includes:
o Attitudinal surveys
o Specific assessments
o Structured interviews
o Ability tests
o Focus groups
 PM Authority: legitimate (assigned in project charter), reward, penalty, expert
(need to be earned), referent (charisma and likeable, with people with higher
power), representative (elected as representative)
o Expert > Reward are best forms of power. Penalty is worst.
 Tuckman Model: Forming – Storming – Norming – Performing – Adjourning
 the cultural difference should be considered when determining award and
recognition
 recognition should focus on the win-win reward for the team (NOT
competitive-based)
 team building is important throughout the whole project period
 Motivational Theories
o Maslow’s Hierarchy of Needs – personal needs (Physiological >
Security > Social > Esteem > Self Actualization)
o Herzberg’s Hygiene Theory – satisfaction (motivators) vs
dissatisfaction (hygiene factors to avoid dissatisfaction but do not
provide satisfaction, also called KITA factors e.g.
incentives/punishments), hygiene factors include good working
conditions, a satisfying personal life, and good relations with the boss
and coworkers
o Expectancy Theory – Expectancy (extra work will be rewarded)
Instrumentality (good results will be rewarded) Valence (the

59
individual‘s expected reward), for a person to be motivated,
efforts/performance/outcome must be matched – will only work hard
for achievable goals
o Achievement Theory – three motivation needs: achievement (nAch),
power (nPow), affiliation (nAff), best is a balanced style for the PM
o Contingency Theory – task-oriented/relationship-oriented with stress
level (high stress -> task-oriented better)
 Leadership Theory
o including analytical (with expertise), autocratic (with power),
bureaucratic, charismatic, consultative, driver (micromanagement),
influencing, laissez-faire (stay out)
o Theory X – assumes employees are lazy and avoid work, need
incentive/threats/close supervising
o Theory Y – assumes employees may be ambitious and self-motivated,
will perform given the right conditions
o Theory Z – (Japanese) increasing loyalty by providing job for life with
focus on well-being of employee (on and off job), produces high
productivity and morale
o Situational Continuum Leadership – directing/telling >
coaching/selling (manager define the work) > supporting/participating
(subordinate define the work) > delegating according to
maturity/capability of the subordinate
 Team Performance Assessments: assess team performance as a whole
vs project performance appraisals: individual performance
Manage Team

Reports, Team Performance Assessments, EEF, OPA
 Tools & Techniques: Interpersonal and Team Skills, Project Management
Information System
 Outputs: Change Requests, Project Management Plan Updates, Project
Documents Updates, EEF Updates
 in the executing process group

 track team member performance, provide feedback, resolve issues and
manage team changes

60
 when managed properly, differences of opinion can lead to increased
creativity and better decision making
 Project Documents Input
o issue log is fed from Manage Stakeholder Engagement – used to
understand who is responsible for resolving specific issues
o Lessons learned register
o Project team assignments
o Team charter
 conflicts: schedule, project priority, resources, technical opinions,
administrative overhead (too much administration work), cost, personality
 Interpersonal and Team Skills
o conflict management: conflicts force a search for alternatives, need
openness, not personal, focus on present and future
o conflict resolution
 collaborate/problem solve[confrontation of problem] (best)
 compromise/reconcile (give-and-take, temporary/partially
resolve)
 force/direct (worst/short-lived)
 smooth/accommodate (emphasis common grounds and
avoid/touch lightly the disagreements for harmony/relationship)
 withdraw/avoid (other leads to lose-lose)
o compromise is lose-lose
o Forcing would only provide a temporary solution
o Award decisions are made during the process of project performance
appraisals
o Decision making
o Emotional intelligence
o Influencing
o Leadership
 monitoring and controlling of the performance of the staff assigned is
typically performed by functional managers/HR for functional org
Control Resources

Reports, Agreements, EEF
 Tools & Techniques: Data Analysis, Problem Solving, Interpersonal and Team
Skills, Project Management Information System

61
Management Plan Updates, Project Documents Updates
 in the monitoring and controlling process group

 ensure that the physical resources assigned to the project are available as
planned
 monitor the planned versus actual utilization of resources and take corrective
action with changes requests (if needed)
 Data Analysis
o Cost-benefit analysis
o Trend analysis
 Problem-solving steps:
1. Identify the problem
2. Define the problem
3. Investigate
4. Analyze
5. Solve
6. Check the solution

62
Project Communications Management
 assure the timely collection, generation, distribution, storage, retrieval and
ultimate disposition of project information
 this Knowledge Area is very important to the ultimate success of the project
 message transmission: 7% in word, 38% in vocal pitch, 55% in body language
(according to Albert Mehrabian)
 must not delay in communicating good and even bad news
 the sender has the responsibility to ensure the receiver correctly understand
the message
 if part of the project is procured, more formal written communication will be
expected
Plan Communications Management

OPA
 Tools & Techniques: Expert Judgement, Communication Requirements
Analysis, Communication Technology, Communication Models, Interpersonal
and Team Skills, Data Representation, Meetings
 Outputs: Communications Management Plan, Project Management Plan
Update, Project Documents Update
 identify the needs for communication with stakeholders of the project

o including the who, what, when (frequency), why, where and how of
communications needs and the persons responsible
o may need to limit who can communicate with whom and who will
receive what information
o time and budget for the resources, escalation path, flow charts,
constraints, guideline and templates
 efficient communication: only the required messages
 effective communication: right timing, right format, right medium
 Communication Methods
o interactive (multidirectional communication, most effective)
o push (active, messages sent without validation of receipt)
o pull (passive, access directly by stakeholders)
 low context vshigh context (Japanese — more polite)

63
 (Shannon-Weaver model) Sender-Receiver Model: i) encoded the idea, ii)
message and feedback, iii) medium, iv) noise level, v) the decoded idea. The
sender to ensure info is clear, complete and the recipient correct
understands. The recipient to ensure the complete message is received (to
acknowledge) and provide feedback/response.
 Effective Listening:
o feedback
o active listening
o paralingual (voice expression, nonverbal elements)
 Communication channels: N (N -1) / 2 // N is the number of team
members
 meetings should facilitate problem-solving
 As a norm, PM spends 90% of their time on COMMUNICATION activities,
50% of the time is spent on communicating with the team
Manage Communications

Reports, EEF, OPA
 Tools & Techniques: Communication Technology, Communication Models,
Communication Skills, Project Mangement Information System, Project
Reporting, Interpersonal and Team Skills, Data Representation, Meetings
 Outputs: Project Communications, Project Management Plan Update, Project
Documents Update, OPA Update
 create, collect, distribute, store, retrieve and dispose of project information

according to the Communications Management Plan
o ensures good communication, noises managed, stakeholders may
feedback on how to improve
 Communication Barriers vs Communication Enhancers
 55% message thru body language, 38% thru paralingual, 7% thru words
used
 Types of Communications: Formal Written, Formal Verbal, Information Written,
Informal Verbal
 Interpersonal and Team Skills include:
o Active listening
o Conflict management

64
o Cultural awareness
o Meeting management
o Networking
o Political awareness
 Project Reporting: status, progress, variance, trend, earned value reports and
forecasts, summary of changes, risks and issues
 PM Plan Update to show the latest performance (against Performance
Measurement Baseline)
 Feedback from stakeholders are to be stored in OPA
Monitor Communications

Data, EEF, OPA
 Tools & Techniques: Expert Judgement, Project Management Information
System, Data Analysis, Interpersonal and Team Skills, Meetings
Management Plan Update, Project Documents Update
 to ensure optimal information flow for effective stakeholder expectation

management
 issue log is to document the issues and monitor its resolutions (by the person
responsible)
 Data Analysis tool includes stakeholder engagement assessment matrix — to
assess the current situation of communication effectiveness through the
review of changes between the desired and current engagement and
adjusting communications (alternative ways/frequency/methods) as necessary

65
Project Risk Management
 Project Risk Management is involved in risk identification, management and
response strategy impacts every area of the project management lifecycle
o risk = uncertainty
o risk management= increase the probability of project success by
minimizing/eliminating negative risks (threats) and increasing positive
events (opportunities)
o everyone is responsible for identifying risks for the project
 risk has one or more causes and has one or more impacts
 risk attitudes (EEF): risk appetite (willingness to take risks for rewards),
tolerance for risk (risk tolerant or risk-averse), risk threshold (level beyond
which the organization refuses to tolerate risks and may change its response)
 pure (insurable) riskvs business risk (can be +ve or -ve)
 known risks that cannot be dealt with proactively (active acceptance) should
be assigned a contingency reserve or if the known risks cannot be analyzed,
just wait for its happening and implement the workaround (which is
considered passive acceptance)
Plan Risk Management

OPA
 Outputs: Risk Management Plan
 The Plan Risk Mangement process is involved in defining and providing

resources and time to perform risk management.
o including methodology, roles and responsibilities, budget, timing
(when and how often), risk categories (e.g. risk breakdown structure
RBS), definitions, stakeholder tolerances (an EEF), reporting and
tracking
 performed at project initiation and early in the Planning process
 failure to address risks early on can ultimately be more costly later on in
the project
 Data Analysis techniques include stakeholder risk profile analysis (using the
stakeholder register), strategic risk scoring sheets, etc.

66
 a risk breakdown structure (RBS) (included in the PM Plan) – risks grouped
by categories and occurring areas
 key risk categories:
o scope creep
o inherent schedule flaws
o employee turnover
o specification breakdown (conflicts in deliverable specifications)
o poor productivity
Identify Risks
 Inputs: Project Management Plan, Project Documents, Agreements,

Procurement Documentation, EEF, OPA
 Tools & Techniques: Expert Judgement, Data Gathering, Data Analysis,
Interpersonal and Team Skills, Prompt Lists, Meetings
 Outputs: Risk Register, Risk Report, Project Document Updates
 to find out and document all risks affecting the project from all aspects of the
project, including:
o agreements/contracts within/outside of the organization
o procurements
o requirements, schedule, cost, resource, quality, scope, etc. from the
project management plan
 Data Gathering Techniques: brainstorming, checklists, interviews, Delphi
technique [a panel of independent experts, maintain anonymity, use
questionnaire, encourage open critique],
o root cause analysis [performed after an event to gain understanding
to prevent similar events from occurring], SWOT analysis, assumption
and constraint analysis
 root cause analysis: safety-based (prevent accidents),
production-based, process-based (include business process),
failure-based, systems-based (all above)
 root cause analysis tools: FMEA, Pareto Analysis, Bayesian
Inference (conditional probability), Ishikawa Diagrams, Kepner-
Tregoe
o Monte Carlo analysis can identify points of schedule risks

67
 Prompt List
o The prompt list (newly added in PMBOK® Guide 6th Edition) is a
predetermined list of risk categories that are at the lowest level of the
risk breakdown structure which is used to assist in identifying risks of
the projects
o examples of prompt lists:
 PESTLE (political, economic, social, technological, legal,
environmental)
 TECOP (technical, environmental, commercial, operations,
political)
 VUCA (volatility, uncertainty, complexity, ambiguity)
 Risk Register (typically not including the risk reserve)
o The Risk Register may include a risk statement
o any risk with a probability of >70% is an issue (to be dealt with
proactively and recorded in the issue log)
 The Risk Report (new in PMBOK® Guide 6th Edition) is a document used to
present information (e.g. no. of identified threats and opportunities,
distribution of risks across risk categories, metrics and trends) on overall
project risk. It also includes a summary information on individual project risks.
Perform Qualitative Risk Analysis

 Tools & Techniques: Expert Judgement, Data Gathering, Data Analysis,
Interpersonal and Team Skills, Risk Categorization, Data Representation,
Meetings
 Outputs: Project Document Updates (e.g. Risk Register)
 prioritizing risks for further analysis/action and identify high priority risks
o risks requiring near-term responses are more urgent to address
o need to identify bias and correct it (e.g. risk attitude of the
stakeholders)
 Data Analysis Techniques include:
o Risk data quality assessment
o Risk probability and impact assessment

68
o Assessment of other risk parameters (e.g. urgency, proximity,
dormancy, manageability, controllability, detectability, connectivity,
strategic impact, propinquity)
 Data Representation Tools:
o qualitative risk assessment matrix (format described in the Risk
Management Plan)
o hierarchical-type charts
 the risk register is updated along the following processes: Perform Qualitative
Risk Analysis, Perform Quantitative Analysis, Plan Risk Responses and Monitor
& Control Risks
Perform Quantitative Risk Analysis

 Tools & Techniques: Expert Judgement, Data Gathering, Interpersonal and
Team Skills, Representation of Uncertainty, Data Analysis
 Outputs: Project Document Updates
 the cost, schedule and risk management plan contains guidelines on how to
quantitatively analyze risks
o involves mathematical modelling for forecasts and trend analysis
 Representation of Uncertainty (probability distribution) reflects the risks as a
probability distribution, which can be in the following distribution types:
o Triangular
o Normal (bell-shaped curve)
o Lognormal
o Beta
o Uniform
o Discrete
o sensitivity analysis (using the tornado diagram as presentation) for
determining the risks that have the most impact on the project
o Failure Modes Effects Analysis (FMEA)
o FMEA for manufactured product or where risk may be undetectable,
Risk Priority Number (RPN) = severity (1-10) x occurrence ([0.07%] 1-10

69
[20%]) X detectability (1-10 [undetectable]), also a non-proprietary
approach for risk management
o Expected Value / Expected Monetary Value (EMV), probability x
impact (cost/effort lost), opportunities (+ve values), threats (-ve values)
o Simulations/Monte Carlo Analysis – by running simulations many
times over in order to calculate those same probabilities heuristically
just like actually playing and recording your results in a real casino
situation, ‗S‘ curve (cumulative distribution) will result, may use
PERT/triangular distribution to model data, may use thousands of data
points (a random variable), for budget/schedule analysis
o Decision Tree Analysis – another form of EMV, branching: decision
squares (decision branch – options), circles (uncertainty branch –
possible outcomes)
o Influence Diagram – graphical representations of situations showing
causal influences, time ordering of events, and other relationships
among variables and outcomes
Plan Risk Responses

 Tools & Techniques: Expert Judgement, Data Gathering, Interpersonal and
Team Skills, Strategies for Threats, Strategies for Opportunities, Contingent
Response Strategies, Strategies for Overall Project Risks, Data Analysis,
Decision Making
 Outputs: Change Requests, Project Management Plan Updates, Project
Document Updates
 plan response to enhance opportunities and reduce threats

 each risk is owned by a responsible person
 the watch list is the list of low priority risks items in the risk register
 a fallback planwill be used if 1) risk response not effective, 2) accepted risk
occurs
 Negative Risk Strategies:
o eliminate/avoid (not to use, extend the schedule)
o transfer (outsource, warranty, insurance)

70
o mitigate (reduce the risk of more testing/precautionary
actions/redundancy)
o accept (passive – do nothing or active – contingency)
o escalate (escalates a risk to the appropriate party — can be deleted
from the risk register or retain in the risk register with a remark)
 Positive Risk Strategies:
o exploit (ensure opportunity by using internal resources e.g. reduce
cost/use of top talents/new tech)
o share (contractor with specialized skills, joint venture)
o enhance (increase likelihood / impact e.g. fast-tracking, add resources
etc.)
o accept
 passive risk acceptance to be dealt with when the risk occurs
 Strategies for Overall Project Risk
o the PM needs to address the overall project risks with one of the
following strategies:
 Avoid
 Exploit
 Mitigate/Enhance
 Accept
 Contingency Plan (contingent response strategies) (plan A) are developed
for specific risk (when you have accepted a risk) with certain triggersvs
Fallback Plan (plan B)
 Residual Risks – risks remain after the risk response strategy was
implemented, may be identified in the planning process (may subject to
contingency/fallback planning) They don‘t need any further analysis because
you have already planned the complete response strategy you know in
dealing with the risk that came before them.
 Secondary Risks – risk arises when the risk response strategy was
implemented
 Reserve Types
o Contingency Reserve: known unknowns (determined risk), part of cost
baseline
o Management Reserve: unknown unknowns (discovery risk), part of
project budget
 The Risk Register is now completed with: risks and descriptions, triggers,
response strategy, persons responsible, results from qualitative and

71
quantitative analysis, residual and secondary risks, contingency and fallback,
risk budget/time
Implement Risk Responses
 Inputs: Project Management Plan, Project Documents, OPA

 Tools & Techniques: Expert Judgement, Interpersonal and Team Skills, Project
Management Information System
 Outputs: Change Requests, Project Document Updates
 in the Executing process group

 implementing risk responses is the responsibilities of the risk owners
 to ensure that agreed upon risk responses (as from the Plan Risk Response
process) are executed as planned to
o address overall project risk exposure
o minimize individual project threats
o maximize individual project opportunities
 the Project Management Information System provides the information to
allow agreed-upon risk response plans and associated activities to be
executed alongside other project activities
Control Risks
 Inputs: Project Management Plan, Project Documents, Agreements, Work

Performance Data, Work Performance Reports
 Tools & Techniques: Data Analysis, Audits, Meetings
Management Plan Updates, Project Document Updates, OPA Updates
 when all the above risk planning processes have been performed with due
diligence, the project is said to have a low-risk profile
 responsibilities include:
o to check if assumptions are still valid, procedures are being followed
and any deviance
o to identify new risks and evaluate effectiveness of risk response plan
o any need to adjust contingency and management reserves

72
o to re-assess the individual risk response strategies to see if they are
effective
 risk audits deal with the effectiveness of risk response and the risk
management process
o risk audits are usually performed by experts outside project team for
the whole risk management process
o reserve analysis – apply only to the specific risks of the project for
which they were set aside
o technical performance analysis
 workaround: when no contingency plan exists, executed on-the-fly to address
unplanned events – still need to pass through normal change control if
change requests are needed
o determine the workaround is performed in control risks

73
Project Procurement Management
 sellers are external to the project team
 need to go through all 4 processes for each and every procurement
 Contract Elements:
o offer (seller offer buyer)
o acceptance (buyer criteria)
o capacity (physical/financial capabilities)
o consideration (seller receive)
o legal purpose (must be legal under law)
 PM needs to understand terms and conditions, identify risks, include
procurement schedule and involve in negotiations
 Centralized contracting vs Decentralized contracting
 Procurement Categories:
o major complexity (high risk)
o minor complexity (low risk, expensive)
o routine purchase (Commercial Off the Shelf Products COTS)
o goods and services (to perform part of our product)
 Suppliers can be:
o sole source
o single source (preferred, for building a long-term relationship)
o oligopoly (very few sellers)
 a contract is not required to be written, it can be verbal or handshake, for
internal projects, a formal contract is best
Plan Procurement Management
 Inputs: Project Charter, Business Documents, Project Management Plan,

Project Documents, EEF, OPA
 Tools & Techniques: Expert Judgement, Data Gathering (e.g. Market Research),
Data Analysis, Source Selection Analysis, Meetings
 Outputs: Procurement Management Plan, Procurement Strategy, Bid
Documents, Procurement Statement of Work, Source Selection Criteria,
Make-or-buy Decisions, Independent Cost Estimates (inside or outside the
organization), Change Requests, Project Documents Update, OPA Updates
 identify explicitly what is needed

74
 identify possible sellers and pre-meeting with them
 make-or-buy analysis (determine whether to obtain products/services
outside of the organization) is a compulsory process, needs to take risks into
considerations
o carefully written terms and conditions can transfer/share risks
o teaming agreements or joint ventures
 Procurement Documents:
o request for proposal (RFP)
o invitation for bid (IFB)
o request for quote (RFQ)
o request for information (RFI)
o tender notice
o invitation for negotiation
o seller initial response
 The procurement management plan specifies how a project will acquire
goods/services from outside, includes contract type, risk management,
constraints and assumptions, insurance requirements, form and format, pre-
qualified sellers, metrics used, etc.
o Return on investment (ROI)
o Internal rate of return (IRR)
o Discounted cash flow
o Net present value (NPV)
o Benefit/cost analysis (BCA)
 target cost = total cost = estimated cost, total price = total cost + total profit
 Point of Total Assumption – (in fixed-price (incentive fee) contracts) in
budget overrun, the point at which the seller assumes all additional costs for
delivering the product/service
o PTA = (Ceiling Price – Total Price) / Buyer’s Share Ratio + Target
Cost
o PTA = Target Cost + (Ceiling Price – Target Price) / % Share of Cost
Overrun
 Procurement Statement of Work (SOW) is a legal document subject to legal
reviews, legal advice should be sought throughout the whole procurement
process, can be developed by the seller or buyer and must be detailed enough
to allow the potential sellers to decide whether they want/are qualified (at a
minimum) to pursue the work
o performance (describe what can be accomplished)

75
o functional (convey the end purpose or result)
o design (convey precisely what are to be done),
 Evaluation Criteria: risk, understanding of need, life-cycle cost, technical
capability, management approach, technical approach
 Procurement Strategy (new in PMBOK® Guide 6th Edition)
o the procurement strategy determines the project delivery method:
 with/without subtracting, joint venture, representative, etc.
 turnkey, design and build (DB), build own operate transfer
(BOOT), etc.
o contract payment types:
 Firm Fixed Price (FFP) – the price is fixed, specifications are well
known, risk on the seller
 Fixed Price Incentive Fee (FPIF) – incentives for faster/better than
contracted
 Fixed Price with Economic Adjustment / Economic Price
Adjustment (FPEA / FP-EPA) – inflation are taken into account
 Purchase Order (PO) – for off-the-shelf goods/services with
published rates
 Cost Reimbursable (CR) / Cost Plus – buying the expertise (not
the products), outcome is not clear, risk on the buyer, little
incentive to control costs on buyer, need invoice audits
 Cost Plus Fixed Fee (CPFF)
 Cost Plus Incentive Fee (CPIF) – incentive for performance,
sharing of unused money if under/over contracted
amount
 Cost Plus Award Fee (CPAF) – award to be given based on
agreed criteria, solely decided by the customer on the
degree of satisfaction
 Cost Plus Percentage of Costs (CPPC) – illegal for
contracts with US Government
 Cost Contract – no profit, for NGO
 Best Efforts – obligates the seller to utilize best attempts, high
uncertainty in meeting the goal
 Time and Materials (T&M) – (hybrid type) when scope is not
known, need constant monitoring to control schedule and cost,
simple, for short duration, good for proof-of-concept type
projects
o procurement types

76
 Bid Documents
o Request for Proposal (RFP) – cost reimbursable contract,
functional/performance SOW
o Invitation for Bid (IFB) / Request for Bid (RFB) – fixed-price contract,
design SOW
o Request for Quote (RFP) – time and material, any type of SOW
 Contractual Terms
o Cancellation for Convenience – buyer can cancel and pay up to the
point
o Cancellation for Cause – default by either party, may result in legal
actions
o Escrow – survivability of seller in doubt, put the product in escrow (esp.
if seller does not give up intellectual properties)
o Force Majeure – standard disclaimer refers to ‗Acts of God‘
o Indemnification / Liability – responsible party
o LOI Letter of Intent – not legally binding
o Privity – the contractor may use sub-contractor, no direct contractual
relationship with buyer
o Retainage – amount to be withheld to ensure delivery
o Risk of Loss – how the risk is shoulder by the parties
o Time is of the Essence – delay in delivery will cause cardinal breach of
contract
o Work Made for Hire – all work owned by the buyer
Conduct Procurements

Procurement Documentation, Seller Proposals, EEF, OPA
 Tools & Techniques: Expert Judgement, Advertising, Bidder Conferences, Data
Analysis, Interpersonal and Team Skills
 Outputs: Selected Sellers, Agreements, Change Requests, Project Management
Plan Updates, Project Documents Update, OPA Updates
 identify the sellers and award the contracts

 PM may not be the lead negotiator on procurement but may be present to
assist
o may need senior management approval before awarding the contracts

77
 bidder‘s conference is a Q&A session with bidders, all bidders receive the
same information (bidder are careful not to expose their technical approach
during the session => may not have many questions)
 remember NOT to have secret meetings or communications with individual
vendors
 review seller proposals: weighting systems, independent estimates, screening
systems (screen out non-qualified vendors), seller rating systems (for past
performance), expert judgement
 Data Analysis includes ensuring that proposal is full and complete
 Contract Negotiations and Tactics
o Fait Accompli – not negotiable terms
o Deadline – deadline for deliverables
o Good Guy/ Bad Guy – one friendly, one aggressive
o Missing Man – decision maker is missing
o Limited Authority – not given authority
o Fair and Reasonable – what is fair?
o Unreasonable – making unreasonable demands
o Delay – esp in critical moments
o Attack – force compliance
 The agreement is legally binding and should include (PM should NOT attempt
to write the agreement):
o statement of work, schedule baseline, performance reporting, the
period of performance, roles and responsibilities, warranty, payment
terms, fees and retainers, incentives, liability, penalties, etc.
Control Procurements

Procurement Documentation, Approved Change Requests, Work Performance
Data, EEF, OPA
 Tools & Techniques: Expert Judgement, Claims Administration, Data Analysis,
Inspection, Audits
 Outputs: Closed Procurements, Work Performance Information, Procurement
Documentation Updates, Change Requests, Project Management Plan
Updates, Project Documents Update, OPA Updates
 would be performed by both seller and buyer

78
 manage procurement relationships, monitor contract performance, make
change and corrections
o Earned value analysis (EVA)
o Trend analysis
 the procurement administrator may be external to the project team
o to close a procurement, the project management team should check
and approve all deliverables and a written notice be sent to the seller
(closed procurement)
o may identify early signs and capture details for pre-mature termination
of a contract
 For Fixed Price contracts, look out for Bait and Switch (replace with cheaper
materials), look out for excessive change requests
 For Cost Reimbursable contracts, audit all invoices, look out for additional
charges, tie payment to milestones, make sure people with the required skill
sets are doing the job
 For Time and Materials contracts, ensure hours are not padded, follow the
milestone dates
 the claims administration process deals with changes/disputes, disputes is
best to be settled through negotiation > ADR
 may need Alternative Dispute Resolution (ADR) by 3rd parties in case disputes
cannot be settled
 OPA may include the seller‘s performance
(The “Close Procurements” process in PMBOK® Guide 5th Edition has been
moved and merged into “Control Procurements and Close Project or Phase”)

79
Project Stakeholder Management
 stakeholders are groups/individuals who may affect/be affected by the
project
 identify stakeholders is a continual process throughout the project lifecycle as
some stakeholders may become irrelevant while new stakeholders may be
identified as the project evolves
 the Project Manager is responsible for the engaging and managing the
various stakeholders in a project
o identify stakeholders, communicate and engage them, manage
expectations and focus on satisfaction
o stakeholder satisfaction is a key project objective
Identify Stakeholders
 Inputs: Project Charter, Business Documents, Project Management Plan,

Project Documents, Agreements, EEF, OPA
 Tools & Techniques: Expert Judgement, Data Gathering, Data Analysis, Data
Representation, Meetings
 Outputs: Stakeholder Register, Change Requests, Project Management Plan
Update, Project Documents Update
 identify stakeholders and document the importance/influence (=active

involvement) /impact/interest/involvement of stakeholders/groups of
stakeholders
 stakeholders from procurement process and operation process needed to be
included
o agreements are used for determining external stakeholders such as the
seller
 Data Gathering Tools:
o Questionnaires and surveys
o Brainstorming
o stakeholder analysis techniques

80
 Interest, rights (legal or moral rights), power/interest,
power/influence or impact/influence grid, salience model,
prioritization, etc.
 Data Representation Tools:
o Power/interest grid, power influence grid or impact/influence grid (3
‗I‘s: importance, interest, influence)
 determine the stakeholders‘ hot buttons (what response in specific situations)
and develop support strategies
 stakeholders have the greatest influence in the initial stage of the project
 stakeholder analysis matrix is part of the stakeholder management strategy
(output of Identify Stakeholders Process)
 Salience Model: describing stakeholders based on the power (influence),
urgency and legitimacy
 document only influential stakeholders if there is a large number of
stakeholders
 document the impact using a power/influence grid, power/interest grid,
influence/impact grid, salience model
Plan Stakeholder Engagement
 Inputs: Project Charter, Project Management Plan, Project Documents,

Agreements, EEF, OPA
Making, Data Representation, Meetings
 Outputs: Stakeholder Engagement Plan
 strategies to engage stakeholders throughout the project lifecycle

 Stakeholder Engagement Plan contains: current/desired engagement levels,
scope and impact to stakeholders, interrelationships, communication
requirements and forms, how to update the plan
o The distribution of this plan requires precautions as the engagement
level of stakeholders is a very sensitive information
 Data Analysis Tools:
o Assumptions and constraint analysis
o Mind mapping

81
o Stakeholder Engagement Assessment Matrix: (C-current level, D-
desired level)
o SWOT analysis
 Engagement Level
o Unaware
o Resistant: resistant to change
o Neutral
o Supportive: supportive of change
o Leading: actively engaged in project success
Manage Stakeholder Engagement
 Inputs: Project Management Plan, Project Documents, Agreements, EEF, OPA

 Tools & Techniques: Expert Judgement, Communication Skills, Interpersonal
and Team Skills, Ground Rules, Meetings
 Outputs: Change Requests, Project Management Plan Update, Project
Documents Update
 ultimate aim is to increase support and minimize resistance from

stakeholders by addressing issues with a view to increasing the success of the
project
o communicate and work with stakeholders to meet their
needs/expectations and address issues
o build trust and resolve conflicts, negotiation skills, communication skills
o need to communicate bad news/issues in a timely manner (not to
hide, not to delay)
 the communication requirements of individual stakeholder are recorded in the
Project Communication Plan
 PM may call upon the sponsor for assistance
 Ground rules are created to set the expected behaviour of project team
members and other stakeholders (for stakeholder engagement)
 the Issue Log (Action Item Log): to identify issues/define impacts, owner
(most important element) and priority/with the due date

82
Monitor Stakeholder Engagement

Data, EEF, OPA
 Tools & Techniques: Data Analysis, Decision Making, Data Representation,
Communication Skills, Interpersonal and Team Skills, Meetings
Management Plan Update, Project Documents Update
 monitor overall stakeholder relationships and adjusting strategies to achieve

the desired level of stakeholder engagement
 Decision-Making Tools:
o Multicriteria decision analysis
o Voting

83

PMBOK Study Notes PDF

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

PMBOK Study Notes PDF

Caricato da

Copyright:

Formati disponibili

PMP Exam

Based on A Guide to the

 Project – a temporary endeavor to create a unique product, service or result

Project Management Solutions BD

 Project Management – the application of (all appropriate) knowledge, skills,

Project Management Solutions BD

The Project Management Process Groups

 Planning and Executing are iterative. Monitoring and Controlling is exercised

Project Management Solutions BD

 align project purposes with stakeholders’ expectations

Project Management Solutions BD

 coordinating human/infrastructure resources in accordance with the project

Monitoring and Controlling

 measure performance, address change requests, recommend corrective/

 either project finished or cancelled

Project Management Solutions BD

1. Project Integration Management – assemble and combine all the various

49 processes of Project Management

Project Management Solutions BD

Each project management process is now categorized into:

 used once or at predefined points in the project

It is important to understand the differences between PMBOK® Guide 6th edition

Project Management Tools and Techniques (T&T)

 The organizational system determines the power, influence, competence,

Project Management Solutions BD

Project Management Solutions BD

 Project Manager: an individual assigned by the organization to lead the team

Project Management Solutions BD

 Project Life Cycle: includes: initiating, planning and organizing, carrying

Project Management Solutions BD

Code of ethics and professional conduct

 in the best interest of the society, public and environment

 show respect to others

 transparency in decision making

Project Management Solutions BD

 understand the truth and be truthful

Other Important Project Management Terms

 The Configuration Management Knowledge Bases contain baselines of all

Project Management Solutions BD

Project Management Solutions BD

Project Management Solutions BD

 integration management is required when different project management

Develop Project Charter

 Inputs: Business Documents (including business case), Agreements, EEF, OPA

 to formally authorize the project and allow the PM to apply organizational

Project Management Solutions BD

Develop Project Management Plan

 Inputs: Project Charter, Outputs from other processes, EEF, OPA

 the project management plan is a formal written document on how the

Project Management Solutions BD

Direct and Manage Project Work

 Inputs: Project Management Plan, Project documents (including change log,

Project Management Solutions BD

Manage Project Knowledge

 Inputs: Project Management Plan, Project documents, Deliverables, EEF, OPA

 This newly added Manage Project Knowledge process is involved in

Project Management Solutions BD

Monitor and Control Project Work

 Inputs: Project Management Plan, Project documents, Work performance

Project Management Solutions BD

 Inputs: Project Management Plan, Project documents, Work performance

 changes in the project arise as a result of missed requirements, views of

Project Management Solutions BD