06 project time management m

Project Time
management
BY: OMER ALSAYED OMER
MBA, PMP, B.Sc.(Civil Eng.) : PMO manager EWU-DIU

quote
It is useless to desire more
time if you are already
wasting what little you
have.”
-– James Allen
“

Project Scope Management processes
• establishing the
policies, procedures,
and documentation for
planning, developing,
managing, executing,
and controlling the
project schedule.
6.1 Plan Schedule
Management
• identifying and
documenting the
specific actions to be
performed to produce
the project deliverables.
6.2 Define Activities
• identifying and
documenting
relationships among the
project activities.
6.3 Sequence
Activities
• estimating the type and
quantities of material,
human resources,
equipment, or supplies
required to perform
each activity.
6.4 Estimate Activity
Resources
• estimating the number
of work periods needed
to complete individual
activities with estimated
resources.
Durations
• analyzing activity
sequences, durations,
resource requirements,
and schedule
constraints to create
the project schedule
model.
6.6 Develop Schedule
• monitoring the status of
project activities to
update project progress
and manage changes
to the schedule
baseline to achieve the
plan.
6.7 Control Schedule

Project Management Process Group
and Knowledge Area Mapping
Knowledge Area Initiating Planning Executing M& C Closing
4. Project Integration Management
4Develop
Project Charter
4.2 Develop Project
Management Plan
4.3 Direct & Manage Project
Work
4.4 Monitor & Control Project Work
4.5 Perform Integrated Change Control
4.6 Close Project
or Phase
5. Project Scope Management
5Plan Scope Management
5.2 Collect Requirements
5.3 Define Scope
5.4 Create WBS
5.5 Validate Scope
5.6 Control Scope
6. Project Time Management
6Plan Schedule Management
6.3 Sequence Activities
6.4 Estimate Activity Resources
6.5 Estimate Activity Durations
7. Project Cost Management
7Plan Cost Management
7.2 Estimate Costs
7.3 Determine Budget
7.4 Control Costs
8. Project Quality Management 8Plan Quality Management 8.2 Perform Quality Assurance 8.3 Control Quality
9. Project Human Resource
Management
9.1 Plan Human Resource
Management
9.2 Acquire Project Team
9.3 Develop Project Team
9.4 Manage Project Team
10. Project Communications
Management
10Plan Communications Management 10.2 Manage Communications 10.3 Control Communications
11. Project Risk Management
11Plan Risk Management
11.2 Identify Risks
11.3 Perform Qualitative Risk Analysis
11.4 Perform Quantitative Risk Analysis
11.5 Plan Risk Responses
11.6 Control Risks
12. Project Procurement
Management
12Plan Procurement Management 12.2 Conduct Procurements 12.3 Control Procurements
12.4 Close
Procurements
13. Project Stakeholder
Management
13Identify
Stakeholders
13.2 Plan Stakeholder
Management
13.3 Manage Stakeholder
Engagement
13.4 Control Stakeholder
Engagement
OSO OCT 2013
Planning M& C

schedule terms
Scheduling Tool.
• A tool that provides schedule component names, definitions,
structural relationships, and formats that support the
application of a scheduling method.
Schedule Model.
• A representation of the plan for executing the project’s
activities including durations, dependencies, and other
planning information, used to produce a project schedule
along with other scheduling artifacts.
Schedule Data.
• The collection of information for describing and controlling
the schedule.
Scheduling
method(ex.CPM)
Scheduling
Tool
Schedule
Model
Project
schedule

6.1 Plan Schedule Management
Plan Schedule Management is the process of establishing the policies, procedures,
and documentation for:
provides guidance and direction on how the project
schedule will be managed throughout the project
planning, developing, managing, executing, controlling
the project schedule

6.1 Plan Schedule Management:
Inputs, Tools & Techniques, and Outputs
Inputs
Project management plan
Project charter
Enterprise environmental
factors
Organizational process
assets
T&T
Expert judgment
Analytical techniques
Meetings
Outputs
Schedule management
plan

4 Integration 5 Scope 6 Time 7 Cost 8 Quality 9 H. Resource 10 Commn. 11 Risk 12 Procurement 13 S/holders
EEF
OPA
Enterprise/
Organization
6.1 Plan Schedule
Management
Schedule management
plan
6.2 Define
Activities
OSOOCT2013
4.1 Develop
Project charter
Project charter
6.1 Plan Schedule Management
Data Flow Diagram
6.3 Sequence
Activities
6.4 Estimate
Activity Res.
4.2 Develop
Project M Plan
Project M Plan 6.5 Estimate
Activity Durations
6.6 Develop
Schedule
11.2 Identify
Risks
11.4 Perform
Quantitative
Risk Analysis

