#Pmp in a3 edition_1

Classification: Internal Use
linkedin.com/in/mohamed-kassem-8630a872
PROJECT MANAGEMENT KNOWLEDGE AREA(S) IN A3
BY : MOHAMED YAKOUT KASSEM
2020
Edition#1
REV0.00

04- Project Integration management.
05- Project Scope management.
06- Project Schedule management.
07- Project Cost management.
08- Project Quality management.
09- Project Resources management.
10- Project Communication management.
11- Project Risk management.
12- Project Procurement management.
13- Project Stakeholder management.
- Project Manager Tasks .
This Booklet provide a high-level summery for
PMBOK Knowledge area(s) , objective to support
whom study PMP or willing to get a helicopter
view for Project management Knowledge.
“It’s a way to knowledge simplification”.
PMP_IN A3
This document is not PMP
main dish , it’s Just snacks
To get the Knowledge you need
to dig deeper.
All Document available through :
PMBOK 6th edition
linkedin.com/in/mohamed-kassem-8630a872
https://www.linkedin.com/feed/hashtag/?keywords=pmp_in_a3
Mohamed Yakout Kassem
LinkedIn: linkedin.com/in/mohamed-kassem-8630a872

7
6
6
4
3
6
3
7
3
4
4911210242
PMBOK® Guide Key
Component
Brief Description
Project life cycle The series of phases that a project passes through from its start to its completion.
Project phase
A collection of logically related project activities that culminates in the completion of one or more
deliverables.
Phase gate
A review at the end of a phase in which a decision is made to continue to the next phase, to
continue with modification, or to end a program or project.
Project management
processes
A systematic series of activities directed toward causing an end result where one or more inputs
will be acted upon to create one or more outputs.
Project Management
Process Group
A logical grouping of project management inputs, tools and techniques, and outputs. The Project
Management Process Groups include Initiating, Planning, Executing, Monitoring and Controlling,
and Closing. Project Management Process Groups are not project phases.
Project Management
Knowledge Area
An identified area of project management defined by its knowledge requirements and described in
terms of its component processes, practices, inputs, outputs, tools, and techniques.
Description of PMBOK® Guide Key Components
Project Life Cycle
Starting
the Project
Organizing
and Preparing
Carrying Out
the Work
Ending the
Project
initiating
Processes
Planning
Processes
Executing
Processes
Closing
Processes
Monitoring
and
Controlling
Processes
Process Group
10 Knowledge Areas
Phase
Gate
Project
Phase
Potential
Use Timeline
49 Process
PMPINA#3

Example Decision Tree
IN:
1. Business documents
- Business case. ”Describes the
necessary information from a
business standpoint to determine
whether the expected outcomes
of the project justify the required
investment” The business case is
created as a result of one or more
of the following:
• Market demand
• Organizational need
• Customer request
• Technological advance
• Legal requirement
• Ecological impacts
• Social need
- Benefits management plan.
2. Agreements “Agreements are used to
define initial intentions for a project. Could
be MOUs , SLA,LOI Typically, a contract is
used when a project is being performed for
an external customer.
3. Enterprise environmental factors
4. Organizational process assets
------------------------------------
TT:
1. Expert Judgment.
2. Data gathering
- Brainstorming “This technique is used to
identify a list of ideas in a short period of time”
- Focus groups
- Interviews
3. Interpersonal and team skills
- Conflict management
- Facilitation “ ability to effectively guide a
group event to a successful decision, solution, or
conclusion.”
- Meeting management
4. Meetings-
-----------------------------------
O:
1. Project charter
high-level information on the project such as:
- Project purpose;
- Measurable project objectives and
related success criteria;
- High-level requirements;
- High-level project description,
boundaries, and key deliverables;
- Overall project risk;
- Summary milestone schedule;
- Preapproved financial resources;
- Key stakeholder list;
- Project approval requirements (i.e.,
what constitutes project success, who decides the
project is successful, and who signs off on the
project);
- Project exit criteria (i.e., what are the
conditions to be met in order to close or to
cancel the project or phase);
- Assigned project manager, responsibility,
and authority level; and
- Name and authority of the
sponsor or other person(s)
authorizing the project charter.
1. Assumption log
1- Develop Project Charter
DEVELOP PROJECT CHARTER :
Process of developing a document that formally
authorizes the existence of a project and provides the
project manager with the authority to apply
organizational resources to project activities.
The key benefits of this process are that it provides a
direct link between the project and the strategic
objectives of the organization, creates a formal record
of the project, and shows the organizational
commitment to the project.
PMBOK Page 75 PDF/114
IN:
1. Project charter
2. Outputs from other processes
------------------------------------
TT:
1. Expert Judgment.
2. Data gathering
- Brainstorming
- Checklists “organizations have standardized
checklists available based in their own
experience or use checklists from the
industry. A checklist may guide the project
manager to develop the plan or may help to
verify that all the required information is
included in the project management plan.”
- Focus groups ”Bring together stakeholders”
- Interviews “Interviews are used to obtain
specific information from stakeholders to
develop the project management plan or
any component plan or project document”
- Facilitation
4. Meetings
------------------------------------
O:
1. Project management plan
Subsidiary management plans:
- Scope management plan.
- Requirements management plan
- Schedule management plan
- Cost management plan.
- Quality management plan
- Resource management plan
- Communications management plan
- Risk management plan.
- Procurement management plan
Baselines:
- Scope baseline.
- Schedule baseline.
- Cost baseline.
Additional components. “PMBOK_Page_88”
- Change management plan.
- Configuration management plan.
- Performance measurement baseline.
- Project life cycle.
- Development approach.
- Management reviews.
2- Develop Project Management Plan
3- Direct and Manage Project Work
PMBOK Page 90 PDF /129
DEVELOP PROJECT MANAGEMENT PLAN
Process of defining, preparing, and coordinating all plan
components and consolidating them into an integrated
project management plan.
The key benefit of this process is the production of a
comprehensive document that defines the basis of all
project work and how the work will be performed.
4- Manage Project Knowledge
5- Monitor and Control Project Work
6- Perform Integrated Change Control
1- Develop Project charter “IN” 2- Developed Project management Plan “PL” 3- Direct and Manage Project Work “EX” 4- Manage Project Knowledge “EX” 5- Monitor and Control Project Work “M&C” 6 – Perform Integrated Change Control “M&C” 7- Close Projector Phase “C”
PROJECT INTEGRATION MANAGEMENT
IN:
- Any component
2. Project documents
- Change log
- Lessons learned register
- Milestone list
- Project communications
- Project schedule
- Requirements traceability matrix
- Risk register
- Risk report
3. Approved change requests
4. Deliverables
------------------------------------
TT:
1. Expert Judgment.
2. Project management information system
3. Meetings
------------------------------------
O:
1. Deliverables
2. Work performance data
3. Issue log “may include: Issue type, Who
raised the issue and when, Description,
Priority, Who is assigned to the issue,
Target resolution date, Status, and Final
solution.
4. Change requests “ Change requests may
include , Corrective action, Preventive
action. Defect repair, Updates.”
5. Project management plan updates
- Any component
6. Project documents updates
- Activity list
- Assumption log
- Requirements documentation
- Risk register
- Stakeholder register
7. Organizational process assets updates
IN:
1. Project management Plan
- All components
“provides information on
effective practices in
knowledge management”.
- Project team assignments
- Resource breakdown structure
- Source selection criteria
3. Deliverables “typically tangible
components completed to meet
the project objectives .
------------------------------------
TT:
1. Expert Judgment.
2. Knowledge management
Networking, Communities of practice
; Meetings ;Work shadowing / reverse
shadowing; Discussion forums such as
focus groups; Knowledge-sharing events
such as seminars /conferences;
Workshops; Storytelling; Creativity
/ideas management techniques
;Knowledge fairs and cafés, Training
that involves interaction between
learners.
1. Information management “Lessons
learned register; Library services; web
searches / reading published articles , PMIS
- Active listening - Facilitation
- Leadership - Networking
- Political awareness
------------------------------------
O:
1. Lessons learned register
- Any component
updates
IN:
- All components
- Any component
4. Work performance information
5. Agreements
------------------------------------
TT:
1. Expert Judgment.
2. Data analysis
- Alternatives analysis
- Cost-benefit analysis
- Earned value analysis
- Root cause analysis
- Trend analysis
- Variance analysis
3. Decision making “technique that can be
used includes but is not limited to voting
;Voting can include making decisions based
on unanimity, majority, or plurality.
4. Meetings
------------------------------------
O:
1. Work performance reports
2. Change requests
- Any component
- Cost forecasts
- Issue log
- Risk register
- Schedule forecasts
IN:
- Change management plan
- Configuration management plan
- Scope baseline
- Schedule baseline
- Cost baseline
- Basis of estimates
- Risk report
4. Change requests
------------------------------------
TT:
1. Expert Judgment.
2. Change control tools
“Configuration control is focused
on the specification of both the
deliverables and the processes,
while change control is focused on
identifying, documenting, and
approving or rejecting changes to
the project documents,
deliverables, or baselines.
3. Data analysis
4. Decision making
- Voting
- Autocratic decision making
- Multi criteria decision analysis
5. Meetings
------------------------------------
O:
- Any component
- Change log
7- Close Project or Phase
IN:
1. Project charter
- All components
- Assumption log
- Change log
- Issue log
- Milestone list
- Quality control measurements
- Quality reports
- Risk register
- Risk report
4. Accepted deliverables
- Business case
- Benefits management plan
6. Agreements
7. Procurement documentation
------------------------------------
TT:
1. Expert judgment
2. Data analysis
- Document analysis
- Regression analysis
- Trend analysis
- Variance analysis
3. Meetings
------------------------------------
O:
1. Project documents updates.
2. Final product, service, or result transition.
3. Final report.
4. Organizational process assets updates.
DIRECT AND MANAGE PROJECT WORK
Process of leading and performing the work defined
in the project management plan and implementing
approved changes to achieve the project’s
objectives.
The key benefit of this process is that it provides
overall management of the project work and
deliverables, thus improving the probability of project
success.
MANAGE PROJECT KNOWLEDGE
Process of using existing knowledge and creating
new knowledge to achieve the project’s objectives
and contribute to organizational learning.
The key benefits of this process are that prior
organizational knowledge is leveraged to produce
or improve the project outcomes, and knowledge
created by the project is available to support
organizational operations and future projects or phases.
MONITOR AND CONTROL PROJECT WORK
process of tracking, reviewing, and reporting the overall
progress to meet the performance objectives defined in
the project management plan.
The key benefits of this process are that it allows
stakeholders to understand the current state of the
project, to recognize the actions taken to address any
performance issues, and to have visibility into the future
project status with cost and schedule forecasts.
PERFORM INTEGRATED CHANGE CONTROL:
Perform Integrated Change Control is the
process of reviewing all change requests;
approving changes and managing changes to
deliverables, project documents, and the
project management plan; and
communicating the decisions.
This process reviews all requests for changes
to project documents, deliverables, or the
project management plan and determines the
resolution of the change requests.
The key benefit of this process is that it
allows for documented changes within the
project to be considered in an integrated
manner while addressing overall project risk,
which often
arises from changes made without
consideration of the overall project objectives
or plans.
https://www.linkedin.com/feed/hashtag/?keywords=pmp_in_a3PMPINA#3
Knowledge
Area (4)
CLOSE PROJECT OR PHASE
Close Project or Phase is the process of finalizing all
activities for the project, phase, or contract.
The key benefits of this process are the project or phase
information is archived, the planned work is completed,
and organizational team resources are released to pursue
new endeavors.
- Assumption log
- Cost forecasts
- Issue log
- Milestone list
- Quality reports
- Risk register
- Risk report
- Schedule forecasts
X Actions and activities necessary to satisfy completion or exit criteria
for the phase or project such as:
- Making certain that all documents and deliverables
are up-to-date and that all issues are resolved;
- Confirming the delivery and formal acceptance of
deliverables by the customer;
- Ensuring that all costs are charged to the project;
- Closing project accounts;
- Reassigning personnel;
- Dealing with excess project material;
- Reallocating project facilities, equipment, and other resources;
- Elaborating the final project reports as required by
organizational policies.
X Activities related to the completion of the contractual agreements
applicable to the project or project phase such as:
- Confirming the formal acceptance of the seller’s work,
- Finalizing open claims,
- Updating records to reflect final results,
- Archiving such information for future use.
X Activities needed to:
- Collect project or phase records,
- Audit project success or failure,
- Manage knowledge sharing and transfer,
- Identify lessons learned,
- Archive project information for future use by the organization.
X Actions and activities necessary to transfer the project’s products,
services, or results to the next phase or to production and/or operations.
X Collecting any suggestions for improving or updating the policies and procedures of
the organization, and sending them to the appropriate organizational unit.
X Measuring stakeholder satisfaction.
Risk & Cost of change VS project Time Process Group interaction with a project or Phase
Initiation
Planning
Executing
M&C
Closing
RISK
Probability
Highest
High
Medium
LOW
Lowest
Cost
LOW
LOW
Highest
Lower
Lowest
Stakeholder
influence
Highest
High
Medium
Lower
Lowest
Cost of
changes
Lowest
LOW
Medium
High
Highest
Initiation Planning Executing M&C Closing

