Project Scheduling Rules Course

Course Aim

Managing a project is like conducting an orchestra, and the project plan is its symphony.

Nader K. Rad, Project Scheduling Rules (2012)

 

Yes, the project plan is the symphony for the project orchestra; and time schedules are the heart of project plans, making the pleasant sound of success possible.

This heart needs enough attention and care, which is not possible without having enough knowledge and expertise on the one hand, and putting sufficient effort on the other hand. This course tries to cover the most important aspects of the needed knowledge; the aspects that will strongly help you avoid many of the problems usually faced in project time management.

The main aims of this course are:

  • Help you understand how to create a dynamic, well-formed schedule
  • Help you understand how to avoid common mistakes in forming the schedule
Course Content

This course follows the content of the Project Scheduling Rules book by Nader K. Rad:

  • Rule 01 – Scheduling methodology should be documented and approved
  • Rule 02 – The schedule should have a complete scope
  • Rule 03 – Level-of-efforts should not be critical and should not have variance
  • Rule 04 – Activities should have unique names
  • Rule 05 – Activity names should have a verb
  • Rule 06 – Each activity should have at least one predecessor and one successor
  • Rule 07 – Activities should not be dangling
  • Rule 08 – Most relationships should be FS
  • Rule 09 – SF relationships should be avoided as much as possible
  • Rule 10 – Long lags should not be used
  • Rule 11 – The number of lags should be the fewest possible
  • Rule 12 – The number of leads should be the fewest possible
  • Rule 13 – Activities should not have negative floats
  • Rule 14 – Activities should not have long floats
  • Rules 15 – Activities should not be split
  • Rule 16 – Date constraints should be the fewest possible
  • Rule 17 – Date constraints had better be implemented through milestones
  • Rule 18 – Activities should not have long durations
  • Rule 19 – Duration units had better be the same

Course Format

The course will be delivered through lecture and interactive workshop.

Course Duration

Course can be delivered in either of the following setups:

  • Evening course: 2 Evenings (4 hours each)
  • Day Course: 1 Day (7 hours)
Course Pre-Requisites

Being familiar with project time scheduling, and preferably with operating planning software such as Microsoft Project or Primavera P6.