A Task with a Start/Finish date that is later than its baseline Start/Finish
Why does it matter if items in the project have Start/Finish Late to Baseline?
Tasks with Start/Finish dates later than their baseline are carrying a schedule variance and may be contributing to late deliverables or increased cost, scheduled or technical risk on the project.
Resolving Start/Finish Late to Baseline
Perform the Audit and Click on each item in the resulting tasks list to go to the offending task. You can also click Filter for Items Below to display tasks with audit issues and record the offending condition in the Integrity Note log field.
Since being late to the original baseline has already occured, there is little the project can do to resolve late past performance. SSI recommends that project teams post progress at short intervals. Furthermore, SSI suggests that , in addition to setting a baseline at the inception of the project, the project scheduler also record the start and finish date of each task, as a current period "Snapshot" before posting any updates at the reporting interval. Taking a "Snapshot" enables current period schedule variance (via the "snapshot") as well as cumulative period schedule variance (via the baseline). At the end of each reporting period, the scheduler and the project team must address and resolve current period variances, in real time, as soon as they occur. Resolving current period variances avoids the accumulation of these variances to the point where little can be done to mitigate the impact accumulated late tasks have on due dates, deliverables and overall project performance.
What Else to Consider
The DCMA 14 Point Assessment tests for Baseline Execution Index (BEI)
BEI: The ratio of the number of tasks completed to the number that should have been completed (per the baseline dates) by the status date. BEI should be > .95