SCOPE MANAGEMENT PLAN:
How the project and product scope will be defined,
validated, and controlled.
guidance and direction on how scope will be
managed throughout the project.
Requirement document :
Functional requirements : describe the
behaviors of the product examples actions
,processes data and interaction.
Non Functional requirements: describe the
environmental conditions example reliability
,security , performance
IN:
1. Project charter
- Scope management plan
- Requirement management plan
- Stakeholder engagement plan
3. Project document
- Assumption log
- Business case
5. Agreement (project and product requirement/ contract)
------------------------------------
TT:
1. Expert Judgement
2. Data gathering
- Brain storming (generate & collect Multiple Ideas)
- Interviews (confidential information)
- Focus group (prequalified stakeholders and SME)
- Questionnaire and surveys ( large # of respondents)
- Benchmarking (comparing , best practices, generate ideas
for improvement , provide basis of measuring performance
“could be internal or external”)
3. Data analysis
- Document analysis (agreement, Business plan…..etc.)
4. Decision making
- Voting (Unanimity ‫االجماع‬ - Majority – plurality ‫االكثرية‬)
- Autocratic decision making ‫االستبدادي‬ ‫القرار‬ ‫صنع‬
- Multi criteria decision analysis ) uses a decision matrix to provide
a systematic analytical approaches --- evaluate and rank many ideas)
5. Data representation
- Affinity diagrams ( large numbers of idea – classified into
groups)
- Mind mapping (generate new Idea )
- Nominal group technique ( vomiting to rank most useful
ideas for prioritization)
- Observation/ conversation ( Direct way of viewing
individuals -- how they perform their jobs --- uncover
hidden requirements )
- Facilitation ( bring Key stakeholder together to define
requirements --- cross functional requirements – build
trust , foster relationships and improve communication )
7. Context diagram ( visually depict the Product scope by
showing a business system --- Show inputs & actor –outputs
and the actor receive output )
8. Prototypes ( method of obtaining early feed back --- small
scale product , computer greeted 3D , Mock-ups)
------------------------------------
O:
1. Requirements traceability Matrix ” LINK requirement to
deliverables - -- ensure requirement adds business value -
document delivered at the end of the project – structure
managing changes to the product scope)
2. Requirement documentation “ business requirements ,
Stakeholder requirement ,solution requirement , Functional &
non functional requirements , Quality requirements ,project
requirements )
2-Collect requirement
IN:
1. Project charter
3. Project document
- Assumption log
- Requirement documents
- Risk register
------------------------------------
TT:
1. Expert Judgment
2. Data analysis
- Alternative analysis (used to evaluate ways
to meet the requirements and the objectives
identified in the charter.
3. Decision making
- Voting (Unanimity ‫االجماع‬ - Majority – plurality ‫)االكثرية‬
- Multi criteria decision analysis ) uses a
decision matrix to provide a systematic
analytical approaches --- evaluate and rank
many ideas)
- Nominal group technique ( vomiting to rank
most useful ideas for prioritization)
- Observation/ conversation ( Direct way of
viewing individuals -- how they perform their jobs ---
uncover hidden requirements )
- Facilitation ( bring Key stakeholder together to define
requirements --- cross functional requirements – build
trust , foster relationships and improve communication )
5. Product analysis
Product breakdown, Requirements
analysis, Systems analysis, Systems
engineering,, Value analysis, and Value
engineering.
------------------------------------
O:
1. Project scope statement
- Project scope description ,
- Acceptance criteria,
- Project deliverables ,
- Project exclusions ,
- Project constraints,
- Project assumptions
2. Documentation Update
- Assumption loge
- Requirements reachability matrix
3-Define scope
DEFINE SCOPE IS PROCESS :
Developing a detailed description of the project
and product, Describes the product, service, or
result boundaries and acceptance criteria.
The project scope is defined and described with
greater specificity as more information about the
project is known. Existing risks, assumptions, and
constraints are analyzed for completeness and
added or updated as necessary.
IN:
2. Project document
- Project scope statement
------------------------------------
TT:
1. Expert Judgement.
2. Decomposition.
- Identifying and analyzing the
deliverables and related work,
- Is a technique used for dividing and
subdividing the project scope and
project deliverables into smaller ,more
manageable parts.
- The work package level is the lowest
level in the WBS that the cost and the
durations can be estimated and
managed.
------------------------------------
O:
1. Scope base line
- Project scope statement.
- WBS. is a hierarchical decomposition of
the total scope of work
- WBS dictionary. is a document that provides
detailed deliverable, activity, and
scheduling Information
• Code of account identifier
• Description of work
• Assumptions and constraints,
Responsible organization
• Schedule milestones, Associated
schedule activities
• Resources required, Cost estimates,
Quality requirements
• Acceptance criteria
• Technical references
• Agreement information.
- Work package. lowest level of the WBS
- Planning package, work breakdown structure
component below the control account and
above the work package
2. Documentation Update
- Assumption loge
4-Creat WBS
CREATE WBS PROCESS : Subdividing project
deliverables and project work into smaller, more
manageable components.
The key benefit of this process is that it provides a
framework of what has to be delivered. This process is
performed once or at predefined points in the project
IN:
- Scope baseline
2. Project document
- Quality reports
3. Verified deliverables ( FROM Control Quality )
( FROM Direct and mange Project work)
------------------------------------
TT:
1. Inspection.
Inspections are sometimes called reviews,
product reviews and walkthroughs
2. Decision making
- Voting (Unanimity ‫االجماع‬ - Majority – plurality ‫)االكثرية‬
------------------------------------
O:
1. Accepted deliverables
(To close Phase or project )
(To monitor and control Project work)
information about progress such as which deliverables have
started their progress which deliverables have finished or
accepted
3. Change requests
(To Perform integrated change control )
4. Project document updates
5- Validate Scope
VALIDATE SCOPE PROCESS :
Formalizing acceptance of the completed project
deliverables.
The key benefit Increases the probability of final
product, service, or result acceptance by validating
each deliverable.
IN:
- Change management plan
- Configuration management plan
- Scope baseline
- Performance measurement baseline
2. Project document
( FROM Direct and mange Project work)
------------------------------------
TT:
1. Data Analysis
• Variance analysis
Used to compare the baseline to the actual
results and determine if the
variance is within the threshold amount or if
corrective or preventive action
is appropriate
• Trend analysis
Examines project performance over time to
determine if performance is improving or
deteriorating
“scope creep: The uncontrolled expansion to
product or project scope without
adjustments to time, cost, and resources.
------------------------------------
O:
2. Change requests
3. Project management plan Updates
- Scope baseline
- Schedule baseline
- Cost baseline
- Lessons learned register “The lessons
learned register can be updated with
techniques that are efficient and effective in
controlling scope, including causes of
variances and corrective actions chosen”
6- control Scope
CONTROL SCOPE PROCESS :
Monitoring the status of the project and product
scope and managing changes to
the scope baseline.
The scope baseline is maintained throughout the
project.
1- Plan Scope management “PL” 2- Collect requirement “PL” 3- Define scope “PL” 4- Create WBS “PL” 5- Validate scope “M&C” 6 – Control scope “M&C”
PROJECT SCOPE MANAGEMENT Knowledge
Area (5)
IN:
1. Project charter documents the project
purpose, high-level project description ,
assumptions, constraints, and high-level
requirements that the project is intended
to satisfy.
- Project life cycle description.
- Development Approach (Waterfall
,Iterative, adaptive, agile ,hybrid )
------------------------------------
TT:
1. Expert Judgment
2. DATA ANALYSIS “Alternative analysis
“Various ways of collecting requirements,
elaborating the project and product
scope, creating the product, validating the
scope, and controlling the scope are
evaluated”.
3. Meeting
------------------------------------
O:
1. Scope management Plan “ Include”
- Process for preparing a project scope
statement;
- Process that enables the creation of the
WBS from the detailed project scope
statement;
- Process that establishes how the scope
baseline will be approved and
maintained; and
- Process that specifies how formal
acceptance of the completed project
deliverables will be obtained.
2. Requirement management Plan
- How requirements activities will be
planned, tracked, and reported;
- Configuration management activities
such as: how changes will be initiated;
how impacts will be analyzed; how they
will be traced, tracked, and reported; as
well as the authorization levels required to
approve these changes;
- Requirements prioritization process;
- Metrics that will be used and the
rationale for using them; and
- Traceability structure that reflects the
requirement attributes captured on the
traceability matrix.
1-Scope management Plan
COLLECT REQUIREMENTS :
The key benefit of this process is that it provides the basis for
defining the product scope and project scope.