6.1 Plan Schedule Management :
Inputs
• Scope baseline. project scope statement and the work breakdown structure (WBS) details used for defining
activities, duration estimation, and schedule management; and
• Other scheduling related cost, risk, and communications decisions
Project charter
• summary milestone schedule and project approval requirements that will influence the management of the
project schedule
Enterprise environmental factors
• Organizational culture and structure can all influence schedule management;
• Resource availability and skills that may influence schedule planning;
• Project management software provides the scheduling tool and alternative possibilities for managing the
schedule;
• Published commercial information, such as resource productivity information, is often available from
commercial databases that track;
• Organizational work authorization systems
Organizational process assets
• Monitoring and reporting tools to be used;
• Historical information;
• Schedule control tools;
• Existing formal and informal schedule control related policies, procedures, and guidelines;
• Templates;
• Project closure guidelines;
• Change control procedures; and
• Risk control procedures including risk categories, probability definition and impact, and probability and impact
matrix.

6.1.2 Plan Schedule Management: Tools and Techniques
6.1.2.2 Analytical Techniques
PSM process may involve choosing strategic options to estimate and schedule the project such as:
◦ scheduling methodology,
◦ scheduling tools and techniques,
◦ estimating approaches,
◦ formats,
◦ project management software.
detail ways to fast track or crash
Organizational policies and procedures influence scheduling techniques
rolling wave planning
leads and lags
alternatives analysis
methods for reviewing schedule performance

6.1.2 Plan Schedule Management: OUTPUTS
6.1.3.1 Schedule Management Plan
establishes the criteria and the activities for developing, monitoring, and controlling the
schedule.
Project schedule model
development.
•The scheduling methodology and the scheduling tool
Level of accuracy. •The acceptable range used in determining realistic activity duration estimates (+contingencies).
Units of measure. •Each unit used in measurements (staff hours, weeks ,meters)
Organizational procedures links.
•The WBS provides the framework for the schedule management plan, allowing for consistency
with the estimates and resulting schedules.
Project schedule model
maintenance.
•The process used to update the status and record progress
Control thresholds. •Variance thresholds for monitoring schedule performance.
Rules of performance
measurement.
•EVM rules or other physical measurement rules of performance measurement are set. (% CALC)
Reporting formats. •The formats and frequency for the various schedule reports are defined.
Process descriptions. •Descriptions of each of the schedule management processes are documented

identifying and documenting the specific actions to be performed to produce
the project deliverables.
to break down work
packages into activities
that provide a basis for:
 estimating,
 scheduling,
 executing,
 monitoring,
 Controlling
the project work
Inputs
Schedule management
plan
Scope baseline
Enterprise
environmental factors
assets
T&T
Decomposition
Rolling wave planning
Expert judgment
Outputs
Activity list
Activity attributes
Milestone list

EEF
OPA
Enterprise/
Organization
6.1 Plan Schedule
Management
Schedule M plan
6.2 Define
Activities
OSOOCT2013
5.4 Create WBS
Scope baseline
Data Flow Diagram
6.3 Sequence
Activities
6.4 Estimate
Activity Res.
6.5 Estimate
Activity Durations
6.6 Develop
Schedule
Activity list
Activity attributes
Milestone list

6.2.1 Define Activities: Inputs
6.2.1.1 Schedule Management Plan:
•prescribed level of detail necessary to manage the work
6.2.1.2 Scope Baseline
•WBS, deliverables, constraints, and assumptions documented
6.2.1.3 Enterprise Environmental Factors
•Organizational cultures and structure,
•Published commercial information from commercial databases, and
•Project management information system (PMIS).
6.2.1.4 Organizational Process Assets
•Lessons learned knowledge base containing historical information
•Standardized processes,
•Templates that contain a standard activity list
•Existing formal and informal activity planning-related policies, procedures, and guidelines (scheduling methodology)

6.2.2 Define Activities:
Tools and Techniques
6.2.2.1 Decomposition
• dividing and subdividing the project scope and project deliverables into smaller, more manageable parts.
• Activities represent the effort needed to complete a work package.
• The Define Activities process defines the final outputs as activities rather than deliverables, as done in
the Create WBS process
6.2.2.2 Rolling Wave Planning
• an iterative planning technique in which the work to be accomplished in the near term is planned in detail, while
the work in the future is planned at a higher level.
• It is a form of progressive elaboration
6.2.2.3 Expert Judgment
• who are experienced and skilled in developing detailed project scope statements, the WBS, and project schedules

