Welcome to PCO Blogs

This is a place for Registered Users to share their technical view and opinions in form of blogs which they think might be useful to the greater PCO community. We invite prolific writers to share their insights and witticisms, but remind all contributors to be mindful of any copyright rules. ProjectControlsOnline will not be held responsible for any breach in rights and responsible users will be held accounted for the same.

Please note that you may NOT get badges, stars etc. by posting blogs here as they are pretty meaningless as they do NOT make you wealthier, fitter or more attractive to the opposite sex! The best you will get from contributing here is the satisfaction/self-respect from knowing you have helped others.  So, please continue to make positive contribution to this community portal and extend whatever help you can to your fellow colleagues.  Thanks!


Please read this help page before creating a blog

Latest blog entries

Best Practices for Schedule development

Jan 26

Written by:
26/01/2010 20:08  RssIcon

  1. Schedule should reflect the workflow.
  2. There shouldn’t be conflicts between concurrent activities.
  3. Realistic resource loading should be done to support the planned construction operation.
  4. Make sure that subcontractors and suppliers meet the planned construction schedule.
  5. The schedule early dates should be realistic, reasonable and achievable.
  6. Standard company activity codes and ID structure should be used.
  7. All contractual milestones must be met in schedule.
  8. Make sure the correctness of Project Calendars.
  9. Compare resource loading with duration to determine if both are logical, reasonable and mutually supportable.
  10. All activities relationships should be complete & valid.
  11. Schedule should cover the complete project scope.
  12. Schedule should be detailed enough as per the type of schedule. In case it is a working schedule, it should be detailed enough to be make it useful during the execution of project.
  13. The critical path should be reasonable. Make sure the activities are correctly linked to get the correct critical path(s) : e.g. make sure that every activity has FS (Finish-to-Start)/FF (Finish-to-Finish) link with other activity or milestone in P3.
  14. Level 3 activities should be coded for : a) WBS,  b) OBS, c) Workcode, d) Project Stage (EPC),  e) Discipline,  f) Responsibility
  15. Eliminate all dangles
  16. Avoid use of lags ,especially long duration lags
  17. Roll ups from Level 3 to Level 2 must be "many to one " with no splitting of Level 3 activities into individual level 2's
  18. Use Constraints only for milestones. Avoid them as much as possible


Copyright ©2010 Anil Godhawale

Search Blogs