Project Scheduling
Project Scheduling
Management
Project Management
Players (cont...)
schedules and assigns the activities
to specific members of the project
team
coordinates activities
monitors events
evaluates and reports on the
progress of the activities and events
Project Scheduling
GANTT Charts
◦ developed by Henry L. Gantt
◦ a horizontal bar that graphically illustrates a
schedule
◦ horizontal axis : time
◦ vertical axis : activity
◦ length of the bar indicates duration of the
activity
GANTT Charts...
GANTT Charts (cont...)
◦ positioning of the bar shows the start and end
of the activity
◦ useful for tracking and reporting progress
◦ graphically displays a schedule
◦ often used to report progress because they
present an easily understood picture of project
status
GANTT Charts...
Problems
◦ no indication of activity dependencies
◦ how an activity which is behind schedule can
influence the entire project
◦ no. of hours per day required to complete an
activity is not shown
◦ no. of people assigned is also not shown
◦ it can not determine how far ahead/behind
schedule a project is
Create a Gantt Chart
◦ Task 1 – Jan. 14 – Feb 10
◦ Task 2 – Feb 19 – Mar 18
◦ Task 3 – Mar 16 – Apr. 24
◦ Task 4 – May 4 – May 31
◦ Task 5 – Mar 19 – Apr 14
◦ Task 6 – Apr 16 – Jun 6
◦ Task 7 – May 16 – July 14
PERT/ CPM Charts
Charting Conventions
◦ Activity
- Describes each task
Shown as vectors
-Line with an Event
Represented as branches (lines)
-Identified by letters
- Start/end of an activity
PERT/ CPM Charts...
Event
◦ displayed graphically as nodes, circle or
rectangle
◦ identified as node in the network
Path
◦ sequence of activities leading from the
beginning node to the final node
PERT/ CPM Charts...
Dummy Activities
◦ indicated by dotted lines
◦ no labeled process description/time
◦ used to ensure continuity
Simultaneous activity
◦ serial arrangement means one after the other
◦ parallel format shows overlapping activities
PERT/ CPM Charts...
Concepts:
◦ Optimistic time estimate – completion time
expected if everything went exactly as planned
◦ Pessimistic time estimate – completion time
expected if everything possible went wrong
◦ Most likely time estimate – only if normal
problems are encountered
◦ Critical Path – defines the most sensitive part of
the chart that may affect the schedule of the
whole project (longest time to complete)
◦ Slack – extra time to do an activity without
affecting project schedules
Getting the Estimated Time and Slack
Steps included:
1. determine the activities needed to
complete the project
2. sequential relationship of these activities
(try to establish as many simultaneous
activities as possible
3. estimate the completion time for each
activity
4. draw the PERT/CPM network, showing
the relationship activities as determined in
STEP 2
PERT/ CPM Charts...
Steps included:
5. starting with the beginning node of the
network, use the earliest start – earliest
finish relationships to determine the
project completion time (Forward Pass)
6. moving to the end node of the network,
use the latest start – latest finish
relationships to determine the activities on
the critical path and the float for activities
not on the critical path
PERT/ CPM Charts...