6.2.3 Define Activities: Outputs
6.2.3.1 Activity List
• comprehensive list that includes all schedule activities required on the project.
• The activity list also includes the activity identifier and a scope of work description for each activity in sufficient detail.
• Each activity should have a unique title that describes its place in the schedule, even if that activity title is displayed outside the context of the project
schedule.
6.2.3.2 Activity Attributes
• identifying the multiple components associated with each activity.
• the activity identifier (ID), WBS ID, and activity label or name,
• activity codes, activity description, predecessor activities, successor activities, logical relationships, leads and lags, resource requirements, imposed dates,
constraints, and assumptions.
• person responsible, geographic area, calendar, type (LOE),
• used for schedule development and for selecting, ordering, and sorting the planned schedule activities in various ways within reports.
6.2.3.3 Milestone List
• MS is a significant point or event in a project (zero duration).
• A milestone list is a list identifying all project milestones (mandatory, or optional)
• Milestones are similar to regular schedule activities, with the same structure and

identifying and documenting RELATIONSHIPS among the project activities
defines the logical
sequence of work
to obtain the
greatest efficiency
given all project
constraints
Inputs
Schedule management plan
Activity list
Activity attributes
Milestone list
Project scope statement
Enterprise environmental
factors
T&T
Precedence diagramming
method (PDM)
Dependency determination
Leads and lags
Outputs
Project schedule network
diagrams
Project documents updates

EEF
OPA
Enterprise/
Organization
6.1 Plan Schedule
Management
Schedule M plan
6.2 Define
Activities
OSOOCT2013
5.3 Define
Scope
Project scope
statement
Data Flow Diagram
6.3 Sequence
Activities
6.6 Develop
Schedule
Activity list
Activity attributes
Milestone list
Project documents
updates
Project schedule
network diagrams
Project documents
 Activity lists,
 Activity attributes,
 Milestone list, and
 Risk register.

6.3.1 Sequence Activities: Inputs
6.3.1.1 Schedule Management
Plan:
• identifies the scheduling method and tool to be used for the project, which will guide how the
activities may be sequenced
6.3.1.2 Activity List • contains all schedule activities required on the project, dependencies and other constraints
6.3.1.3 Activity Attributes • describe a necessary sequence of events or defined predecessor or successor relationships
6.3.1.4 Milestone List • scheduled dates for specific milestones, which may influence the way activities are sequenced
6.3.1.5 Project Scope Statement
• contains the product scope description (product characteristics), deliverables, project
constraints, and project assumptions
6.2.1.3 Enterprise Environmental
Factors
• Government or industry standards,
• Project management information system (PMIS),
• Scheduling tool, and
• Company work authorization systems.
6.2.1.4 Organizational Process
Assets
• project files used for scheduling methodology, existing formal and informal activity
planning-related policies, procedures, and guidelines, templates. Related activity attributes
information in templates can also contain additional descriptive information

6.3.2 Sequence Activities: Tools and Techniques
6.3.2.1 Precedence Diagramming Method
technique used for constructing a schedule model in which activities are represented by nodes
and are graphically linked by one or more logical relationships to show the sequence in which
the activities are to be performed.
Activity-on-node (AON) is one method of representing a precedence diagram
Finish-to-start (FS).
• successor activity cannot start until
• predecessor activity has finished.
• Example: The awards ceremony (successor) cannot start until the race (predecessor) has finished.
Finish-to-finish (FF).
• successor activity cannot finish until
• predecessor activity has finished.
• Example: Writing a document (predecessor) is required to finish before editing the document (successor)
can finish.
Start-to-start (SS).
• successor activity cannot start until
• predecessor activity has started.
• Example: Level concrete (successor) cannot begin until pour foundation (predecessor) begins.
Start-to-finish (SF).
• successor activity cannot finish until
• predecessor activity has started.
• Example: The first security guard shift (successor) cannot finish until the second security guard shift
(predecessor) starts

6.3.2.1 Precedence Diagramming Method
Finish
-to-
Start
(FS).
Finish
-to-
Finish
(FF).
Start
-to-
Start
(SS).

6.3.2.2 Dependency Determination
MANDATORY DEPENDENCIES
(HARD LOGIC).
◦ legally or contractually required or inherent in
the nature of the work.
◦ often involve physical limitations:
◦ erect the superstructure >> after the foundation has been
built
◦ a prototype has to be built >> before it can be tested.
◦ Technical dependencies may not be mandatory.
DISCRETIONARY DEPENDENCIES
(SOFT /PREFERRED LOGIC).
◦ established based on knowledge of best
practices within a particular application area or
some unusual aspect of the project where a
specific sequence is desired, even though there
may be other acceptable sequences.
◦ Discretionary dependencies should be fully
documented (create arbitrary total float values
and can limit later scheduling options).
◦ fast tracking >> should be reviewed and
considered for modification or removal.

6.3.2.2 Dependency Determination
EXTERNAL DEPENDENCIES.
relationship between project activities and
non-project activities.
usually outside the project team’s control.
For example, the testing activity in a software
project may be dependent on the delivery of
hardware from an external source, or
governmental environmental hearings may
need to be held before site preparation can
begin on a construction project.
INTERNAL DEPENDENCIES.
a precedence relationship between project
activities and are generally inside the project
team’s control.
For example, if the team cannot test a
machine until they assemble it, this is an
internal mandatory dependency.

