Reviewing The Building Blocks

1
ReviewingThe Building Blocks
Project Scheduling
2
Task Interdependencies

• Task Interdependencies Specify Task Relationships
• All tasks are Related To
• Other Schedule Activities
• Mandatory or Hard Logic
• Discretionary or Soft Logic
• External Events
• Dependent Dates
• Required Dates

Network Diagram
3
Types of Task Relationships

• FS Finish Start

• SS Start Start

• FF Finish Finish

4
Leads and Lags
Normal Finish - Start
Finish Start Modified by a Lead
Finish Start Modified by a Lag

• Lead and Lag are used to Modify Relationships
• Lead and Lag Can be used with any Relationship
  Type (FS, FF, SS)

5
Defining the Critical Path

• The Critical Path
• The Sequence of Tasks that takes the Longest to
  Complete
• Defines Duration of the Project
• Determines the End Date of the Project
• The Overall Duration of the Project Cannot be
  Reduced without shortening the Critical Path

6
Critical Path

• Critical Path
• The Longest Sequential Path of Activities which
  are Absolutely Essential for Completion of the
  Project
• Critical Task
• A Task that is on the Critical Path
• Non-Critical Task
• A Task that is not on the Critical Path

7
Critical Path

• Free Float
• The Amount of Extra Time the Task can be Delayed
  or Extended without Affecting the Start of a
  Successor task
• Total Float
• The Amount of Extra Time the Duration of the Task
  can Expand without Affecting the Project End Date
• Negative Float
• Negative Total Float is the Amount of Time by
  which a Critical Task Misses its Required Date

8
The Gantt Chart

• Gantt Chart Overview
• The Gantt Chart Displays the
• Project Schedule in a Time
• Phased Format
• The Gantt Chart Indicates
• Start End Dates
• Task Durations
• Float
• Baselines
• Task Completion Status
• Parallel Activities
• Major Project Events

9
WSDOT Project Scheduling

• Who are the players?
• What do we use a project schedule for?
• The Project Delivery Information System (PDIS)
• The WSDOT Master Deliverables List (MDL)
• Working with the MDL (Task Planning)

10
Construction Project Office
Bridge Structure Design
Local Agencies
Environmental (Hydraulics, Biology, Permitting,
etc.)
PROJECT
Utilities
Traffic
Materials Geotechnical
DesignProject Office
Real Estate Services
11
WSDOT Project Scheduling

• Who are the players?
• What do we use a project schedule for?
• The Project Delivery Information System (PDIS)
• The WSDOT Master Deliverables List (MDL)
• Working with the MDL (Task Planning)

12
Your road map for getting from here to there.
The Project Schedule
What information can we get from the schedule?

• What tasks will be done
• Who will do them
• How long will they take
• What sequence will they be done
• How much will they cost

You got to be careful if you dont know
where youre going, because you might not get
there. -Yogi Berra
13
WSDOT Project Scheduling

• Who are the players?
• What do we use a project schedule for?
• The Project Delivery Information System (PDIS)
• The WSDOT Master Deliverables List (MDL)
• Working with the MDL (Task Planning)

14
1997
Olympic Region
Project Development
How and where can we sharpen our tools and skills
so as to be more effective?
15
usingSciformaProject Scheduler 8 (PS8)

• Managing Project Delivery
• Information System
• (PDIS)

16
What are the primary motivations for implementing
the Project Delivery Information System using
PS8?

• Opportunities for Improvement
• Coordination Communication
• Management of multiple projects

17
(No Transcript)
18
WSDOT Project Scheduling

• Who are the players?
• What do we use a project schedule for?
• The Project Delivery Information System (PDIS)
• The WSDOT Master Deliverables List (MDL)
• Working with the MDL

19
Master Deliverables List (MDL)
20
Master Deliverables List (MDL)
Level 1
Construction
Pre-Construction
Phase
Level 2
Processes
Level 3
Deliverables
Level 4
Deliverables (in some cases)
Level 5-10
Tasks
21
Scheduling Terminology

• Work Breakdown Structure (WBS)
• A deliverable oriented hierarchical decomposition
  of the work to be executed by the project team to
  accomplish the team mission and create the
  required deliverables. The WBS defines the
  project scope.

22
Scheduling Terminology

• Deliverable
• Any unique and verifiable product or result that
  must be produces to complete a project. Usually
  the lowest level of the WBS.

23
Scheduling Terminology

