Académique Documents
Professionnel Documents
Culture Documents
projacstraining.com
Course Instructor
Bassam Samman, PMP, PSP, EVP, CRA
■ Mr. Bassam Samman, PMP, PSP, EVP, CRA is a Project Management
Consultant with a 26-year service record, who has provided project
management consulting services for more than 40 organizations in different
sectors including Government, Construction, Engineering, Oil and Gas,
Petrochemical, Shipbuilding, Information Technology and New Product
Development.
■ Mr. Samman is thoroughly experienced in complete project management
including project management control systems, computerized PCS
software, risk analysis, site management, claims analysis and prevention
and alternative dispute resolution.
■ Mr. Samman is a Civil Engineer, Kuwait University with a Masters Degree in
Engineering Administration from the George Washington University. He is a
certified Project Management Professional (PMP) and a certified Planning
and Scheduling Professional (PSP) and a Certified Earned Value
Professional (EVP). He is a founding member of the Project Management
Institute (PMI) Arabian Gulf Chapter and served on their board of directors
for more than 6 years. Mr. Samman is the CEO/Founder of CMCS.
Course Agenda
DAY ONE
What Is PSP?
PSP Exam
■ Part I is Basic Knowledge. It consists of multiple-choice questions
concerning the basics of planning and scheduling.
■ Part II is Planning and Scheduling Applications. It consists of
multiple-choice questions involving planning and scheduling
scenarios.
■ Part III is a Practical Exercise. This part entails answering a series
of multiple-choice questions concerning various aspects of a single
problem.
■ Part IV is a real-time Communications Exercise. It requires the
candidate to draft the equivalent of a one-page typewritten
(maximum) memorandum to simulate reporting on planning and
scheduling analysis to the project manager, explaining the issues
and proposing a solution regarding a given problem.
Project Related
Definitions
■ What is a Subproject?
■ What is a Program?
■ What is a Projects Portfolio?
■ Project Life Cycle
■ Relation Between Product and Project Life Cycle
What Is A
Project?
■ An organization of people as well as other resources, brought
together to meet specific objectives within a finite period of time by
carrying out a set of planned activities.
Project
Categories
1. Aerospace/Defense Projects
2. Business & Organization Change Projects
3. Communication Systems Projects
4. Event Projects
5. Facilities Projects
6. Information Systems (Software) Projects
7. International Development Projects
8. Media & Entertainment Projects
9. Product and Service Development Projects
10. Research and Development Projects
What Is A
Subproject?
■ Projects are frequently divided into more manageable components
or subprojects.
■ Subprojects are often contracted to an external enterprise or to
another functional unit in the performing organization.
What Is A
Program?
■ A program is a group of projects managed in a coordinated way to
obtain benefits from the projects. It also provides the control not
available from managing projects individually.
What Is A
Portfolio?
■ It is a collection of projects and/or programs and other work that are
grouped together to facilitate the effectiveness of that work to meet
strategic objectives.
Organization
Project 100 Project 200 Project 300 Program 400 Project 500
Portfolio
Subproject
Subproject
Subproject
Subproject
102
103
104
■ The project life cycle defines the phases that connect the beginning of a
project to its end.
■ The transition from one phase to another within a project’s life cycle
generally involves, and is usually defined by, some technical transfer or
handoff.
■ Deliverables from one phase are usually reviewed for completeness and
accuracy and approved before work starts on the next phase.
Project
Life Cycle
Importance of
Phase Reviews
Interim
Evaluations
■ The main questions that are raised and need to be answered:
Are we meeting our basic objectives?
Are our basic objectives still worthwhile?
Do we want to change our basic objectives?
Do we want to terminate the project?
Are we ready for the next phase?
Have we secured all stakeholders approvals?
Interim
Evaluations
Characteristic Of
Project Phases
■ The completion and approval of one or more deliverables
characterizes a project phase.
■ A deliverable is a measurable, verifiable work product such as
specifications, drawings, model, etc.
Project
Stakeholders
Project Stakeholders
Stakeholders In
Construction Project
Project Stakeholders
1/3
■ Steering committee: A group of high-level executives from functional company
areas (and customer representatives) who provide guidance and overall strategic
direction. By contributing their functional expertise, they add strategic input to the
project.
■ Project champion: A senior executive who promotes and defends your project within
the larger parent organization.
■ Performing organization: The company or group doing the work.
■ Project organization: A group that serves the project and participants.
Project Stakeholders
2/3
■ Project manager: The person who manages the project daily.
■ Customer: The buyer expected to use the product or service that the project creates.
■ Project Team member: Anyone performing work on the project. In addition to people
loaned from other departments or from resource pools, the team also includes all
contractors and consultants.
■ Individual contributor: Anyone working on the project without a management role
but sharing accountability for achieving results.
Project Stakeholders
3/3
■ Functional manager: Handles the business and technical management of a
functional group – in particular their performance review.
■ Project accountant: Provides cost and budget information for the project. This
member of the accounting department ensure that invoices for project work get paid
on time and can provide data for your earned value measurements.
■ Project influencer: Is positively or negatively impacted because of the result of the
project or potential changes from the project.
■ Information sources: Individuals who provide helpful information. They may have
special knowledge of the project as a result of their roles in similar projects, or they
might be customers of similar products.
Project Planning
■Input/Data ■Project Variables
Contract
Stakeholders’ Input Physical Environment
Constructibility Analysis
■Considerations/Constraints
Contractor Methods
■Resources Funding
Human
Equipment Labor Agreements
Capital Delivery Methods
■Value Engineering
Optimize Cost ■Output/Deliverables
Optimize Schedule
Optimize Quality
Work Breakdown Structure
■Stakeholders Schedule Scope of Work
Owner
Suppliers
Define Project Goals
Contractors Periodic Forecasts
Public Agencies
Designers Baseline Plan
Public Groups Recovery Plans
Develop The
Baseline Plan
1. Initiating A
Project
■ Only when a project is authorized by senior management, planning
can proceed.
■ Initiating a project will detail the project objectives, key assumptions
and constraints, key milestones, budget, high-level risks, and other
important details.
Defining A
Project
■Project ID ■Project Risk Level
■Project Title ■Project Leveling Priority
■Project Description ■Funding Sources
■Project Planned Start Date ■Project Codes
■Project Planned Finish Date ■Project Objectives
■Project Planned Duration ■Project Assumptions and Constraints
■Project Budget ■Project Performance Measures
■Project Manager ■Others
Zone 1 Zone 2
Project 1
Project 2
Enterprise Project
Structure (EPS)
■ The Enterprise Project Structure (EPS) will provide a hierarchical
structure for breaking down programs into projects and showing how
projects fit with each other.
■ Similarly, it is used to show what programs and projects exist within
an organization.
To Which Portfolio
Does This Project Belongs?
■ Projects and Programs can be part of one or many portfolios.
Accordingly, the project need to assigned to those portfolios.
Translating
Project Requirements
■ List all deliverables
■ Use an experienced team to help decompose and refine each of the
task requirement
■ Develop WBS
■ Identify risks
■ Develop strategies for completing the project
Planning Requirements
In Contract Documents
■ Each project has requirements for Planning and Schedule reporting.
The level of Planning and Schedule reporting could widely vary
depending on the client requirements.
Specification Sections
Relevant To Planning1
■ Section 01310. Project Management and Coordination
Project schedule: Baseline, Updates and Revised
Project schedule reports
Cost-Loaded Schedule
Schedule delays
Material and drawings submittal and approval
Material Procurement
Daily, Weekly and Monthly Progress reports
Project meetings
Project Planner/Scheduler
Construction Photographs
Accidents and other reports
1 The Appendix include sample specifications from current projects in the region
What to
Check?
■Milestones ■Updating the schedule
■WBS Requirements ■Baseline Schedule Submission
■Schedule Level of Detail ■Revised Schedule Submission
■Activity Durations ■Quality Control Forms
■Cost loaded schedule ■Safety Checklists
■External Dependencies ■Document Workflow
■Owner Activities ■Staff requirements
■Approval Periods ■Software requirements
■Reporting Requirements ■Training Requirements
■Time Extension Application ■Others
Deliverables
Requirements for
Scope Decomposition
■ The project scope shall be decomposed into a WBS
■ The WBS shall include the entire scope of work for the project
■ The scope of work elements shall be mutually exclusive
WBS
Meaning
■ Work. Sustained physical or mental effort to overcome obstacles and
achieve and objective or result; a specific activity, duty, function or
assignment often being a part of some larger undertaking; something
produced or accomplished by effort, exertion, or exercise or skill.
■ Breakdown. To divide into parts or categories; to separate into simpler
substances; to undergo decomposition.
■ Structure. Something arranged in a definite pattern of organization.
WBS Characteristics
Benefits of WBS
Developing A WBS
■ Project management
■ Documentation
As Built Documents
■ Product implementation
Training and Operations
■ End product evaluation
■ Project closure
WBS By Product
WBS By Phase
WBS Levels
Project
WBS Level 1
Level 2 Hardware Software Syst. Engr Proj. Mgt. Syst. Test Data Mgt.
1.1 1.2 1.3 1.4 1.5 1.6
Level 3
1.1.2 1.2.2
Level 4
1.2.2.3
1.1.2.9 1.5.4.5
1.1.2.9.4 – Level 5
Should WBS Be
Decomposed Further? 1/2
■ Is there a need to improve the accuracy of the cost and duration estimates?
■ Is more than one individual responsible for the work contents?
■ Is there a need to know precisely the timing of activities internal to the work package?
■ Is there a need to cost-out activities internal to the work package?
■ Are there any dependencies between the internal activities and other work packages?
■ Are there any significant time breaks in the execution of the work processes internal
to the work elements?
Should WBS Be
Decomposed Further? 2/2
■ Do resource requirements within the work package change over time?
■ Do the prerequisites differ among the internal deliverables within the work element?
■ Are there any acceptance criteria applicable before completion of the entire work
package?
■ Can a portion of the work to be performed within the work package be scheduled as a
unit?
■ Are there any specific risks that require focused attention to a portion of the work
package, requiring further division to separate them?
■ Is the work package understood clearly and completely to the satisfaction of the
various stakeholders?
Source: T. Raz and S. Globerson, “Effective Sizing and Content Definition of Work Packages”, Project Management Journal,
December 1998: 17-23
WBS Dictionary
■ A document that describes each component in the work breakdown structure (WBS).
■ A WBS dictionary is designed to control what work is done and when, to prevent
scope creep and to increase understanding of the effort of each task.
■ For each WBS component, the WBS dictionary includes a brief definition of the scope
or statement of work, defined deliverable(s), a list of associated activities, and a list of
milestones.
■ Other information may include: responsible organization, start and end dates,
resources required, an estimate of cost, charge number, contract information, quality
requirements, and technical references to facilitate performance of the work.
Stakeholder Analysis
■ Stakeholder analysis identified the influence and interest of the various stakeholder and
document their needs, wants and expectation.
■ The analysis then selects, prioritized and quantifies the needs, wants and expectations
to create requirements. Unquantifiable expectations, such as customer satisfaction,
are subjective and entail a high risk of being successfully accomplished.
■ Stakeholders interests may be positively or negatively affected by execution or
completion of the project and they may also exert influence over the project its
deliverables.
Stakeholders In
Construction Project
Dynamics Of
Stakeholders Needs
■ A project’s stakeholder needs do not remain static throughout the
project and needs to be identified, re-assessed, tracked and
managed appropriately throughout the project lifecycle.
Stakeholder
Analysis
STAKEHOLDER ANALYSIS
Name of Project Made By Approved By
New Premises Project Manager Project Owner
4-Nov-04 30-Nov-04
Stakeholder Area Of Interest Contributions Expectations Power Strategy Responsible
CEO Finance, Decision on project Increased revenue Can stop Must be involved Project
Outcome of Project scope and better market project Manager
position
Integrating WBS
With Project Documents
■ One of the key objectives of WBS is to define what is included in the
project scope and what is excluded.
■ Contract documents provide the source for contractually identifying
the project scope.
■ Accordingly, the WBS must be closely coordinated with the different
project documentation to ensure integrity.
Document
Categories
■ Specifications
■ Method Statements
■ Drawings
■ Contract Documents
■ QA/QC Records
■ Safety Records
■ Material brochures
■ Permits and approvals
Construction Contract
Documents
■Volume I ■Volume III
Instruction to Tenderers Preamble to Method of Measurements
Conditions of Contract Bill of Quantities
Form of Agreement ■Volume IV
Model of Performance Bond Architectural Specifications
Preamble and List of Drawings Structural Specifications
Soil Investigation Report Electrical Specifications
■Volume II Mechanical Specifications
Information to be provided with the ■Volume V
Tender Architectural Drawings
Form of Tender Structural Drawings
Appendix to Form of Tender Electrical Drawings
Mechanical Drawings
Document Breakdown
Structure (DBS)
■ The Document Breakdown Structure is used to identify all
documents that are needed for the proper delivery of a project.
■ It allows organizing those documents in a structured format that will
ease accessing and reviewing the same.
■ It will help in identifying missing documents and maintaining track of
latest revisions.
WBS Development
Techniques
■ Brainstorming
■ Delphi technique
■ Mind Mapping
Brainstorming
■ Help people think creatively in a group setting without feeling
inhibited or being criticized by others
Delphi
Method
■ Derives consensus using a panel of experts to arrive at a
convergent solution to a specific problem
■ Useful for large and critical risk impacts
Mind
Mapping
■ Mind-mapping is a creative thinking that helps the analytic and
creative sides of the brain.
■ Mind-mapping is a visual deception of an idea, concept, or issue.
■ Mind-mapping mirrors the way our minds actually work.
Sample Mind-Mapping
Approach
Resulting WBS in
Chart Form
3. Assign
Responsibility
■ Assign responsibility for accomplishment of each element of the
work at appropriate management level.
Requirements for
Assigning Responsibility
■ Performance responsibility shall be assigned for each element of the
project and for the project in total
■ Management responsibility shall be clearly defined
■ Internal managers shall be responsible for any work to be performed
externally
Roles and
Responsibilities
■ The following need to be addressed when listing the roles and
responsibilities needed to complete the project.
Role. The label describing the position of a project for which a person is
accountable.
Authority. The right to apply project resources, make decisions, and sign
approvals.
Responsibility. The work that a project team member is expected to perform in
order to complete the project’s activities.
Competency. The skill and capacity required to complete project activities.
Accountability
Authority Responsibility
and and
Responsibility Accountability
Operational Level
The
Project Sponsor
■ A single individual assigned by management to approved projects who has
sufficient organizational authority to determine the scope of a project and
approve the corresponding time and cost elements which will deliver the
approved scope.
■ The role of the sponsor is to be focal point for project decisions that are
beyond the authority of the PM.
Role Of
Project Sponsor
■ Approve the business case for a project.
■ Approve the business requirements for a project.
■ Approve the negotiated scope, time, and costs and secure final approval for the
project.
■ Approve project scope changes and consequent changes in time and/or cost over the
lifespan of the project.
■ Review progress and provide strategic direction to the Project Manager.
■ Set priorities and resolve conflicts escalated by the Project Manager, customer, or
functional managers.
The
Project Manager
■ Is responsible for the coordination of the project team and,
ultimately, for managing the project plan to enable the successful
completion of the project on time, within budget and at the expected
level of quality.
Role of
Project Manager
■ Identify the skills needed on the team, and negotiate with the resource managers for assignment
of appropriate people.
■ Coordinate tasks on the work breakdown structure (WBS).
■ Negotiate the time frames in which tasks are to be performed.
■ Develop and consolidate project plans.
■ Track milestones, deadlines, schedules, recourse utilization, budgets, risks, changes of scope,
quality of deliverables, and other project elements.
■ Act as a liaison with top management and the project client.
■ Issue status reports and conduct status review meetings.
■ Coordinate with outside subcontractors, consultants, and vendors.
■ Recommend changes to schedule, resource requirements, and budgets, when required.
The
Resource Manager
■ Is responsible for having available a department of subject-matter
experts, engineers, software programmers, lawyers, or other
professionals and service providers. They form the resource pool
from which the manager of the project staffs his or her project.
Role of
Resource Manager
■ Hire, fire, train, discipline, and motivate the functional department’s employees.
■ Generate performance reviews for these employees.
■ Develop and manage within departmental budgets.
■ Plan the allocation of resources.
■ Interpret upper-management’s direction, and implement its policy.
■ Solve problems as they arise.
■ Assign people to the project team.
■ Develop and provide a challenge to employees
■ Set and maintain productivity standards.
■ Accept accountability for a quality product that is to be delivered on schedule.
■ Be proactive when possible and reactive when necessary.
■ Validate time estimates for tasks.
■ Monitor project work.
■ Represent the functional group to the rest of the organization.
The Project
Team Member
■ The project team member is a representative of a functional
department and a contributor to the project team.
Role of Project
Team Member
■ Provide input regarding project objectives and scope.
■ Define/design/perform assigned tasks, or assign people to do so.
■ Determine time estimates for tasks that are to be performed.
■ Interact with other functional areas and other team members.
Organization
Charts
■ Hierarchical-type charts
A graphic display of project team members and their reporting relationships.
Showing who reports to who
■ Matrix-based charts
Illustrates the connections between work that needs to be done and project team
members.
■ Text-oriented formats
Describes roles and responsibilities of each position on the project.
Organization
Charts
What is a
Job Description?
■ A Job Description is a document which outlines a particular role and set of responsibilities on a
project. The purpose of a job description is to clarify the scope of work that a particular role is
responsible for undertaking and the skills, experience and qualifications necessary to ensure that
the role is undertaken effectively. It includes:
An overview of the respective role
A list of the specific responsibilities associated with the role
Clarification of where the role fits within the project organization structure
A list of the skills, experience and qualifications required
Measurable performance criteria
A statement describing the work environment
The salary package on offer.
RACI Chart
RACI Chart
Other Possible
Sets Of Actions
■ 1 = Actual Responsibility
■ 2 = General Supervision
■ 3 = Must be Consulted
■ 4 = May be Consulted
■ 5 = Must be Notified
■ 6 = Final Approval
Other Possible
Sets Of Actions
■ A = Approved The Deliverable
■ R = Reviews the Deliverable (and provide feedback)
■ C = Responsible for Creating the Deliverable – Could be C1 for primary and
C2 for backup
■ I = Provides Input
■ N = Notified When Deliverable is Complete
■ M = Manages the Deliverables
Responsibility
Assignment Matrix (RAM)
■ A structure that relates the project organizational breakdown
structure to the work breakdown structure to help ensure that each
component of the project’s scope of work is assigned to a
responsible person.
Sample
RAM
Cont.
EREC
P.M
A/E
No. Tasks / Activities Description
R
1.0 Bonds Guarantees & Insurance Policies, Permits
1.1 Advance Payment Guarantees A R2 R1 P
1.2 Performance Guarantees A R2 R1 P
1.3 Insurance Policies A R2 R1 P
1.4 Building Permit K K S P
Organization Breakdown
Structure (OBS)
■ The Organization Breakdown Structure is used to identify all the
roles and responsibilities in a project. The OBS breaks down a
project into descending levels of responsibilities, naming all the
individuals required to supervise and manage the deliverables
named in the project scope of work.
OBS
Control
Account
■ A management control point where the integration of scope, budget, actual cost, and
schedule takes place, and where the measurement of performance will occur.
■ Control accounts are placed at selected management points of the work breakdown
structure. Each control account may include one or more work packages, but each
work package may be associated with only one control account.
■ Each control account is associated with a specific single organizational component in
the organizational breakdown structure (OBS).
Control Account
Matrix
Control Account
Manager (CAM)
■ Integration of the WBS and OBS establishes the control account
where the performance measurement necessary for project
management is performed. This intersection results in designation of
a focal point for management control, the control account manager
(CAM).
4. Schedule
The Work
■ Create a schedule for all the work which identifies activities, durations,
milestones and interdependencies.
■ A project schedule is the agreed upon set of tasks and due dates used to
guide and monitor the project to completion.
Project
Constraints
Project
Assumptions
■ Assumptions are external circumstances or events that must occur
for the project to be successful, and they involve some risk.
■ Assumptions are factors that, for planning purposes, will be
considered true, real or certain.
Activity list
Characteristics Of
An Activity
■ Work is performed and described in terms of a verb, objective and noun- there is
action performed
■ A single person is responsible for an activity- accountability
■ It has defined start and finish dates
■ Usually, there is a tangible output or product at completion
■ It fits logically under an existing WBS element
■ It is of a size and duration that is sufficient for control
■ The labor and costs necessary to perform the activity can be estimated
■ Actual progress data can be collected for the activity
Milestone
Hammock
Work Package
Work
Package
WBS and
Activity Link
What Is Enough
Detail?
■ Activities Should Be:
Assignable
Clearly Defined
Duration Can Be Estimated
Cost Can Be Estimated
Progress Can Be Tracked
Practical
Tips
■ Only Detail Tasks if You Have Enough Information
■ More Detail for Earlier Phases
■ Leave Later Phases at a Lower Level of Detail
■ Set Milestones For Developing Further Detail
Progressive
Elaboration
■ Continuously improving and detailing a plan as more detailed and
specific information and more accurate estimates become available
as the project progresses, and thereby producing more accurate and
complete plans that result from the successive iterations of the
planning process.
Rolling
Wave Planning
■ Is a form of progressive elaboration planning where the work to be
accomplished in the near term is planned in detail at a low level of
the WBS, while work far in the future is planned for WBS
components that are at a relatively high level of the WBS.
Activity
Steps
■ For selected activities, the activity could be divided into steps.
■ Each step will have a weight value representing the importance of
this step for completing an activity.
■ Steps are not necessarily to be completed in the same order.
Activity
Steps
Step templates
All Rights Reserved. Bassam A. Samman PMP, PSP, EVP, CRA
Collaboration, Management & Control Solutions FZ - LLC
projacstraining.com
Arrow Diagram
Method
■ The arrows are used to represent tasks.
■ The boxes represent task dependencies.
■ This method uses:
Only finish-to-start relationships between tasks
May use dummies
Dummy
Activity
■ An activity that consumes no time or resources and shows only that
a dependency exists between two activities.
Arrow Diagram
Method
Activity A Activity B Activity C Activity D
10 12 14 16 18
Precedence
Diagramming Method
■ Nodes (or boxes) are used to represent tasks and arrows show task
dependencies.
■ The method adds leads and lags to relationship and:
Has four type of relationships (FS, SS, FF and SF)
Precedence
Diagramming Method
A B C
Start Finish
D E F
Types of
Dependencies
■ Mandatory (Hard Logic): Inherent in the nature of the work being done
(e.g., you must design before you can construct).
■ Discretionary (Preferred, Preferential or Soft Logic): Based on
experience, desire or preferences.
■ External: Based on the needs or desire of a party outside the project (e.g.,
government or suppliers).
Precedence Relationships
Finish to Start (FS)
Task A Task B
Precedence Relationships
Start to Start (SS)
Task B
The direction of the arrow defines
which task is the predecessor and
which is the successor.
Precedence Relationships
Finish to Finish (FF)
Task A
Precedence Relationships
Start to Finish (SF)
Task A
Lag
■ A modification of a logical relationship that directs a delay in the
successor activity. For example, in a finish-to-start dependency with
a ten-day lag, the successor activity cannot start until ten days after
the predecessor activity has finished.
Lead
Finish-To-Start
With Lag
100 110
FS 7
Construct Construct
Building Building Exterior
Foundation and Structure
Start-To-Start
With Lag
110
Construct
Building Exterior
and Structure
Installation of
Interior Belt
Conveyors can start
SS 5 five days or more
after Construct
Building Exterior and
Structure starts.
220
Install Interior
Belt Conveyors
Finish-To-Finish
With Lag
110
Construct
Building Exterior
Construct Loading
and Structure Dock can finish
three days or more
after Construct
FF 3 Building Exterior
and Structure
finishes.
120
Construct
Loading Dock
Quiz
Answer
Lag Time= -5
FS(- 5)
Incorrect
Logic
■ The activity logic included in the network schedule must be correct. If the
logic is not correct, the network schedule will not accurately represent the
way construction will actually be carried out.
■ For example, the selection of an interior architect paint color by the
architect should not restrain the application of the roof in the network
because these two activities are not logically related.
■ Incorrect activity logic reduces the effectiveness of the network schedule as
a planning and management tool.
Redundant
Logic
■ Redundant logic is not incorrect but should be avoided when
constructing activity networks. Redundant logic tends to
unnecessarily complicate an activity network. Redundant logic
makes modifying and analyzing an activity network more difficult.
Redundant
Logic
Excavate
Footings
Redundant
Logic
Formwork,
Reinforcement
Place
Concrete
Logic
Loops
■ As noted previously, activity networks used in construction normally have a
unidirectional flow from the start to completion of the project.
■ Logic loops violate this basic premise and result in an impossible situation
where a predecessor activity cannot start until a successor activity is
completed.
■ Loops not only result in impossible network logic but also prevent the
schedule from being calculated using the forward and background pass
technique.
Loops
Open Ends/
Dangling
■ It is recommended that project plans have single start and end
points. This will help in ensuring that logic is complete as well as it
makes presentation neater.
Open
Ends
FINISH
10 70
START
20 30 50 60 80 90
40
NOTE: We recommend that each project have only two open ends, the first milestone activity and the
last milestone activity.
PERT
PERT
P= Pessimistic
M = Most Likely
O = Optimistic
SD = Standard Deviation
GERT Diagram
End Of Section
DAY TWO
Activity Resource
Estimating
■ Estimating the type and quantities of resources required to perform
each schedule activity.
Resource
Types
■ Labor/People Resources
Technical
Non-Technical
■ Equipment Resources
■ Material Resources
Definition Of
Resource
■ Labor (people)
Measured in units of time
Generally, reused between activities and projects
Recorded in terms of price/unit e.g., $50.00/hour
■ Non-labor (equipment)
Measured in units of time
Generally, reused between activities and projects
Recorded in terms of price/unit e.g., 1 training room per day
■ Material
Measured in units other than time
Generally, consumed by the activity to which it is assigned
Recorded in terms of price/unit .e.g., $4.50/square foot
Resource
Availability
■ Information on which resources are potentially available is used for
estimating resource types.
Alternative Analysis
RBS
projacstraining.com
Resource
Calendar
■ Documenting working and non-working days for which a resource
will be active or idle.
Activity Duration
Estimating
■ Define a time duration for each activity based on estimated work and
historical productivity rates.
Underestimating Activities
Estimating Activity
Durations
■ The duration of an activity is a function of the amount of work that must
be accomplished and the rate at which that work can be accomplished.
Simply stated, the duration of an activity is the quantity of work divided
by the production rate. The basic formula for estimating activity
durations is as follows:
Work
Quantity
■ The work quantity is the amount of work that must be accomplished
which is normally defined by the construction documents.
■ The quantity of work is expressed in some measurable quantity that
could be the amount of materials or equipment that need to be
installed.
■ The quantity of work includes all work that is necessary to complete the
scope of work defined by the activity.
Production
Rate
■ The production rate should be the planned average daily production rate
based on the available resources and the environment within which the
work will be performed.
■ It also includes the idle and nonproductive time associated with the
movement and setup of equipment, break times, expected equipment
downtime for maintenance and repair, and other expected downtime.
Factors Affecting
Productivity
Analogous
Estimating
■ Using the actual duration of a previous similar schedule activity as
the basis for estimating the duration of a future activity.
Parametric
Estimating
■ Estimating the basis for activity durations can be quantitatively
determined by multiplying the quantity of the work to be performed
by the productivity rate.
Schedule
Development
CPM Schedule
Calculation
■ Forward Pass
■ Backward Pass
■ Float
■ Critical Path
Forward Pass
Definitions
■ Early Start Date (ES)
Earliest possible point in time an activity can start, based on the
■ Duration (DU)
Number of work periods, excluding holidays or other nonworking periods, required to complete the activity;
■ Forward Pass
Starting at the beginning (left) of the network develop early start and early finish dates for each task,
Forward
Pass
A
5
ES 1 EF 5
C
15
ES 11 EF 25
B
10
ES 1 EF 10
Forward pass
Forward Pass
Calculation
ES DU EF
Task
EF = ES + DU – 1 LS Float LF
3 DU = 2 4
Paint Trim
1 DU = 2 2 3 DU = 3 5 9 DU = 2 10
Prep Paint Ceiling
Clean-up
3 DU = 4 6 7 DU = 2 8
Paint Walls Paint Walls (2nd
Coat)
Task Identification
Forward Pass
Name Duration ES EF
Prep 2 1 2
Paint Trim 2 3 4
Paint Ceiling 3 3 5
Paint Walls 4 3 6
Paint Walls (2nd Coat) 2 7 8
Clean-up 2 9 10
Backward Pass
Definitions
■ Late Start Date (LS)
Latest point in time that an activity may begin without delaying that activity’s successor
If the activity is on the critical path, the project end date will be affected
■ Late Finish (LF)
Latest point in time a task may be completed without delaying that activity’s successor
If the activity is on the critical path, the project end date will be affected
■ Backward Pass
Calculate late start and late finish dates by starting at project completion, using finish times
and working backwards
Backward
Pass
Backward pass
LS 6 LF 10
A
5
ES 1 EF 5 LS 11 LF 25
C
15
LS 1 LF 10 ES 11 EF 25
B
10
ES 1 EF 10
Backward Pass
Calculation
Total
Float
■ The amount of time an activity can slip from its early start without
delaying the project
■ The difference between an activity’s late dates and early dates
■ Activities with zero total float are critical.
■ Late Dates - Early Dates = Total Float
Total
Float
LS LF
Positive float
ES EF
Positive float
LS LF
Zero float
(critical)
ES EF
LS LF
Negative Float
(extremely
critical) ES EF
Negative float
Critical
Path
Backward pass
LS 6 LF 10
A
5
ES 1 EF 5 LS 11 LF 25
h
TF = 5
al Pat
tic
Cri C
15
LS 1 LF 10 ES 11 EF 25
TF =0
B
10
ES 1 EF 10
TF = 0
Forward pass
LS 1 LF 5
Must Finish By:
A Day 20*
5
ES 1 EF 5 LS 6 20*
LF 25
TF = 0
C
15
LS -4 LF 5 ES 11 EF 25
TF = -5
B
10
ES 1 EF 10
TF = -5
Task Identification
Forward and Backward Passes
The Critical
Path
■ The critical path is the longest duration path through a network
diagram and determines the shortest time to complete the
project.
Near-Critical
Activity
■ A schedule activity that has low total float. The concept of near-
critical is equally applicable to a schedule activity or schedule
network path. The limit below which total float is considered near
critical is subject to expert judgment and varies from project to
project.
Driving
Relationship
■ Relationship from a predecessor that determines an activity’s early
start.
■ How This Is Represented:
A solid relationship line = driving
A dashed relationship line = non-driving
11-15
All Rights Reserved. Bassam A. Samman PMP, PSP, EVP, CRA
Collaboration, Management & Control Solutions FZ - LLC
projacstraining.com
Driving
Relationship
A
5
ES 1 EF 5
C
15
ES 11 EF 25
B Driving Relationship
10
ES 1 EF 10
Path
Convergence
■ In mathematical analysis, the tendency of parallel paths of
approximately equal duration to delay the completion of the
milestone where they meet.
Path
Convergence
Formwork &
Reinf Ftgs
Area 2
Cast Cast
Concrete Concrete
Area 1 Area 2
Path
Divergence
■ Extending or generating parallel schedule network paths from the
same node in a project schedule network diagram. Path divergence
is characterized by a schedule activity with more than one successor
activity.
Path
Divergence
Excavate Excavate
Footings Footings
Area 1 Area 2
Formwork &
Reinf Ftgs
Area 1
Exercise
PDM
Network
The Project
Schedule
Activity DU ES EF LS LF TF
A 10 1
B 5
C 15
D 5
E 20
F 15
G 10
H 5
I 10
J 5
Answer
The Project
Schedule
Activity DU ES EF LS LF TF
A 10 1 10 1 10 0
B 5 11 15 16 20 5
C 15 11 25 11 25 0
D 5 11 15 36 40 25
E 20 16 35 26 45 10
F 15 16 30 21 35 5
G 10 26 35 26 35 0
H 5 16 20 41 45 25
I 10 36 45 36 45 0
J 5 46 50 46 50 0
Activity
Calendars
■ Holidays
Public Holiday Days
Events
■ Weekends
5 Day Week
6 Day Week
International Weeks
Activity
Calendars
Date
Constraints
■ Date Constraints used to constrain the scheduling of activities during
the forward (early date constraints) and backward (late date
constraints) passes based on calendar dates.
■ Date constraints take precedence over schedule when performing
schedule calculations.
Why It
Is Needed?
■ Imposed date restrictions used to reflect project requirements that
cannot be built into the logic.
■ Schedule more accurately reflects the real world aspects of the
project
■ Provides additional control to the project
■ Use to impose a restriction on the entire project or an individual
activity
Activity
Constraints
■ Start Date Constraints
Start No Earlier
Start No Later
Start On
■ Finish Date Constraints
Finish No Earlier
Finish No Later
Finish On
■ Float Constraints
Zero Free Float
Zero Total Float
Start On
Start
On
Start On
or Before
■ Forces the activity to start no later than the constraint date
Shifts the late start to the constraint date
Affects the late dates of its predecessors
Used to place a deadline on the start of an activity
Start On
or Before
Start On
or After
■ Used to set the earliest date an activity can begin.
■ Forces the activity to start no earlier than the constraint date
■ Pushes the early start to the constraint date
■ Affects the early dates of its successors
Start On
or After
LS LF LS LF
A B
ES * EF ES EF
LS LS LF LF LS LS LF LF
A A B B
ES ESEF
* EF ES ESEF EF
Start On
or After
Finish
On
■ Forces the activity to finish on the constraint date
Shifts both early and late finish dates.
Delays an early finish or accelerates a late finish
Used to satisfy intermediate project deadlines
Finish
On
Finish On
or Before
■ Used to set intermediate completion points in a project.
■ Forces the activity to finish no later than the constraint date
■ Pulls the late finish date to the constraint date
■ Affects the late dates of its predecessors
Finish On
or Before
LS LF LS LF *
A B
ES EF ES EF
AA BB
ESES EFEF ESES EFEF
Finish On
or Before
Finish On
or After
■ Forces the activity to finish no earlier than the constraint date
Shifts the early finish to the constrained date
Affects the early dates of its successors
Used to prevent an activity from finishing too early
Finish On
or After
As Late
As Possible
■ Delays an activity as late as possible without delaying its successors
Shifts the early dates as late as possible
Also called a zero free float constraint
As Late
as Possible
Mandatory Start
and Finish
■ Forces early and late dates to be equal to the constraint date
Affects late dates of predecessors and early dates of successors
May violate network logic
Mandatory
Start
Mandatory
Finish
Shortening The
Schedule
■ Re-estimating: Reduce the buffer allowed in activity duration that contains the most
unknowns.
■ Fast Tracking: Doing critical path activities in parallel that were originally planned in
series.
■ Process Improvement: Increasing productivity based on different work process,
technologies and/or machinery.
■ Limited Overtime: Increasing the number of hours per day/week available to work
on tasks.
■ Crashing: Adding more resources to critical path activities.
What is
re-estimating?
■ Decreasing project and activity cost by eliminating the risks in
activities.
What is
fast tracking?
■ Schedule compression by doing more critical path activities in
parallel.
Fast
Tracking
Traditional Approach
Time
4
and Cost
2
6
1
Saved
Construction
Construction
What is
crashing?
■ Scheduling compression through analyzing costs and schedule
trade-offs to obtain the greatest compression for the least cost.
■ Adding resources to critical path tasks.
Schedule
Compression
■ Focus on Critical Activities
■ Logic Revisions
■ Activity Duration Reduction
■ Network Constraints
Reducing Activity
Duration # 1
Activity Y Activity Z
Plan Dur=6D Plan Dur=10D
Min Dur=4D Min Dur=6D
($4,000/D) ($3,000/D)
Activity X
Plan Dur=18D
Min Dur=14D
($2,000/D)
As-Planned
Reducing Activity
Duration # 2
Activity Y Activity Z
Plan Dur=6D Plan Dur=10D
Min Dur=4D Min Dur=6D
($4,000/D) ($3,000/D)
Activity X
Plan Dur=16D
Min Dur=14D
($2,000/D)
Reducing Activity
Duration # 3
Activity Y Activity Z
Plan Dur=6D Plan Dur=8D
Min Dur=4D Min Dur=6D
($4,000/D) ($3,000/D)
Activity X
Plan Dur=14D
Min Dur=14D
($2,000/D)
Schedule Compression
Example
■ As Planned Schedule
■ Revise Logic
■ Reduce Activity Duration
■ Project Time/Cost Curve
As Planned
Schedule
Revise
Logic
Reduce Activity
Duration
Activity B
Time-Cost Curve
22,500
22,000 Minimum Duration
21,500 (Crash) Point
Activity Total Cost
21,000
Activity
20,500
$1,200/Day Time-Cost
20,000 Curve
19,500
19,000
Planned
18,500
Duration
18,000
6 7 8 9 10 11
Activity Duration (Days)
Reduce Activity
Duration
Reduce Activity
Duration
Reduce Activity
Duration
Project Compression
Summary
Project Time/Cost
Curve
130,000
128,000
126,000
Project Cost
124,000
122,000
120,000
118,000
116,000
25 27 29 31 33 35 37
Project Duration (Working Days)
Resource
Plan
■ A list of the types of resources (labor, equipment and materials)
required
■ A schedule outlining when each of the resources is required to be
utilized
■ An assignment of each resource to a set of activities to be
completed.
Resource
Leveling
■ It is used to address schedule activities that need to be performed to meet
specified delivery dates, to address the situation where shared or required
resources are only available at certain times or only available in limited
quantities, or to keep selected resources usage at a constant level during
specific time periods of the project work.
Resource Requirements
After Scheduling
Resource Leveling
With Limited Resource Availability
Resource Leveling
With Fixed Project Completion
How Resource
Leveling Affects A Schedule?
■ Case 1: Resource is available, no effect on activity.
■ Case 2: Resource is not available, delay activity until resource becomes available.
■ Case 3: Activity is delayed because its predecessor has been delayed as a result of case 2.
■ Case 4: Activity is delayed as a result of case 2, but when it reached the new time period, the
resource had been already consumed thus became unavailable. Therefore activity will be delayed
until resource becomes available.
■ Case 5: The activity requirement of the resource exceeds maximum availability levels, therefore
activity will not be changed as it requires special consideration.
Case
Study
■ A Contractor is required to complete a painting job in 30 days.
■ The job has been divided into 8 zones for which each would require one
painter per day to complete the work.
■ The duration for each zone has been estimated based on work to be done.
■ The Contractor has a resource limit of two painters per day (16 man-
hours/day).
The Current
Status
After Resource
Leveling
A Complete
Project Schedule
■ A complete project schedule must cover in addition to the on-site construction
schedule, the following:
Mobilization and Demobilization
QA/QC Activities
Testing and Commissioning
Material and Drawings Submittal Schedule
Material Procurement Schedule
Employer furnished equipments and material
Permits and Approvals
Subcontractor and Suppliers Selection
Temporary activities and staging
Substantial Completion and Handover activities
Interfaces with other contracts
Project Management activities (progress meetings, reviews, etc.)
Submittal
Schedule
■ It should include:
Scheduled Date For First Submittal
Specification references
Submittal Type and category (sample, drawings, brochure, method, etc.)
Name of manufacturer
Description of work covered
Needed date for final approval
Scheduled dates for PO and first project delivery
Scheduled dates for commencement of installation
Schedule
Baseline
■ It is a specific version of the schedule that has been accepted and
approved by the project management team as the schedule
baseline.
5. Develop Time
Phased Budget
■ The Financial Plan is the formal document for justifying and
obtaining approval for the funding for the contracts and related
services required in support of the project.
■ It represents the Approved Baseline Budget for the project.
Cost
Estimating
■ Developing an approximation of the costs of the resources needed
to complete project activities.
Chart
of Accounts
■ Any numbering system used to monitor project costs by category
(e.g., labor, supplies, materials). The project chart of accounts is
usually based upon the corporate chart of accounts of the primary
performing organization.
Cost Breakdown
Structure (CBS)
How To Develop
The Cost Loaded Plan
■ List the types of costs to be incurred on the project
■ Identify the cost per unit for each cost type
■ Identify the cost per activity
■ Identify when each of the costs will be incurred
Type Of
Costs
■ Direct Costs:
Costs that are proportional to the project
Material for products, workers, project managers
■ Direct Costs are also known as Variable Costs
They vary with requirements
■ Indirect Costs:
Costs expended regardless of the size of the Project
Management, advertising for company, taxes
■ Indirect Costs are also known as Fixed Costs
They do not vary with requirements
Bottom-Up
Estimating
■ It is based on determining the cost of each activity in
the project plan:
The schedule must include all activities including
administrative activities.
Resources are transformed into cost using the unit
price rate.
Expenses need to be assigned to activities.
Activity Costing
Considerations
■ What cost rate to use? (internal, preferred, budget, etc.)
■ Does the cost rate reflect variance over time?
Cost
Baseline
■ Is a time-phased budget that is used as a basis against which to
measure, monitor, and control overall cost performance on the
project.
Cost
Baseline
■ Is a time-phased budget that is used as a basis against which to measure, monitor,
and control overall cost performance on the project.
■ Is a time-phased budget that is used as a basis against which to measure, monitor,
and control overall cost performance on the project.
■ Using the project schedule early and late dates, produce the cost baseline envelope.
■ The cost baseline will indicate the scheduled earnings during the project life.
S-Curve
6. Schedule Compliance
With QA/QC Plan
■ The QA/QC Plan describes the strategy and methods the project will
deploy to ensure two things:
That the project is being managed, developed, and deployed in a
sound, reasonable way.
That the project's deliverables are of acceptable quality before they are
delivered to the project's clients.
Why Is This
Important?
■ Quality doesn't happen by accident. It must be planned so there is
agreement about how quality is measured, when quality checks occur and
how corrective actions are determined and implemented.
■ The QA/QC Plan is a tool that can help the project deliver the highest
possible quality result within committed resources, schedule and budget.
Approaches To Conformance
Quality Management
Empowerment
Quality Assurance
Quality Control
Inspection
Blame
Oriented
Reactive Proactive
Quality Assurance
Plan
■ To provide the customer with assurance that the quality targets will
be met, ‘Quality Assurance’ (QA) techniques should be defined. QA
techniques are the preventative steps taken to eliminate any
variances in the quality of the deliverable produced from the quality
targets set.
QA
Techniques
■ Historical Data
■ Requirements definition
■ Standards Definition
■ Skilled Staff
■ Quality Reviews
■ Change Control
Quality
Control
■ In addition to undertaking QA to improve deliverable quality, a series
of ‘Quality Control’ (QC) techniques may be implemented.
■ QC is defined as the remedial steps taken to eliminate any
variances in the quality of the deliverable produced from the quality
targets set.
Quality Control
Forms 1/2
■Material Inspection Report ■Record of Testing – On or Off Site
■Material Inspection Report for Epoxy Coated ■Off-site Inspection Report
Reinforcement Steel ■Advice of Defects
■Material Deliveries Storage Checklist ■Non-Conformance Report
■Deliveries of Steel Checklist ■Status Summary on Non-Conformance Notices
■Request for Inspection and Approval ■Maintenance Inspection Check List
■Request for Inspection and Approval ■Record of Ceiling Space Closure
(Demolition) ■Internal Procedures
■Field Inspection Daily Report ■Concrete Cube Test Report
■Record of Concrete Pour ■Mortar Cube Test Results
■Pre-Concrete Inspection Record
Quality Control
Forms 2/2
■Block Works Checklist ■Pre Engineered Building Checklist
■Certificate of Hydrostatic / Pneumatic Test ■Calibration of Unit Weight of Sand
■HVAC Checklist ■Sieve Analysis
■Duct Leakage Test Report ■Determination of Modified Proctor
■Airflow Test Report ■Survey Works Checklist
■Drainage Pipe Water Line Pipe Checklist ■Request for Alternative or Substitution
■Checklist Electrical Underground Conduits & ■Inspection and Test Plan
(Electrical Ducts) ■Field Memorandum
■Protected Membrane Roofing Roof Water ■Handing Over Between Package Contractors
Proofing Checklist
■Metal Door / Frame Checklist
Submittal Packages
and Submittal Items
■ Submittals that are interrelated due to specification requirements will be
grouped into submittal packages.
■ Each submittal package will identify the discrete submittal items that need to
reviewed and approved.
■ Submittal items will be linked to the project schedule to identify the approval
needed dates to avoid delaying on-site activities that depend on this
submittal approval.
Communications
Requirements Analysis
Communication
Technology
■ Factors that can affect the project include:
The urgency of the need for information
The availability of technology
The expected project staffing
The length of the project
The project environment
Stakeholder
Stakeholders
Needs
■ What information needs to be collected and when
■ Who will receive the information
■ Methods used to gather and store information
■ Limits, if any, on who may give direction and to whom
■ Reporting relationships
■ Listing of contact information for all stakeholders
■ Schedule for distribution of each type of communication
Performance
Reports
■ Status report – describing where the project now stands
■ Progress report – determining what has been accomplished
■ Trend report – examining project results over time to see if performance is
improving or deteriorating
■ Forecasting report – predicting future project status and performance
■ Variance report – comparing actual results to planned
■ Earned value – integrating scope, cost and schedule measures to assess project
performance.
Communication
Management Plan Attributes
■ Communication Item
■ Purpose
■ Frequency
■ Start/end dates
■ Format/medium
■ Responsibility
Communication Plan
Audiences
What When How Responsible Project
Sponsor Who?
Team
Project Kickoff Project Start (include date when Meeting Project Approve Receive
planned) Manager
Project Plan Start & Upon Updates Document
Details Of
Communication Plan
■ What – List items or occurrences to be communicated.
■ When - Indicate when the item should be generated and or updates distributed.
■ How – Indicate the form the communication will take.
■ Responsible – Indicate the name of the person or team responsible for producing and/or delivering the
communication.
■ Audiences – Add more columns as needed and replace “Who?” with names of persons, entities or groups
impacted by the communication plan. In their respective columns, indicate an appropriate level of involvement for
that person, entity or group. Four common areas of involvement include:
Person(s) who consult with the communication lead to produce the communication.
Person(s) who have input on the communication and whose comments will result in changes to the communication before it
occurs.
Person(s) who approve the communication prior to dissemination or distribution.
Person(s) who receive or review the communication, but who do not have review or approval role in the communication.
Web-Enabled Workspaces
Needed Features In
Project Reporting
■ Drill Down and Roll Up
■ Dice and Slice
■ Exceptions
■ Short and Long Term Reporting
■ Aggregate
■ Cause Effect Analysis
■ Trending
■ Visual
Drill Down
And Roll Up
■ The WBS, OBS, CBS, RBS and other breakdown structures
provides an excellent tool to roll-up detailed project data to selected
summary levels. Similarly, those breakdown structures provides the
tool to drill down to the desired level of detail with confidence.
Example
Reports
■ Master Schedule
■ Detailed Construction Schedule
■ Summary Schedule By Zone
■ Summary Schedule By Trade
■ Summary Schedule By Work Type
■ Detailed Cost Loaded Schedule
■ Summary Cost Loaded Schedule
Tabular
Report
Dice and
Slice
■ Activity codes which are added to identify locations, type of work,
responsibility, department, vendor, phase, etc. provides the means
to analyze the overall project data from different perspectives that
will provide better understanding of the project.
Bar Chart
Report
Example
Reports
■ Detailed Submittal Schedule
■ Detailed Procurement Schedule
■ Concreting Schedule
■ Accountability Reports
Exceptions
■ The ability to filter and select project data provides the project team
with the capability to concentrate on specific parts of the project that
might require additional analysis as well as it enable them to use the
same to trigger an alert to take an action or make a decision.
Example
Reports
■ The Project Critical Path
■ The Project Near Critical Path
■ Delayed Activities Report
■ Threshold Reports
■ Alert Reports
■ Troubled Activities Report
Example
Reports
■ 2-Weeks Look Ahead Schedule
■ 45-Days Look Ahead Schedule
■ 3-Month Look Ahead Schedule
Aggregate
Example
Reports
■ Project S-Curve Report
■ Staffing Plan
■ Major Equipment Utilization Schedule
Manpower
Table
Histogram
Cause Effect
Analysis
■ Project team members are interested in visualizing the effect of
actions that they might do now on future project results. Or, they
might need to identify the causes that had resulted in an action.
Further, by having this capability, project team members can
simulate the impact of different actions on project results.
Example
Reports
■ Time Impact Analysis
■ What If Scenario
Trending
■ Analyzing actual project data will help the project team in establishing
performance trends that need to be reflected on remaining similar tasks or
simply be documented for future projects. In addition, by analyzing trends,
project team members will be able to identify corrective measures to stop an
undesirable trend from continuing in a project. Finally, trends can be used to
benchmark project performance with other projects.
Example
Reports
■ Key Performance Indicators
■ Average Turnaround Report
■ Productivity Reports
■ Performance Reports
Visual
■ There are many project stakeholders that will not be able to visualize
the project performance from reviewing reports and graphs.
Accordingly, reporting key project indicators in a pictorial format will
help in conveying the needed project information.
Formatting
Reports
■ What Type Of Presentation?
■ What Activity Data To Show?
■ What Project Activities To Show?
■ How To Organize Data?
■ How To Order Data?
■ What Level Of Detail?
■ What Time Scale?
What Type
Of Presentation?
■ Project schedule data can be shown in different format depending on the
reader requirements.
■ Data can be presented in:
Tabular format to allow showing more data
Bar Chart format to provide the time phasing aspect with the option to show
logical links
Pure Logic to show the relationships between activities
Histograms to show resource and cost aggregation data per period and
cumulative.
How To
Organize Data?
■ Project activities can be grouped in different formats depending on
the user requirement.
■ Activities can be grouped by:
WBS, OBS,CBS, RBS and other breakdown structures
Codes for location, type, etc.
Dates (early and late)
Float
How To
Order Data?
■ Activities can be ordered or sorted in accordance with the user
requirement.
■ Activities can be ordered by:
Dates
Float
Duration
Codes
Resources and Cost Data
Activity ID
What Level
Of Detail?
■ Activities can be summarized into summary activities depending on
the user requirements.
■ Activities can be summarized based on:
WBS
Codes
Resources
What
Time Scale?
■ Activities can be shown at different time windows of the project as
well as the time scale can be based on Calendar, Ordinal or
Financial dates.
■ In additional, time scale could be vary to be days, weeks, months or
quarters depending on the selected time window.
End Of Section
DAY THREE
Course Agenda
Day Three
■ Develop The Baseline Plan
Develop The Risk Management Plan
Assign Objective Measures Of Performance
■ Implement The Project Management Plan
Manage The Project Schedule
Manage The Project Budget
Risk
Categories
■ Technical, Quality and Performance
■ Project Management
■ Organizational
■ External
Project Management
■ Requirements
■ Benefits
■ Schedule
■ Budget
■ Deliverable
■ Scope
■ Issues
■ Supplier
■ Acceptance
■ Communication
■ Resource
Requirements
Benefits
Schedule
Budget
Deliverables
Scope
Issues
Suppliers
Acceptance
Communication
Resources
Organizational
■ Weak infrastructure
■ Unclear organizational objectives
■ Intra-organizational resource conflicts
■ Shifting funding availability
External
■ Legal challenges
■ Shifting customer goals
■ Natural disasters
■ Legal shifts
Resource Breakdown
Structure (RBS)
■ A source oriented grouping of project risks that organizes and
defines the total risk exposure of the project. Each descending level
represents an increasingly detailed definition of sources of risk to the
project.
■ The RBS is used to structure and guide the risk management
process.
RBS
Hierarchy
■ Level 0 Project Risks
■ Level 1 Category
■ Level 2 Sub-Category
■ Level 3+ Risk Detail
Risk Breakdown
Structure (RBS)
RBS
1/2
The requirements have not been clearly specified
Requirements The requirements specified do not match the customer's needs
The requirements specified are not measurable
The business benefits have not been identified
Benefits The business benefits are not quantifiable
The final solution delivered does not achieve the required benefits
The schedule doesn’t provide enough time to complete the project
Schedule The schedule doesn’t list all of the activities and tasks required
The schedule doesn’t provide accurate dependencies
PROJECT RISKS
RBS
2/2
Lack of controlled communication causes project issues
Communication
Management
Key project stakeholders are ‘left in the dark’ about progress
Project
Staff allocated to the project are not suitably skilled
Resources Insufficient equipment is available to undertake the project
There is a shortage of materials available when required
Higher performance goals
INTERNAL
Technology shifts
Technical Platform changes
New industry standards
PROJECT RISKS
Complex technology
Unproven technology
Weak infrastructure
Organizat-ional
External
Earthquakes
Natural disasters Floods
Landslides
Exchange rate fluctuation
Economic/Financial Interest rate instability
Inflation
Legal shifts
The Use Of
RBS
■ Risk Identification Aid. Can be used as a prompt list to identify risks.
■ Risk Assessment. Can be used to categorize risks by their source.
■ Comparison Of Projects.
■ Risk Reporting. Roll-up of risks.
■ Lessons Learned.
The Three
Elements Of Risk
■ The perception that something could happen
■ The likelihood or probability of something happening
■ The consequences if it happens
Challenges In
Identifying Risks
■ Are we able to identify all risks?
Unknown or Unforeseeable risks
Future risks
Emergent risks
Invisible stakeholders
Perceptually concealed
■ When a risk is not a risk?
Risks versus issues. Issues due to difficulties, personality, political or
organizational matters.
Distinguishing Between
Cause and Effect
Describing A
Risk
■ As a result of (definite cause), (uncertain event) may occur, which
would lead to (effect on objective or objectives).
Causes will use present tense phrases such as “is, do, has, has not,
are, ,,,”
Risks are described with words like “may, might, could, possibly”
Effect uses conditional future tense “will, would, could, ..”
Example
“Cause & Effect”
Lack of No Lack of
quality conformance customer
Vague specs assurance to specs involvement
Customer
Rejects
Design
Triggers
■ Also known as:
Risk symptoms
Triggers
Warning signs
■ Indications that a risk occurred or is about to occur
Risk
Register
■ Contains the outcomes of the other risk management processes as
they are conducted.
Example List of
Identified Risks
Risk ID Description Source Risk Category WBS Element Trigger
010 Well depths more than expected, which Insufficient testing Cost Well drilling Results of initial boring tests
might require heavier drilling equipment
020 Rework to structural elements, delaying the Insufficient detail in Schedule Structural work Work interruptions due to
schedule structural design lack of detail
030 Delay in arrival of custom built control room Supplier’s optimistic Schedule Control room setup Delay in local development
sections estimates milestones set for supplier
040 Failure to meet minimum safety requirements Unfamiliarity with new Quality Environmental testing Vague or unclear
for emissions environmental regulations recommendations from
environmental committee
050 Not enough space to build 4 processing units Variations between actual Scope Processing section 1st processing unit installed
environment than original taking considerably more
design space than expected
Risk Analysis
Goals
■ Decision support
■ Increase understanding of the project in general
■ Identify the alternatives available in delivery and methods
■ Ensure that uncertainties and risks are adequately considered in a
structured and systematic way, which allows them to be incorporated into
the planning and project development process
■ Establish implications of uncertainties and risks
Types of
Risk Analysis
Risk Probability
and Impact
■ Risk probability is the likelihood that a risk will occur
■ Risk impact (or consequence) is the effect on project objectives if
the risk event occurs
Impact of
A Risk
■ The impact of a risk is a numerical rating of the effect that the risk
would have on the project, should it occur. (Impact is sometimes known
as consequence).
■ Typically a five-level scale is used to measure impact:
1 very low
2 low
3 medium
4 high
5 very high
Impact Of Risk
On Project KPI
IMPACT ON
SAFETY
IMPACT ON IMPACT ON
TIME TEAM WORKING
RISK ITEM
CONTRACTOR
PROVIDES
DEFECTIVE
SERVICE
IMPACT ON IMPACT ON
COST QUALITY
Likelihood
Components of
Likelihood
■ Likelihood is divided into two components:
Probability of Occurrence: the probability that the risk events will occur if we take
no action
Intervention Difficulty: the extent to which we are able to influence events
■ Likelihood is the lower of the two ratings for probability of occurrence and
intervention difficulty.
Generic Likelihood
Scales
4 More likely to happen than not Your resources and authority are sufficient to permit only a minor effect on
the outcome
3 Just as likely to happen as not Additional time and effort will be required to move towards an acceptable
outcome
2 Less likely to happen than not Careful oversight of your normal management processes will probably bring
about an acceptable outcome
1 You would be surprised if this happened Your normal management processes should easily ensure an acceptable
outcome
Probability/ Impact
Risk Rating Matrix
■ Matrix that assigns risk ratings (or score) to risks or conditions
based on combining probability and impact scales
■ P-I matrix can be based on ordinal or cardinal scales
■ Risk score helps put the risk into a category that will guide risk
response actions
Risk
Score
Probability-Impact
Matrix
Likelihood
Exposure
Impact
Mapping Risks
Into Activities
■ Team Mobilization and Building
■ QA/QC Tasks
■ Permits and Approvals
■ Deliverables Acceptance
■ Vendors Approvals
■ Shipping and Delivery
■ Project Startup and Handover
■ Access and Areas Release
■ External including off-site Activities
Risk Register:
Mapping Risks
Quantitative Analysis
Will Quantify
■ The delay to the project completion date if the risk or group of risk
do not occur, if they occur within acceptable range and if they occur
at extreme level.
■ The increase in project budget if the risk or group of risk do not
occur, if they occur within acceptable range and if they occur at
extreme level.
Simulation
■ Usually using Monte Carlo technique
■ A model translates the uncertainty at the detail level into their
potential impact on objectives that are expressed at total project
level
■ Will perform the project many times to provide a statistical
distribution of the calculated results.
Monte Carlo
Simulation
■ The probability of completing the project on any specific day
■ The probability of completing the project for any specific amount of
cost
■ The probability of any task actually being on the critical path.
Simple Distributions
Estimate uncertainty
Duration/Cost
?
Task Existence
Outcome A
? Outcome B
Outcome C
Criticality
Analysis
■ Criticality analysis identifies which activities could become most
critical if not effectively managed.
■ Tasks are assigned a value between zero and 100% according to
their potential to affect the duration of the project. Further statistical
analysis can identify which activities are most likely to introduce the
most uncertainty to the project.
Cumulative Frequency
Plots (S Curves)
■ Cumulative frequency plots are often used to represent the likelihood of
certain milestones achieving targets and are often used in determining bid
prices and project budgets.
■ The plotting of these “S” shaped curves can be used to quantify the
interaction of the likelihood of certain events and their cumulative effect
upon the project as a whole.
Optimistic Schedule
& Merge Bias effect
■ Single-Path Schedule
■ CPM schedule finishes on December 10,
relies on combinations of durations that equal 70 days
Optimistic Schedule
& Merge Bias effect
Optimistic Schedule
& Merge Bias effect
■ This project also completes on December 10
■ Parallel paths account for this risk
Optimistic Schedule
& Merge Bias effect
Optimistic Schedule
& Merge Bias effect
Why does the project become more risky?
Real Life to
Complex for PM Software
PROBABILITIC BRANCHING
■ When the outcome of an activity is not clear
Article is not certain to pass the test the first time
■ The successor activity may be one or the other
Pass the test? ==> Certify
Fail the test? ==> FIXIT and retest
■ Each one of these is a “branch” and has some probability
Pass the test and certify = 70%
Fail the test and FIXIT = 30%
Real Life to
Complex for PM Software
■ Integration & test has uncertainty, set up in P3e for modelling
Modelling condition 2
• Rig is >80% before freeze
• Completed on-route
Modelling condition 3
• Rig is <80% before freeze
• Rig shipped after the
freeze
• Delivery Penalty
Risk Response
Strategies
■ Developing options and determining actions to enhance
opportunities and reduce threats. They may include changing the
planned approach to completing the project- e.g. changes to WBS,
time, quality plan and budget.
■ These strategies cannot eliminate all risks.
Strategies For
Negative Risks or Threats
■ AVOIDANCE - Eliminate the threat by eliminating the cause.
■ MITIGATION (CONTROLLING)- Reduce the probability or the consequences of an
adverse risk .
■ TRANSFERENCE (DEFLECTION, ALLOCATION) - Make another party responsible
for the risk through purchasing of insurance, warranties, guarantees or outsourcing.
■ ACCEPT- Recognizing that residual risks must be taken, and responding either
actively by allocating appropriate contingency (also known as Containing), or
passively doing nothing except monitoring the status of risks (also known as
Assuming).
Strategies For
Negative Risks or Threats
X Avoid = Mitigate
RISK RISK
Transfer RISK RISK Accept
Avoid Mitigate
X =
Accept
EFFECT EFFECT EFFECT EFFECT
Strategies For
Negative Risks or Threats
AVOID, MITIGATE
SIGNIFICANT
OR TRANSFER
IMPACT
MANAGE MODERATE
ACCEPT MINOR
Risk Cost
and Frequency
Cost
Transfer Avoid
Retain Treat
Frequency
Avoidance
Actions
■ Additional boreholes at selected locations
■ Prototype and Modeling
■ Carry out complete pre-qualification and short-listing for
Consultants, Contractors, Subcontractors, and Key Suppliers.
■ Add contract clauses to deal with adverse weather conditions.
Mitigation
Actions
■ Carrying out formal design review and document cleansing
■ Increase material submittal review and approval
■ Increase shop-drawings submittal review and approval
■ Increase field inspection and testing
■ Provide training for staff
■ Adopt less complex processes
■ Choose more stable seller
Transference/ Deflection
Actions
■ Additional work to be outsourced
■ Alternative project delivery methods such as Design-Build (EPC).
■ Additional insurance coverage and policies to be purchased
■ Additional warranties to be purchased
■ Exclusion contract clauses
Contracting/
Outsourcing
■ Hiring someone outside your organization to complete the work
when it would decrease risk.
■ This is dealt with in detail in “Procurement Management”
Suggested Allocation
Owner
Contractor
Contract Type CPPF CPIF CPFF FPPI FFP
CPPF-Cost Plus Percentage Fee, CPIF-Cost Plus Incentive Fee, CPFF-Cost Plus Fixed
Fee, FPPI-Fixed Price Plus Incentive, FFP-Firm Fixed Price
All Rights Reserved. Bassam A. Samman PMP, PSP, EVP, CRA
Collaboration, Management & Control Solutions FZ - LLC
projacstraining.com
Factors Influencing
Contract Selection
■ How well-defined the scope of work is or can be
■ The frequency of changes expected after the project starts
■ The level of effort and expertise the buyer can devote to managing
the seller
■ Industry standards of the type of contract used
Handling Risk in
Contracts
■ Clear definition of risks and their assignment
■ Positive incentives linked to risk assignment
■ Flexibility for assignment of different risks between parties
■ Strong emphasis on good management practices designed to avoid
unnecessary risks
Insurance
Insurance Documents
Required In Construction Contracts
■ Contractor’s All Risks Policy (CAR) or Erection All Risks Policy
(EAR) to include General Third Party Liability
■ Construction Plant and Machinery Policy to include all equipment at
various areas
■ Workmen’s Compensation Insurance on Staff in accordance with
statutory Workmen’s Compensation ordinance.
Acceptance
Methods
■ Contingency allowance (time, money, and resources) or reserve is
most common acceptance response. Also known as Risk Buffering
(or Risk Hedging)
■ Fallback plan for high impact risks. This will be the actions that will
be taken if the contingency plan is not effective.
Strategies For
Positive Risks or Opportunities
■ EXPLOIT/PURSUE (instead of AVOIDANCE). Eliminate the uncertainty associated
with a particular risk by making the opportunity definitely happen.
■ ENHANCE (instead of MITIGATION). Modify the “size” of an opportunity by
increasing probability (likelihood) and/or positive impacts (consequences), and by
identifying and maximizing key drivers of these positive-impact risks.
■ SHARE (instead of TRANSFER or ALLOCATION). Allocating ownership to a third
party who is best able to capture the opportunity for the benefit of the project.
■ IGNORE (instead of ACCEPT). Ignore minor opportunities by adopting a reactive
approach without taking explicit actions.
Strategies For
Positive Risks or Threats
Exploit + Enhance
RISK RISK
Share RISK RISK Ignore
Exploit Enhance
+
Ignore
EFFECT EFFECT EFFECT EFFECT
LIKELIHOOD
Share Exploit
Ignore Enhance
IMPACT
Exploit/ Pursue
Actions
■ Value Engineering and Life Cycle Costing.
■ Pre-defined supplier
■ Adding bonus clauses for early project completion
Enhance
Actions
■ Requesting multiple offers for expanding project scope.
Share
Actions
■ Alternative project delivery methods that will allow share of revenue:
BOOT, BOO, etc.
■ Assign independent project management firm to fast track project
delivery.
■ Including savings share clause in contractor’s agreements.
What are
reserves?
■ Time or cost added to the project to account for risk.
■ There are two categories:
Contingency reserve. To deal with the known unknown risks. That is
identified residual risks that remain after risk response planning.
Management reserve. To deal with unknown unknown risks. That is
risks that have not been identified.
Factors For
Determining Reserve
■ Project life cycle position
■ Estimating approach
■ Type of contract
■ Risk exposure
■ Risk tolerance levels
■ Risks accepted
■ Consequences of overruns
■ Other
Risk Reserve In
Project Budget
Total Contract Price
Allowance for
estimating inaccuracy
Allowance for
Passively accepted risks
Allowance for
Actively accepted risks
Contingency
Planning
■ Planning the specific actions that will be taken if a risk event occurs,
or the planned response does not work.
■ These plans can be put in place later, if needed, without meetings or
increased impact to the project caused by delayed action.
Revised Project
Plan
■ The efforts spent in risk management will result in changes to the
project plan. Tasks could be added, removed or assigned to
different resources. Thus, planning is an iterative process.
Adding Activities
To Respond To Risks
■ Vendor submittal re-submission
■ Quality assurance and quality control
■ Deliverables acceptance
■ Snag list and hand over
■ Permits and approvals
■ Mobilization and demobilization
■ Qualifying and selecting vendors
■ Acquiring and building the project team
■ Design review and coordination
■ Mockup and samples
■ Shipping and handling
Adding Relationships
To Respond To Risks
■ Continuity and Flow of resources
■ Damage Control
■ Site Safety
■ Avoid site congestion (Limit Concurrent Activities)
■ Site Security
■ Quality Assurance
■ Resource Leveling and Smoothing
Adding Milestones
To Respond To Risks
■ Issuance of insurance
■ Selection of vendors
■ Access to site and zones
■ Project Deliverables
■ Key Client Decisions
■ Interfaces from other projects/ contracts
■ Interfaces from external organizations
Other Actions
To Respond To Risks
■ Add holidays and off-periods to calendars
■ Allow for learning curve estimate for activity duration
■ Adjust productivity rates during summer season and Ramadan
9. Assign Objective
Measures Of Performance
■ Specify the objective measures to be used to measure work
achievement.
Identify
Thresholds and KPIs
■ Determine the control methods and mechanisms.
■ Establish and document the KPI's for managing project
performance.
Sample
Metrics
■ Schedule
■ Milestones
■ Cost
■ Deliverables Status
■ Issues
■ Action Items
■ Client Satisfaction
Schedule
Schedule
Metrics
■ Total Float
■ Finish Date Variance
■ Start Date Variance
■ Schedule Variance (SV)
■ Schedule Performance Index (SPI)
Milestones
■ While closely linked to the schedule, this metric is at high level. Milestones
should be outcome based, and their completion should be easy to
determine.
■ Milestones tracking involve a summary listing and a graph of major
milestones with planned (initial), projected (updated periodically), and actual
completion dates. Milestones typically encompasses 4-6 weeks of effort.
Milestone
Metrics
Cost
■ The tracking of cost is integral to schedule management. Tracking one
without the other will not provide an estimation of the likelihood of a project
coming in on time and at budget. Actual cost versus budget should be
compared, with respect to charged hours and money spent. Monitoring
delays in key milestones, along with the associated budget designated to
complete the milestones, provides a good estimate of project performance.
Cost
Metrics
■ Cost Variance
■ Cost Performance Index (CPI)
■ Resource Utilization. The total amount of work assigned in a given
period to a resource versus availability.
■ Resource Productivity. The difference between estimated and actual
man-hours.
Deliverables
Status
■ Keeping track of project deliverables is essential, especially when
work has been contracted out from an outside client.
■ Without deliverables, a project is in breach of contract, regardless of
how much work is done.
Quality Of
Deliverables Metrics 1/2
■ Percentage of Deliverables Reviews Resulting In Acceptance From
The First Time
■ Number of Client Change Requests To Revise Scope
■ Number of Hours Of Rework to Previously Completed Deliverables
Quality Of
Deliverables Metrics 2/2
■ Defect Weight. A weighted number to show the total number of
verified defect points for a deliverable. A low priority defect will
receive a low number, whereas a critical defect will receive high
number.
■ Delivered Defect Weight. Defect Weight minus the total removed
defect points.
Issue
Items
■ Issue items need to be tracked, along with an assignment of responsibility,
resolution, and date of closure. Issue items have significant impact on the
project delivery.
■ Issues need to be documented so that (1) progress toward their completion
can be tracked and (2) it is clear when they are complete.
Issue
Metrics
■ Issue Trends which details the number of issues opened, closed and
active, for a given reporting period.
■ Issue Elapsed Time. Details the time it takes to close an issue.
Client
Satisfaction
■ This metric is best applied when there is a client-contractor relationship. A
responsive contractor organization will keep track of significant feedback on
each project, positive or negative, to help the project manager and senior
management to assess the client-contractor relationship at any time, and to
make sure that negative feedback is properly addressed and resolved,
where possible.
Client
Satisfaction
■ Overall Client Satisfaction With Deliverables
■ Overall Client Satisfaction With Project Team
■ Turnaround Time Required To Respond To Client Queries and
Problem
■ Average Time Required To Resolve Client Related Issues
Project
Plan Approval
■ The project plan must receive approval from management, stakeholders
and project team.
■ Formal approval means sign-off.
■ Project Manager must insure that stakeholders needs and objectives are
in the plan.
■ A project cannot effectively start without formal approval of the project
plan.
Reviewing and
Analyzing The Schedule
■ Reviewing The Schedule
To ensure that the schedule is reasonable and complete.
■ Analyzing The Schedule
To ensure that the schedule represents a workable plan
considering available managerial and production resources.
Reviewing
The Schedule
■ Is the schedule complete?
■ Are activity durations reasonable?
■ Are activity relationships complete?
■ Are activity relationships valid?
■ Is the project calendar correct?
■ Is the schedule duration within the contract time?
■ Are contractual milestones met?
Is the
Schedule Complete?
■ Does the schedule activities accurately reflect the project’s contractual
scope of work?
■ Each activity in the schedule represents a discrete part of the project that
can be planned, scheduled, monitored, and controlled. The total work
described by all activities in the schedule must equal the project’s
contractual scope of work.
Is the
Schedule Complete?
■ The purpose of the schedule will determine the level of detail contained in
the schedule. Therefore, it is not uncommon for any single activity in a
schedule to represent more than one operation.
■ During the review process it is important that the schedule be reviewed to
ensure that the scope of work described by each activity is fully defined and
that all schedule activities taken together accurately reflect the project’s
scope of work.
Are Activity
Durations Reasonable?
■ Activity Durations must be reasonable and based on the quantity of
the work as well as the planned resources that include labor,
material and equipment.
■ The nature of the work and anticipated physical conditions when the
work is planned to be carried out must also be considered.
Are Activity
Relationships Valid?
■ Not only do activity relationships need to be complete, activity relationships
must also be valid. Activity relationships must accurately reflect the planned
sequence of the work as well as the required physical, and resource activity
relationships.
■ Activity relationships that do not accurately reflect the planned sequence of
work and required relationships between activities will result in a schedule
that cannot be used to effectively plan and manage the project.
Is The
Project Calendar Correct?
■ In order for the schedule to be a reliable planning and management
tool, the schedule calendar must be accurate so that the project
team can use the schedule confidently to plan and schedule day-to-
day project operations.
Are Contractual
Milestones Met?
■ In addition to the schedule showing the overall project completing within the
contract period, contractual milestones must also be met in the contractual
schedule and project schedule. Contractual milestones might include the
completion of predefined parts of the project, that would be turned over to
other parties for a specific use. If contractual milestones are not met in the
schedule then the schedule needs to be analyzed to determine why the
contractual milestones not met.
Analyzing
The Schedule
■ Is the critical path reasonable?
■ Are there multiple critical paths?
■ What activities are near critical?
■ How does the work flow?
■ Are their conflicts between concurrent activities?
■ Is there an excessive amount of work at any time?
■ Are there sufficient resources to support concurrent activities?
■ Can subcontractors and suppliers meet the schedule?
■ Are any activities scheduled out of season?
Is the critical
path reasonable?
■ When analyzing the schedule, the first thing that should be determined is
what activities are on the critical path and is the critical path reasonable.
■ In other words, are the activities that make up the critical path the activities
that should be critical and determine the project?
■ The schedule critical path should accurately represent the sequence of
activities that will determine the overall project duration during execution.
Are there
multiple critical paths?
■ Whenever a schedule contains multiple critical paths, the project team
should review and analyze the parallel sequences of critical activities to
determine why each is critical.
■ From a network standpoint, there is nothing wrong with multiple critical
paths. However, from a management standpoint the parallel critical
paths should be minimized if at all possible in order to increase the
probability of completing the project on schedule.
What activities
are near critical?
■ As important as identifying critical activities is the identification of
near critical activities are those activities that have little total float
and could easily become critical as a result of unforeseen
circumstances or conditions during project execution.
How does
the work flow?
■ The scheduled work should flow in a logical manner from the start of the
project to the completion of the project. If the work does not flow in the
schedule, then the work probably won’t flow well during execution and this
will result in increased costs and time due to productivity loss.
Is there an excessive
amount of work at any time?
■ There is a limit to the amount of work that can be performed productively on
a project at any time.
■ The amount of work that can be performed productively on a project
depends on a number of factors that include the type of project, stage of the
project, and the nature and proximity of concurrent activities among other
things. These factors need to be considered when analyzing the schedule.
Baseline
projacstraining.com
10. Using
Templates To Define Projects
■ Organizations can document their experience and knowledge in
delivering projects in what is known as templates.
■ Project Templates will detail the WBS, OBS, DBS, Activities,
Sequence, Duration, Resource Requirements and other related
information.
Templates As
An Organizational Asset
■ Templates represents historical information about the organization
past projects that had been captured from previous projects.
■ Organizational Assets are the formal and informal policies,
procedures and guidelines that could impact how a project’s scope
is managed.
What A Template
Would Usually Include?
■ Work Breakdown Structure
■ Document Breakdown Structure
■ Organization Breakdown Structure
■ List Of Activities and Sequence
■ Resource Requirements
■ Costs and Expenses
■ Risks
Work Authorization At
Each Level Should Identify
■ What is to be done
■ Who is to do it
■ When it is to be done
■ Amount of resources budgeted
■ Acceptance by person responsible for work
■ How progress and actual cost (AC) are to be aggregated
Scope Verification
■ Reviewing the work products and results to ensure that all are
completed correctly and satisfactory
■ Conducting inspections, reviews, audits
■ Determining whether results conform to requirements
■ Determining if work products are completed correctly
■ Documenting completion of deliverables
■ Gaining formal sign-off
Inspection
Acceptance
Form
■ An Acceptance Form is a document which is completed to request formal acceptance
of a project deliverable by the customer.
■ Acceptance Forms typically include:
Summarized project information
Details of the deliverable, requester and request date
A list of the acceptance criteria and standards required to be met
A summary of the results of the acceptance testing undertaken to determine whether or not
the deliverable meets the criteria and standards specified
A section allowing the customer to approve the deliverable.
When to use
an Acceptance Form?
■ Although one Acceptance Form may be completed per deliverable, an Acceptance
Form may be completed for a set of related deliverables for which customer
acceptance is sought. The Acceptance Form is typically completed by the Project
Manager and formally distributed to the customer for review and sign-off.
■ Only those deliverables which have been completed and are believed to meet the
requirements of the customer should be put forward for acceptance.
Acceptance
Management Plan
■ An Acceptance Management Plan is used to ensure that every
deliverable produced by the project is formally:
Completed
Documented
Reviewed
Approved
Project
Deliverables
Acceptance
Management Plan
Complete
Deliverable
■ This process involves undertaking all activities and tasks to complete the
deliverable to a level which is likely to gain customer acceptance. The
following procedures are instigated:
Undertake all tasks required to complete the deliverable
Document the final deliverable components
Inform the Project Manager that the deliverable is now ready for customer
acceptance.
Punch List
(Snag List)
■ A log of items that do not comply with the contract requirements and
need to rectified by the Seller.
■ Details shown for each item include:
Description
Due Data
Ball In Court
Estimate To Rectify
Status
Date Rectified
Purpose Of
Time Management
■ Calculate the total time currently spent against each individual task and therefore the
total staff cost of undertaking each task on the project
■ Identify any task slippage on the project plan, thereby enabling the Project Manager
to control the level of resource allocated to each task
■ Identify the percentage of each task completed plus any outstanding work required to
be undertaken to complete the task in its entirety.
Work Performance
Information
■ Information on the status of the project activities being performed to
accomplish the project work is routinely collected as part of the
project management plan execution.
Work Performance
Information
■ Deliverables that had been completed and those not completed
■ Schedule activities that have started and that have been finished
■ Extent to which quality standard are being met
■ Costs authorized and incurred
■ Estimates to complete the schedule activities that have started
■ Percent physical completion of activities
■ Documented Lessons Learned
■ Resource Utilization Detail
Schedule
Updates
■ Completed Activities
Actual Start and Finish Dates
Actual Resource Hours and Quantity
Actual Expenses Incurred
■ In Progress Activities
Actual Start and Remaining Duration
Actual Resource Hours and Quantity To Date and Estimated Balance To
Complete
Actual Expenses Incurred To Date
Actual Start
Date
■ Actual Start Date is when work on an activity actually started with
the intention of completing the activity within the planned duration.
■ The actual start date is not necessarily the first date that work was
performed on the activity.
Actual Finish
Date
■ Actual Finish Date occurs when work on an activity is substantially
complete.
■ An activity is substantially complete when only minor or remedial work
remains and successor activities can proceed to substantial completion
without being hindered by any remaining minor work on the
predecessor activity being reviewed.
■ The actual finish date is not necessarily the last day that work was
performed on an activity.
Actual
Duration
■ The actual number of days worked on the activity.
Forecasts
Remaining
Duration (RD or RDU)
■ The time needed to complete an activity.
Estimate To
Complete (ETC)
■ The estimate to complete the remaining work for an activity, work package
or control account.
What is the
Data Date?
■ The date to which actual performance data is reported and the date
from which future work is scheduled.
Date that is used as the starting point for schedule calculations.
Always starts at the beginning of the day.
■ Also known as Time Now and Cut-Off Date.
Data Date
J F M A M J J A S
Schedule
Plan
Data
Actual
Date line
Resource
Resource Time
Quantity
(person -
days)
Time
Cost
Time
Status Line
Statusing
the Activities
Data Date
AS
ES AF
EF
5d
AS
ES EF
10d /5d RD
ES EF
8d
ES EF
2d
06-Jan-03
Setting the
New Data Date
Data Date New Data Date
AS AF
5d
AS EF
10d /5d RD
ES EF
8d
ES EF
2d
Statusing Period
06-Jan-03 13-Jan-03
Rescheduling
the Project
AS AF
5d
AS EF
10d/ 5d RD
ES EF
8d
ES EF
2d
06-Jan-03 13-Jan-03
Retained Logic
and Progress Override
■ It is possible that activities might progress in a format that differs
what was assumed in the planning phase although this should not
result in altering the activity sequences established in the planning
phase.
■ This could be due for many reasons including availability of work
area, resources, etc.
RETAINED
LOGIC
PROGRESS
OVERRIDE
All Rights Reserved. Bassam A. Samman PMP, PSP, EVP, CRA
Collaboration, Management & Control Solutions FZ - LLC
projacstraining.com
Analyze Schedule
Status
■ What Is The Basis For Evaluating Schedule Status?
■ What Is The Planned Completion Date?
■ Has The Critical Path Shifted And How?
■ Has The Float Of Any Activity Changed And Why?
■ Has Weather Become A Factor For Any Activities?
■ Are There Any Trends Worth Watching?
■ Have There Been Any Changes Since The Last Update?
Types of
Costs
■ Typical types of costs include:
Labor costs (e.g. staff, external suppliers, contractors and consultants)
Equipment costs (e.g. computers, furniture, building facilities, machinery and
vehicles)
Materials costs (e.g. stationery, consumables, building materials, water and
power)
Administration costs (e.g. legal, insurance, lending and accounting fees).
2.4. Implement
QA/QC Plan
■ Quality Assurance (QA)/ Quality Control (QC) Management ensures
that a project is on track with scheduled deliverables and within
budget.
■ This regular evaluation of project performance provides the
confidence that the project is progressing in a satisfactory manner.
Perform
Quality Assurance
■ Applying the planned, systematic quality activities to ensure that the
project employs all processes required to meet requirements.
Perform
Quality Control
■ Monitoring specific project results to determine whether they comply
with relevant quality standards and identifying ways to eliminate
causes of unsatisfactory performance.
Quality
Control
■ Holding periodic inspections
■ Ensuring that authorized approaches and processes are followed
■ Identifying the need for corrective action
■ Making changes or improvements to work and processes
■ Reworking completed work to meet the requirements
■ Making decisions to accept or reject work
■ Evaluating the effectiveness of corrective actions
■ Reassessing the effectiveness of project control plans
■ Improving quality
2.6. Capturing
Lessons Learned
■ Lessons learned is knowledge derived from experience to promote the
recurrence of desirable outcomes or preclude the recurrence of undesirable
outcomes.
■ Lessons learned enable the knowledge gained from past experience to be
applied to current and future projects to avoid the repetition of past failures
and mishaps.
■ Lessons learned documentation can represent both positive and negative
experiences.
Lessons
Learned
■ A document which talks about what was done right or wrong and
what should be done differently and whether the project should be
redone.
■ It covers three areas:
Technical Aspects of the Project
Project Management (PMBOK)
Management (Leadership and Management)
Lessons
Learned
■ Mistakes to be avoided
■ Opportunities to be addressed
■ Risks identified
■ Knowledge gained
■ Good practices
■ Performance evaluation
■ Alternative products
Lessons
Learned
Project Lessons Learned
Lesson learned Context Keywords Owner/
resource name
Accounting will The project team failed to fill out the form, Accounting, Canada, John Doe,
require form 421A for assuming that since the Regina, SK office Currency, Exchange, Project
all foreign was linked to Minneapolis, no currency International, Foreign Manager
transactions, exchange form would be required. The
including Canadian project payments to vendors were delayed by
four weeks
Acme Enterprises One team member’s charges came in on an Acme, credit, charge, Jane Doe,
appreciates vendors Acme card early in the project, and the client card Project
who use the Acme acknowledged the transaction in a meeting, Manager
card for project praising us for “knowing the customer”. The
transactions, and rest of the team applied for Acme cards
considers it a major before the week was over.
step toward customer
goodwill
End Of Section
DAY FOUR
3. Analyze Project
Performance Data
■ Identify and analyze CV and SV and develop estimates of cost at
completion and forecasts of schedule completion.
Earned
Value
■ A method for measuring project performance
■ Compares the cumulative value of the budgeted cost of work
performed (EV) at the original allocated budget amount to both
the budgeted cost of work scheduled (PV) and to the actual cost
of work performed (AC).
Language Of
EV
■Project Budget Pyramid
CBB – Contract Budget Base
PMB – Program Management Baseline Contract Budget Base
CAs – Control Accounts CBB
PPs – Planning Packages
WPs – Work Packages
MR – Management Reserve
UB – Authorized funds
undistributed to a work Program
package Management M PMB
Baseline R
PMB + MR = CBB
Summary U Distributed Budget
PP’s B
Control Undistributed Budget
Accounts
DB + UB = PMB
PP’s Defined
Discrete AP LOE Planning Out Discrete
work WPs WPs packages Year Work
packages
Near Term
Language of EV
■ Contract Budget Base (CBB). The negotiated contract cost value plus the
estimated value of authorized but unpriced work.
■ Program Management Baseline (PMB). The schedule and resource
baseline established after contract award or supplemental agreement that
becomes the basis for earned value status assessment.
■ UnDistributed Budget (UB). Authorized funds that have not been assigned
to a control account or summary-level planning package.
What EV
Can Answer?
■ Are we ahead or behind schedule?
■ How efficiently are we using our time?
■ When is this project likely to be completed?
■ Are we currently under or over budget?
■ How efficiently are we using our resources?
■ How efficiently must we use our remaining resources?
■ What is the remaining work likely to cost?
■ What is the entire project likely to cost?
■ How much we will be under or over budget at the end?
Planned
Value (PV)
■ Is the budget cost for the work scheduled to be completed for an
activity up to a given point in time.
■ Used to be known as BCWS or BQWS
Earned
Value (EV)
■ Is the budgeted amount of the work actually completed on the
schedule activity during a given time period.
■ Used to be known as BCWP or BQWP
Performance Measurement
Methods
■ Discrete Effort
Percent complete. Estimate the percent complete of a task.
Start/Finish (fixed formula)
50/50 Rule. A task is considered 50% complete when it begins and gets credit for the last 50% only
when it is completed.
20/80 Rule. A task is considered 20% complete when it begins and gets credit for the last 80% only
when it is completed.
0/100 Rule. A task does not get for partial completion, only full completion.
Incremental Milestone- % Complete based on milestone completion
Units Complete- Physical quantity count
■ Apportioned Effort
■ Level of Effort (LOE)
Discrete
Effort
■ Work effort that is directly identifiable to the completion of specific
work breakdown structure components and deliverables, and that
can be directly planned and measured. Contrast with apportioned
effort.
Apportioned
Effort (AE)
■ Effort applied to project work that is not readily divisible into discrete
efforts for that work, but which is related in direct proportion to
measurable discrete work efforts. Contrast with discrete effort.
Level of
Effort (LOE)
■ Work that does not result in a final product (such as liaison,
coordination, follow-up, or other support activities) and which cannot
be effectively associated with a definable end product process
result.
■ Level of effort is measured only in terms of resources actually
consumed within a given time period.
START FINISH
100%
ACTUAL
PERCENT
X% COMPLET
0%
TIM E
Discrete Effort
Units Completed Method
1 2 3 4
NOTE: Total Quantity is from
the EAC or Forecast. It is not
COM PLETE 5 6 7 8 the baseline value.
9 10 11 12
TO BE DONE 13 14 15 16
17 18 19 20
Discrete Effort
Incremental Milestone Method
Discrete Effort
EV vs. Percent Complete
100%
TASK 2
TASK 1
0%
10%
TASK 3
TIME
NOW
EV Metrics
65
■ SV =
60 EV – PV = 45 – 30 = 15
55 ■ SV% =
50 SV/PV X 100 = 15/30 X 100 = 50%
45
■ SPI =
40
35
EV/PV = 45/30 = 1.5
Value
30 ■ CV =
25 EV – AC = 45 – 55 = -10
20 ■ CV% =
15
CV/EV X 100 = -10/45 X 100 = -22%
10
5
■ CPI =
0 EV/AC = 0.82
1 2 3 4 5 6 7 8 9 10 11 12 13 ■ TCPI =
Time (BAC-EV)/(BAC-AC) = 15/5 = 3.0
PV EV AC
EV Measures
Performance Schedule
Measures SV > 0 & SPI > 1.0 SV = 0 & SPI = 1.0 SV < 0 & SPI < 1.0
EV Example 1/5
Project Duration
Activity Budget 1 2 3 4 5 6 7 8 9 10 11 12 13 14
6 6
1 12
8 12 16 12
2 48
7 21
3 28
18
4 18
4 8 10 6
5 28
8 8
6 16
150 6 14 12 16 19 21 22 8 10 6 8 8
PV 6 20 32 48 67 88 110 118 128 134 142 150
EV
AC
EV Example 2/5
PV Chart
200
150
Value
100 PV
50
0
1 2 3 4 5 6 7 8 9 10 11 12
Month
EV Example 3/5
Project Duration
Activity Budget 1 2 3 4 5 6 7 8 9 10 11 12 13 14
6 6
1 12
8 12 16 12
2 48
7 0 21
3 28
18
4 18
4 8 10 6
5 28
8 8
6 16
150 6 14 12 16 19 21 22 8 10 6 8 8
PV 6 20 32 48 67 88 110 118 128 134 142 150
EV 6 20 32 48 67 67
AC 6 22 36 54 72 75
EV Example 4/5
PV Vs. EV
200
150
PV
Value
100
EV
50
0
1 2 3 4 5 6 7 8 9 10 11 12
Month
EV Example 5/5
EV Chart
200
150
PV
Value
100 EV
AC
50
0
1 2 3 4 5 6 7 8 9 10 11 12
Month
Schedule Analysis
& Forecasting
■ Are we ahead or behind schedule?
Schedule Variance (SV) = EV – PV
= 67 – 88 = -11
SV% = SV/PV = -11/88 = -12.5%
■ How efficiently are we using our time?
Schedule Performance Index (SPI) = EV/PV
= 67/88 = 0.76
■ When is this project likely to be completed?
EAC = (BAC/SPI)/(BAC/months)
EAC = (150/0.76)/(150/12) = 15.76 Months
Cost Analysis
& Forecasting 1/2
■ Are we currently under or over budget?
Cost Variance (CV) = EV- AC = 67 – 75 = - 8
CV% = CV/EV = -8/67= - 11.9%
■ How efficiently are we using our resources?
Cost Performance Index (CPI) = EV/AC
= 67/76 = 0.89
■ How efficiently must we use our remaining resources?
To Complete Performance Index (TCPI)
= (BAC-EV)/(BAC-AC) = (150 – 67)/(150 – 75)= 1.1
Cost Analysis
& Forecasting 2/2
■ What is the remaining work likely to cost?
Estimate To Complete (ETC) = (BAC-EV)/CPI
ETC = (150-67)/0.89 = 93.25
■ What is the entire project likely to cost?
Estimate At Completion (EAC) = BAC/ CPI
EAC = 150/0.89 = 168.54
■ How much we will be under or over budget at the end?
Variance At Completion (VAC) = BAC – EAC
VAC = 150 – 168.54 = -18.54
ETC Based on
Atypical Variances
■ Used when current variances are seen as atypical and similar
variances will not occur in the future.
■ ETC = (BAC- EVc)
■ Where
ETC is Estimate To Complete
BAC is Budget Cost At Completion
EVc is cumulative Earned Value To Date
ETC Based on
Typical Variances
■ Used when current variances are seen as typical of future variances.
■ ETC = (BAC- EVc)/CPIc
■ Where
ETC is Estimate To Complete
BAC is Budget Cost At Completion
EVc is cumulative Earned Value To Date
CPIc is cumulative Cost Performance Index
ETC Based on
Typical Variances- Additional Cases
■ ETC will be influenced by factors of 80% of past cost and 20% past
schedule performance
ETC = (BAC-EV)/ (0.8 X CPI + 0.2 X SPI)
■ ETC will be influenced by last 3 months cost performance
ETC = (BAC-EV)/ (CPI1+ CPI2+ CPI3)
■ ETC will be influenced by past cost and schedule performance
ETC = (BAC-EV)/ (CPI X SPI)
EAC Using
A New Estimate
■ Used when past performance shows that the original estimating
assumptions were fundamentally flawed or that they are no longer
relevant due to a change in condition.
■ EAC = ACc + ETC
EAC Based
On Atypical Variances
■ Used when current variances are seen as atypical of future
variances.
■ EAC = ACc + BAC - EV
EAC Based On
Typical Variances
■ Used when current variances are seen as typical of future variances.
■ EAC = ACc + ((BAC- EV)/ CPIc)
EVPM
Reports
■ C01 Cumulative Performance Chart
■ C02 “At Completion” History Chart
■ C03 Combined Performance Chart
■ C04 Variance Chart- Period Data
■ C05 Variance Chart- Cumulative Data
■ C06 Variance Chart- Cumulative In Percent
■ C07 “Bull’s Eye” Chart
■ C08 Efficiency Chart
■ C09 EVPM Tables
■ C10 Independent Estimate At Completion Chart
C01- Cumulative
Performance Chart
■ Presents the cumulative performance for a project by depicting the
basic data elements it conveys an overall picture of project
performance.
C3- Combined
Performance Chart
■ The chart presents the cumulative performance (the S-Curves). It
also displays changes to the Project Budget, BAC and EAC. By
displaying the basic data elements is one chart it conveys an overall
picture of project performance.
C8- Efficiency
Chart
■ The chart compares past performance with performance required from now
until the end if the target is to be achieved. For example, the chart
compares cost efficiency to date, the CPI, with the level of efficiency that
must be achieved on the remaining work in order to each the EAC or to
meet the BAC. This information is of use in determining the validity of the
Project’s EAC or the attainability of the BAC.
C09- EVPM
Tables
■ The table contains several mathematical indicators for each WBS
element or activity. The table can be filtered, organized, ordered and
summarized to display the information is ways to suit the user’s
needs.
4. Reporting Project
Status
■ Summarize the overall progress to date and any key achievements.
Then state whether the project is currently on schedule and within
budget. List the key deliverables accepted by the customer so far
and describe all high priority risks and issues. Finally, describe any
changes affecting the project.
What To
Report On?
■ Schedule
■ Expenses
■ Effort
■ Quality
■ Risk and Issues
Schedule
■ List the deliverables accepted by the customer
■ Identify the scheduled completion date for each deliverable
■ Identify the actual completion date for each deliverable
■ List actual and scheduled completion date variances
■ Identify the new forecast completion date for each deliverable
■ List the scheduled and forecast completion date variances
Expenses
■ List each expense type; such as labor, equipment & materials
■ Identify the budgeted expenditure, per expense type
■ Identify the actual expenditure, per expense type
■ List actual and budgeted expenditure variances
■ Identify the forecast expenditure, per expense type
■ List budgeted and forecast expenditure variances
Effort
■ List all of the major activities that staff have spent effort on
■ Identify the amount of effort originally budgeted per activity
■ Identify the actual effort expended per activity
■ List actual and budgeted effort variances
■ Identify the forecast effort, per project activity
■ List budgeted and forecast effort variances
Quality
■ List the high priority risks raised during the reporting period
■ Rate the likelihood of each risk occurring and its project impact
■ List the high priority issues raised during the reporting period
■ Rate the current impact of the issue on the project
5. Maintain The
Baseline Plan
■ Manage and track the introduction of approved changes to the
Performance Management Baseline (PMB).
Requirements for
Maintaining The Baseline
■ Changes to the Baseline planning shall be accomplished only with
attendant approved changes to the Scope, Schedule or Budget of
the project.
■ All Changes to the Baseline shall be documented and traceable.
■ Retroactive changes to Baseline Schedule, Cost or Scope shall not
be made.
Scope
Creep
■ features and functionality (project scope) without addressing the
effects on time, costs, and resources, or without customer approval.
Corrective
Actions
■ Corrective actions are documented, authorized directions required to
bring expected future project performance into conformance with the
project management plan.
Recommended
Approved
Implemented
Recommended
Corrective Actions
■ Corrective actions are documented recommendations required to
bring expected future project performance into conformance with the
project management plan.
Implemented
Corrective Actions
■ Implemented corrective actions that had been implemented by the
project management team to bring expected future project
performance into conformance with the project management plan.
Requested
Changes
■ Changes requested to expand or contract project scope, to modify policies,
project management plan, procedures, costs or budgets, revise schedules
are often identified while project work is being performed.
■ Requests for a change can be direct or indirect, externally or internally
initiated, and can be optional or legally/contractually mandated.
Change
Requests
■ Change requests are the documented, authorized changes to expand or
contract project scope. Change requests can also modify policies, project
management plan, procedures, costs or budgets, revise schedules.
Requested
Rejected
Approved
Implemented
Implemented
Change Requests
■ Approved change requests that have been implemented by the
project management team during project execution.
When A Plan
Need To Be Revised
■ A delay in the approved baseline schedule by more than 30
calendar days
■ A change in work sequence instituted by the contractor
■ A change in order which significantly affects the progress of the
original contract work
Revising The
Network Logic
■ Reflect changes in planned means and methods for completing an
activity.
■ React to unanticipated conditions or changes that make the original
planned activity sequence obsolete.
■ Shift the performance of an activity to a better weather conditions in
order to avoid out-of-season construction.
Revising
Activity Duration
■ The planned quantity of work associated with an activity has either
increased or decreased.
■ The amount of resources which include labor, equipment, and material
dedicated to the completion of an activity has either increased or
decreased.
■ The anticipated productivity of labor and equipment is either higher or lower
than originally planned.
Adding and
Deleting Activities
■ Activities may be deleted because the project scope of work has been
reduced and certain work deleted.
■ Activities may be added because the project scope of work has been
expanded requiring the addition of activities to plan and manage the
additional work.
■ Dividing existing schedule activities in order to provide greater schedule
definition.
Analyze The
Updated Schedule
■ Once updated, the schedule needs to be reviewed and analyzed to
determine that the updated schedule is complete and accurately reflects the
way that the work will be carried out. If the updated schedule does not
accurately reflect the way in which the work will be carried out, then the
updated schedule will not be an effective tool for managing the day-to-day
work and monitoring work in progress.
Recovery
Schedule
■ Provides detail of actions that will be performed by the Contractor to
complete the delayed remaining project scope of works within the
originally approved or revised milestone dates.
Capturing
Lessons Learned
■ Lessons learned is knowledge derived from experience to promote the
recurrence of desirable outcomes or preclude the recurrence of undesirable
outcomes.
■ Lessons learned enable the knowledge gained from past experience to be
applied to current and future projects to avoid the repetition of past failures
and mishaps.
■ Lessons learned documentation can represent both positive and negative
experiences.
Lessons
Learned
■ Mistakes to be avoided
■ Opportunities to be addressed
■ Risks identified
■ Knowledge gained
■ Good practices
■ Performance evaluation
■ Alternative products
End Of
Section