Skip to content
ProjectControls.com
Planning, Scheduling & Programming Discussion

Schedule Quality Check

In the Open Standard
Jithin KambhikanamMember for 15 years 6 months
Created
4
4
0

Hello Everyone,

 

For a quality of a schedule what points to be checked, I have listed few but not sure if its right.

 

  • Open end on 2 activity only, one without Predecesor and another without sucessor.
  • SF logic shouldnt be used
  • All activities should be linked either with FS logic or that perticular activity should have both SS and FF logic

 

Also please let me know others to be checked.

 

Thanks

Jithin

Save Follow Follow forum Report
Reply New topic

4 replies

Oldest first
  1. 0
    Patrick Weaver ·
    #1

    Hi Jithin,A good start is the

    Hi Jithin,

    A good start is the DCMA 14 point review (you don't necesarily need all 14):   https://mosaicprojects.com.au/WhitePapers/WP1088_DCMA-14-Point.pdf 

    There's several good software tools to do the checks, see: https://mosaicprojects.com.au/PMKI-SCH-020.php#Process2

    Report
  2. 0
    Rafael Davila ·
    #2

    https://www.tacticalprojectma

    https://www.tacticalprojectmanager.com/start-to-finish-dependency-example/

    https://www.tacticalprojectmanager.com/finish-to-finish-dependency/

    DCMA 14-Point Assessment

    Dangling Logic in Project Schedules – TomsBlog

    Report
  3. 0
    Peter Holroyd ·
    #3

    Hi Jithin,loads of sites to

    Hi Jithin,

    loads of sites to look at which cover schedule network logic integrity (start with a simple schedule checker) and a few try to cover how some of these parameters are good (or bad) for your project but that really is just the start.

    Having a QA planning department procedure with a comprehensive check list which you can review and get your PM to sign off on is a must. It is after all not your schedule but the teams.

    A written Basis of Schedule which backs up the fundamental assumptions contained within the schedule is also needed. This pulls together the documents you used to define the scope, delivery methodology (Project Management, D&E, Procurement, Construction Plans etc), resources, risks, signed of productivity rates, contract constraints, assurance and resilience measures to be used. 

    Report
  4. 0
    Jithin Kambhikanam ·
    #4

    Hello All, Thank you very

    Hello All,

     

    Thank you very much, was a real good info.

     

    Thanks

    Jithin

    Report

Log in or join to reply

ProjectControls.com is free to join. Members can post questions, reply, vote and follow discussions.

Log inJoin free

Existing members: your original username and password still work. Forgot password?