Logic-i

We continue the discussion on the importance of using integrity checks to ensure project schedules remain on track. Here senior planner Ashley Trodden examines other examples:

Continuing our discussion on the importance of using integrity checks to keep a project schedule on track, we examine other examples.

• High Durations: Duration checks can be used to validate the estimated time for each task, ensuring they are realistic. Too many activities with high durations can be a sign that the activities have not been broken down into a sufficient level of detail.
• As with all these integrity checks, different organisations may set the metrics differently. For example, the DCMA requires no more than five percent of incomplete tasks to have durations of more than 44 days.
• High Float: High float checks can validate the number of activities perceived to contain a high total float, defined as the amount of time an activity can be delayed without impacting on the project completion date.Too many activities with high float may indicate that the schedule is unreliable.

• Negative Float: Negative float in a schedule is created when the early dates of an activity are later than the late dates and usually indicates that constraints have been applied to critical activities. Although negative float can indicate how far behind schedule certain activities have fallen, it’s good practice not to have a negative float contained within the project schedule
• Constraint Checks: These validate any imposed constraints to ensure they are realistic, achievable, and are not in conflict with other areas of the schedule. Constraints are normally separated into two categories, Hard and Soft constraints. Hard constraints can create serious problems within a schedule if not used correctly and should be kept to a minimum or avoided.
• Invalid Dates: Invalid date checks within a schedule are used to analyse forecasted and actual dates in relation to the data date. If an activity has a forecasted start or finish date prior to the data date or status date or has an actual start or finish date beyond the data date or status date, it is classed as invalid. Invalid dates should not be present within a schedule and must be corrected when identified
• Resources: Resource Checks validate whether allocated resources, such as manpower, equipment, or budget are sufficient and available to complete the tasks. Schedules may also be required to be cost loaded. The number of activities with resources and costs can indicate the schedule’s reliability.
• Critical Path: Validating the critical path is crucial in any project. The integrity of the critical path can be tested by ensuring it has a continuous flow through the project

Part 3 of the article follows next week when we examine the benefits of incorporating integrity checks in your project schedule