• Scheduled Activity (task)
• A component of work performed to create a
  deliverable.

24
Master Deliverables List (MDL)
Example
(Preconstruction) PC
Level 1 (Project Phase)
(Hydraulics) PC - 25
Level 2 (Process)
(Type B Report) PC-25 . 02
Level 3 (Deliverable)
Levels 4-10 (Tasks sub tasks)
(Assignable Tasks) PC-25.02 . 01
PC-25.02 . 02 etc
25
WSDOT Project Scheduling

• Who are the players?
• What do we use a project schedule for?
• The Project Delivery Information System (PDIS)
• The WSDOT Master Deliverables List (MDL)
• Working with the MDL

26
Working with the MDL

• Process of Elimination
• Preferential Re-ordering
• By family
• WBS completion sufficiency
• Define tasks (levels 4 10)
• Task Planning
• Network (precedence) Diagram
• Gantt Chart

27
Master Deliverables List (MDL)
Level 1
Construction
Pre-Construction
Phase
Level 2
Processes
Level 3
Deliverables
Level 4
Tasks (Deliverables in some cases)
Level 5-10
Sub-Tasks
28
Type B Report
Task Planning Worksheet
29
Type B Report
PC-25.02
Prepare Hydraulic Report Type B for Review
PC-25.02.01
Prepare Hydraulic Report Type B according to the
standards prescribed in the Highway Runoff Manual
and Storm water Management Policy. Includes
verification of existing drainage facilities on
project site. When completed, report will be
sent to Region Hydraulics Engineer for review and
concurrence.
30
Defining Activities/Tasks

• Definition
• Assignment
• Significance

31
Type B Report
PC-25.02
Prepare Hydraulic Report Type B for Review
PC-25.02.01
Prepare Hydraulic Report Type B according to the
standards prescribed in the Highway Runoff
Manual. Includes verification of existing
drainage facilities on project site. When
completed, report will be sent to Region
Hydraulics Engineer for concurrence.
32
Task Planning
Estimating Percent Complete

• Is key to simplify schedule tracking and used to
  calculate EVM values for the project.
• Methods to calculate percent complete
• Units Produced
• Milestones (Agreement) Method
• 50 50 Convention
• 0 100 Convention
• Proportional Relationships (hammock)

33
Task Planning
Estimating Percent Complete

• Units Produced
• Ratio of units completed to the total planned
• Units must be nearly identical
• Examples
• Drilling 10 holes, 4 completed 40 complete
• Paving 5 lane miles, paved 4 lane miles 80
  complete

34
Task Planning
Estimating Percent Complete

• Milestone (Agreement) Method
• At the onset of the project, agree with the
  project team members on percent complete of
  various stages of the process/deliverable. These
  points can be entered as interim schedule
  milestones for the deliverable.
• Example
• Data Collection 10
• Draft Traffic Signal Design 70
• Final Traffic Signal Design 90
• Traffic Signal PSE 100

35
Task Planning
Estimating Percent Complete

• 50 50 Convention
• The 50 50 convention is best used when an
  accurate estimate is nearly impossible and when
  durations are relatively short (less than the
  reporting frequency).
• This method is a good method for higher-level EVM
  and when there are several processes (or
  deliverables) to be evaluated.
• The more tasks/deliverables evaluated, the more
  accurate the EVM. 50 complete is assumed when
  the task/deliverable has started. 100 complete
  is assumed when the task/deliverable is finished.

36
Task Planning
Estimating Percent Complete

• 0 100 Convention
• The 0 100 convention is best used when a
  task/deliverable has no value unless it is
  completed and when durations are relatively short
  (less than the reporting frequency).
• This method is also a good method for
  higher-level EVM and when there are several
  processes (or deliverables) to be evaluated.
• 0 complete is assumed until a task/deliverable
  is complete. 100 complete is assumed when the
  task/deliverable is finished.

37
Task Planning
Estimating Percent Complete

• Proportional Relationship
• This method is used when the completion of a
  measurable amount of one work package indicates
  the completion of another task that cannot be
  easily measured.
• This method works well for the on-going or
  hammock tasks within the project schedule.
• Example
• 40 of the project is complete, so 40 of the
  project management task is complete.

38
Type B Report
PC-25.02
Prepare Hydraulic Report Type B for Review
PC-25.02.01
Prepare Hydraulic Report Type B according to the
standards prescribed in the Highway Runoff
Manual. Includes verification of existing
drainage facilities on project site. When
completed, report will be sent to Region
Hydraulics Engineer for concurrence.
X
39
Task Planning
Duration Estimating