PLAN SCHEDULE MANAGEMENT PROCESS
Plan Schedule Management is the process of
establishing the policies, procedures, and
documentation for planning, developing, managing,
executing, and controlling the project schedule.
guidance and direction on how the project schedule
will be managed throughout the project
IN:
- Scope baseline “The project WBS,
deliverables, constraints, and
assumptions documented in the
scope baseline are considered
explicitly while defining activities.”
- Lessons learned repository
- Standardized processes,
- Templates that contain a standard
activity list or a portion of an activity
list from a previous project
- Existing formal and informal activity
planning-related policies,
procedures, and guidelines
------------------------------------
TT:
1. Expert Judgment
2. Decomposition
3. Rolling wave planning “is an
iterative planning technique in which the
work to be accomplished in the near term
is planned in detail, while work further
in the future is planned at a higher
level. It is a form of progressive
elaboration applicable to work packages,
planning packages, and release planning
when using an agile or waterfall approach.
Therefore, work can exist at various levels
of detail depending on where it is in the
project life cycle. During early trategic
planning when information is less defined,
work packages may be decomposed to the
known level of detail. As more is known
about the upcoming events in the near
term, work packages can be decomposed
into activities. PMBOK_Pag #185
4. Meetings
------------------------------------
O:
1. Activity list “includes the schedule
activities required on the project.”
2. Activity attributes ”identifying
multiple components associated with
each Activity”
3. Milestone list
4. Change requests
- Schedule baseline
- Cost baseline
2-Define Activities
IN:
- Scope baseline
- Activity attributes
- Activity list
- Assumption log
- Milestone list
------------------------------------
TT:
1. Precedence diagramming method “PDM” is a
technique used for constructing a schedule model in
which activities are represented by nodes and are
graphically linked by one or more logical relationships
to show the sequence in which the activities are to be
performed.
PDM includes four types of dependencies or logical
relationships
Finish-to-start (FS). A logical relationship in which a successor
activity cannot start until a predecessor activity has
finished. .
Finish-to-finish (FF). A logical relationship in which a successor
activity cannot finish until a predecessor activity has
finished.
Start-to-start (SS). A logical relationship in which a
successor activity cannot start until a predecessor
activity has started.
Start-to-finish (SF). A logical relationship in which a successor
activity cannot finish until a predecessor activity has
started.
2. Dependency determination and integration
- Mandatory dependencies. ”legally or
contractually required or inherent in the nature of
the work”
- Discretionary dependencies. “preferred logic,
preferential logic, or soft logic. Discretionary”
- External dependencies. “involve a relationship
between project activities and nonproject activities.
These dependencies are usually outside of the
project team’s control.”
- Internal dependencies. ” relationship between
project activities and are generally inside the project
team’s control”
3. Leads and lags
- A lead is the amount of time a successor activity can
be advanced with respect to a predecessor activity.
- A lag is the amount of time a successor activity will
be delayed with respect to a predecessor activity.
4. Project management information system ”PMIS”
------------------------------------
O:
1. Project schedule network diagrams
- Activity list
- Assumption log
- Milestone list
3-Sequence Activities
SEQUENCE ACTIVITIES PROCESS :
Sequence Activities is the process of identifying and
documenting relationships among the project
activities.
The key benefit of this process is that it defines the
logical sequence of work to obtain the greatest
efficiency given all project constraints.
IN:
1. Project charter
- Scope baseline
- Activity list
- Assumption log
- Milestone list
- Resource calendars
- Resource requirements
- Risk register
4. .3 Enterprise environmental factors
5. .4 Organizational process assets
------------------------------------
TT:
1. Expert Judgment
2. Analogous estimating “using historical
data from a similar activity or project.”
3. Parametric estimating “based on
historical data and project parameters.
Parametric’
4. Three-point estimating ‘Most likely
(tM)., Optimistic (tO)., Pessimistic (tP).
Equation tE = (tO + tM + tP) / 3.
5. Bottom-up estimating by aggregating the
estimates of the lower level components
of the WBS. When an activity’s duration
cannot be estimated with a reasonable
degree of confidence, the work within the
activity is decomposed into more detail.
The detail durations are estimated. These
estimates are then aggregated into a total
quantity for each of the activity’s
durations
6. Data analysis
- Reserve analysis
7. Decision making
8. Meetings
------------------------------------
O:
1. Duration estimates
2. Basis of estimates
- Assumption log
4- Estimate Activity Durations
ESTIMATE ACTIVITY DURATIONS IS PROCESS :
Estimate Activity Durations is the process of
estimating the number of work periods
needed to complete individual activities with
estimated resources.
the amount of time each activity will take to
complete.
IN:
- Scope baseline
3. Agreements
------------------------------------
TT:
1. Schedule network analysis
2. Critical path method “used to estimate the minimum project duration
and determine the amount of schedule flexibility on the logical network
paths within the schedule model”
3. Resource optimization
- Resource leveling “start and finish dates are adjusted based on
resource constraints with the goal of balancing the demand for
resources with the available supply”
- Resource smoothing. “adjusts the activities of a schedule model such
that the requirements for resources on the project do not exceed
certain predefined resource limits”
4. Data analysis
- What-if scenario analysis “evaluating scenarios in order to predict their
effect, positive or negative, on project objectives
- Simulation “combined effects of individual project risks and other sources
of uncertainty to evaluate their potential impact on achieving project
objectives” ex. Monte Carlo analysis
5. Leads and lags
6. Schedule compression
Crashing. A technique used to shorten the schedule duration for the least
incremental cost by adding resources. Examples of crashing include approving
overtime, bringing in additional resources, or paying to expedite delivery to
activities on the critical path. Crashing does not always produce a viable
alternative and may result in increased risk and/or cost
Fast tracking. A technique in which activities or phases normally done in
sequence are performed in parallel for at least a portion of their duration.. Fast
tracking may result in rework and increased risk. Fast tracking only works when
activities can be overlapped to shorten the project duration on the critical path. Using leads in
case of schedule acceleration usually increases coordination efforts between the activities
concerned and increases quality risk. Fast tracking may also increase project costs.
6. Agile release planning
------------------------------------
O:
1. Schedule baseline
2. Project schedule
3. Schedule data
4. Project calendars
5. Change requests
- Cost baseline
- Activity attributes - Assumption log
- Duration estimates - Lessons learned register
- Resource requirements - Risk register
5- Develop Schedule
DEVELOP SCHEDULE PROCESS :
Develop Schedule is the process of analyzing activity sequences, durations,
resource requirements, and schedule
constraints to create a schedule model for project execution and monitoring
and controlling.
The key benefit of this process is that it generates a schedule model with
planned dates for completing project activities
IN:
- Schedule baseline
- Scope baseline
2. .2 Project documents
- Project calendars
- Project schedule
- Schedule data
------------------------------------
TT:
1. Data analysis
- Earned value analysis
- Iteration burndown chart “tracks the work
that remains to be completed in the
iteration backlog”
- Performance reviews
- Trend analysis
- Variance analysis
- What-if scenario analysis
1. Critical path method
3. Resource optimization
4. Leads and lags
5. Schedule compression
------------------------------------
O:
2. Schedule forecasts
3. Change requests
- Schedule baseline
- Cost baseline
- Assumption log
- Project schedule
- Risk register
- Schedule data
6- Control Schedule
CONTROL SCHEDULE PROCESS :
Control Schedule is the process of monitoring the
status of the project to update the project
schedule and managing changes to the schedule
baseline.
The key benefit of this process is that the
schedule baseline is maintained throughout the project.
1- Plan Schedule management “PL” 2- Define Activities “PL” 3- Sequence Activities “PL” 4- Estimate Activity Durations “PL” 5- Develop Schedule “PL” 6 – Control Schedule “M&C”
PROJECT SCHEDULE MANAGEMENT Knowledge
Area (6)
IN:
1. Project charter
- Development approach
------------------------------------
TT:
1. Expert Judgment
2. DATA ANALYSIS “Alternative analysis
“Various ways of collecting requirements,
elaborating the project and product
scope, creating the product, validating the
scope, and controlling the scope are
evaluated”.
3. Meeting
Project teams may hold planning
meetings to develop the schedule
management plan. Participants at these
meetings may include the project
manager, the project sponsor, selected
project team members, selected
stakeholders, anyone with responsibility
for schedule planning or execution, and
others as needed.
------------------------------------
O:
1. Schedule management Plan “ Include”
- Project schedule model development.
“The scheduling methodology and the
scheduling tool to be used in the
development of the project schedule
model”
- Release and iteration length.
- Level of accuracy. “The level of accuracy
specifies the acceptable range used in
determining realistic activity duration
estimates and may include an amount for
contingencies.”
- Units of measure. “Each unit of
measurement (such as staff hours, staff
days, or weeks for time measures, or
meters, liters, tons, kilometers, or cubic
yards for quantity measures”
- Organizational procedures links.
- Project schedule model maintenance.
- Control thresholds. “Variance thresholds
for monitoring schedule performance may
be specified to indicate an agreed-upon
amount of variation to be allowed before
some action needs to be taken”
- Rules of performance measurement
- Reporting formats. “The formats and
frequency for the various schedule reports
are defined.”
1-Plan Schedule Management
DEFINE ACTIVITIES PROCESS
Define Activities is the process of identifying
and documenting the specific actions to be
performed to produce the project deliverables.
The key benefit of this process is that it decomposes
work packages into schedule activities that provide a
basis for estimating, scheduling, executing,
monitoring, and controlling the project work.
- Activity list
- Assumption log
- Duration estimates
- Project schedule network diagrams
- Risk register
- Milestone list
Control process, is concerned with:
- Determining the current status of the project schedule,
- Influencing the factors that create schedule changes,
- Reconsidering necessary schedule reserves,
- Determining if the project schedule has changed,
- Managing the actual changes as they occur.

https:///
1- Plan Schedule management “PL” 2- Define Activities “PL” 3- Sequence Activities “PL” 4- Estimate Activity Durations “PL” 5- Develop Schedule “PL” 6 – Control Schedule “M&C”
PROJECT SCHEDULE MANAGEMENT
3-Sequence Activities 5- Develop Schedule 6- Control Schedule
Knowledge
Area (6)
Precedence Diagramming Method
precedence diagramming method can be used for creating a project schedule
network diagram which is an output of this process that is used as an input
for the ‘develop schedule’ process.
Predecessor activity
successor activity
Finish
START
Finish-to-Start (FS) dependency,
The successor activity requires the predecessor activity to be finished
before it can be completed.
Start-to-Start (SS) dependency,
The predecessor activity must have started before the successor
activity can start.
successor activity
START
START
Finish-to-Finish (FF) dependency
The successor activity requires the predecessor activity to be finished
before it can be completed.
successor activity
Finish
Finish
Start-to-Finish (SF) dependency
The predecessor activity must have started before the successor
activity can start.
successor activity
START
Finish
rarely used
(4) types of logical relationships in the
precedence diagraming method are:
• Finish-to-Start (FS) dependency,
• Finish-to-Finish (FF) dependency,
• Start-to-Start (SS) dependency,
• Start-to-Finish (SF).
Project schedule net work diagram
project schedule network diagram is a graphical representation of the logical
relationships, also referred to as dependencies, among the project schedule activities
Crashing
is a schedule compression technique that involves determining an
approach that brings maximum reduction in project duration with least
incremental cost and risk, and without changing the scope.
In Crashing, project schedule is compressed by adding more resources to the
project, or working overtime to the critical path activities. The key here is
“critical path activities”. If you apply additional resources to non-critical path
activities, it would not result in a compressed schedule.
schedule compression comparison
Fast tracking
is a schedule compression technique that reduces the project duration
by performing critical path activities in parallel that were originally
planned to be performed in sequence.
in Fast Tracking, activities which are usually performed in sequence are
performed in parallel, to compress the schedule.
As with Crashing, the goal of Fast Tracking is to shorten the duration of the
critical path. Therefore, Fast Tracking only works when activities can be
overlapped to shorten the critical path duration.
Critical Path Method
- Used to estimate the minimum Project duration
- Calculates the early start , early finished , late start and late
finish dates of all activities without regard for any resources
limitations by preforming a forward and backwards pass analysis.
- The critical Path method sequence activities that represent the
longest path through the project
- A critical Path is normally catechized by Zero total float
- The Critical Path is determined when analyze a projects schedule
or network logic diagram and uses the Critical Path Method
(CPM). The CPM provides a graphical view of the project,
predicts the time required for the project, and shows which
activities are critical to maintain the schedule
Resource optimization
Resources smoothing
Resource smoothing when you have to optimize the
resources and you cannot extend the schedule.
Resources leveling
- Resource leveling when project have limited
resources and you may extend the schedule.
- A critical resource may not be available for a
certain duration; A critical resource may not be
available at a certain point of time;
- Sharing a resource with another project; The
demand for a resource exceeds the supply.
Simulation
40 Hours 40 Hours
35 Hours
40 Hours40 Hours
Simulation. Simulation models the
combined effects of individual project risks
and other sources of uncertainty to evaluate
their potential impact on achieving project
objectives. The most common simulation
technique is Monte Carlo analysis in
which risks and other sources of uncertainty
are used to calculate possible schedule
outcomes for the total project. Simulation
involves calculating multiple work package
durations with different sets of activity
assumptions, constraints, risks, issues, or
scenarios using probability distributions
and other representations of uncertainty
shows a probability
distribution for a project
with the probability of
achieving a certain target
date
(i.e., project finish date).
In this example, there is a
10% probability that the
project will finish on or
before the target date of
May 13,
while there is a
90% probability
of completing the project
by May 28
Iteration burndown chart.
This chart tracks the work that remains to be completed in the iteration backlog. It
is used to analyze the variance with respect to an ideal burndown based on the work
committed from iteration planning A forecast trend line can be used to predict the likely
variance at iteration completion and take appropriate actions during the course of the
iteration. A diagonal line representing the ideal burndown and daily actual remaining
work is then plotted. A trend line is then calculated to forecast completion
based on remaining work. PMBOK_Page_226
Today status
Remaining
When all
completed
Project Schedule example
Data entry date
Milestone
Activity
relation
(FS)
28 May13 May

IN:
1. Project charter
provides the preapproved financial resources from which the
detailed project costs are developed. The project charter also
defines the project approval requirements that will influence the
management of the project costs.
- Schedule management plan “establishes the criteria and the
activities for developing, monitoring, and controlling the
schedule. The schedule management plan provides processes and
controls that will impact cost estimation and management.
- Risk management plan ”provides the approach for identifying,
analyzing, and monitoring risks. The risk management plan
provides processes and controls that will impact cost estimation
and management.’
- Organizational culture and structure can influence cost management.
- Market conditions describe what products, services, and results are
available in the regional and global markets.
- Currency exchange rates for project costs are sourced from more than
one country.
- Published commercial information such as resource cost rate
information is often available from commercial
- databases that track skills and human resource costs, and provide
standard costs for material and equipment.
- Published seller price lists are another source of information.
- Project management information system provides alternative possibilities
for managing cost.
- Productivity differences in different parts of the world can have a large
influence on the cost of projects.
- Financial controls procedures (e.g., time reporting, required
expenditure and disbursement reviews, accounting
- codes, and standard contract provisions);
- Historical information and lessons learned repository;
- Financial databases; and
- Existing formal and informal cost estimating and budgeting-related
policies, procedures, and guidelines.
---------------------------------------------------
TT:
2. Data analysis.
- Alternatives analysis can include reviewing strategic funding
options such as: self-funding, funding with equity, or funding
with debt. It can also include consideration of ways to acquire
project resources such as making, purchasing, renting, or leasing.
3. Meetings “Project teams may hold planning meetings to develop the cost
management plan. Attendees may include the project manager, the project
sponsor, selected project team members, selected stakeholders, anyone with
responsibility for project costs, and others as needed”
---------------------------------------------------
O:
1. Cost management plan
The cost management plan is a component of the project management
plan and describes how the project costs will be planned, structured,
and controlled. The cost management processes and their associated
tools and techniques are documented in the cost management plan. For
example, the cost management plan can establish the following:
- Units of measure. Each unit used in measurements (such as staff
hours, staff days, or weeks for time measures; Meters, liters, tons,
kilometers, or cubic yards for quantity measures; or lump sum in
currency form) is defined for each of the resources.
- Level of precision. This is the degree to which cost estimates will be
rounded up or down (e.g., US$995.59 to US$1,000), based on the
scope of the activities and magnitude of the project.
- Level of accuracy. The acceptable range (e.g., ±10%) used in
determining realistic cost estimates is specified, and may include an
amount for contingencies.
1- Plan cost management
PLAN COST MANAGEMENT PROCESS:
Plan Cost Management is the process of defining how the project costs will be
estimated, budgeted, managed, monitored, and controlled.
The key benefit of this process is that it provides guidance and direction on how
the project costs will be managed throughout the project.
IN:
- Cost management plan
- Scope baseline “Project scope statement, Work breakdown structure and WBS dictionary”
- Lessons learned register - Project schedule
- Resources requirements - Risk register
- Market conditions. - Published commercial information.
- Exchange rates and inflation.
- Cost estimating policies, - Cost estimating templates,
- Historical information and lessons learned repository.
---------------------------------------------------
TT:
1. Expert judgment
2. Analogous estimating “uses values, or attributes, of a previous project that are similar to the
current project. Values and attributes of the projects may include but are not limited to:
scope, cost, budget, duration, and measures of scale (e.g., size, weight). Comparison of these
project values, or attributes, becomes the basis for estimating the same parameter or
measurement for the current project.
3. Parametric estimating “uses a statistical relationship between relevant historical data and
other variables (e.g., square footage in construction) to calculate a cost estimate for project
work. This technique can produce higher levels of accuracy depending on the sophistication
and underlying data built into the model. Parametric cost estimates can be applied to a total
project or to segments of a project, in conjunction with other estimating methods.”
4. Bottom-up estimating “The cost of individual work packages or activities is estimated to the
greatest level of specified detail. The detailed cost is then summarized or “rolled up” to
higher levels for subsequent reporting and tracking purposes. The cost and accuracy of
bottom-up cost estimating are typically influenced by the size or other attributes of the
individual activity or work package.”
5. Three-point estimating
- Most likely (cM). The cost of the activity, based on realistic effort assessment for the
required work and any predicted expenses.
- Optimistic (cO). The cost based on analysis of the best-case scenario for the activity.
- Pessimistic (cP). The cost based on analysis of the worst-case scenario for the activity.
Triangular distribution. cE = (cO + cM + cP) / 3
Beta distribution. cE = (cO + 4cM + cP) / 6
1. Data analysis
- Alternatives analysis “used to evaluate identified options in order to select which options
or approaches to use to execute and perform the work of the project.”
- Reserve analysis “Cost estimates may include contingency reserves (sometimes called
contingency allowances) to account for cost uncertainty.”
- Cost of quality “includes evaluating the cost impact of additional investment in
conformance versus the cost of nonconformance.”
2. Decision making “Voting”
---------------------------------------------------
O:
1. Cost estimates ” include quantitative assessments of the probable costs required to complete
project work, as well as contingency amounts to account for identified risks, and
management reserve to cover unplanned work. Cost estimates can be presented in summary
form or in detail. Costs are estimated for all resources that are applied to the cost estimate.
This includes but is not limited to direct labor, materials, equipment, services, facilities,
information technology, and special categories such as cost of financing (including interest
charges), an inflation allowance, exchange rates, or a cost contingency reserve. Indirect costs,
if they are included in the project estimate, can be included at the activity level or at higher
levels.
2. Basis of estimates “Supporting detail for cost estimates may include:
- Documentation of the basis of the estimate (i.e., how it was developed),
- Documentation of all assumptions made,
- Documentation of any known constraints,
- Documentation of identified risks included when estimating costs,
- Indication of the range of possible estimates (e.g., US$10,000 (±10%) to indicate that the
item is expected to cost between a range of values), and
- Indication of the confidence level of the final estimate.
- Assumption log - Lessons learned register - Risk register
2- Estimate Costs
PMBOK Page 240 PDF/ 279
ESTIMATE COSTS PROCESS : Estimate Costs is the process of developing an approximation of the
cost of resources needed to complete project work.
The key benefit of this process is that it determines the monetary resources required for the project. This
process is performed periodically throughout the project as needed.
1- Plan Cost management “PL” 2- Estimate Costs “PL” 3- Determine Budget ” PL” 4- Control costs “M&C”
PROJECT COST MANAGEMENT
IN:
- Scope baseline
- Cost estimates
- Project schedule
- Risk register
- Business case
- Benefits management plan
4. Agreements
---------------------------------------------------
TT:
1. Expert judgment
2. Cost aggregation “Cost estimates are
aggregated by work packages in accordance
with the WBS. The work package cost
estimates are then aggregated for the
higher component levels of the WBS (such
as control accounts) and, ultimately, for the
entire project.”
3. Data analysis
- Reserve analysis
4. Historical information review
5. Funding limit reconciliation “The expenditure
of funds should be reconciled with any funding
limits on the commitment of funds for the project.
A variance between the funding limits and the
planned expenditures will sometimes necessitate
the rescheduling of work to level out the rate of
expenditures. This is accomplished by placing
imposed date constraints for work into the project
schedule.
6. Financing ” If a project is funded externally, the
funding entity may have certain requirements that
are required to be met.”
---------------------------------------------------
O:
1. Change requests
2. Cost baseline
”The cost baseline is the approved version of the
time-phased project budget, excluding any
management reserves, which can only be changed
through formal change control procedures. It is
used as a basis for comparison to actual results”
1. Project funding requirements
- Cost estimates
- Project schedule
- Risk register
3- Determine Budget
DETERMINE BUDGET PROCESS :
Determine Budget is the process of aggregating the
estimated costs of individual activities or work packages
to establish an authorized cost baseline.
The key benefit of this process is that it determines the
cost baseline against which project performance can be
monitored and controlled. This process is performed
once or at predefined points in the project.
IN:
- Cost baseline
3. Project funding requirements
---------------------------------------------------
TT:
1. Expert judgment
2. Data analysis
- Earned value analysis “Planned value.
Planned value (PV), Earned value. Earned
value (EV), Actual cost. Actual cost (AC) “
- Variance analysis “Cost variance (CV) ,
schedule variance (SV) , Schedule
performance Index (SPI) , cost performance
index (CPI)”
- Trend analysis
- Estimation at completion (EAC) , Estimation
to completion (ETC)
- Reserve analysis
1. To-complete performance index (TCPI)
---------------------------------------------------
O:
2. Cost forecasts
3. Change requests
- Cost baseline
- Assumption log
- Cost estimates
- Risk register
4- Control Costs
CONTROL COSTS:
is the process of monitoring the status of the project to
update the project costs and managing changes to the
cost baseline.
The key benefit of this process is that the cost baseline is
maintained throughout the project. This
process is performed throughout the project.
Knowledge
Area (7)
Cost Baseline, Expenditures, and Funding Requirements
cost control includes:
- Influencing the factors that create changes to the
authorized cost baseline;
- Ensuring that all change requests are acted on in a
timely manner;
- Managing the actual changes when and as they occur;
- Ensuring that cost expenditures do not exceed the
authorized funding by period, by WBS component, by
activity, and in total for the project;
- Monitoring cost performance to isolate and
understand variances from the approved cost baseline;
- Monitoring work performance against funds expended;
- Preventing unapproved changes from being included
in the reported cost or resource usage;
- Informing appropriate stakeholders of all approved
changes and associated cost; and
- Bringing expected cost overruns within acceptable limits.
PV: Planed Value
AC: Actual Cost
EV: Earned Value
TCPI: To completion
performance index
BAC: Budget at completion
EAC: Estimate at completion
VAC: Variance at completion
ETC: Estimate to completion
Schedule performance
Index (SPI )
SPI = EV/PV
SPI> 1 Ahead of schedule
SPI< 1 behind schedule
Cost performance Index
(CPI )
CPI = EV/AC
CPI> 1 behind budget
CPI< 1 over budget
Schedule Variance (SV)
SV= EV-PV
+Ve Ahead of schedule
-Ve Behind schedule
Cost Variance (CV)
CV= EV-AC
+Ve behind budget
-Ve Over budget
Estimate at complexion (EAC)
(1) If BAC remain the same
EAC =AC + BAC-EV
(2) If CPI remain the same
EAC= BAC/CPI
(3) If substandard
performance continues
EAC= AC+
(BAC-EV)/(CPI x SPI)
To completion
performance index
TCPI =Remaining work
/ Remaining Fund
TCPI=(BAC-EV)
/(BAC-AC)
Estimate to completion
ETC = EAC-AC
Variance at completion
VAC=BAC-EAC
Project Budget Component
Earned Value, Planned Value, and Actual Costs
To-Complete Performance Index (TCPI)
Activity already
executed
Activity Not yet
executed
Activity already
executed
Activity Not yet
executed
Project Budget = Cost Base line + Management reserve
Chas Out
Cash In
EV
PV
AC

IN:
1. Project charter
- Project management plan
- Requirements management plan
- Risk management plan
- Stakeholder management plan
2. Scope baseline
- Assumption log
- Risk register
----------------------------------------------------
TT:
2. Data gathering.
- Benchmarking
- Brainstorming “To gather data creatively from a group of team members or subject matter experts”
- Interviews
3. Data analysis.
- Cost-benefit analysis “Financial analysis tool used to estimate the strengths and weaknesses of alternatives in
order to determine the best alternative”--- Compares the cost of the quality step to the expected benefit.
- Cost of quality
i. Prevention costs. “Prevention of poor quality in the products, deliverables, or services”
ii. Appraisal cost “Related to evaluating, measuring, auditing, and testing the products”
iii. Failure costs ”Costs related to nonconformance of the products, deliverables, or services “
4. Decision making
- Multicriteria decision analysis
- Flowcharts / process maps “Display the sequence of steps and the branching possibilities that exist for a
process that transforms one or more inputs into one or more outputs. ---- Useful in understanding and estimating
the cost of quality for a process.
- Logical data model “Logical data models are a visual representation of an organization’s data, described in
business language and independent of any specific technology”
- Matrix diagrams
- Mind mapping
6. Test and inspection planning “based on the industrial could be Alpha , Beta , Strength tests..etc.”
7. Meetings
----------------------------------------------------
O:
1. Quality management plan
2. Quality metrics “Describes a project or product attribute and how the Control Quality process will verify
compliance to it.”
- Risk management plan
- Scope baseline
5. Risk register
6. Stakeholder register
Plan Quality management Objective :
Identifying quality requirements and/or standards for the project and its deliverables, and documenting how the project
will demonstrate compliance with quality requirements and/or standards.
Meeting customer requirements by overworking the project team may result in decreased profits and increased levels of
overall project risks, employee attrition, errors, or rework.
Meeting project schedule objectives by rushing planned quality inspections may result in undetected errors, decreased
profits, and increased post-implementation risk.
1- Plan Quality management
IN:
1. Project management plan.
2. Project documents.
- Quality control measurements
- Quality Metrics
- Risk register
3. Organization Process assets.
----------------------------------------------------
TT:
1. Data Gathering .
- Checklist “used to verify that a set of required steps has been performed”
2. Data analysis.
- Alternatives analysis “This technique is used to evaluate identified options in order to
select which different quality options or approaches are most appropriate to use”
- Document analysis
- Process analysis “Examines problems, constraints, and non value added
activities that occur during a process”
- Root cause analysis “Used to determine the basic underlying reason that causes
a variance, defect, or risk risk”
3. Decision making.
4. Data representation.
- Affinity diagrams “organize potential causes of defects into groups”
- Cause-and-effect /fishbone /Ishikawa diagrams Helping to identify the main or root
cause of the problem.
- Flowcharts
- Histograms Show a graphical representation of numerical data.
- Matrix diagrams Shows the relationship between two variables
- Scatter diagrams
5. Audits. “A structured, independent process used to determine if project activities
comply with organizational and project policies , processes , and procedures
6. Design for X. “a set of technical guidelines that may be applied during the design
of a product for the optimization of a specific aspect of the design” ; DfX can
control or even improve the product s final characteristics ‘; DfX may result in cost
reduction , quality improvement , better performance , and customer satisfaction
7. Problem solving.
8. Quality improvement methods. “Quality improvements can occur based on findings and
recommendations from QC processes, the findings of the quality audits, or problem solving in
the Manage Quality process. Plan-do-check-act and Six Sigma are two of the most common
quality improvement tools used to analyze and evaluate opportunities for improvement.”
----------------------------------------------------
O:
1. Quality reports
2. Test and evaluation Documents
3. Change requests
- Scope baseline
- Schedule baseline
- Cost baseline
- Issue Log.
- Lessons learned register.
- Risk register.
2- Manage Quality
Key benefit of this process : Translating the quality management plan into executable quality
activities that incorporate the organizations quality policies into the project. PMBOK_PAGE_288
Manage Quality is sometimes called quality assurance, although Manage Quality has a broader
definition than quality assurance as it is used in no project work. In project management, the focus of
quality assurance is on the processes used in the project. Quality assurance is about using project
processes effectively. It involves following and meeting standards to assure stakeholders that the final
product will meet their needs, expectations, and requirements.. PMBOK_PAGE_289
1- Plan Quality management “PL” 2- Manage Quality “EX” 3- Control Quality “M&C”
PROJECT QUALITY MANAGEMENT
IN:
- Quality metrics
- Test and evaluation documents
4. Deliverables
----------------------------------------------------
TT:
1. Data gathering
- Checklists
- Check sheets /tally sheets “Useful for gathering attributes data
while performing inspections to identify defects.”
- Statistical sampling
- Questionnaires and surveys
2. Data analysis
- Root cause analysis
3. Inspection “Examination to the product to determine if it
conforms to documented standards or to validate defect” repairs.
Also called reviews, audits, or walkthroughs.
4. Testing/product evaluations “intent of testing is to find errors,
defects, bugs, or other nonconformance problems in the product or service.”
- Cause-and-effect diagrams
- Control charts “Used to determine whether or not a process is stable “ ,
Upper and lower specification limits are based on the requirements and
reflect the maximum and minimum values allowed”
- Histogram
- Scatter diagrams
6. Meetings
- Approved change requests review.
- Retrospectives/lesson learned. To discuses (Successful elements in
the project/phase ,What could be improved, What to incorporate in the
ongoing project and what in future projects, and What to add to the
organization process assets.
----------------------------------------------------
O:
1. Quality control measurements “Quality control measurements are
the documented results of Control Quality activities.”
2. Verified deliverables
4. Change requests
- Issue log
- Risk register
- Test and evaluation documents
3- Control Quality
Key benefit of this process :
Monitoring and recording results of executing the quality management activities
in order to assess.
performance and ensure the project outputs are complete, correct, and meet
customer expectations.
verifying that project deliverables and work meet the requirements specified by
key stakeholders for final acceptance.
Knowledge
Area (8)
Control Quality = focus on Product
Manage Quality = focus on process
Scatter diagrams
Relationship between two
variables
Affinity diagrams
Organize potential causes
of defects into groups
Histograms
Number of defects
ranking of the cause of
defects
Control chart
Determine whether or not
a process is stable Limit
Process analysis “non value added activities occur during a process.
Checklists verify that a set of required steps has been performed
Check sheets Collection of useful data about a potential quality problem
Statistical Sampling Choosing a sample from population
Inspection Examination to the product to determine if it conforms to standards
PROBLEM SOLVING
Problem solving entails finding solutions for issues or challenges. It can
include gathering additional information, critical thinking, creative,
quantitative and/or logical approaches. Effective and systematic
problem solving is a fundamental element in quality assurance and
quality improvement. Problems can arise as a result of the Control
Quality process or from quality audits and can be associated with a
process or deliverable. Using a structured problem-solving method will
help eliminate the problem and develop a long-lasting solution.
Problem-solving methods generally include the following elements:
- Defining the problem, Identifying the root-cause,
- Generating possible solutions,
- Choosing the best solution,
- Implementing the solution, and
- Verifying solution effectiveness.
Cause and effect diagrams
Identify the main or root
cause of the problem
PMBOK _ Page _295

IN:
1. Project charter
- Project Quality plan
- Scope base line
- Project schedule
- Risk register
------------------------------------
TT:
2. Data representation.
- Hierarchical charts “ OBS ,RBS”
- Responsibility assignment matrix
”This type illustrates connection between work
packages , or activities and team members Ex: RACI
(R=Responsible, A= Accountable, C=Consult, I= Inform)
- Text-oriented formats
Team member responsibilities that require detailed
descriptions can be specified in text oriented formats. EX
responsibilities , authority , competencies , and
qualifications
1. Organization theory.
Provides information regarding the way in which people,
teams, and organizational units behave
1. Meeting.
------------------------------------
O:
1. Resource management plan ” Training , development
recognition plan ,resource control
2. Team charter Team values and principles . Meeting
guidelines, Communication guidelines, Decision
making process ,Conflict resolution process:
- Assumption log
- Risk register
1- Plan Resources management
Hierarchical charts.
- Work breakdown structures (WBS).
designed to show how project deliverables are broken
down into work packages and provide a way of showing
high-level areas of responsibility
- Organizational breakdown structure (OBS).
Arranged according to an organization’s existing
departments, units, or teams, with the project activities
or work packages listed under each department
- Resource breakdown structure.
Hierarchical structure of identified resources ,Can be
classified by category ( Labor, material, equipment, supplier)
Plan Resources management:
Guidance how project team resources should be estimate, acquire
,defined, staffed , managed, and eventually released . Page312
IN:
- Scope baseline
- Activity list
- Assumption log
- Cost estimates
- Risk register
------------------------------------
TT:
1. Expert Judgement
2. Bottom-up estimating
3. Analogous estimating
4. Parametric estimating
5. Data analysis
6. Project management information system “ PMIS”
7. Meetings
------------------------------------
O:
1. Resource requirements
Identify the types and quantities of resources
required for each work package or activity.
2. Basis of estimates
- Method used to develop the estimate,
- Resources used to develop the estimate (such
as information from previous similar projects),
- Assumptions associated with the estimate,
- Known constraints,
- Range of estimates,
- Confidence level of the estimate, and
- Documentation of identified risks influencing the
estimate.
2. Resource breakdown structure
2- Estimate activity Resources
3- Acquire Resources
Estimate activity Resources is the process :
Estimating team resources and the type , quantities
of materials, equipment, and supplies necessary to
perform project work.
it identifies the type, quantity, and characteristics of
resources required to complete the project.
4- Develop Team
Acquire resource is the process :
Obtaining team members, facilities, equipment,
materials, supplies, and other resources necessary
to complete project work.
Outlines and guides the selection of resources
and assigns them to their respective activities.
5- Manage Team
6- Control Resources
1- Plan Resources management “PL” 2- Estimate activity resources “PL” 3- Acquire resources “EX” 4- Develop Team “EX” 5- Mange Team “EX” 6 – Control resources “M&C”
PROJECT RESOURCES MANAGEMENT
IN:
- Procurement management plan
- Project schedule
------------------------------------
TT:
1. Decision making
“Availability, cost , Ability , experience
Knowledge, International factors , skills
,attitude” ----- “point weight selection”
- Negotiation “ used with Functional manager
& with external ORG & suppliers “
3. Pre-assignment “Sometimes resources are
assigned in advance (defined within charter)
because of their experience “
4. Virtual teams “Team members with little or no
time spent meeting face to face”.
The use of virtual teams creates new possibilities when
acquiring project team members. Virtual teams can be
defined as groups of people with a shared goal who fulfill
their roles with little or no time spent meeting face to face.
The availability of communication technology such as email,
audio conferencing, social media, web-based meetings,
and video conferencing has made virtual teams feasible
------------------------------------
O:
1. Physical resource assignments
2. Project team assignments
3. Resource calendars
Identifies the working days , shifts , start and
end of normal business hours , weekends ,
and public holidays when each specific
resource is available.
4. Change requests
- Cost baseline
- Project schedule
- Risk register
7. Enterprise environmental factors updates
IN:
------------------------------------
TT:
1. Colocation “Placing the active team members
in the same location to enhance their ability
to perform as a team”
2. Virtual teams
3. Communication technology
- Influencing
- Motivation
- Negotiation
- Team building
5. Recognition and rewards
6. Training
7. Individual and team assessments
8. Meetings
------------------------------------
O:
1. Team performance assessments ” TO
Manage team”
2. Change requests ” TO Integ. Change.Cont”.
- Project schedule
- Team charter.
IN:
- Issue log
- Team charter
4. Team performance assessments
------------------------------------
TT:
- Decision making
- Emotional intelligence” reduce tension and
increase cooperation”
- Influencing” little or no direct authority”
- Leadership
------------------------------------
O:
1. Change requests
- Schedule baseline
- Cost baseline
- Issue log
IN:
- Issue log
- Physical resource assignments
- Project schedule
- Risk register
4. Agreements
------------------------------------
TT:
1. Data analysis
- Trend analysis
2. Problem solving
- Negotiation
- Influencing
------------------------------------
O:
2. Change requests
- Schedule baseline
- Cost baseline
- Assumption log
- Issue log
- Physical resource assignments
- Risk register
Roles and responsibilities:
Role: Mech. engineer, business analyst, and inspector .
Authority: The rights to apply project resources, make
decisions, sign approvals, accept deliverables
Develop team is the process :
Improving competencies, team member
interaction, and the overall team environment to
enhance project performance.
improved teamwork, enhanced interpersonal
skills and competencies, motivated employees,
reduced attrition, and improved overall project
performance.
Team Development Stages:
Forming The team members meet and learn
about the project and their formal roles and
responsibilities
Storming There are disagreements as people
learn to work together
Norming begin to work together The team
members learn to trust each other
Performing Team members work effectively
together as well organized unit
Adjourning Team members complete the
work and moves on from the project
Manage team is the process :
Tracking team member performance, providing
feedback, resolving issues, and managing team
changes to optimize project performance.
influences team behavior, manages conflict, and
resolves issues.
Conflict Management:
Collaborate /Problem Solve – WIN-WIN
Incorporating multiple viewpoints and insights
from differing perspectives; requires a cooperative
attitude and open dialogue that typically leads to
consensus. result in a win-win situation.
Force /direct WIN- LOSE Pushing one’s viewpoint at
the expense of others; usually enforced through
a power position to resolve an emergency. often
results to a win-lose situation.
Compromise /reconcile “ LOSE –LOSE” Searching
for solutions that bring some degree of
satisfaction to all parties in order to temporarily
or partially resolve the
Smooth/accommodate Emphasizing areas of
agreement rather than areas of difference. conflict
Withdraw/Avoid Retreating from an actual or
potential conflict situation; postponing the issue
to be better prepared or to be resolved by others.
Control resources is the process :
Ensuring that the physical resources assigned and
allocated to the project are available as planned.
Monitoring the planned versus actual utilization of
resources and taking corrective action as necessary.
Ensuring that the assigned resources are available
to the project at the right time and in the right
place and are released when no longer needed.
Problem solving :
Identify: Specify the problem.
Define: Break it into smaller, manageable problems.
Investigate: Collect data.
Analyze: Find the root cause of the problem.
Solve :Choose the suitable solution from a
variety of available ones.
Check the solution: Determine if the problem
has been fixed
Knowledge
Area (9)
Sample Resource Breakdown Structure

IN:
1. Project charter
--------------------------------------------------------
TT:
2. Communication requirements analysis
3. Communication technology “PMBOK_Page_370”
- Urgency of the need for information.
- Availability and reliability of technology.
- Ease of use.
- Project environment.
- Sensitivity and confidentiality of the information.
4. Communication Models
- Sample basic sender/receiver communication model(Encode –
Transmittal -Decode)
- Sample interactive communication model.
5. Communication Methods
- Interactive communication: “FTF, Meetings, phone calls, instant messaging, some
forms of social media, and videoconferencing.”
- Push communication: “Letters, memos, reports, emails, faxes, voice mails, blogs,
and press releases”.
- Pull communication: Used for large complex information sets ,“ Web portals,
intranet sites, e-learning, lessons learned databases, or knowledge repositories”.
- Communication styles assessment ” A technique used to assess communication
styles and identify the preferred communication method, format, and content for
planned communication activities”
- Political awareness “Political awareness helps the project manager to plan
communications based on the project environment as well as the organization’s
political environment”
- Cultural awareness “is an understanding of the differences between individuals,
groups, and organizations and adapting the project’s communication strategy in the
context of these differences.”
- Stakeholder engagement assessment matrix
9. Meetings
--------------------------------------------------------
O:
1. Communications management plan “PMBOK_Page_377”
- Escalation processes;
- Stakeholder communication requirements;
- Person responsible for authorizing release of confidential information;
- Project Schedule
1- Plan Communication Management
Plan communication management process:
Developing an appropriate approach and plan for project communications activities based
on the information needs of each stakeholder or group, available organizational assets,
and the needs of the project PMBOK_PAGE_366
Documented approach to effectively and efficiently engage stakeholders by presenting
relevant information in a timely manner
On most projects, communications planning is performed very early, during stakeholder
identification and project management plan development.
IN:
- Change log
- Issue log
- Quality report
- Risk report
3. Work performance reports “are circulated to the project stakeholders through this process
as defined in the communications management plan . Example Status reports , progress
report s and work performance reports .”
--------------------------------------------------------
TT:
1. Communication technology
2. Communication methods
3. Communication skills “PMBOK_Page_384”
- Communication competence
- Feedback
- Nonverbal
- Presentations
5. Project reporting
- Active listening “removing barriers that adversely affect comprehension”
- Cultural awareness
• Prepare and distribute the agenda stating the objectives of the meeting.
• Ensure that the meetings start and finish at the published time.
• Ensure the appropriate participants are invited and attend.
• Stay on topic.
• Manage expectations, issues, and conflicts during the meeting.
• Record all actions and those who have been allocated the responsibility for
completing the action.
- Networking
- Political awareness
7. Meetings “support the actions defined in the communication strategy and communications plan”
8. --------------------------------------------------------
O:
1. Project communications “Project communications artifacts may include but are not limited to: performance
reports, deliverable status, schedule progress, cost incurred, presentations, and other information required
by stakeholders.”
- Issue log
- Project schedule
- Risk register
4. Organizational process assets update “PMBOK_Page_388”
- Project records such as correspondence, memos, meeting minutes and other documents used on the project; and
- Planned and ad hoc project reports and presentations.
2- Manage Communication
Manage Communication Process :
Ensuring timely and appropriate collection, creation, distribution, storage, retrieval, management,
monitoring, and the ultimate disposition of project information. “PMBOK_PAGE_379”
The key benefit of this process is that it enables an efficient and effective information flow between the
project team and the stakeholders. This process is performed throughout the project.
The Manage Communications process identifies all aspects of effective communication, including choice of appropriate
technologies, methods, and techniques. In addition, it should allow for flexibility in the communications activities, allowing
adjustments in the methods and techniques to accommodate the changing needs of stakeholders and the project.
1- Identify Stakeholder “IN” 2- Plan Stakeholder Engagement “PL” 3- MANAGE STAKEHOLDER ENGAGEMENT“EX” 4- Monitor STAKEHOLDER ENGAGEMENT“M&C”
PROJECT COMMUNICATION MANAGEMENT
IN:
- Issue log
3. Work performance “data contains data on the types and quantities of
communications that have actually been distributed.”
--------------------------------------------------------
TT:
1. Expert judgment
3. Data analysis
- Stakeholder engagement assessment matrix
- Observation/conversation
5. Meetings Face-to-face or virtual meetings are used for decision
making; responding to stakeholder requests; and having
discussions with suppliers, vendors, and other project
stakeholders.
--------------------------------------------------------
O:
2. Change requests These change requests may result in:
- Revision of stakeholder communication requirements, including
stakeholders’ information distribution, content or format, and
distribution method; and
- New procedures to eliminate bottlenecks.
- Issue log
The impact and consequences of project communications should be
carefully evaluated and monitored to ensure that the right message
with the right content (the same meaning for sender and receiver) is
delivered to the right audience, through the right channel, and at the
right time. Monitor Communications may require a variety of methods,
such as customer satisfaction surveys, collecting lessons learned,
observations of the team, reviewing data from the issue log,
or evaluating changes in the stakeholder engagement assessment
matrix.
The Monitor Communications process can trigger an iteration of the
Plan Communications Management and/or Manage Communications
processes to improve effectiveness of communication through
additional and possibly amended communications plans and activities
2- Monitor Communication
Monitor Communication Process :
is the process of ensuring the information needs of the project and its
stakeholders are met.
The key benefit of this process is the optimal information flow as defined in the
communications management plan and the stakeholder engagement plan.
“PMBOK_PAGE_388”
Knowledge
Area (10)
Communication Model for Cross-Cultural Communication
Communication channel
Equation As per PMBOK-5th edition
n X (n-1)/2
n= number of people “stakeholder”
For this example
n= 6 people
6 X (6-1)/2 = 6*2.5 =
15 Channels .
PMBOK 5th edition
Executing
Process
Controlling
Process
Overall project
control
Various project
process
Project
communications
Project change
control
Projectmanagementplan
andprojectdocuments
update
Approved change
request
Project team Members
Project Stakeholder
T.T Project reporting
Manage communication
process
Output
Input
Work performance data
Work performance information
Work performance reports
Project Data, Information and Report Flow
PMBOK 5th edition
For this example
(5 people)
How many consummation
channel ??
stakeholder

#Pmp in a3 edition_1

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Was ist angesagt?

Was ist angesagt? (20)

Ähnlich wie #Pmp in a3 edition_1

Ähnlich wie #Pmp in a3 edition_1 (20)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

#Pmp in a3 edition_1