6.3.2.3 Leads and Lags
LEAD
A lead is the amount of time whereby a
successor activity can be ADVANCED with
respect to a predecessor activity.
LAG
A lag is the amount of time whereby a
successor activity will be DELAYED with
respect to a predecessor activity.
F-S :lag -2w
landscaping
punch list completion
2w
S-S lag :15 days
editing the draft
punch list completion
15
days

6.3.3 Sequence Activities: OUTPUTS
6.3.3.1 Project Schedule Network Diagrams
Graphical representation of the logical relationships (dependencies).
It can include full project details, or have one or more summary activities.
A summary narrative can accompany the diagram and describe the basic approach used to
sequence the activities.
Any unusual activity sequences within the network should be fully described within the
narrative.
Start
A
B
C
D
Finish

estimating the TYPE & QUANTITIES of material, human resources, equipment, or supplies required
to perform each activity
identifies the type,
quantity, &
characteristics of
resources required
to complete the
activity which
allows more
accurate cost and
duration estimates
Inputs
Schedule management plan
Activity list
Activity attributes
Resource calendars
Risk register
Activity cost estimates
Enterprise environmental factors
T&T
Expert judgment
Alternative analysis
Published estimating data
Bottom-up estimating
Project management software
Outputs
Activity resource requirements
Resource breakdown structure

EEF
OPA
Enterprise/
Organization
6.1 Plan Schedule
Management
Schedule M plan
6.2 Define
Activities
OSOOCT2013
7.2 Estimate
Costs
Activity cost
estimates
Data Flow Diagram
6.4 Estimate
Activity Resource
Activity list
Activity attributes
Project documents
updates
Resource breakdown
structure Project documents
 Activity list,
 Activity attributes, and
 Resource calendars.
Resource
calendars
11.2 Identify Risks
Risk register
9.2 Acquire
Project Team
12.2 Conduct
Procurements
Activity resource
requirements
9.1 Plan HRM
Durations

6.4.1 Estimate Activity Resources: Inputs
6.4.1.1 Schedule Management
Plan:
•identifies the level of accuracy and the units of measure for the resources to be estimated
6.4.1.2 Activity List • identifies the activities which will need resources
6.4.1.3 Activity Attributes
•provide the primary data input for use in estimating those resources required for each
activity in the activity list
6.4.1.4 Resource Calendars •identifies the working days and shifts on which each specific resource is available
6.4.1.5 Risk Register • Risk events may impact resource selection and availability
6.4.1.6 Activity Cost Estimates •The cost of resources may impact resource selection
6.4.1.7 Enterprise
Environmental Factors
• resource location, availability, and skills
Assets
• Policies and procedures regarding staffing,
• Policies and procedures relating to rental and purchase of supplies and equipment,
• Historical information regarding types of resources used for similar work

6.4.2 Estimate Activity Resources:
Tools and Techniques6.4.2.1ExpertJudgment
•assess the
resource-
related
inputs to this
process.
6.4.2.2AlternativeAnalysis
•using various
levels of
resource
capability or
skills,
•different size
or type of
machines,
•different
tools
•Make rent-
or-buy
6.4.2.3PublishedEstimatingData
•updated
production
rates and
unit costs of
resources for
an extensive
array of
labor trades,
material,
and
equipment
6.4.2.4Bottom-UpEstimating
•aggregating
the
estimates of
the lower-
level
components
of the WBS.
6.4.2.5ProjectManagementSoftware
•scheduling
software
tool, has the
capability to
help plan,
organize,
and manage
resource
pools and
develop
resource
estimates

6.4.3 Estimate Activity Resources: Outputs
6.4.3.1 Activity
Resource
Requirements
• types and quantities of resources required for each activity in
a work package.
• These requirements then can be aggregated to determine the
estimated resources for each work package and each work
period
6.4.3.2 Resource
Breakdown Structure
• hierarchical representation of resources by category and type
Project EWR
Human
resource
Project
Controls
Admin & Fin Construction
Materials
Construction
Mat’l
E/M Mat’l Consumables.
Equipment
Plants Vehicles Machineries

estimating the NUMBER of work PERIODS needed to complete individual activities with
estimated resources
provides the
amount of TIME
each activity will
take to complete,
which is a major
input into the
Develop Schedule
process
•Activity duration
estimates
•Project documents
updates
Outputs
•Expert judgment
•Analogous estimating
•Parametric estimating
•Three-point estimating
•Group decision-making
techniques
• Reserve analysis
T&T
• Schedule
management plan
• Activity list
• Activity attributes
• Activity resource
requirements
• Resource calendars
• Project scope
statement
• Risk register
• Resource breakdown
structure
•Enterprise
environmental factors
•Organizational process
assets
Inputs