• Expert Judgment
• Guided by historical information
• Top-down estimating
• Analogous Estimating
• Using actual durations of a previous, similar
  schedule activity as basis for estimating
  duration of future schedule activity.
• Uses expert judgment and historical information
• Top-down estimating

40
Task Planning
Duration Estimating

• Parametric Estimating
• Quantitatively determined by multiplying quantity
  of work to be performed by the productivity
  rate.
• Bottom-up estimating

41
Task Planning
Duration Estimating

• Three-Point Estimates
• Formerly called Program Evaluation and Review
  Technique (PERT)
• Incorporates risk factors into estimate
• Three types of estimates
• Most Likely (ML) Realistic expectations
• Optimistic (O) Best-case scenario
• Pessimistic (P) Worst case scenario
• Typically provides a more accurate duration
  estimate than single point estimating.

42
Task Planning
Duration Estimating
Three-Point Estimates
Task Drive home from class (Yakima to Enumclaw
160 miles)
Most Likely
3.0 hrs
Optimistic
2.5 hrs
Pessimistic
5.5 hrs
3.33 hrs
43
Task Planning
Duration Estimating

• Three-Point Estimates
• Formerly called Program Evaluation and Review
  Technique (PERT)
• Incorporates risk factors into estimate
• Three types of estimates
• Most Likely (ML) Realistic expectations
• Optimistic (O) Best-case scenario
• Pessimistic (P) Worst case scenario
• Typically provides a more accurate duration
  estimate than single point estimating.

44
Type B Report
PC-25.02
Prepare Hydraulic Report Type B for Review
PC-25.02.01
Prepare Hydraulic Report Type B according to the
standards prescribed in the Highway Runoff
Manual. Includes verification of existing
drainage facilities on project site. When
completed, report will be sent to Region
Hydraulics Engineer for concurrence.
X
20d
45
(No Transcript)
46
Task Interdependencies

• Task Interdependencies Specify Task Relationships
• All tasks are Related To
• Other Schedule Activities
• Mandatory or Hard Logic
• Discretionary or Soft Logic
• External Events
• Dependent Dates
• Required Dates

Network Diagram
47
Scheduling Terminology

• Scheduled Activity (task)
• A component of work performed to create a
  deliverable.

48
PC-24.10 Roadway Sections FS
PC-18.07.01 Biological Evaluation FS
TE 2 (Design) Effort 40h None
TT 2 (Design) Effort 80h None
49
Master Deliverables List (MDL)
Level 1
Construction
Pre-Construction
Phase
Level 2
Processes
Level 3
Deliverables
Level 4
Deliverables (in some cases)
Level 5-10
Tasks
50
Project TO (Organization Breakdown Structure -
OBS)

• Plan at Deliverable level
• What (deliverable, constraints, standards)
• How Much?
• Duration

ponsor Sr. Mgmt.
Project Manager
Manager
Team Member
Team Member
Task Planning
51
Executive Order 1032.00

• directs WSDOT employees to deliver capital
  transportation projects consistent with the
  principles and practices of the departments
  project management process.
• Further direction given to
• Executive Managers
• Project Managers
• Project Team Members
• Specialty Groups
• HQ Staff

52
Executive Order 1032.00

• Executive Order
• D. Direction to Specialty Groups
• 1. Provide the Project Manager with the
  schedule and estimate for the tasks assigned.

53
Project TO (Organization Breakdown Structure -
OBS)

• Plan at Deliverable level
• What (deliverable, constraints, standards)
• How Much?
• Duration

ponsor Sr. Mgmt.
Project Manager
Manager
Team Member
Team Member
Task Planning
54
Working with the MDL

• Process of Elimination
• Preferential Re-ordering
• By family
• WBS completion sufficiency
• Define tasks (levels 5 10)
• Task Planning
• Network (precedence) Diagram
• Gantt Chart (From PDIS)

55
Simple Project consisting of 5 Tasks
56
Working with the MDL

• Process of Elimination
• Preferential Re-ordering
• By family
• WBS completion sufficiency
• Define tasks (levels 5 10)
• Task Planning
• Network (precedence) Diagram
• Gantt Chart (From PDIS)

57
(No Transcript)
58
Project Performance Baseline
Progressive Elaboration