EEF
OPA
Enterprise/
Organization
6.1 Plan Schedule
Management
Schedule M plan
OSOOCT2013
5.3 Define Scope
Project scope
statement
Data Flow Diagram
Resource
Activity list
Activity attributes
Resource breakdown
structure
Project documents
 Activity attributes
 Assumptions made in
developing the activity
duration estimate
Resource
calendars
11.2 Identify Risks
Risk register
9.2 Acquire
Project Team
12.2 Conduct
Procurements
Activity resource
requirements
11.2 Identify Risks
Durations
Activity duration estimates

6.5.1 Estimate Activity Durations: Inputs
Senior draughtsman
1 hours/sheet
1 No.
Junior draughtsman
4 hours/sheet
4 No.

6.5.1 Estimate Activity Durations: Inputs
6.5.1.4 Activity Resource
Requirements
• the level to which the resources assigned to the activity meet the requirements will significantly
influence the duration of most activities
6.5.1.5 Resource Calendars • availability of specific resources, type of resources, and resources with specific attributes.
6.5.1.6 Project Scope Statement
• assumptions (Existing conditions, Availability of information, and Length of the reporting periods).
• Constraints (Available skilled resources, and Contract terms and requirements).
6.5.1.7 Risk Register • provides the list of risks, along with the results of risk analysis and risk response planning.
6.5.1.8 Resource Breakdown
Structure
• provides a hierarchical structure of the identified resources by resource category and resource
type.
6.5.1.9 Enterprise Environmental
Factors
• Duration estimating databases and other reference data,
• Productivity metrics,
• Published commercial information, and
• Location of team members.
Assets
• Historical duration information,
• Project calendars,
• Scheduling methodology, and
• Lessons learned.

6.5.2 Estimate Activity Durations:
6.5.2.1 EXPERT JUDGMENT 6.5.2.2 ANALOGOUS ESTIMATING
uses parameters from a previous, similar
project, such as duration, budget, size, weight,
and complexity, as the basis for estimating the
same parameter or measure for a future
project.
less costly ,time
less accurate
Provide/recommended duration estimate
information (from prior similar projects).
Determine whether to combine methods of
estimating and how to reconcile differences
between them.

6.5.2.3 PARAMETRIC ESTIMATING 6.5.2.4 THREE-POINT ESTIMATING
The accuracy of single-point activity duration
estimates may be improved by considering
estimation uncertainty and risk.
approximate range for an activity’s duration:
◦ tM (Most likely): given the resources likely to
be assigned, their productivity, realistic
expectations of availability for the activity,
dependencies on other participants, and
interruptions.
◦ tO (Optimistic). best-case scenario for the
activity.
◦ tP (Pessimistic). the worst-case scenario for
the activity.
algorithm is used to calculate cost or duration
based on historical data and project
parameters.
Parametric estimating uses a statistical
relationship between historical data and other
variables
This technique can produce higher levels of
accuracy depending upon the sophistication
and underlying data built into the model.
A. Duration of design project =
No of drawings X No of labor hours per drawing
tE = (tO + tM + tP) / 3 (Triangular Distribution)
tE = (tO + 4tM + tP) / 6 (Beta Distribution)

6.5.2.5 GROUP DECISION-MAKING TECHNIQUES 6.5.2.6 RESERVE ANALYSIS
Duration estimates may include contingency reserves
(time reserves or buffers), into the project schedule to
account for schedule uncertainty. (“known-unknowns,”
, %AD, a fixed number of work periods, or may be
developed by using quantitative analysis
Contingency reserves may be separated from the
individual activities and aggregated into buffers.
As more precise information about the project
becomes available, the contingency reserve may be
used, reduced, or eliminated.
Management reserves “unknown-unknowns” are a
specified amount of the project duration withheld for
management control purposes and are reserved for
unforeseen work that is within scope of the project.
Team-based approaches, such as
brainstorming, the Delphi or nominal group
techniques, are useful for engaging team
members to improve estimate ACCURACY and
commitment to the emerging estimates.

6.5.3 Estimate Activity Durations: Outputs
6.5.3.1 Activity Duration Estimates
quantitative assessments of the likely number of time periods that are required to complete an
activity.
2 weeks ± 2 days, (8 to 12 weeks assuming a five-day workweek);
15 % probability of exceeding three weeks

ANALYZING activity sequences, durations, resource requirements, and schedule
constraints to create the project schedule model.
scheduling tool
• schedule activities,
• durations,
• resources,
• resource availabilities,
• logical relationships
schedule
model

• Schedule baseline
• Project schedule
• Schedule data
• Project calendars
• Project management plan updates
• Project documents updates
Outputs
• Schedule network analysis
• Critical path method
• Critical chain method
• Resource optimization techniques
• Modeling techniques
• Leads and lags
• Schedule compression
• Scheduling tool
T&T
• Schedule management plan
• Activity list
• Activity attributes
• Project schedule network
diagrams
• Activity resource requirements
• Resource calendars
• Activity duration estimates
• Project scope statement
• Risk register
• Project staff assignments
• Resource breakdown structure
• Enterprise environmental factors
• Organizational process assets
Inputs

EEF
OPA
Enterprise/
Organization
6.1 Plan Schedule
Management
Schedule M plan
OSO OCT 2013
Data Flow Diagram
5.3 Define Scope
Project scope statement 6.4 Estimate Act. Resource
Activity list
Activity attributes
Project documents (u)
Resource breakdown
structure
Project documents
 Activity resource requirements.
 Activity attributes
 Risk register
11.2 Identify Risks
Risk register
9.2 Acquire
Project Team
12.2 Conduct
Procurements
Activity resource
requirements
Durations
Activity duration estimates
Project m. plan updates
Project schedule network
diagrams
Project staff assignments
Resource calendars
Schedule baseline
Project schedule
Project calendars
4.2 Develop Project
Management Plan
7.2 Estimate Costs
7.3 Determine Budget
12.1 Plan Procurement
Management
Schedule data  Schedule baseline
 Schedule management plan

6.6.1 Develop Schedule: Inputs
6.6.1.1 Schedule
Management Plan:
• Identifies the scheduling method and tool used to create the schedule, and
how the schedule is to be calculated.
6.6.1.2 Activity List • identifies the activities that will be included in the schedule model
6.6.1.3 Activity Attributes • provide the details used to build the schedule model
6.6.1.4 Project Schedule
Network Diagrams
• Contain the logical relationships of predecessors and successors that will be
used to calculate the schedule
6.6.1.5 Activity Resource
Requirements
• identify the types and quantities of resources required for each activity used to
create the schedule model
6.6.1.6 Resource Calendars • contain information on the availability of resources during the project
6.6.1.7 Activity Duration
Estimates
• contain the quantitative assessments of the likely number of work periods that
will be required to complete an activity that will be used to calculate the
schedule

6.6.1 Develop Schedule: Inputs
6.6.1.8 Project Scope
Statement
• contains assumptions and constraints that can impact the development of the
project schedule.
6.6.1.9 Risk Register
• provides the details of all identified risks and their characteristics that affect
the schedule model.
6.6.1.10 Project Staff
Assignments
• specify which resources are assigned to each activity.
6.6.1.11 Resource
Breakdown Structure
• provides the details by which resource analysis and organizational reporting
can be done.
6.2.1.3 Enterprise
Environmental Factors
• Standards,
• Communication channels
• Scheduling tool to be used in developing the schedule model.
6.2.1.4 Organizational
Process Assets
• scheduling methodology and project calendar(s)

6.6.2 Develop Schedule: Tools and Techniques
6.6.2.1 Schedule Network Analysis
technique generates the project schedule model ,employs various analytical techniques to calculate the
early and late start and finish dates for the uncompleted portions of project activities:
critical path
method
critical chain
method
what-if
analysis
resource
optimization
techniques

6.6.2.2 Critical Path Method
a method used to estimate the MINIMUM project duration and determine the amount of
scheduling flexibility on the logical network paths within the schedule model.
calculates the early start, early finish, late start, and late finish dates for all activities (without
regard for any resource limitations) by performing a forward and backward pass analysis
 The critical path is the sequence of activities that represents the LONGEST path through a
project, which determines the SHORTEST possible project duration.
CPM is used to calculate the amount of scheduling FLEXIBILITY (the amount of time that a
schedule activity can be delayed or extended from its early start date without delaying the
project finish date or violating a schedule constraint, and is termed “TOTAL FLOAT.”

6.6.2.2 Critical Path Method
A
1 0 5
1 5 5
<ACTIVITY NAME>
LS TF LF
ES DU EF
C
6 0 15
6 10 15
D
16 0 30
16 15 30
B
11 5 15
6 5 10START
FINISH

6.6.2.3 Critical Chain Method
CCM is a schedule method that allows to place buffers on any project schedule path to account for limited
resources and project uncertainties.
It is developed from the critical path method approach and considers the effects of resource allocation,
resource optimization, resource leveling, and activity duration uncertainty on the critical path determined
using the critical path method.
The critical chain method uses activities with durations that do not include safety margins, logical
relationships, and resource availability with statistically determined buffers composed of the aggregated
safety margins of activities at specified points on the project schedule path to account for limited resources
and project uncertainties.
The resource-constrained critical path is known as the critical chain.

6.6.2.3 Critical Chain Method
A
C D
B
START
FINISH
E
G
F
FB
FB
PB
Critical Chain LINK
NON Critical Chain LINK
duration buffers: • non-work schedule activities to manage uncertainty.
project buffer: • at the end of the critical chain protects the target finish date from slippage along the critical chain.
feeding buffers:
• at point where a chain of dependent activities that are not on the critical chain feeds into the critical chain.
(protect CC from slippage along the FC)

6.6.2.4 Resource Optimization Techniques
RESOURCE LEVELING:
◦ A technique in which start and finish dates are
ADJUSTED based on resource constraints with
the goal of balancing demand for resources with
the available supply.
◦ Resource leveling can be used when shared or
critically required resources are only available at
certain times, or in limited quantities, or over-
allocated,
◦ Resource leveling can often cause the original
critical path to change, usually to increase
A
C
B
START
DAY-1 DAY-2 DAY-3
2
1 1
A CBSTART
DAY-1 DAY-2 DAY-3
1
1 1
1

RESOURCE SMOOTHING
A technique that adjusts the activities of a
schedule model such that the requirements
for resources on the project DO NOT exceed
certain predefined resource limits.
the project’s critical path is NOT CHANGED and
the completion date may not be delayed
(opposed to resource leveling).
activities may only be delayed within their free
and total float.
not be able to optimize all resources
A
C
B
START
DAY-1 DAY-2 DAY-3
2
1 1
1 DAY
1 DAY
1 DAY
A
C
B
START
DAY-1 DAY-2 DAY-3
1
1 1
2 DAY
1 DAY
1 DAY
1

6.6.2.5 Modeling Techniques
WHAT-IF SCENARIO ANALYSIS.
process of evaluating scenarios in order to predict their
effect, positively or negatively, on project objectives.
“What if the situation represented by scenario ‘X’
happens?”
A schedule network analysis is performed using the
schedule to compute the different scenarios, (delaying a
major component delivery) The outcome of the what-if
scenario analysis can be used to assess the feasibility
of the project schedule under adverse conditions, and in
preparing contingency and response plans to overcome or
mitigate the impact of unexpected situations.
SIMULATION
Simulation involves calculating multiple project
durations with different sets of activity
assumptions, usually using probability
distributions constructed from the three-point
estimates to account for uncertainty. The most
common simulation technique is Monte Carlo
analysis, in which a distribution of possible
activity durations is defined for each activity
and used to calculate a distribution of possible
outcomes for the total project

6.6.2.7 Schedule Compression
CRASHING
A technique used to shorten the schedule duration
for the least incremental cost by ADDING resources.
◦ approving overtime, bringing in additional resources, or paying
to expedite delivery to activities on the critical path.
Crashing works only for activities on the critical path
where additional resources will shorten the
activity’s duration.
Crashing does not always produce a viable
alternative and may result in increased risk and/or
cost.
FAST TRACKING
technique in which activities or phases normally
done in SEQUENCE are performed in PARALLEL for
at least a portion of their duration.
Fast tracking may result in rework and increased
risk.
Fast tracking only works if activities can be
overlapped to shorten the project duration
techniques used to shorten the duration without reducing scope, to meet schedule constraints, imposed dates, or other objectives
foundation
Arch Design
foundation
DAY-1 DAY-2 DAY-3 DAY-4 DAY-5
Arch Design

6.6.3 Develop Schedule: Outputs
6.6.3.1 Schedule Baseline
approved version (by the appropriate stakeholders ) of a schedule model that can be CHANGED ONLY
through formal change control procedures and is used as a basis for comparison to actual results.
During monitoring and controlling, the approved baseline dates are compared to the actual start and finish
dates to determine whether variances have occurred.

The project schedule is an output of a schedule model that presents linked activities with planned dates, durations, milestones, and
resources. (minimum includes a planned start date and planned finish date for each activity).
If resource planning is done at an early stage, then the project schedule remains preliminary until resource assignments have been
confirmed and scheduled start and finish dates are established.
This process usually occurs no later than the completion of the project management plan
The project schedule presentation may be presented in summary form, or in detail (tabular form, graphically):
◦ Bar charts (Gantt charts)
◦ Milestone charts
◦ Project schedule network diagrams.
◦ in the activity-on-node diagram format showing activities and relationships without a time scale, sometimes referred to as a pure logic
diagram,

2013
Design
CONSTRUCTION
•21/3/2013
•1/8/2013
DecOctSepAugJulyJuneAprilMarchFebJan May Nov
•1/11/2013
EQUIPMENT INSTALLATION
•1/1/2013
•1/3/2013
TESTING & COMMISSIONING
EXT. W. & FINISHING
Bar charts (Gantt charts)
HANDOVER
MS
3
MS
1
MS
2
EQPT RP
START
A • ES …
• EF ..
B • ES …
• EF ..
C • ES …
• EF ..
MS
Milestone
• only identify the scheduled start or
completion of major deliverables and key
external interfaces
HAMMOCK
•more comprehensive summary activity between
milestones or across multiple interdependent work
packages, and is displayed in bar chart reports
network
diagrams
•in the activity-on-node diagram format showing
activities and relationships without a time scale,
sometimes referred to as a pure logic diagram

6.6.3.3 Schedule Data & 6.6.3.4 Project Calendars
6.6.3.3 SCHEDULE DATA
collection of information for describing
and controlling the schedule includes
at least :
◦ milestones, schedule activities, activity
attributes, assumptions and constraints.
◦ supporting detail includes:
◦ Resource requirements by time period (resource
histogram)
◦ Alternative schedules (best-case or worst-case, not
resource-leveled, or resource-leveled)
◦ Scheduling of contingency reserves.
6.6.3.4 PROJECT CALENDARS
working days and shifts that are available for
scheduled activities.
It distinguishes time periods that are available
to complete scheduled activities from time
periods that are not available.
A schedule model may require more than one
project calendar to allow for different work
periods for some activities to calculate the
project schedule.

MONITORING the status of project activities to update project progress and manage
changes to the schedule baseline to achieve the plan.
provides the
means to
recognize
deviation from the
plan and take
corrective and
preventive actions
and thus minimize
risk.
Inputs
Project schedule
Work performance data
Project calendars
Schedule data
assets
T&T
Performance reviews
Project management software
Resource optimization
techniques
Modeling techniques
Leads and lags
Schedule compression
Scheduling tool
Outputs
Work performance information
Schedule forecasts
Change requests
updates
updates

Data Flow Diagram

Agile approach
COMPARING the total amount of work delivered and accepted against the estimates of work
completed for the elapsed time cycle,
Conducting RETROSPECTIVE reviews (scheduled reviews to record lessons learned) for correcting
processes and improving, if required,
REPRIORITIZING the remaining work plan (backlog),
Determining the RATE at which the deliverables are produced, validated, and accepted (velocity) in
given time per iteration (agreed work cycle duration, typically two weeks or one month),
Determining that the project schedule has CHANGED & Managing the actual changes as they occur.

6.7.1 Control Schedule: Inputs
6.7.1.1 Project
Management
Plan
• how the schedule will be managed and
controlled.
• schedule baseline -reference -compare with
actual - change, corrective action, or preventive
action
6.7.1.2 Project
Schedule
• the most recent version with notations to indicate
updates, completed activities, and started
activities.
6.7.1.3 Work
Performance
Data
• project progress information (actual duration,
remaining duration, and physical percent
complete)

6.7. 2 Control Schedule : Tools and Techniques
6.7.2.1 Performance Reviews
Trend analysis
•examines project performance over time to determine whether performance is improving or deteriorating (Using
Graphical analysis techniques).
Critical path method
•Comparing the progress along the critical path.
•The variance on the critical path will have a direct impact on the project end date.
•Evaluating the progress of activities on near critical paths can identify schedule risk.
Earned value management
•SV and SPI are used to assess the magnitude of variation to the original schedule baseline.
•The total float and early finish variances are also essential planning components
•determining the cause and degree of variance relative to baseline
•estimating the implications of those variances for future work to completion
•deciding whether corrective or preventive action is required.
Performance reviews measure, compare, and analyze schedule performance

6.7. 2 Control Schedule : Tools and Techniques
6.7.2.2-7
6.7.2.2 Project Management Software
• provides the ability to track planned vs. actual, to report variances ,progress , forecast.
• involve the scheduling of activities and the resources required taking into consideration both the resource availability and the project time.
6.7.2.4 Modeling Techniques
• review various scenarios guided by risk monitoring to bring the schedule model into alignment with the project management plan and
approved baseline.
6.7.2.5 Leads and Lags
• applied during network analysis to find ways to bring project activities that are behind into alignment with the plan.
6.7.2.6 Schedule Compression
• find ways to bring project activities that are behind into alignment with the plan by fast tracking or crashing schedule for the remaining work.
6.7.2.7 Scheduling Tool
• perform schedule network analysis to generate an updated project schedule.

6.7.3 Control Schedule: Outputs
6.7.3.1 Work Performance Information
• SV and SPI time performance indicators for WBS components, are documented and communicated to stakeholders.
6.7.3.2 Schedule Forecasts
• estimates or predictions of conditions and events in the project’s future based on information and knowledge available
6.7.3.3 Change Requests
• Schedule variance analysis, along with review of progress reports, results of performance measures, and modifications to the project scope or project
schedule may result in change requests to the schedule baseline, scope baseline, and/or other components of the project management plan.
6.7.3.4 Project Management Plan Updates
• Schedule baseline.
• Project Schedule
• Risk Register
6.7.3.6 Organizational Process Assets Updates
• Causes of variances
• Corrective action chosen and the reasons
• Other types of lessons learned from project schedule control.

06 project time management m

More Related Content

What's hot (20)

Viewers also liked (20)

Similar to 06 project time management m (20)

More from Omer Alsayed PhD,MBA, PMP® (20)

Recently uploaded (20)

06 project time management m